Edius 5.51 to Neo 3 and back

[spurfilm]

OK, thanks everyone. That's cleared that on up. All seems very logical to me.

[GrassValley_PS]

There has been some readjustments in some of the alpha handling, so anything involving alpha should be checked.

[Bluetongue]

While there's no guarantee, I believe you're right.

Neo 3.0 and EDIUS 6.0 are the same "foundation" so for the most part it should go.

EDIUS 6.5, however, is new, so unsure.

And as you've discovered, once you go forward to a newer "foundation" it is unlikely to be able to go backward to an older one.

Edius 6 will open project files from 6.5, just drops off the effects not in 6
Works the other way also but some effects seem to need readjusting
Chromakey for one

Regards Barry

[GrassValley_BH]

While there's no guarantee, I believe you're right.

Neo 3.0 and EDIUS 6.0 are the same "foundation" so for the most part it should go.

EDIUS 6.5, however, is new, so unsure.

And as you've discovered, once you go forward to a newer "foundation" it is unlikely to be able to go backward to an older one.

[rob stowell]

No other version of Neo has had edl/aff import/export, and I don't think this has changed in Neo 3 (shame- I'd love that!) But I get the impression Neo WILL open files from Edius, as long as it's the same (or earlier? or JUST earlier?) version. BUT it will strip out all the fx etc that Neo doesn't support- and needs to be in a Neo-compatible format.
Can't check this for Neo 3/Edius 6 yet, as I haven't installed E6. Been waiting for the institutional roll-out of Win 7, but I'm starting to think that's a mistake (it was supposed to be March!)

[GrassValley_BH]

I don't remember if Neo supports EDLs... but that's the current workaround.

From experience I wouldn't hold my breath for any formalized version-specific formats or the ability to save to them.

Then again... other "blue-in-the-face" items have appeared, like the ability to use non-GV/Canopus hardware, so who knows? :)

[rob stowell]

Just to confirm: 5.5 will not open a Neo 3 project- says 'data invalid'.
A great option would be 'save as backwards compatible' ... which would allow a bit of 'back and forth', (and assuming that it would also ditch features).
Most of my work is fairly basic: cuts, audio tweaks, and simple titles.

[spurfilm]

Rob, thank you so much. That would be great.

[rob stowell]

I'll check in the morning, if you're still interested.
I've been using both, and while the changes in Neo 3 haven't been too hard to get my head around, just had a big waste of time around the (obvious) not remembering to select 'between in and out' on export. Grrr- someone flew off without discs, which I will have to mail.
There's a slightly annoying lack of project interchangeability, imho. I liked how I could open Edius 5 projects in Neo, they'd just loose any effects etc Neo didn't have. Now I'm a little worried anything I work on in Neo, I can't go back until I upgrade to 6.

[spurfilm]

Thanks. I guessed this might be so.

[Zorro]

Neo 3 is based on Edius 6. So there's a good chance that you can open a 5.51 project in Neo 3 but you can't go back to 5.51 after you've saved the project in Neo 3.

[spurfilm]

I want to edit on a laptop with Neo 3. Does anyone know if a job created on v5.51 can be opened successfully on Neo 3? The existing job is HDV (as Canopus HQ) 2-channel stereo. No FX or titles. Then, later, I want to open the modified project back in v5.51. I am not sure about cross-compatibility. Will this work?