Steinberg Announces issues with Cubase 7

[SCDBM]

The postman just arrived....... off to install

[tehlord]

So far I know of two people who have installed and iLok1 works fine.


Do continue to shake your pitchforks though.

Edit - 'Legacy' pre 2.4 VST's appear to be fine too.

[JLiRD808]

Originally Posted by teknatronik

I just want to be able to re size my mixer view!!!!! lol

Im kinda confused here...Ive seen comments like this around, but haven't read EVERY word of the C7 features.

Were people saying that you COULD expand/stretch the mixer? Do other DAWs let u do that? I've never thought it was too small, but it would be interesting.

[Lawrence]

Originally Posted by shanabit

This bad logic seems to permeate this place.

I assume you mean the net in general, not just this board.

Logic would be too easy. You know, like waiting for the demo to see if your iLok 1 and your pre VST 2.4 plugs work? That would interrupt the joy of impulse buying and being among the few early people who get to shout...

Yay! I got it!

Frankly, I wouldn't buy (or buy an upgrade of) any software without trying a demo first, unless it was free, then of course, I wouldn't be buying it. "Pre-order" is not in my vocabulary.

[teknatronik]

Originally Posted by JLiRD808

Im kinda confused here...Ive seen comments like this around, but haven't read EVERY word of the C7 features.

Were people saying that you COULD expand/stretch the mixer? Do other DAWs let u do that? I've never thought it was too small, but it would be interesting.

in 6.5 you and change width and extend view, but you cannot change height... It is important for me so I can make the mixer smaller and arrangement 1/3rd the screen so i no longer have to hit f3...

[spiderman]

Originally Posted by sluttypat

Ilok v1 is not compatible with cubase 7. Wtf?

This is a big dealbreaker for me. Goodbye C7.

The spoiled belly-aching that goes on in this vast wasteland of newbies is absurd.

The program has only been available for 1 day.... and is a X.0 release.... If a short list of "known issues" hurts your feelings, please return to mommy's nipple and take a nap before posting your rants.

[nott]

Originally Posted by spiderman

The spoiled belly-aching that goes on in this vast wasteland of newbies is absurd.

The program has only been available for 1 day.... and is a X.0 release.... If a short list of "known issues" hurts your feelings, please return to mommy's nipple and take a nap before posting your rants.

be careful! batman will catch you

[ilter]

"Goodbye C7".

lol

And C7 waves back...

[The dman]

The mixer graphic bug got me. If this happens deselect everything in the "Setup window layout" menu and the mixer will go back to normal

[diogo_c]

^Thanks for posting the workaround!

[teknatronik]

Originally Posted by The dman

The mixer graphic bug got me. If this happens deselect everything in the "Setup window layout" menu and the mixer will go back to normal

I am not understanding what happened.

[albatrossy]

Originally Posted by schmuck

sorry if i missed something or misunderstood - but audio damage is not ilok - so are they supposed to work with cubase 7 or not?

