MuTools

Nickl · Post by **Nickl** » Wed Mar 06, 2013 8:08 pm

Is anyone using Noatikl VST in Mulab? I would be interested to know of any issues experienced in implementing it - supposed to be a bit of a challenge!

> DiGiT < · Post by **> DiGiT <** » Thu Mar 07, 2013 4:08 am

that would be easy in mux

Nickl · Post by **Nickl** » Thu Mar 07, 2013 10:15 am

Thanks. Yes, that's what I thought so I have now tried it. Runs Ok if I just feed the audio from Noatikl through Mulab. However It also sends midi data on up to 16 channels and I was hoping to route the midi output to other synths in Mulab. Noatikl only shows 1 audio and 1 event output in the session Mux - if I connect the event output to a basic musynth, Mulab crashes. I lost patience with it this morning, I'll experiment further later but any help in the meantime would be appreciated.

> DiGiT < · Post by **> DiGiT <** » Thu Mar 07, 2013 1:27 pm

youre not connecting to musynth while the sequencer is running are you?

Nickl · Post by **Nickl** » Thu Mar 07, 2013 1:53 pm

Yes - the vst doesn't have it's own transport controls so I use the main Mulab ones; there are no midi tracks on the sequencer so as far as I can see there should not be conflicting midi messages. I'll spend some more time fiddling with it later - there is probably something simple that I'm missing and a bit of analysis will reveal.

Nickl · Post by **Nickl** » Fri Mar 08, 2013 11:03 am

The vsti vision of Noatikl is still proving to be a bit of a challenge. I have trial copies of both the vsti and standalone visions of Noatikl. Using Maple midi router I can get the standalone vision of Noatikl to run multiple synths in Mulab; the correct midi sequences flow from Noatikl through the selected channels to the relevant synths in Mulab. No problems with the sound.

Using the midi channel splitter in Mulab, I can get the correct midi sequences to flow from Noatikl vsti through the selected channels to the relevant synths in Mulab, but the sound breaks up almost immediately and Mulab crashes.

The difference between the two set-ups is Maple midi router - I can't see how or why I would need that for a vsti within Mulab. Any ideas as to what I am missing here please?

RalphRoisterDoister · Post by **RalphRoisterDoister** » Fri Mar 08, 2013 1:31 pm

I use Noatikl with Mulab on a Mac and they play quite well together. I'm not sure about Windows, but on my Mac I have Noatikl's midi out on Bus 1, and Midi in on Bus 2 (Partikl, Sync, Listen and Use Patch all unchecked ). In Mulab I select Bus 1 as my input port 1 in Midi Setup. I then use the Midi Input Channel Target selector to route each midi channel from Noatikl to a separate instrument rack. When I start Noatikl I can make whatever changes I need without issue. As I said, I have know experience with windows, so this might not help at all.

Nickl · Post by **Nickl** » Fri Mar 08, 2013 1:47 pm

Thank you - that's very encouraging. It looks very similar to the way I set it up on Windows, except that Bus1 and Bus 2 are not an option. I'll have to look at this more closely this evening.

RalphRoisterDoister · Post by **RalphRoisterDoister** » Fri Mar 08, 2013 2:46 pm

Bus 1 and Bus 2 are separate mid ports for the MAC IAC midi driver. You need to set up 2 ports for your midi router. Also, I forgot to mention that I am using the stand-alone version, not the plug-in.

Nickl · Post by **Nickl** » Fri Mar 08, 2013 3:47 pm

OK - that's a pity. As I said earlier, I can get the standalone version to run with Mulab but not the vsti. Probably a question for Jo - if the standalone version of Noatikl appears to work OK with Mulab, albeit using a 3rd party midi router in Windows, why would the vsti version not work?

MuTools · Post by **MuTools** » Fri Mar 08, 2013 3:55 pm

I can't answer the question as it seems to be specific for a specific VST. Unfortunately i can't install and check out each and every VST plugin (version). If there is clear reason that there would be something wrong in MuLab's VST interface then i'll research. Hope you understand. (limited dev time)

Nickl · Post by **Nickl** » Fri Mar 08, 2013 4:53 pm

Thanks for the quick response Jo. I wasn't looking for you to undertake a detailed investigation, I'm more interested in understanding where the issue possibly lies. If I understand your response correctly, it is possible that the midi routing implementation in Mulab will not handle streams of midi data coming from a single vst going through up to 16 channels to 16 different targets, at least not in the way that it has been implemented in Noatikl.

As I said at the outset of this thread, the Noatikl vsti is acknowledged as being a bit of a challenge to implement because of its per channel usage. The developers only list 4 DAWs where they know for certain the vsti works OK ( Sonar, Cubase, Reaper, GarageBand).

janamdo · Post by **janamdo** » Fri Mar 08, 2013 11:04 pm

I think it is a old issue ..for a a few times as subject discussed here on this forum, but there was no reaction from the developer.
I think this composer's midi output must be routed to a midi input of a vst
instrument

Nickl · Post by **Nickl** » Sat Mar 09, 2013 9:14 am

I have now managed to get the Noatikl vsti to work in Mulab using Maple midi router to connect its midi output to synths in Mulab racks. The only remaining issue is that the last note being played by a synth hangs when Noatikl stops playing.

MuTools · Post by **MuTools** » Sat Mar 09, 2013 9:41 am

And does Noatikl send out the note off for that note? Connect an Event Monitor to check the event output stream of Noatikl.