Final cut pro OMF import wrong time code location

For users of legacy Steinberg Nuendo software
Post Reply
RGEgroup
New Member
Posts: 8
Joined: Mon Dec 27, 2010 7:23 pm
Contact:

Final cut pro OMF import wrong time code location

Post by RGEgroup » Mon Dec 27, 2010 7:47 pm

Hi,
we are running N5 on win7 64 bit with Blackmagic Intesity. in our post facilities we use Final Cut pro for video editing. when we get an OMF file from FCP to the sound rooms we open it using the import OMF option. in the import window we select all media and all audio tracks, and we choose to import it in absolute time in order to get the media in the right place. 01:00:00:00 as usualy. but the media and the tracks are allways imported to the begining of the timeline. i checked that the Final cut timeline is starting at 01:00:00:00 and it is. my time line in N5 is starting in 00:58:00:00.
when i choose to import the OMF to "time code position" all the clips are opened in the correct tracks but they are all in the start of the timeline and not in the right edited order. (i hope you understand me)
after i import the OMF, i checked in the pool and saw that the files are aiff and the original time is 00:00.

we have Pro tools 9 on one PC Win 7 64 bit, and when i import the same OMF file to PT9 it is open in the right TC. as edited by the video editor. this is the reason i suspected Nuendo.

i am sory for my English. i will try to explain my self better if you need.

thank you.
Eyal

psvennevig
Member
Posts: 345
Joined: Wed Dec 15, 2010 11:12 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by psvennevig » Mon Dec 27, 2010 8:36 pm

Hi,

If you do not have a project open when you import the OMF, N5 will create a new project that doesn't start at 0 TC.
It will just start the timeline a bit of time before the imported content. And that's totally ok as long as the imported content is at the correct TC.
If I understood you correct it is?

Try this:
Start N5
Create a new project
Import the OMF, you will now have one hour of free space before the imported content.
Content placed at correct TC?

I do a lot of imports from FinalCut, and have very little problems.

Pål
Nuendo 7.0.x, nMP 8-core with 2xD700, 64GB, Macbook Pro Retina15" i7, RME UFX, RME Babyface, Artist Mix, Control and Transport, CC121.

RGEgroup
New Member
Posts: 8
Joined: Mon Dec 27, 2010 7:23 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by RGEgroup » Mon Dec 27, 2010 10:27 pm

Hi,
thank you for your reply.

i open a blank project from a template i created. the project start at 00:58:00:00. i import the OMF to this project and i do not create a new one. the OMF media should placed at 01:00:00:00 but the media start at the begining of the timeline at 00:58:00:00. and if i place my playhead at 01:00:00:00 and tells nuendo to import the media to " time code position" the media from the OMF all imported to the start of the time line. it is like all the clips are snapped to to start of time line.
tommorrow i will post the pictures to let you understad it better.
can i send you the OMF for you to test it on your system? and can you send me your FCP OMFs for me to try here on my system.

thanx
Eyal

psvennevig
Member
Posts: 345
Joined: Wed Dec 15, 2010 11:12 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by psvennevig » Mon Dec 27, 2010 11:52 pm

You should use "absolute time" when importing.
Can you try with a new empty project, NOT using your template?
What's the result then?

Maybe your template have a TC offset set in the project setup dialog (shift-s)

P
Nuendo 7.0.x, nMP 8-core with 2xD700, 64GB, Macbook Pro Retina15" i7, RME UFX, RME Babyface, Artist Mix, Control and Transport, CC121.

RGEgroup
New Member
Posts: 8
Joined: Mon Dec 27, 2010 7:23 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by RGEgroup » Tue Dec 28, 2010 9:41 am

Ok,
here are the pictures:
1. importing the OMF from FCP to Nuendo without opening a project before importing.
import omf to blank project.jpg
Pic. 1
(121.31 KiB) Downloaded 204 times
2. Nuendo importing the OMF
importing.jpg
Pic. 2
(90.42 KiB) Downloaded 204 times
3. after import at absolute time. with project setup window.
wrong TC absolute.jpg
Pic. 3
(415.63 KiB) Downloaded 204 times
continue in next thread...

