Maybe you mean “freeze”? All Kontakt instruments sustain, but you can not freeze an instrument which has a natural decay like all plucked or mallet instruments e.g. pianos, marimba, harp etc.
1 Like
That’s good to know. I’ve been wondering how high one can go safely, while so far I’m fine averaging 20%.
I understand. I’m just getting started and still have a way to go. When I get the basic things I want in place and working the way I want them to work, I can look into streamlining the whole thing.
About the ramping, I really looked closely at all the commands in the MC6 and nothing explains that behavior—though given my limited knowledge, there might be. I’ll have a look at what the monitor says.
Yes, Arkhis works fine. I have it too. Many instruments work, others don’t. I think @Dutti67 is right. What he wrote makes sense (thanks for the input, Dutti). I noticed that any instrument that is pad-like sustains, while those more on the side of soloing don’t necessarily. Which is OK. I can work with that.
About GP5 mixers, I’ll have to experiment. Given that it does offer a few kinds and how flexible its routing is, I trust I can find what I’m looking for. And if not, there’s always their own helpful forum.
Enso. Right. I looked a little into it and I’ll look some more. I did read various posts about people using the different loopers. I asked you because whichever way one goes, it seems to be tricky to set things up in an effective way. The MC6 comes with a “looper mode” though, which might come handy. Up to now, I’ve used hardware loopers at the end of my chain, but I’d really like to be able to do everything ITB, in-the-box.
PS: Latest addition is that I got Lumbeat’s Jazz Drummer—which is my favorite virtual drummer, so far—to Play/Stop with the MC6, thanks to the help of Chatgpt. Useful assistant that. Sometimes.
@Vaultnaemsae Update. The ramping problem is fixed. As I happened to come across one of @LoFiLeiF videos again where he talks about the patchbay, I noticed the settings in the window that opens when you click on the CC# and saw that the 3rd setting was set to “expressive” rather than “latched”. So the FS-6 ramped up, as it should, rather than be an ON/OFF switch. And we learn.
Now, to a recurring (since it happened in the past) and real problem. Although I individually save the single patch of MG3 I use in every GP rackspace, when I switch rackspace MG3 doesn’t load that patch but loads one of the Factory patches. Which it shouldn’t as I never saved that. Any idea why this happens, @LoFiLeiF ?
PS: Unrelated to all this (though who knows) as I was working on this setup, the fans of my Macbook M1 Pro with 32G of RAM started to work. And that, for the very first time as far as I can recall. Which is strange, to say the least. I wonder why…
Glad it’s fixed but I’m unable to reproduce this.
Which factory patch? Is it the same factory preset loading in each rackspace?
Because it’s working hard and needs to cool down.
I use for now the same simple, basic MG3 patch I made, in each rackspace (which I named “Arkhis-Best” as I first created it using Arkhis). But saving it in each instance of MG3 doesn’t stick.
I just fired up that setup now and it’s doing it again. Rather than loading my patch, MG3 loads in each rackspace a factory patch, randomly on top of it. I don’t know why. It might be a bug. At this point, if it keeps happening it looks like the only solution is to remove the factory patches folder from its location, store it somewhere else if ever I want to use any of them, so that MG3 can only load my saved patch.
I know that. That’s obvious. But I have this laptop since a few years and I’ve been running on it all kinds of things including intensive Logic Pro recording sessions without the fans ever kicking in. And both GP and MG3 CPU meters were not running high, so it’s an unusual behavior, to say the least, which I can’t explain. It doesn’t make sense, but there it was. Ah well. Life… Expect the unexpected, as someone had it.
as laptops age, their cooling arrangements can get blocked by dust which reduces airflow.
after a time, tasks which didn’t produce noticeable fan noise may now do so.
going at it with a compressed air duster might improve things.
And I asked very specifically “Which factory patch?” in the hope that we might be able to find a clue as to why it’s happening. From your description, it sounds like there’s a particular patch being loaded when you change GP rackspaces (typically controlled by program changes). I see in your posted image that you have the Morningstar active as MIDI input in MG3’s patchbay.
@Vaultnaemsae That’s right, I use the MC6 to switch rackspaces, which works fine, and in each rackspace, as I wrote, the same MG3 patch is saved, but it doesn’t stick. It randomly loads a factory patch rather than the one saved. Which defeats the whole purpose.
I wonder if it’s a bug. Guess I could report it as one and see what JamO responds to that.
Hi @Bernard. Maybe I’m not asking the right question because I know no more now than I did before your reply.
You wrote “It randomly loads a factory patch rather than the one I saved” but I do not know what this means exactly.
- Which MG3 factory patch is being loaded? (I already asked this but I’ll ask again…)
- Is it the same factory patch each time you load a rackspace?
I’m sure it isn’t actually “random” since there is nothing random about MIDI (and my hunch is that a MIDI program change event is triggering this). If you can give the community a specific description, one of the very knowledgable members here will surely help you with a specific solution.
1 Like
Do you use your Morningstar pedal to change rackspaces in GP5 with PC messages?
If so, there is a chance that these messages are also reaching MG3 via the patchbay, if you are using “Any MIDI Controller” or “Morningstar Pro” there.
Try resaving the GP5 patch using the “No MIDI controller” setting in MG3 as a test, and then switch beteween backspaces. If the PC messages was the problem, you should not get any patch switching in MG3.
(This is by no stretch of the imagination the only way things could go wrong, but it seems like a reasonable place to start)
1 Like
I’m also 99% sure the MIDI PC thing is the issue, obviated by my line of inquiry and further validated by the fact that in @Bernard’s thread (that ended 10 days ago with the faulty assumption that @xtian82 had provided incorrect info) we addressed the very same issue.
MG3, Gig Performer and Morningstar MC6 misbehavior
In the above thread, we already solved the problem of MG3 chaning presets by setting “No MIDI Controller” in the MIDI patchbay. I’m pretty sure @Bernard and I also discussed the very same issue on the Gig Performer forum and the mods there posted an image referencing the solution from here.
1 Like
Ah sorry! I am obviosly not up to date with all the latest. 
1 Like
@Vaultnaemsae @Vaultnaemsae Thanks for responding. I’ll fire up my setup, make changes accordingly, see what happens, and report back.
Question: Since many apps operate that way, it occurred to me: Is MG3 programmed in such a way that, when we save a patch, it saves the state it’s in when we close it, so that it reopens where we left it ? Because if it’s not, that would explain it—then it loads one patch or another, randomly, and one always has to go into the menu, select whatever patch one wants to load, and load it.
If you’re using MG3 as a plugin (not standalone) the settings you have at the moment you saved your project in the DAW/host will be recalled upon reopening the same project file, including any changes you made to a preset but didn’t save as a preset within the MG3 file/patch system.
Don’t be sorry, @LoFiLeiF – your input is always helpful and most welcome! I was merely pointing out that the OP is taking us over old ground. The issue has already been solved – I was wondering why I was sensing deja vu…guess my memory isn’t that good either.
1 Like
@Vaultnaemsae @LoFiLeiF Update—took me a while to come back to this as I’ve been busy getting things ready for an album release and launch this coming sunday.
So, switching the patchbay to “no MIDI controller” didn’t really work. I say that because at first it looked like it was working. I switched to that in every MG3 instance patchbay, in every rackspace, and tested it by going back and forth between rackspaces and it worked. But then, the next day, when I powered everything up—and this is without having done any change in my setup, on both the hardware and software sides—the same issue happened again. MG3, rather than loading the patch saved, loaded the “default” patch. So I’m back to square one.
I just looked over my MG3 testing notes in which I see entries where there was a documented bug with MG3 (plugins only) receiving Program Changes even when the “no MIDI input” option was selected. This was more than 20 experimental versions ago but I’m sure the public beta has not received the correction yet – it has been addressed for the forthcoming version though.
As a workaround, until the next stable beta arrives, I would recommend that you backup then remove all user and factory presets. MIDI PCs will not be able to trigger anything if there are no patches there to trigger. Then use the MIDI Guitar MINI starter preset and send the MIDI out to destination synths in GP5.
The other option is to use MG3 in standalone and send MIDI out to GP5.
I realise it’s a lot of working around just to get moving. You may rather just wait for the next version to drop and try again when that time comes.
EDIT:
DISCLAIMER — I’m not 100% certain that this is the problem but I think there’s a fairly high probability that it is the reason why it’s happening. If you search, there is a thread on this forum about a MainStage 3 user who experienced something very similar.
@Vaultnaemsae Thanks for the input. At this point, I also feel that something(s) is not working quite right. Yet. Hopefully.
Another example… I have the first MG3 instance in GP5 first rackspace working fine. The MIDI OUTPUT block shows “MIDI Guitar Out” which appears when one selects the “Virtual MIDI output” option. Now, when I switch to the second rackspace in GP5, which has exactly the same MG3 patch loaded, when I select the same option—“Virtual MIDI output”—it doesn’t lead to “MIDI Guitar Out”, but to “No MIDI output”. There is no “MIDI Guitar Out” available now, although as I wrote everything is exactly the same, all the settings in MG3 and GP5.
I’ll try using the MINI patch, while I have to see if I can manage with MINI to have the same parameters working the way they worked in my patch—which are CC#11 for volume with an expression pedal and CC#1 for the Sustainer triggered by another pedal, both routed through the MIDI Device.
“…use MG3 in standalone and send MIDI out to GP5.” Interesting idea. I’ll look into that too. I also thought that I could try using only one instance of MG3, in the Global rackspace, from there wired to the rackspaces with each their instrument, and see what happens.
In the end, another possibility is to switch back to MIDI Guitar 2 and see how that goes, with my initial setup and the other options.
The issues you are experiencing (and more) have been under repair in the experimental versions. The forthcoming version will certainly address this.
I think I alluded to this in an earlier recommendation to use a single instance of MG3 in the GP5 global rackspace. That would likely help tidy up your MG3 issues — at least for now. The reason is that MG3 creates a virtual MIDI port that remains active as long as the MIDI Output module is active. Duplicating instances could generate issues.
FWIW, many things have been changing in the background and even different plug-in formats were displaying different behavior… so it’s a little tough to keep track of.
1 Like