Hi

I just thought I would share my experience with you. After a long series of arguments and denials Steinberg have finally accepted that neither cubase 5.5.3 nor Cubase 6 sends MIDI volumes properly when a project is loaded. This happens on most plugins VST 2.4 and older. Examples of such plugins are Edirol Orchestral HQ, Bossendorfer, Halion 2 and 3, Halion 1, etc... the list goes on. Importantly Halion one is shipped with Cubase 5.5.3 so for this not to work properly suggests a bug to me......?

The telephone conversation went like this:

'No this is not a bug because there is a workaround'....... 'but you have written a DAW which can't even remember what MIDI volume i've set a track to'.......'only on old obsolete plugins'.......'but Halion One shipped with Cu5.5.3'.......'yes but it's obsolete'.....'well it is now, but when Cu5.5.3 was out it was current, so this is a bug'......'it's not a bug because there is a workaround'............. the workaround being that I have to put an automation point in the volume track for it to 'remember'.

My point is this: Steinberg do not want to write a DAW which let's you use any plugins older than about three years. They do not admit it when their software has a bug.....they have fundamentally written a DAW which cannot do the most basic of things.

If you want to see this bug in action:

1) Open up cu5.5.3 on a pc
2) make a new midi track, assign it to a halion one in the instrument track. Record some midi.
3) click the button on the midi track to reveal the volume automation track. Set the volume using the inspector to any arbitrary value.
4) Save then re-open the track.
5) Press play. The track will play at v=100 rather than the value you have set it to.

My advice...... go Protools.....

Oh well I will then.

Joined 4 days ago, 4 posts, 3 of which relate to hacking Cubase

pro tools? no way jose. Good software but i like mine to able to freeze, bounce parts quickly offline and render song offline.

And did anyone ever tell you it's a known fact that pro tools has about only 50 yes 50% of the performance as other major hosts when it comes to using instrument plugins?/

I am sure that's why there is no rtas diva version yet

it is probably impossible to make it run

pro tools will be a contender IMO when those stupid and persistently stubborn shortcomings are addressed.

Confirmed in Cubase Studio 5.5.3.

However, I always use the mixer faders and VST channel automation lanes for volume settings not the midi faders/channels so it's not a problem for me. I'm sure it rains on many a parade though.

Well, it rains until you put up an umbrella .. as in put an automation point.

Someone from PT calling out Cubase MIDI is hysterical or tragic. Not sure which. Maybe both.

Both...

Well, I have Logic, Cubase and ProTools - My Advice.... go OctaMed....

I've used a lot OctaMED, interesting piece of software! (Not kidding)

...
Last edited by geroyannis on Wed Jan 11, 2012 5:48 am; edited 1 time in total

Cubase is fu@king awesome. Just use an automation point, jeez.

Go back to 32-bit? Suuuuuuuuure.

Not to mention everything else that has been said in this thread.

Chris, I understand your frustration at Steinberg. I sold Cubase a while ago, then tried to migrate to Studio One. I had major Steiny issues. Especially as they told me I needed to pay for C4 if i wanted it, as I was like a week over the 'grace' period or whatever jargon they used, and SX3 cost me so much I cannot fathom paying that now... (AH it's all coming back... AAAHH) anyways, When I went and bought C6 (to have compatiability with a friend I write with on occasion), I realised how much I missed it, and sold Studio One that week. To tell you the honest truth, I've had about 3-4 crashes with it so far, out of many long hours punnishing it with all kinds of demanding and buggy plugins, which aint too bad. And most of those crashes were changing patches too quick on third-party plugs...

Long story short, C6 is the shizna in my book. I can't find that flow to MIDI editing anywhere else. BUT, Steiny ain't like your Camel Audios, or your eaReckon friendly cornershop awesome support plugin guy ok. Steiny sucks the biggest balls there are. They could have a warehouse full of shipping containers full of crates full of boxes full of BAGs of balls, and they still couldn't get enough of them to suck. My advice is, if you like the interface, then just take a deep breath, and calmly say to yourself - "f**k you Steiny", and get back to mashing up the frequencies. If you don't like the workflow, then just CAN it and start demoing other trackers... 'cos Steiny aint listening, and you're preaching to the choir here.

Cubase is the bitch you love to hate.

I can just see me in my rocking chair, macbook with logic on my lap, fending off Steinys with my winchester... aaaaah future good times

This is a very minor bug particularly since there is an easy workaround. There are worse bugs in Cubase for them to concentrate on like its inability to close properly...

Inability to close properly? Is the auto-crash function still buggy?

Thanks everyone.

I'm actually gonna have to stick with Cubase as most of my projects were started in 5.1. It just fundamentally annoys me that Steiny point blank refuse to accept that this is a bug which needs fixing. I have to say I have spent literally years dealing with Steinberg bugs and I am now seriously regretting not having switched to Logic 15 years ago. I would have saved tons of time.

Cu5.5.3 is actually fairly bug free compared to previous versions, but just when I thought Steiny had got it's act together (due to being bought by Yamaha) they go and release a version of their software which basically means NONE of my previous songs will load properly without me completely going through every single track adding automation points. Also as most of my plugs are over a year old pretty much half of them don't remember the MIDI volume. I know there is a workaround, but the 'add an automation point' workaround basically 'fixes' the volume of each track so that I can't do a simple tweak of the track volume using my Korg controller as I could in Cu5.1.

What really ticks me off is the utter refusal of Steiny to admit there is a bug. It's like talking to robots. I phoned them and they simply refused to accept that a DAW not remembering MIDI volumes might be a bug. Please note also that even if you press the read button for the track, it still won't send the MIDI volume to the VST unless you actually enter an automation point. This is WROOOOOONG!!!

I like Cubase overall, but I just feel like every time they look like they are going to release a stable version they put in some kind of massive clanger which makes it unusable. At least with other DAW's you know what you're getting. The new lanes behaviour in Cu6 is an example. What an utter shambles.