C 5.0.1 maintenance update is out.

[The Guru]

:piss2:

[TAFKAT]

Hey Nate,

Brian announced it here earlier as well.. :-)

So who's going to be the first to check out the automation, solo mute , video truncation .. :eusa_whistle:

Read some reports over at c.net that REVerence is greatly improved..:clap:

[zvenx]

is solo/mute and automation fixed?
I do nt' see that in the pdf...
or am I going blind?
rsp

[shanabit]

Id like to see them name the updates BP1, BP2 etc for Bug Patch, has a better ring to it

Unless Im blind , I dont see the SOLO /MUTE issue fixed

ftp://ftp.steinberg.net/Download/Cubase_5/5.0.1.147/Cubase_5.0.1_Version_History.pdf

[MattiasNYC]

If I'm not mistaken, and I could be, SB said that Cubase would get new features and some fixes, then Cubase update, then Nuendo 4 would get an update with fixes, and finally Nuendo 5.

So this of course means Cubase users will have to live with the solo/mute issue and mpg truncation a lot longer than Nuendo users.

I think that was the point...

[shanabit]

What Steiny says is NEVER concrete by any means. I remember the SX3 final drop, DX drop without warning, things like that

Allow me to interpret Steiny for ya here. What this means is the bug will still be there in C6 and then theyll promise to fix it in that cycle.

Im staying at the end of the cycle with this app

[Michael Tibes]

Anyone tried it, how's it working out?

I gave it a shot last night and it rendered my C5 useless, weird graphic issues and stuff. I assume something went wrong here, it couldn't have passed any betatesting like that (not even Steinbergs). I wonder what I might have missed...

Michael

[Heuristic]

Anyone tried it, how's it working out?

I gave it a shot last night and it rendered my C5 useless, weird graphic issues and stuff. I assume something went wrong here, it couldn't have passed any betatesting like that (not even Steinbergs). I wonder what I might have missed...

Michael

Went fairly well for me until I called reverence up in one of my mixes.. crashed me out.... Chris B at the other place suggested trashing my prefs, as it does not seem to happen in new projects... no time until next week to try, so we'll see! I don't do GA or LM, so not sure how that's working for others. When Reverence did work, the latency issue was greatly improved. Might actually make it useful!

[D]

Anyone tried it, how's it working out?

I gave it a shot last night and it rendered my C5 useless, weird graphic issues and stuff. I assume something went wrong here, it couldn't have passed any betatesting like that (not even Steinbergs). I wonder what I might have missed...

Michael

You have my condolences.:eusa_wall:

[leggy]

