Nuendo 4 won't open Cubase 5 files

[Daryl]

OK, so we all know this. I ran into a problem today when a client sent me files, and I didn't know that he had updated to Cubase 5. Nuendo 4 and Cubase 4 won't even open these files.

However, I can open them in Nuendo 3. Why has Steinberg purposely crippled Nuendo 4? This makes no sense to me at all. I know that the much mooted update for Nuendo 4 will open C5 files, but in the meantime, at least I have found a workaround.

D

[RiffWraith]

You can open v5 files in v3?

[Daryl]

You can open v5 files in v3?
It worked in Nuendo 3, but crashed SX3. However, I'm not saying that this won't work, just that I couldn't get it to.

There was information lost (obviously), but as I just needed the MIDI and where the audio files (and video)were supposed to go, it was fine.

D

[RiffWraith]

So, the "no bwds comp" that SB has always maintained, is only to the immediate previous version, but not others? Wierd...

"It worked in Nuendo 3, but crashed SX3."

Not surprised there. That may be a features/plug-in thing.

Cheers.

[MattiasNYC]

I seem to recall a mention that the final version of N4 would open C5 files. Can't remember right now where I read it. Perhaps Gearslutz, or Nuendo.com. Check those two places for statements by one of the SB employees and/or Fredo....

[Daryl]

I seem to recall a mention that the final version of N4 would open C5 files. Can't remember right now where I read it. Perhaps Gearslutz, or Nuendo.com. Check those two places for statements by one of the SB employees and/or Fredo....
Yes that's correct, but what I find interesting is that SB has purposely put something in the code to stop C4 and N4 opening C5 files, because an error message comes up saying that the versions are not compatible. that message didn't program itself, so it was deliberate. therefore, saying backwards compatibility wasn't an option was a lie. SB just want people to upgrade, and are prepared to add unnecessary code to insure that it happens. That's just dishonest.

D

[LEX]

Yes that's correct, but what I find interesting is that SB has purposely put something in the code to stop C4 and N4 opening C5 files, because an error message comes up saying that the versions are not compatible. that message didn't program itself, so it was deliberate. therefore, saying backwards compatibility wasn't an option was a lie. SB just want people to upgrade, and are prepared to add unnecessary code to insure that it happens. That's just dishonest.

D

Nice. Really nice and really deceptive. Well, another reason to side step the whole SB thing anyway.

I mean their new releases barely work to begin with, so you often have to go back to the previous version.

Other than the midi aspect, if this is how they like to treat their users, then.

:098:

LEX

[TerryG]

I just opened the Cubase 5 Shubert demo with Nuendo 3...
No error messages, but there are some differences with the location of the data.

Of course they'll argue that backwards capability is impossible because of new feature data. But, this C5 to N3 test proves that IF they made more of an effort to maintain as much reverse compatibility as possible, issues would be minimized.

[TAFKAT]

However, I can open them in Nuendo 3.

Say What.. ?

Even if its close but not perfect , it means that backward compatibility to some degree is possible ..

I have read that the last N4 update will have some form of seq5 compatibility as well, and rightfully so. What that also hints at is N5 is miles away , so they need something to appease the fallout that more and more are encountering due to their idiotic M.O of leapfrogging..

Its a never ending train crash in slow motion..

[Timo Wildenhain]

Hello,

the next maintenance update of Nuendo 4 will fully support
Cubase 5 files.

Thanks,
Timo

[TAFKAT]

... the next maintenance update of Nuendo 4 will fully support Cubase 5 files.

:clap:

[Audiocave]

In the meantime *.xml files are fully supported and here Cubase 5 *.xml archives transfer perfectly to Cubase 4. Don't have Nuendo 4 but...

... have you tried those?

Obviously, (and unfortunately) those don't include instruments in the instrument rack for some strange reason though.

[Daryl]

In the meantime *.xml files are fully supported and here Cubase 5 *.xml archives transfer perfectly to Cubase 4. Don't have Nuendo 4 but...

... have you tried those?

Obviously, (and unfortunately) those don't include instruments in the instrument rack for some strange reason though.
It wasn't so easy to get anything new over the weekend, and with the time difference it was just as well that Nuendo 3 could open them.

I'll suggest that we test the XML route when we have time.

D

[Audiocave]

It wasn't so easy to get anything new over the weekend, and with the time difference it was just as well that Nuendo 3 could open them.

I'll suggest that we test the XML route when we have time.

D

Cool. If it's all audio and/or audio midi with instrument tracks just shift select all the tracks in the project, export selected tracks, (copy if moving to a different computer, reference if not) and then import that track archive into a blank N4 project set at the same tempo.

It should take all of 5 minutes to find out and should cover just about everything you'll need to pick up the project in N4. I've even loaded C5 xml archives in SX3.1... although going that far back loses some of the translation of plugs etc.

[Timo Wildenhain]

Yes that's correct, but what I find interesting is that SB has purposely put something in the code to stop C4 and N4 opening C5 files, because an error message comes up saying that the versions are not compatible.
D

