KVR Audio

Rozzer · Post by **Rozzer** » Thu Dec 16, 2004 5:27 pm

Sahul wrote:So Roomworks is just Ambience with a new GUI and surround compatibility?

Having just done a 1to1 comparison of the two, I'd say was definately Ambience with a new front end. Oddly enough though, you can't share presets between the two.

I'm kind of with you really. Ambience is great, but I was hoping for something new. Ah well... nice skin job anyway!

And midi d&d... YAY

ahja · Post by **ahja** » Thu Dec 16, 2004 5:31 pm

Hey... Could someone please try to load the 'fingerprints' skin, and tell me if it works? Doesn't seem to want to load over here.

english · Post by **english** » Thu Dec 16, 2004 5:32 pm

Sascha Franck wrote:So, nobody on the MIDI "device" thing yet?
I'd REALLY like to know as this could be quite something I was missing in previous versions!

Yea sash, this works well now. This update is REALLY nice at first impressions. Everything is so much tighter and stable. Also they seem to have fixed the output latency when using dsp plugs on the master chan.
Its not mentioned in the update but thats one class fix.

eng

Rozzer · Post by **Rozzer** » Thu Dec 16, 2004 5:32 pm

Sascha Franck wrote:So, nobody on the MIDI "device" thing yet?
I'd REALLY like to know as this could be quite something I was missing in previous versions!

You mean this: "MIDI devices can control audio channel insert plug-in parameters and VST instrument parameters"....

not sure I understand it.

Sahul · Post by **Sahul** » Thu Dec 16, 2004 5:37 pm

rozzer wrote:And midi d&d... YAY

Can you please confirm that? I'm at work right now and I can't test the update yet. So the lovely Midiview plugin works again with 3.01?

I was waiting for the update just for this.

Sahul · Post by **Sahul** » Thu Dec 16, 2004 5:41 pm

Its not mentioned in the update but thats one class fix.

According to the guys at cubase.net, there seems to be A LOT of important things also addressed on this update but not mentioned in the PDF.

Rozzer · Post by **Rozzer** » Thu Dec 16, 2004 5:42 pm

Sahul wrote:
rozzer wrote:And midi d&d... YAY
Can you please confirm that? I'm at work right now and I can't test the update yet. So the lovely Midiview plugin works again with 3.01? I was waiting for the update just for this.

Yep, Midiview is working again

Sahul · Post by **Sahul** » Thu Dec 16, 2004 5:46 pm

rozzer wrote:Yep, Midiview is working again

Thanks!

Sascha Franck · Post by **Sascha Franck** » Thu Dec 16, 2004 6:12 pm

Rozzer wrote: You mean this: "MIDI devices can control audio channel insert plug-in parameters and VST instrument parameters"....

not sure I understand it.

Well, from what I *seem* to understand this means that you could assign MIDI controllers (freely?) to mixer and VST(i) parameters.
But I can't find anything how this is supposed to work and to be set up.
I wish SOOO much this was like I understand it because I just hate any sort of trackbased automation (btw, the same is true for Logic's automation) - I'd prefer recording *plain* MIDI data any day to control VST(i) and audio channel parameters!

So, anybody found out the "how to" yet?

ahja · Post by **ahja** » Thu Dec 16, 2004 6:17 pm

Hey Sascha,

With Cubase SX3.0.1, the unique MIDI device panels system is now also available for editing effect plug-ins in audio channels as well as VST instruments, making any parameters of those objects instantly accessible not only in the Project Window, but also on the appropriate channel mixer strip and the track inspector through user-defined panels.

I guess this basically works just like the Hardware synth/effect device panels. But, you are able to select the few parameters that you need in plain view at all times right in your inspector, or wherever you want it. I could see how this would be useful for such VSTi's as Spectrasonics where they only allow CC data. This will enable you to use synths like those as standard VST automation, or appear to, atleast. From what I gather, you'd rather record basic CC information rather than track/VST automation, so I don't know if this will benifit you at all.

And yes, Freely. It is set up via the Midi Device Panel in your Devices menu.

Sascha Franck · Post by **Sascha Franck** » Thu Dec 16, 2004 6:22 pm

ahja wrote: I guess this basically works just like the Hardware synth/effect device panels. But, you are able to select the few parameters that you need in plain view at all times right in your inspector, or wherever you want it. I could see how this would be useful for such VSTi's as Spectrasonics where they only allow CC data. This will enable you to use synths like those as standard VST automation, or appear to, atleast. From what I gather, you'd rather record basic CC information rather than track/VST automation, so I don't know if this will benifit you at all.

And yes, Freely. It is set up via the Midi Device Panel in your Devices menu.

Hm, thanks - I will have a look into it. Defenitely sounding promising.
And yes, recording CC information rather than track automation data would be kickass in my book!

Rozzer · Post by **Rozzer** » Thu Dec 16, 2004 6:26 pm

Sascha Franck wrote:
Rozzer wrote: You mean this: "MIDI devices can control audio channel insert plug-in parameters and VST instrument parameters"....

not sure I understand it.
Well, from what I *seem* to understand this means that you could assign MIDI controllers (freely?) to mixer and VST(i) parameters.

I suspect you're going to be disappointed. As ahja says, I think its something to do with Midi Device Panels, which don't accept midi cc# from the outside world either.

Still, I've fished about and I can't seem to find out how it works at all. Midi Devices can still only be assigned to physical midi ports, and their Panels automatically go to the same port, so how does one set up a panel for a VSTi/VST.

Maybe I've misunderstood. I started a thread on cubase.net to see if anyone can shed some light.

Sascha Franck · Post by **Sascha Franck** » Thu Dec 16, 2004 6:43 pm

Rozzer wrote: Maybe I've misunderstood. I started a thread on cubase.net to see if anyone can shed some light.

Please paste here once someone answers.
(Yeah, I know, I should finally get used to Cubase.net, but right now... uhm).

ahja · Post by **ahja** » Thu Dec 16, 2004 7:25 pm

http://forum.cubase.net/forum/Forum2/HTML/074319.html

cold c · Post by **cold c** » Thu Dec 16, 2004 8:36 pm

Rozzer wrote: I suspect you're going to be disappointed. As ahja says, I think its something to do with Midi Device Panels, which don't accept midi cc# from the outside world either.

That's what I thought it was, but it looks like they are talking about remote devices not MIDI devices, as I can't see any way to route a MIDI device map to a VSTi (which could be useful for automating sfz via a gui or similar tasks) and that seems a strange omission.

If someone finds a way to do that please post here.

It loooks like the "new feature" is an old feature that was missing in the initial release.

Cubase SX 3.01 b514 update released