SquaredHeads Nora: Arpeggiator (2.5 Released!)

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
Nora

Post

This looks almost like a DAW within a DAW (like a mini Live).

Post

aMUSEd wrote:This looks almost like a DAW within a DAW (like a mini Live).
My thoughts exactly when I first saw it!

Post

VariKusBrainZ wrote:
squaredheads wrote:
lnikj wrote: Live notoriously cannot route midi in this way. Recompose's Liquid Notes appears to have pulled it off with a max4live device but I am not aware of any easy solution to this problem. If anybody has one please speak up.
Could not use Live plugin 'effects' before an instrument in a track? If it cannot, another solution could be using a plugin chainer (like FL Studio one) that can have inside different paths for each plugin you load.
Place midi plugin on one track.
Place synth on another track and set its midi in to point at Nora
That's not the problem.

The problem is how to pipe several Nora tracks, each on its discreet MIDI channel, to several corresponding MIDI synth tracks.

Please read the above handful of posts and then you're welcome with a solution. ;-)

/Joachim
If it were easy, anybody could do it!

Post

Spitfire31 wrote:
VariKusBrainZ wrote:
squaredheads wrote:
lnikj wrote: Live notoriously cannot route midi in this way. Recompose's Liquid Notes appears to have pulled it off with a max4live device but I am not aware of any easy solution to this problem. If anybody has one please speak up.
Could not use Live plugin 'effects' before an instrument in a track? If it cannot, another solution could be using a plugin chainer (like FL Studio one) that can have inside different paths for each plugin you load.
Place midi plugin on one track.
Place synth on another track and set its midi in to point at Nora
That's not the problem.

The problem is how to pipe several Nora tracks, each on its separate MIDI channel, to several corresponding MIDI synth tracks.

Please read the above handful of posts and then you're welcome with a solution. ;-)

/Joachim
If it were easy, anybody could do it!

Post

As lnikj said, you cannot do this in live since it muxes all midi outputs from a plugin in to one channel. You'll have the same problem with other vsts like consequence or anything that outputs over multiple midi channels. You could probably code up something in m4l that maybe could receive all midi afterwards and then has m4l plugins that can choose which midi channel from the sending device on individual tracks. But that all depends if even m4l can see the separate midi channels before live muxes them

Liquidnotes its probably a special case since the m4l device is generating (or receiving them from the external liquid notes app) so it is aware of all of the midi channels before live interferes with them

Post

As I said, Kirnu's Cream handles multiple MIDI outputs in Live just fine.

It's not a Live problem, it's the midi plugin that needs to make its outputs available.
Last edited by iDesignSound on Mon Dec 08, 2014 7:49 pm, edited 3 times in total.

Post

Have you tried using what you are showing and been able to receive separate channels from cream? To actually receive midi from a plugin you choose the track in the first drop down. The second drop down should have a midi output stating the name of the vst itself (or at least this is how its always worked since Ive used live):

Image

Every midi plug Ive ever used has had this issue because live does not handle them. Consequence which I have seen work in other daws that do handle multiple midi outputs work fine, but live muxes them all to the single output just like cream shown here. Ive never seen multiple midi outputs from a vst. Its also why its all over the feature requests in the live beta forums

Post

ezelkow1 wrote:Have you tried using what you are showing and been able to receive separate channels from cream? To actually receive midi from a plugin you choose the track in the first drop down. The second drop down should have a midi output stating the name of the vst itself (or at least this is how its always worked since Ive used live):

Image

Yes, it works just fine. See below...
Screenshot 2014-12-08 19.46.15.png
You do not have the required permissions to view the files attached to this post.

Post

what is 'cream 2'? Your first track is just cream. Cream 2 would be something else then? What does your midi setup in live look like?

Its just that if you've somehow managed to have multiple midi outputs from a vst working in live then you've managed to do something that people on the forums have been asking for for ages and ableton has as a known request.

Post

That's just because I deleted the first instance of Cream and then reloaded it, so Ableton named it Cream 2.

Well I don't know what to say. It's always worked for me.