I tried it today for the first time. Very unstable compared to N4. Loads of crashes. Oh dear :(

[TAFKAT]

Not sounding too promising,

I was about to do another round of scaling shootouts using SONAR 8.3, v C5.01, v Reaper 3.0 BETA..

I'll give it a run up and report back

[RiffWraith]

Automation: fixed.

Solo/mute bug: will be fixed by the end of the year - CB

Runs fine - identical to 501, actually.

Hey Bri - if you are reading this, who to address, re: the export audio mixdown window changed functionality, to try and get it back to the way it was? Currently it's, well, a PITA.

Thanks!

[ibmcgovern]

Jeff:

The audio mix-down is pretty straightforward, in my opinion and is still similar to the previous. You will only go into Channel Export mode if you tell it to. What about it exactly causes you concern?

[RiffWraith]

Hey Brian - thanks for the quick response.

The functionality has changed drastically. Well, at least on the user side of things.

C4:

Open export window
Type file name
Hit enter 2x; mixdown begins. *

C5:

Open export window
Hit tab four times to get to the name field
Type file name
Hit enter 2x; window closes; mixdown does not begin

C5 again:

Open export window
Hit tab four times to get to the name field
Type file name
Hit tab sixteen times to get the export button
Hit enter; mixdown begins.

So, the new code/functionality is basically forcing the end user to grab the mouse, release it, go for the kbd, grab the mouse, release it, go for the kbd.

I was hoping to kindly and lovingly :eusa_angel: inject a little common sense into whoever is responsible for this, and try to convince them that the old behaviour is much more user freindly, and the new behaviour is a workflow killer and counterproductive.

Hopefully that explains it; if you need anything else from my end, please ask.

Thank you!

*First enter takes the focus off of the name field; 2nd activates <export>

[TAFKAT]

Automation: fixed.

Fixed as in they returned the functionality of C4 , or fixed as in they actually implemented all of the required fill modes to the new automation ?

First option means they simply hacked the old behavior back in, and the new control panel is simply window dressing and has no correlation to the improved automation of Nuendo , or option 2 , they actually "fixed" the new automation..

[RiffWraith]

Fixed as in they returned the functionality of C4 , or fixed as in they actually implemented all of the required fill modes to the new automation ?

First option means they simply hacked the old behavior back in, and the new control panel is simply window dressing and has no correlation to the improved automation of Nuendo , or option 2 , they actually "fixed" the new automation..

Good Q/points there.

ATP, I would have to say they hacked the old behavior back in. I have not delved deeply into it here, but knowing SB the way I do, and knowing that they are/were concentrating on other things, and knowing that they probably still want to keep an automation difference between N and C, even w/o checking - I really don't think they actually implemented all of the required fill modes to the new automation.

But while I have your atten-HUT! :ninja: - what should I look for here to do a thorough check?

[shanabit]

Hey, Ive figured it out finally. Im going to WAIT till the END of the C5 cycle to upgrade/update things. 4.5.2 is running fine here

[OpenMind]

Hey, Ive figured it out finally. Im going to WAIT till the END of the C5 cycle to upgrade/update things. 4.5.2 is running fine here
+1 ... And I might even wait untill the end of the C6 or C7 cycle as C5 doesn't add any interesting new options that I didn't have already.

[shanabit]

I've said it before. If I can't make music with the tools I have then I should just give it all up and take up basket weaving.


Basket weaving doesnt pay now, unemployment for a minute maybe

I have two brother-in-laws and three sister-in-laws jobless in the basket weaving thing. Longaberger Baskets

[Sound Drifter]

Even though I'm not welcome "over there", I still read all the posts. What I noticed with this update is that the people that used to find all of the bugs aren't there any more for whatever reason. The number of issues that have been reported doesn't represent the complete picture, IMHO, because of that fact. To me, this says there will me many issues overlooked in the release. Steinberg have shot themselves in the foot and the repercussions are just beginning.\

I've said it before. If I can't make music with the tools I have then I should just give it all up and take up basket weaving.

I can't speak for anyone else, but I've been using C5 every day for the past month or so. I don't think I've had one crash. I'm a little leery to install the update because I'm in the middle of projects. I don't think I even downloaded it yet. I dunno... Maybe it's solid for a lot of people or they don't want to feck with a stable system. I did the release info for the fixes and was like, we waited that long..... for what. Disappointed after reading the release info I thought: why chance it.

[Sound Drifter]

Oh, it is Spring too. A lot of forums get tumbleweeds this time of year.

Or Steinberg drove the peeps away.

[dada]

Oh, it is Spring too. A lot of forums get tumbleweeds this time of year.
Or Steinberg drove the peeps away.
Probably the later ...
After years of fighting, to improve the app,
They made me realize that it's just wasted time.

First of all : demanding users are treated like unwanted children ( or worse ).
2nd : There are simply no resources, to fix all the major issues,
that only affect a smaller number of users ( Minority Issues ).
3rd : their priority system for fixing issues is completely screwed, IMHO.
( 'dangerous' fixes, like solo/mute and db-law flaw, are delayed for years ... )

So there's no point in going into details.
Just find workarounds or move on.

Nevertheless, I'm still reporting things, every now and then.
But with minimum use of time and energy ...

V5 did well, so far. Only took me a day, to programm all needed workarounds ...
And yes, it's definitely not made for users with two soundcards, external FX and different setups for one of the soundcards.

Will install 5.01 now. ( fingers crossed )

bye, Jan

[Sid Chigger]

I've got C5 @ the studio and here at home.. I use the home system as the "test" PC.. I loaded the 5.0.1 and the install went off without a hitch. When I launched the program it hung.. Splash screen showed it hung initializing B4.. 15 minutes.. ctrl-alt-del end process... Relaunch.. got past B4 and hung on Sampletank... ctrl-alt-del end process.. Relaunch.. Got all the way to initializing Content (the last thing I see before the program opens) and it sat there maybe 4 minutes? Then opened.. Putzed around some in a project, closed and exited.. Relaunched and opened with no hiccups or slowdowns... Reverence seems to be way better optimized..

Installed on the Studio PC yesterday with ZERO problems.. First launch after the update it initialized all my plugs and vsti's but no hangups... Worked in various projects for over 5 hours, with no probs..

SC

[TAFKAT]

Hey Sid,

Whats the difference in the configurations between the home and studio systems ?

Are the same plugs installed ?

[Sid Chigger]

Hi Vin

Home: Basic Dell Core 2 Duo 2.8ghz, XP Pro, 2GB Ram, 1 UAD2 Duo, 2 UAD1's

Studio: AMD 4400, A8V, 2GB Ram, XP Pro, 4 UAD1's..

Vsti's are the same in both.. Latest UAD versions in both..

[norbury brook]

Done my last two projects in Cubase 5,no problems,very stable,no crashes just annoying little GUI things that have been fixed according to the update.

This is on a newly built Xp sp3 machine, Q6600 @3.6 ghz,4 gigs ram,UAD-2,UAD -1,SSL Duende PCIe,POCO pci, 2x MR816's etc etc

Had a terrible time on OSX and reverted back to windows,the sun's shone ever since :D


Marcus

[paulwr]

+1 ... And I might even wait untill the end of the C6 or C7 cycle as C5 doesn't add any interesting new options that I didn't have already.

The vst expression looks like it would be very valuable, at least for orchestral composing/orchestrating. The plug-oriented stuff........ I haven't yet jumped on any new version of anything just to gain a plug or two.

Maybe sometime before the end of the year for me. We'll see.....

-Paul

[Animus]

Yes, I am looking forward to VST Expression myself. Does anyone know if you can assign your own articulations with it or does the vsti have to support it?

[paulwr]

Much of it is like keyswitching, I believe. But you get to names the choices that show up in the lane under the note grid. I know there's more, but that is part of it.

-Paul

[Home Studio 87]

Yes U can Have VST Expression With Your libray (I've made some for the EWQLSO Gold) just need key switch or Program Change or even More :
I can now have multiple midi channel on "Instrument Track" (not playing together but 1 by1 That's very usefull with virtual guitarist when U want multiple styles but one sound !)