Hello,

there was nothing "purposely put in the code" to stop opening C5 files, sorry that's nonsense. The only and simple reason is that both C5 and N5 are developed on a new development branch. One reason for that was to make the programs more stable - which was already achieved with C5. And of course, N5 will be able to open C5 files as well. Beforehand, the new N4 update will also be able to open C5 files.

Thanks,
Timo

[Sam]

Hi Timo,

I think he was wondering why N3 could open a C5 session (albeit not perfectly but the edits were right) BUT N4 wont even let you try to see how it goes.....I think it was more that a check was put in place to make sure the app wouldn't open a C5 session and stuff it up - whereas in N3 there was no such check - makes it look a little dodgy though :)

Sam

[Daryl]

Hello,

there was nothing "purposely put in the code" to stop opening C5 files, sorry that's nonsense. The only and simple reason is that both C5 and N5 are developed on a new development branch. One reason for that was to make the programs more stable - which was already achieved with C5. And of course, N5 will be able to open C5 files as well. Beforehand, the new N4 update will also be able to open C5 files.

Thanks,
Timo
So why can N3 open them? Did some code slip into N4 by accident? That's the only conclusion I can come to, if it wasn't put in on purpose.

The fact is that SB have coded an error message for N4, so they must have done this on purpose. I just wonder why?

D

[MattiasNYC]

So why can N3 open them? Did some code slip into N4 by accident? That's the only conclusion I can come to, if it wasn't put in on purpose.

The fact is that SB have coded an error message for N4, so they must have done this on purpose. I just wonder why?

D

You don't know that they "coded an error message for N4". It could simply be that there were some things in N4 from the get go that made it impossible to open a seq5 project, things that didn't exist in seq3. They could have been the result of simply developing new features etc, not as a result of deliberately trying to cripple future import. In order to do this they would have had to think about this when they created seq4, right? So the question is why they'd do that. I really don't think they would have.

And if this was their goal, why then would they now tweak N4 to be able to open C5 files?

[TAFKAT]

So why can N3 open them?

Can't wait to hear the spin on this one..

I'm with you Daryl, if N3 had simply refused the session point blank , then there isn't a case to answer, that it did open it , well at least to some degree is more than a little suspicious and needs to be clarified.

:pop_corn:


And if this was their goal, why then would they now tweak N4 to be able to open C5 files?

You really need clarification on that.. ?

Hows this for some speculation , because they are looking like right royal monkeys again , N5's release is going to have an extended delay due to the resources assigned to the face saving hack and patch of N4 , so while they were at it , they have hacked in the forward compatibility, meaning they could have had that "feature" in all previous if they had really wanted to..

Same Ole , Same Ole.. :willy_nilly:

[Daryl]

You don't know that they "coded an error message for N4". It could simply be that there were some things in N4 from the get go that made it impossible to open a seq5 project, things that didn't exist in seq3. They could have been the result of simply developing new features etc, not as a result of deliberately trying to cripple future import. In order to do this they would have had to think about this when they created seq4, right? So the question is why they'd do that. I really don't think they would have.

And if this was their goal, why then would they now tweak N4 to be able to open C5 files?
Look, if an error message pops up telling me that I can't open a C5.01 file in N4, then someone had to type that message and enter it into the code of N4 on purpose.

D

[John Lance]

Look, if an error message pops up telling me that I can't open a C5.01 file in N4, then someone had to type that message and enter it into the code of N4 on purpose.D

Generic message about unknown file type structure. The header is still there in a sufficiently unaltered format so that basic information can be retrieved, such as the name of the application that created it. That information is dropped into a generic message format that "this app" cannot open "that app" created file.

It is possible that N3 simply couldn't recognize that it cannot completely and properly open the file. Try saving it. I'll bet that C5 project gets corrupted as far as C5 is concerned.

[TAFKAT]

John,

It may well be a generic message of unknown file type, question still begs to be answered how/why N3 recognised it as a known file type, opened the file and allowed Daryl the ability to work with the data.

All of this session compatibility tap dance isn't new..

Anyone here remember the disaster of opening VST 5 files in N3 , whereas N2/SX2 opened them without issue with some minor routing and panning issues. No message of unknown file types, no warnings of possible incapabilities just a total and utter incoherent mess , while SX3 opened the files fine.

In this instance N3 opened the files, while SX3 crashed, its just an inconsistent merry go round , so I am looking forward to hearing Mr Wildenhain's official clarification..

:pop_corn:

[Animus]

Hello,

there was nothing "purposely put in the code" to stop opening C5 files, sorry that's nonsense. The only and simple reason is that both C5 and N5 are developed on a new development branch. One reason for that was to make the programs more stable - which was already achieved with C5. And of course, N5 will be able to open C5 files as well. Beforehand, the new N4 update will also be able to open C5 files.

Thanks,
Timo


That's a good step in the right direction. From now on I highly recomend you guys always maintain compatibility between the programs regardless of the leapfrogging. I think you will have a lot less ill-will and more happiness.