RGEgroup
New Member
Posts: 8
Joined: Mon Dec 27, 2010 7:23 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by RGEgroup » Tue Dec 28, 2010 9:52 am

4. after importing at "time code position".
wrong TC at tc pos.jpg
Pic. 4
(418.74 KiB) Downloaded 203 times
5. Pro tools open the same OMF at the right TC.
Pro tools 9 same OMF.jpg
Pic 5
(593.43 KiB) Downloaded 203 times
i think that this is a bug in Nuendo. i can send the omf for you to try on your N5 system.
please steinberg team, resolve this for us.

thanx,
Eyal

titi_fleancu
New Member
Posts: 2
Joined: Fri Dec 17, 2010 10:02 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by titi_fleancu » Wed Jan 05, 2011 12:13 am

Hi,
I'm not in the front of Nuendo now to check, but I think if you have a template already open the importing OMF will go on the cursor position (and start with CH selected if exist). Try to put cursor at the 01:00:00:00 and import OMF with ABSOLUTE TIME select. Good luck!

Dog and Pony
Member
Posts: 408
Joined: Wed Dec 15, 2010 7:33 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by Dog and Pony » Wed Jan 05, 2011 7:25 am

I'm with Eyal, I have never had Nuendo 4.x or Nuendo 5.x open an OMF from FCP at the proper timecode position, I always have to grab the media and move it to the proper start time. John.
5 systems with N7, N8, Cubase 9.5, Nuage, Artist Series, Faderport 16, Windows 10, MacOSX 10.12 and many more toys.

User avatar
Thorsten Marx
Moderator
Posts: 57
Joined: Thu Dec 16, 2010 10:20 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by Thorsten Marx » Fri Jan 07, 2011 1:27 pm

Hi,
it is a bug, and it is fixed with the upcoming Nuendo update.

Best regards,
Thorsten
Thorsten Marx, Product Planning Manager Pro Audio
Steinberg Media Technologies GmbH
Hamburg, Germany

Check out Steinberg on YouTube, Twitter and Facebook!


psvennevig
Member
Posts: 345
Joined: Wed Dec 15, 2010 11:12 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by psvennevig » Fri Jan 07, 2011 2:44 pm

Great!
Nuendo 7.0.x, nMP 8-core with 2xD700, 64GB, Macbook Pro Retina15" i7, RME UFX, RME Babyface, Artist Mix, Control and Transport, CC121.

User avatar
MattiasNYC
Grand Senior Member
Posts: 3666
Joined: Thu Dec 16, 2010 9:27 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by MattiasNYC » Fri Jan 07, 2011 3:37 pm

never mind....
Nuendo 7.1.4 / Lynx TWO-B / Windows 10 Pro 64-bit / Ryzen 1700 3.7GHz (oc) / 16GB Corsair Vengeance DDR4@3200MHz / Nvidia GTX 660 / ASUS x370-A mobo/ 500GB WD Blue system drive / Crucial BX100 250GB SSD media / spinners for library/backup ::::: iZotope RX / Phoenixverb Surround / DaVinci Resolve / Faderport / Applied Acoustics UltraAnalog / my pet pony Frank

Dog and Pony
Member
Posts: 408
Joined: Wed Dec 15, 2010 7:33 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by Dog and Pony » Mon Jan 10, 2011 8:18 pm

Thank you!
5 systems with N7, N8, Cubase 9.5, Nuage, Artist Series, Faderport 16, Windows 10, MacOSX 10.12 and many more toys.

Hugh
Member
Posts: 248
Joined: Wed Dec 15, 2010 8:24 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by Hugh » Mon Jan 10, 2011 10:43 pm

Hello,
Good news indeed.

RGEgroup
New Member
Posts: 8
Joined: Mon Dec 27, 2010 7:23 pm
Contact:

Re: Final cut pro OMF import wrong time code location

Post by RGEgroup » Tue Jan 11, 2011 9:40 am

