Posted
I've created 12 Descriptions for my 12 LoopBE30 MIDI out ports (Tons of MIDI channels), all of them are setup the same way just pointing to different output ports and added sounds that points to the various instrument tracks hosted in Ableton Live.
On some of them it says in Red: Ambiguous
The tooltip says: "Edit your divice to make this indication go away"
If only I knew what to edit :?
Everything seems to be working fine, so I don't know if it's just a warning or cautionary message that I can safely ignore.
Wed, 2013-04-24 - 11:47 Permalink
Make sure you select a device category and enter an instrument name....
But....
You might find better stability and tighter timing if you use the drones in ableton. A standard drone can host a vst...but you need to make it a midi drone and route it to a new track for ableton instruments... However your experience might be different, just the loopbe drivers used to be the only way and I used to find it fragile.
Wed, 2013-04-24 - 15:55 Permalink
All the sounds I've added have cateogories, just double checked so I don't think it's that.
As far as I can tell, all the Devices I've added for the LoopBe30 ports are Identical except for the sounds added to each of course.
I'm getting rock solid timing and no jitter I can detect just running LoopBE30 virtual MIDI. I checked latency with loopback test and it's is around 12ms, that's no problem for me.
The reason I haven't bothered with the drones is I have over 60 MIDI tracks and around 80 audio return tracks comming back from my VEP5 slaves hosting all my sample libraries running on a couple i7 machines, and I'm not sure how the drones are going to handle all that, it's very stable as is so I don't want to "rock the boat" hehe.
I tried activating the 64 engine in Synfire just to check how the VEP5 plugins would run natively in Synfire, but I got a large latency trying that.
Wed, 2013-04-24 - 16:31 Permalink
Ambigous means the device can not tell whether it is channel-based (sounds on fixed channels) or program-based (sounds selected dynamically on any available channel).
This is not critical, but you should look into the sounds if you have accidentally set fixed channels or programs where you did not want them.
Wed, 2013-04-24 - 18:23 Permalink
Ok that put me on the right track. Seems this is caused if you have sounds where you select the sound by specifying a midi channel and at the same time have a program change. I did that because before I upgraded to Pro I didn't have articulations, and LA Scoring Strings reacts to keyswitches but also accepts program changes to select articulations, so I at least always had the Kontakt patch initialized to the Legato articulation by issuing program change 1
I removed it now and the warning went away.