![]() MIDI plug-ins for some reason do affect the source, I would think that is something that would not necessarily be tied to the source channel strip. There is *some* flexibility to aliased channel strips, so we can change octave transposition without affecting the source channel strip, but. There are some other drawbacks to this approach. What's actually the right way to copy/paste (as alias) multi-timbral channel strips, and in particular, the audio auxes for the 2nd thru last stereo pair? It's been about 16 hours today - I think I can get away with using concert level auxes, there are 64 of those. it's selectable as an aux, but it needs to persist. it's there in the target patch/channel strip. The trick that has to work here is this, the INPUT, which is an aux, related to the channel strip that was originally copied. I use two keyboard controllers, it's absolutely possible to have the same string pad on both, one as a layer and then one as a solo line. When did it start going wrong? Pasting two of the same channel strips as aliases. I think I confused MainStage though and since then these are simply NOT saving which makes this approach worthless. Was building these all day, no crashes, saved well, performance was amazingly good, and I'm CERTAIN that after a save, the routings were still good. When pasting, I have to reselect the source aux (the ones that MS wired up on it's own for multi-timbral outputs (after the 1st pair, so in a 16x2 in creates 15 auxes, for the 2nd thru 16th pair). Then, I started taking these and again pasted the alias and the accompanying AUX audio strip into patches. Built these up from scratch all day, saved, reloaded, it all worked. I made a bunch of individual patches, using a pasted alias the multi, and a copy of "wired up" aux, so K3-4, set the midi input to multi-timbral, assigned main controller to the proper midi channel, en voila, I can almost treat the multi as if it were just a rack of stuff. So, I've got this 16x2 Kompakt multi and this 8x2 Omni multi. Gave up on that, it's not the question here, but if someone can confirm this, then I'll make a bug report. Well, we *can* tell it do this, but it doesn't work, or it does, and then it does, and then it doesn't anymore. ![]() MainStage "wires up" a bunch of auxes for us, that's 3-4, 5-6, 7-8, so forth an so on that we get when we press the "+" button on a multi-timbral instance. We can't tell the aliased multi to output to a patch bus, because. Been doing this for years.įor a MULTI-TIMBRAL multi though, things are different. If pasting a non-multi-timbral instance of a given plugin, one can change the output of the plug-in to be a patch bus on the path, add an audio channel that "picks up" that patch and voila, one piano goes a long, long way as they can all be effected ad nauseum in that patch. Purpose is to copy/paste as alias only need it to be more "flexible". Pianos, horns, Strings - all the general purpose stuff. What's in there? Anything that might get used more than once in the concert. Need someone to verify this situation, if possible.īuilt two multi racks, one in Kontakt and one in Omnisphere 2. ![]() Please let me know if there is any other information I should provide.I either confused MainStage or it simply has got me dumbfounded again. On Mainstage, can I check the patches to see if they are detuned? Can these controllers inadvertently be sending pitch detune messages? If so, how do I turn it off? This has occurred on various controllers, including the Korg X50, the Alesis Vortex Wireless, and the Alesis V61. The out-of-tune pitches have occurred with sounds in Omnisphere 2, sforzando (playing sf2 files consisting of 24-bit, 44100 Hz AIF samples), and other instruments. I've seen a few similar posts on this issue and I wanted to ask for tips on isolating the cause or causes of the problem. The problem is fixed when I close the concert and reload it, but this obviously is not a good solution during band rehearsal and performances. On numerous occasions, shortly after loading a concert, patches from various software instruments play out of tune. I'm running Mainstage 3 on a Macbook Air (2013) with an i7 processor, 8 GB RAM and 512 GB SSD containing over 100 GB of free space.
0 Comments
Leave a Reply. |