Hi guys, new to Ableton...
Just want to know if there is a reason why the Schwarzonator won't release the notes when using an external vst like Sylenth ect. For some reason, it keeps playing one note, until it hits the next one. It wont release in between notes. I'ts fine when using Operator or Analog. I've tried with a bunch of different external synths and encounter the same problem. Hope I'm making sence..
Thanks for any help with this!
Cheers
p.s..forgot to say, this happens only with midi
Microsoft Windows 7 Home Premium
Studio XPS 8100
System Type x64-based PC
Processor Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz, 2934 Mhz, 4 Core(s), 8 Logical Processor(s)
RAM 8.00 GB
The Schwarzonator not releasing notes with external vst's
Re: The Schwarzonator not releasing notes with external vst's
Ok, so I may have solved it...but now I have a new problem...
I was using more than one instance of the Schwarzonator, and not the "little brother". As soon as I used only the Schwarzonator on one synth, and "little brothers" on say 2 other synths..It all works fine.
So that means I can only use 1 Schwarzonator with it's little brothers in the whole track?
What if I want to use another Schwarzonator on a different synth, because say I want to use the "add more notes" and "spread" function, so that it differs from the first Schwarzonator, is this possible?
Cheers
I was using more than one instance of the Schwarzonator, and not the "little brother". As soon as I used only the Schwarzonator on one synth, and "little brothers" on say 2 other synths..It all works fine.
So that means I can only use 1 Schwarzonator with it's little brothers in the whole track?
What if I want to use another Schwarzonator on a different synth, because say I want to use the "add more notes" and "spread" function, so that it differs from the first Schwarzonator, is this possible?
Cheers
Re: The Schwarzonator not releasing notes with external vst's
Got the same problem, anyone?
-
josquin2000
- Posts: 36
- Joined: Wed Mar 16, 2005 5:24 pm
- Location: Deep in 'it'.
Re: The Schwarzonator not releasing notes with external vst's
Well, you should verify with the released code, but typically, such a tool will set up a set of "named send - receive pairs" : one set of sends in the main app, and a set of corresponding receives in the "little brother" apps. These pairs are how the two apps communicate with each other.
Note, though, no matter how many little brothers you have , they all listen to the same set of named send objects in the one main app; And when you add another main app, things get really screwy, since there will be two different sets of send objects, *named the same*, telling the receive objects two sets of information:
one swartzenator sez: "play these pitches", the other sez "NO play *these* pitches", and the poor lil brothers cannot tell who to believe/receive from.
It is an issue that has come up in max dev repeatedly: once send<->receive remote communications are set up in maxmspjitter apps, they are truly global to all running instances under that max runtime.
A simple solution, if you have the edit ability of the full max app *and* max4live:
Open the swatzenator app and little bro app in max4live editor. Find each send and receive object (name is also shortened to 's' and receive ('r'), so be careful) in either app, and add, say '2' to each name
from
send arbitraryString
to
send arbitraryString2...most of these will prob be in main app...
now, same for all recieves, so you'll have to change
receive arbitraryString
to
receive arbitraryString2 somewhere in the lil brother app, prob.
once *all* of these are renamed, in all patchers (important here: open all subpatches, do textbased search, but be thorough!) in either app, save each as "Swartzenator2.amd" and "LittleBrother2.amd" these should now be peacefully coexistent with the original app inside Live. For a third instance, do all this again, using a new set of unique names for the send receive pairs..
You only have to make these once....
but put simply, without such trick as above, you currently can only run one swarztenator/multiple lilbro(s) set at once.
send receive pairs are global by identifying symbol/"name".
g'luck!
cfb aka j2k
Note, though, no matter how many little brothers you have , they all listen to the same set of named send objects in the one main app; And when you add another main app, things get really screwy, since there will be two different sets of send objects, *named the same*, telling the receive objects two sets of information:
one swartzenator sez: "play these pitches", the other sez "NO play *these* pitches", and the poor lil brothers cannot tell who to believe/receive from.
It is an issue that has come up in max dev repeatedly: once send<->receive remote communications are set up in maxmspjitter apps, they are truly global to all running instances under that max runtime.
A simple solution, if you have the edit ability of the full max app *and* max4live:
Open the swatzenator app and little bro app in max4live editor. Find each send and receive object (name is also shortened to 's' and receive ('r'), so be careful) in either app, and add, say '2' to each name
from
send arbitraryString
to
send arbitraryString2...most of these will prob be in main app...
now, same for all recieves, so you'll have to change
receive arbitraryString
to
receive arbitraryString2 somewhere in the lil brother app, prob.
once *all* of these are renamed, in all patchers (important here: open all subpatches, do textbased search, but be thorough!) in either app, save each as "Swartzenator2.amd" and "LittleBrother2.amd" these should now be peacefully coexistent with the original app inside Live. For a third instance, do all this again, using a new set of unique names for the send receive pairs..
You only have to make these once....
but put simply, without such trick as above, you currently can only run one swarztenator/multiple lilbro(s) set at once.
send receive pairs are global by identifying symbol/"name".
g'luck!
cfb aka j2k