Timestamp

[cchristensson]

Hi I've got a problem.
The other day I made stems for a movieproject ( it's shot in 25frs) when the mixer imported the stems in protools the timestamps didn't match. When I look at the files timestamps in Dp they match but in protools they differ and when I look in a program like Bwavreader they differ to, on some files they even show a timestamp on frame 27 in a 25frs project. This is the first feature I made with Dp so now I wonder if anyone else have encountered this or if there's something I've done wrong.
Regards
Christer

[MIDI Life Crisis]

You've done nothing wrong...

http://www.motunation.com/forum/viewtop ... =1&t=53722

and this...

http://www.motunation.com/forum/viewtop ... =6&t=53581

So please report this to MOTU and you can refer to my techlink on the issue...

https://www.motu.com/techsupport/tracke ... e_id=80621

Now your fix... sort of.

You can make an OMF but when I did that PT read my files an mono when they were clearly bwav interlaced stereo and we had to manually import them but at least that time they auto-located - but what a disaster. It added about 6 hours extra time in the studio and the producer is none too happy about that, nor is this composer, post audio supervisor.

So you may also want to make an AAF which should work ok (I haven't had access to a PT rig since the last fiasco). Thing is, DP has a history of having either AAF of OMF working, but never seems to get them both working in the same version. This has been an issue in DP since version 5 as far as my experience goes.

This is completely unacceptable for us film and TV guys. SO much so that if it is not fixed in the next update to DP I will be forced to buy a PT setup and I am not the least bit happy about that, but my clients cannot, will not and should not hear "my software has added a few extra days at the mastering house because DP is fouled up (I'd use the other f word but this is a civil site and we like to keep it that way).

Frankly, as unhappy as I am to hear you have this problem, it is comforting to know it is not onlymy system.

Good luck...

BTW... MOTU?

[MIDI Life Crisis]

ps - please post you system specs for comparison.

[doodles]

having exactly same prob here. dp 7.24 OS 10.6.8

very screwy and pretty major bug

[MIDI Life Crisis]

I've always made OMFs and they've been fine. I'm actually wondering about the PT "translator" as the culprit. Seriously, non-native time stamp reading isn't built into PT? Now that's effed up.

[cchristensson]

Thanks for info and I will send a ticket to Motu.
Hope they fix it soon with an update cause it's not what I call acceptable.
MIDI Life crisis asked about my specs:
early 2008 dual 2.8 on os 10.6.8, 16 gb ram.
Regards
Christer

[MIDI Life Crisis]

Do you know if that's a 3,1 Mac? IOW, is it bootable in 64 bit?

[doodles]

Not to do with protools "translator", as editor having same prob pulling bwavs into final cut pro and avid.

[cchristensson]

Yes it's a 3.1 and bootable in 64bits.
Can I make a difference booting in 64?

[MIDI Life Crisis]

If you're in DP8 and your plugs and VIs are all 64 bit compliant, then booting in 64 bit allows fro accessing more RAM. 32 bit apps top out at 4GB. It makes a huge difference on my Mac which is also a 3,1. These are the first Macs to have the ability to boot in 64 bit and thus the first ones capable of running mountain Lion (which is awesome, IMO). But I was asking as I am wondering if the architecture of the machines may be a contributing factor to the timestamp error. Perhaps not in and of itself, but perhaps some flaw in the coding of DP or even Core services that is creating the problem.

Thanks for the info.

[cchristensson]

Thank you for telling me your experience.
I just finished this project, didn't want to try a new os in the middle of it.
Now when it's done I'm planning to try out mountain.
I can't really see how hardware architecture can affect a file from software, but of course in the universe of computers everythings possible so…
I'll send my ticket and see what Motu has to say about it.
CC

[MIDI Life Crisis]

Not necessarily hardware and and of itself (as above) but clearly, different hardware requires different coding, both for the OS as well as the apps. I couldn't code "Hello World" if my life depended on it, so I'm basically pulling this idea out of my ass, but OTOH, since MOTU hasn't found an answer and Avid could care less AFAIK, my perspective is equally as valid... OK, maybe not so much.

[doodles]

LOL MLC!

[cchristensson]