Are you on a Mac or PC?

Post

iDesignSound wrote:That's just because I deleted the first instance of Cream and then reloaded it, so Ableton named it Cream 2.

Well I don't know what to say. It's always worked for me.

Are you on a Mac or PC?
Well, please let us know when you demo Nora 2.0. If you would get the same results as you have with cream it would be great.
What machine are you running?
I'm using Win7 with Live 32bit....maybe this is the problem??

Post

After researching for a while about the Live problem, I may say that Live unfortunately doesn't support any kind of MIDI Chanel filtering (using track routing). However it supports it when the MIDI is comming from an external device.

What you're seeing in that screenshot "From Cream 2" is because Cream is being used as AU with Virtual MIDI port. You can use Nora aswell as AU and you will have the same result, you will be able to filter the MIDI Channel with the port "Nora Input x".

This trick can be used in PC, but you would need to use a physical MIDI Output and Input, or use any software that generates a Virtual MIDI Port. Windows has not built in this feature.

The problem using MIDI ports are the generated timing problems (Fortunately 2.01 is able to record its own output without any timing issue). I highly recommend using VST instead AU, and a better workaround: using a VST Chainer with VST Channel Filter and the instrument in instrument track. I think there are few ones. I could easily create a VST Channel Filter in a day. But instead this I would allow Nora hosting VST inside. However this is time consuming and I must plan it carefully.

Post

^
Thanks, so I wasnt going insane, figured it was something to do with the virtual midi and routing on macs. Having a drop down full of midi channels was too much like an external input than how live normally treats routing vsts. Thats why i wanted to see the midi setup in the live options to see if it was a virtual port
Last edited by ezelkow1 on Mon Dec 08, 2014 8:24 pm, edited 1 time in total.

Post

woodsdenis wrote:Hi

To eliminate Patchwork from the possibilities I just tested Nora in Studio One 64 bit

When Pressing Stop

Dune 2 100 % a Core
Dune 30 %
GForce Odditty. 30 %
Xfer Serum 30 %

Ones in my system that were ok

Native Instruments
Spectrasonics
Synthmaster
Arturia
Fabfilter
Spire
UHE

So it seems its a Dune issue mainly, it does it in mono so I guess whatever way it handles note offs is strange.
The six core peak was in a session with other plugins, when testing now with just Nora and a vst it was one core that maxed out.

If there is any clue in this is that Cthulhu which I assume does the same all notes off procedure does not make Dune 2 do this.

tx for quick response and a cool product.
Thank for testing. Please, do a final test: play the host with Nora loaded and switch between playlist and pattern mode. Each time you switch the mode, Nora will send the noteOff to all its outputs, like when you stop the host. So, if it's a noteOff problem related with Dune 2, you should have the same results.

Post

squaredheads wrote:After researching for a while about the Live problem, I may say that Live unfortunately doesn't support any kind of MIDI Chanel filtering (using track routing). However it supports it when the MIDI is comming from an external device.

What you're seeing in that screenshot "From Cream 2" is because Cream is being used as AU with Virtual MIDI port. You can use Nora aswell as AU and you will have the same result, you will be able to filter the MIDI Channel with the port "Nora Input x".

This trick can be used in PC, but you would need to use a physical MIDI Output and Input, or use any software that generates a Virtual MIDI Port. Windows has not built in this feature.

The problem using MIDI ports are the generated timing problems (Fortunately 2.01 is able to record its own output without any timing issue). I highly recommend using VST instead AU, and a better workaround: using a VST Chainer with VST Channel Filter and the instrument in instrument track. I think there are few ones. I could easily create a VST Channel Filter in a day. But instead this I would allow Nora hosting VST inside. However this is time consuming and I must plan it carefully.
Yes, was using the AU version. I didn't know it was using Virtual MIDI ports, although I haven't noticed any issues with this. I also use Sundog with a Virtual MIDI port and the timing is always fine.

I'm not sure what you mean by VST Channel Filter. Which chainers support that? I have IL minihost, will that work?

Post Reply

Return to “Instruments”