Hi'
thank you Thorsten Marx for your reply. it is great news for us.
can you tell us when should we expect this upcoming update?
thank you again
Eyal

User avatar
MattiasNYC
Grand Senior Member
Posts: 3666
Joined: Thu Dec 16, 2010 9:27 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by MattiasNYC » Wed Feb 09, 2011 4:08 pm

Thorsten Marx wrote:Hi,
it is a bug, and it is fixed with the upcoming Nuendo update.

Best regards,
Thorsten
Thorsten,

In the "Nuendo_5.1.1_version_history" document it specifically states:

"OMF: Wrong clip positions on import from Apple Final Cut Pro."


1. Was this a different error that was fixed, or is the document incorrect?
2. When will the next update appear?
Nuendo 7.1.4 / Lynx TWO-B / Windows 10 Pro 64-bit / Ryzen 1700 3.7GHz (oc) / 16GB Corsair Vengeance DDR4@3200MHz / Nvidia GTX 660 / ASUS x370-A mobo/ 500GB WD Blue system drive / Crucial BX100 250GB SSD media / spinners for library/backup ::::: iZotope RX / Phoenixverb Surround / DaVinci Resolve / Faderport / Applied Acoustics UltraAnalog / my pet pony Frank

User avatar
MattiasNYC
Grand Senior Member
Posts: 3666
Joined: Thu Dec 16, 2010 9:27 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by MattiasNYC » Mon Feb 14, 2011 11:52 pm

Lydiot wrote:
Thorsten Marx wrote:Hi,
it is a bug, and it is fixed with the upcoming Nuendo update.

Best regards,
Thorsten
Thorsten,

In the "Nuendo_5.1.1_version_history" document it specifically states:

"OMF: Wrong clip positions on import from Apple Final Cut Pro."


1. Was this a different error that was fixed, or is the document incorrect?
2. When will the next update appear?
Hello?..... Is this thing on????>......
Nuendo 7.1.4 / Lynx TWO-B / Windows 10 Pro 64-bit / Ryzen 1700 3.7GHz (oc) / 16GB Corsair Vengeance DDR4@3200MHz / Nvidia GTX 660 / ASUS x370-A mobo/ 500GB WD Blue system drive / Crucial BX100 250GB SSD media / spinners for library/backup ::::: iZotope RX / Phoenixverb Surround / DaVinci Resolve / Faderport / Applied Acoustics UltraAnalog / my pet pony Frank

User avatar
MattiasNYC
Grand Senior Member
Posts: 3666
Joined: Thu Dec 16, 2010 9:27 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by MattiasNYC » Wed Feb 16, 2011 7:17 pm

Considering that OMF/AAF import is essential for a POST daw I would have thought the powers that be would be on top of this and reassure the users asap.

What gives?
Nuendo 7.1.4 / Lynx TWO-B / Windows 10 Pro 64-bit / Ryzen 1700 3.7GHz (oc) / 16GB Corsair Vengeance DDR4@3200MHz / Nvidia GTX 660 / ASUS x370-A mobo/ 500GB WD Blue system drive / Crucial BX100 250GB SSD media / spinners for library/backup ::::: iZotope RX / Phoenixverb Surround / DaVinci Resolve / Faderport / Applied Acoustics UltraAnalog / my pet pony Frank

User avatar
Fredo
External Moderator
Posts: 2450
Joined: Tue Dec 14, 2010 11:20 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by Fredo » Wed Feb 16, 2011 7:46 pm

The bug has been Devtracked with an example OMF and a full description.
The problem occurs (only) when FCP has applied an offset to the project.
So, all is perfectly in place, except for the FCP offset.
Not that this makes it less of a buig though ....

Fredo

User avatar
MattiasNYC
Grand Senior Member
Posts: 3666
Joined: Thu Dec 16, 2010 9:27 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by MattiasNYC » Wed Feb 16, 2011 7:50 pm

