Studio One Namm Deal

[aMUSEd]

Beginning of a petition for Presonus to allow for vst's in Studio One Artist!

It's easy enough to add it using the workaround I posted

[LawrenceF]

Not impressed with their (lack of) support - 10 days now

My guess is that nobody actually has one and has no idea, but yeah... your request seems to be lost in space.

The entire thing is quite strange though because once the midi gets beyond the midi interface and blinks the meters and/or registers in the event window, it has nothing to do with the device itself anymore.

Check your PM's.

[jazzimprov]

Beginning of a petition for Presonus to allow for vst's in Studio One Artist!

It's easy enough to add it using the workaround I posted[/quote


Works great with the VST's but am having issues with VSTi--can't get the ouptput to my external keyboard although I can see the meters jumping from within studio artist . all other non chainer vst's work fine.

If I use the keyboard on the vsti e.g. kontakt, It will play the sound but not thru the keyboard and on independence free, nothing happens from the external keyboard or the one built in.

not complaining for 20.11 in 2011

[standalone]

Not impressed with their (lack of) support - 10 days now

My guess is that nobody actually has one and has no idea, but yeah... your request seems to be lost in space.

The entire thing is quite strange though because once the midi gets beyond the midi interface and blinks the meters and/or registers in the event window, it has nothing to do with the device itself anymore.

Check your PM's.

Frankly speaking, if it was Cubase we would know what to recommend: "move 'enableemulated' and/or 'ignoreportfilter', select 'use system time stamp'...". I think this could be a similar problem but we don't know how S1 can deal with it.

[simesf]

@aMUSEd - I sympathise because I put a request in for technical support and it took a few days for them to get back to me. My guess is that the NAMM sale has led to rather a lot of tech support questions and they are working hard to keep up with the rush.

[standalone]

Not impressed with their (lack of) support - 10 days now

My guess is that nobody actually has one and has no idea, but yeah... your request seems to be lost in space.

The entire thing is quite strange though because once the midi gets beyond the midi interface and blinks the meters and/or registers in the event window, it has nothing to do with the device itself anymore.

Check your PM's.

Frankly speaking, if it was Cubase we would know what to recommend: "move 'enableemulated' and/or 'ignoreportfilter', select 'use system time stamp'...". I think this could be a similar problem but we don't know how S1 can deal with it.

After some tests with S1, Cubase and my midi keyboard I can confirm that the problem is the way that S1 works with emulated midi ports.

My keyboard can work both transmiting midi via usb connection and with a midi cable via my sound card. In the first case there is not a problem both in Cubase and in S1. When I use a midi cable connected to my sound card S1 receives midi data but it doesn't transmit it to the instrument track and the only option shown in it is "All Midi Inputs".

Cubase behaves exactly the same, the emulated port from my sound card doesn't show up in the track and "All Midi Inputs" is not enough. But when I use the classic workaround, putting "enableemulated" and "ignoreportfilter" in Cubase's root folder, the emulated midi port from my sound card shows up in the track, I can select it and everything works fine. Still, "All Midi Inputs" is not enough, one must select the specific emulated midi port for each track.

What Presonus needs to do is enabling emulated ports so they can be selected in every instrument track. I don't know if it is already possible and there is a workaround like the one in Cubase. Let's see if they say something about this.

[aMUSEd]

Thanks - that is interesting but I'm a little confused. The midi port from my NI Kore interface is a real one isn't it? Not emulated? And why would it pick up midi information (you can even see note information showing in the midi analyser) but just not pass it to an instrument? And why would this be specific to when I use the Kore drivers but not the Virus drivers?

[standalone]

Thanks - that is interesting but I'm a little confused. The midi port from my NI Kore interface is a real one isn't it? Not emulated? And why would it pick up midi information (you can even see note information showing in the midi analyser) but just not pass it to an instrument? And why would this be specific to when I use the Kore drivers but not the Virus drivers?

I'm not a specialist here but I think it's emulated because no real midi information runs through the computer, the midi data is always converted in some way to be understood by the applications. With the usb connections it seems to be easier, I don't know why. By the way, my sound card is an Audio Kontrol 1 from NI, so it may also have something to do with the way that NI deals with this things.

As for midi data being received and not transmited to the track, as I said I have experienced the same. I don't know what's inside but the surface of the problem seems to be that in S1 the option to select the emulated port doesn't appear in the track and "All Midi Inputs" is not enough. In Cubase it's the same, selecting "All Midi Inputs" doesn't work, you must select the specific port when using a midi cable and a NI's interface.

[efluon]

midi with windows is not easy to do. in studio one if you go into the options there is an advanced section. which has a midi section. at the bottom of that there are two settings: hide emulated ports, which you should try first (i.e. uncheck and then select an emulated port for machine). and then there is the option to use legacy midi and not directmusic. which may introduce timing inaccuracies, but may work.

[aMUSEd]

Thanks - that is interesting but I'm a little confused. The midi port from my NI Kore interface is a real one isn't it? Not emulated? And why would it pick up midi information (you can even see note information showing in the midi analyser) but just not pass it to an instrument? And why would this be specific to when I use the Kore drivers but not the Virus drivers?

I'm not a specialist here but I think it's emulated because no real midi information runs through the computer, the midi data is always converted in some way to be understood by the applications. With the usb connections it seems to be easier, I don't know why. By the way, my sound card is an Audio Kontrol 1 from NI, so it may also have something to do with the way that NI deals with this things.

As for midi data being received and not transmited to the track, as I said I have experienced the same. I don't know what's inside but the surface of the problem seems to be that in S1 the option to select the emulated port doesn't appear in the track and "All Midi Inputs" is not enough. In Cubase it's the same, selecting "All Midi Inputs" doesn't work, you must select the specific port when using a midi cable and a NI's interface.

afaik Audio Kontrol uses the same drivers as Kore so I'm pleased you can replicate my experience. I'll pass that back to NI and Presonus - thanks

[aMUSEd]

A poster at the S1 forum suggested toggling the hide emulated ports box in options/advanced. If I have this box checked and go to the "Add device" panel where you add a midi device it lists the single Kore midi in normally but if I uncheck it it identifies what appears to be the same midi in as "emulated" (ie there is still only one port listed but now it has "emulated" next to it). However with the Virus Ti drivers the same list shows emulated and non emulated midi ports listed seperately. I think that must be significant.

[efluon]

and, does that work? did you try the legacy ports?

[aMUSEd]

By legacy port do you mean the unemulated ones? Yes and no - the Virus Ti midi in (not emulated) does work but only if I am using the Ti as my soundcard as well (which I prefer not to do if I can help it). It does not seem to work if I use it with the Kore ASIO drivers - I'm not really sure why that should be the case as I'd have thought they should not be so closely interconnected but hopefully one of the devs will. There is a clear pattern here anyway.

[efluon]

no, i meant the windows legacy midi setting (as described above..)

dunno, but this problem seems to be with the directmusic api and the way drivers for directmusic are created.

[aMUSEd]

Ah - I had already found if I uncheck that box I get no midi input at all.