I can see the misunderstanding. I was referring to how the list affected me (the iLok 1 thing didn't phase me). On the bug list, it mentioned that there was something wrong with AudioDamage plugs. Over at KVR, the developer said it was only a minor bug which would be resolved "soon."

[feck]

So I just installed Cubase 7 on my 8 core Intel Mac running 10.7.5. Upon scanning my plugins, the Elysia VST3's crash. So I remove them from the folder thinking it is just a compatibility issue with C7. Then the Vertigo VST3 crashes C7 startup. So I remove it. Then all Abbey Road plugins crash it. So I remove them. Then all the Antares AVOX plugins crash. I am only on the "A"s and can only imagine how many more of my plugins will not scan. I will not continue to remove over half of my plugin collection just so I can boot Cubase 7! What the hell happened with this release? Nuendo 5.5 and Cubase 6.5 have absolutely NO issues with any of these plugins - am I really supposed to not have access to this many of my plugins? Here is hoping for quick fix - releasing a paid version with this sort of compatibility issues is just plain unacceptable.

[shanabit]

Originally Posted by feck

So I just installed Cubase 7 on my 8 core Intel Mac running 10.7.5. Upon scanning my plugins, the Elysia VST3's crash. So I remove them from the folder thinking it is just a compatibility issue with C7. Then the Vertigo VST3 crashes C7 startup. So I remove it. Then all Abbey Road plugins crash it. So I remove them. Then all the Antares AVOX plugins crash. I am only on the "A"s and can only imagine how many more of my plugins will not scan. I will not continue to remove over half of my plugin collection just so I can boot Cubase 7! What the hell happened with this release? Nuendo 5.5 and Cubase 6.5 have absolutely NO issues with any of these plugins - am I really supposed to not have access to this many of my plugins? Here is hoping for quick fix - releasing a paid version with this sort of compatibility issues is just plain unacceptable.

Delete the VST Blacklist pref. or just prefs in general. Its probably pullin them from the 6.5 version

[jmcecil]

[feck]

Originally Posted by shanabit

Delete the VST Blacklist pref. or just prefs in general. Its probably pullin them from the 6.5 version

I can't find them anywhere on OSX 10.7 - they must have moved them from previous OS versions.

[feck]

Aha - stupid OSX 10.7 hides it...

"Since Mac OS X 10.7 (Lion), the user's Library folder is hidden! Here is how to access it: In the menu bar of Mac OS X click on "Go". While the menu is folded out holding down the [ alt ] key (options) will show the "Library" entry.
Rename it (for example to "Cubase 5 hidden") in order to hide it from the sequencer."

[feck]

Deleted Cubase 5,6 and 7 VST prefs and no luck.

[Vdub]

Originally Posted by KorgAddict

You must do what everybody else does. You clone your system and install the new version on it. You check the new stuff and compatibility with your third-party stuff on this system while having the previous version on your main system running great.

Just thinking about what's all going on in apps like Cubase gives me shivers. I don't know how they manage to make it all work.

KA

Can you elaborate on the "clone your system"
I've been looking everywhere to see if i can do it

[ErikG]

Make VERY sure to read this as well:
http://www.steinberg.net/en/support/...0compatibility

[schmuck]

Originally Posted by albatrossy

I can see the misunderstanding. I was referring to how the list affected me (the iLok 1 thing didn't phase me). On the bug list, it mentioned that there was something wrong with AudioDamage plugs. Over at KVR, the developer said it was only a minor bug which would be resolved "soon."

thanks for clearing it up for me. regularly using some audio damage plugs. But I upgraded my HW and 64 bit with cubase 6.5 only relatively recently, and I think I ironed out all the glitches, so will be waiting with the upgrade to cubase 7. But I'll watch closely ;-) =>cheers guys

[Transistor]

Originally Posted by schmuck

sorry if i missed something or misunderstood - but audio damage is not ilok - so are they supposed to work with cubase 7 or not?

According to Mr. AD, Chris R., it's just Kombinat DVA that there are problems with, and they're supposedly already fixed. I have no idea if that means 7.0 or the first maintenance update.

j,

[Sensorychaos]

Here is a bug not listed from steinberg but which seems really specific with my config...
not working on a computer and working on the other....

Unable to get any signal in the new mesurements tools

[kdm]

Most prefs like key commands, templates, etc can simply be copied from the Cubase 6.x folder. On PC it's under Users - (you) - AppData - Roaming - Steinberg - Cubase 6x/7.

Prefs in both are stored in xml files. You can even copy Project Logical Editor presets, generic remote xmls (if you saved it from 6.x - or you can just open 6.x, save it, and copy that to the respective C7 preset/pref folder).

Took me 5 minutes to get my prefs back the way I wanted them. I did have to config part of the Control Room and I/O manually, but most of it actually did carry over. Not sure why the installer doesn't copy over the above, but at least there is a way around it.

[albatrossy]

Originally Posted by Paul in SoCal

Just finished upgrading. Wow, as an upgrade, it's pretty "stupid" in the sense that it's not retrieving any of my 6.5 preferences. I had to reconfigure everything, from the UFX (it default-loaded drivers for the realtek internal audio, I mean, really?) to VST2 paths. Basically it's like the installer is completely oblivious that 6.5 is installed.

For comparison, when I upgraded from Sonar X1 to X2, the installer retrieved ALL settings, down to the most insignificant ones. Evidently windows management is not the only thing Steinberg can learn from Cakewalk.

Weird... I'm on PC and it transferred all of my preferences over. Everything from key commands to my card setup.

[feck]

Originally Posted by Paul in SoCal

Just finished upgrading. Wow, as an upgrade, it's pretty "stupid" in the sense that it's not retrieving any of my 6.5 preferences. I had to reconfigure everything, from the UFX (it default-loaded drivers for the realtek internal audio, I mean, really?) to VST2 paths. Basically it's like the installer is completely oblivious that 6.5 is installed.

For comparison, when I upgraded from Sonar X1 to X2, the installer retrieved ALL settings, down to the most insignificant ones. Evidently windows management is not the only thing Steinberg can learn from Cakewalk.

Agreed - same here on Mac. Had to find the workaround for importing existing key commands, had to re-configure all input/output presets. That's stuff that should be automatically transferred.

[bace]

I like the new features a lot. But this is a beta software. I guess that their marketing decided to sale must be before christmas. This one has so many new features so 2-3 maintenance releases will be required until this is ready.

[Animus]

Originally Posted by feck

Agreed - same here on Mac. Had to find the workaround for importing existing key commands, had to re-configure all input/output presets. That's stuff that should be automatically transferred.

Back in the day i† was always advised to rebuild your preferences in a major upgrade because things could get weird.


Looks like I am just waiting for Nuendo 6, and if and when it gets VCA. Looks like this release was rushed out the door.

[feck]

Originally Posted by Animus

Back in the day i† was always advised to rebuild your preferences in a major upgrade because things could get weird.


Looks like I am just waiting for Nuendo 6, and if and when it gets VCA. Looks like this release was rushed out the door.

It certainly was rushed....I definitely recommend waiting for N6.

[bace]

It was even worse than I expected. The first updates is coming the 19 dec about one month earlier than their plan. I hope that one will be useful...