Ok, so is this a different bug from which was supposedly and reportedly fixed?
Nuendo 7.1.4 / Lynx TWO-B / Windows 10 Pro 64-bit / Ryzen 1700 3.7GHz (oc) / 16GB Corsair Vengeance DDR4@3200MHz / Nvidia GTX 660 / ASUS x370-A mobo/ 500GB WD Blue system drive / Crucial BX100 250GB SSD media / spinners for library/backup ::::: iZotope RX / Phoenixverb Surround / DaVinci Resolve / Faderport / Applied Acoustics UltraAnalog / my pet pony Frank

User avatar
Fredo
External Moderator
Posts: 2450
Joined: Tue Dec 14, 2010 11:20 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by Fredo » Wed Feb 16, 2011 10:06 pm

It looks like it that there were two issues, of which one masked the other one.
And only the the one was fixed.

Fredo

User avatar
MattiasNYC
Grand Senior Member
Posts: 3666
Joined: Thu Dec 16, 2010 9:27 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by MattiasNYC » Fri Feb 18, 2011 12:52 am

Ok. Thanks for your answer Fredo (though I was hoping official employees would respond). I guess I'll keep on waiting before I upgrade to v5 then.

It's really irritating that a bug that amounts to:

"OMF: Wrong clip positions on import from Apple Final Cut Pro."

Is apparently fixed, only to unmask a bug that amounts to:

"OMF: Wrong clip positions on import from Apple Final Cut Pro."

And that the version history document then says that a bug that amounted to:

"OMF: Wrong clip positions on import from Apple Final Cut Pro."

has been fixed. It gives the user and prospective buyer (me) the impression that everything is hunky-dory, when, in fact, it appears not to be......


PS. You already pointed out that perhaps beta testing wasn't the issue, so the only thing that remains a problem then in my opinion - as if it isn't clear enough above - is how one can insinuate that an issue is resolved when it appears not to be. To the end-user it doesn't matter if the original problem has been fixed if there's a "hidden issue" behind that results in essentially the same outcome, right?.....
Nuendo 7.1.4 / Lynx TWO-B / Windows 10 Pro 64-bit / Ryzen 1700 3.7GHz (oc) / 16GB Corsair Vengeance DDR4@3200MHz / Nvidia GTX 660 / ASUS x370-A mobo/ 500GB WD Blue system drive / Crucial BX100 250GB SSD media / spinners for library/backup ::::: iZotope RX / Phoenixverb Surround / DaVinci Resolve / Faderport / Applied Acoustics UltraAnalog / my pet pony Frank

User avatar
Fredo
External Moderator
Posts: 2450
Joined: Tue Dec 14, 2010 11:20 am
Contact:

Re: Final cut pro OMF import wrong time code location

Post by Fredo » Fri Feb 18, 2011 8:52 am

What might have happened is following:

-Bug is reported: "OMF: Wrong clip positions on import from Apple Final Cut Pro."
-OMF (without offset) is provided which repro's the problem.
-OMF is analised, fixed and tested with that very same OMF

===>>>> bug is flagged" fixed" and passes through QA after testing with this OMF and other test OMF's.

-Bug is reported: "OMF: Wrong clip positions on import from Apple Final Cut Pro."
-OMF (with offset) is provided which repro's the problem.


The problem here is that OMF is a moving target. It started with ProTools which has introduced a bunch of dialects into their own OMF protocol, which made that all other applications needed to "search" how these dialects were working. At this moment, every application -including Nuendo- has more dialects written into their OMF specs than documented specs, which means that the slightest difference, the slightest change wiil probably break something else.

Fortunately for everybody, ProTools has kinda stopped this strategy of making OMF a moving target for the competition, but nevertheless it still is anything but exact science. In other words, it might very well be that with the next FCP or Avid update, other problems surface. I just had a problem with an OMF from FCP where the editor used files with different bit depths, which resulted in half od the files being distorted after export. Same as with files from an Avid mediacomposer where EQ or another effect is applied, these also result in distortion. Something that is not a problem with OMF files coming from Final Cut. And so on, and so on ...


Fredo

Post Reply

Return to “Older Nuendo versions”

Who is online

Users browsing this forum: No registered users and 2 guests