Daniel Frome
1
COW Coin
Forum Replies Created
-
Avid on MAC had not had working V-sync nor “expand luminance range for computer displays” in OSX lion. I was under the impression that this was not a Windows issue at all, so I am a little stumped.
-
You can import SWF files into After Effects or Premiere Pro. From there just render out a DNxHD quicktime and put it into Avid.
-
Are you talking about “next edit” with trim mode on a specific track? Or do you just want to be able to move the playhead to the next edit regardless of what track the edit takes place on?
-
I am not a software engineer, but I do know that many of Avid’s transcoding functions don’t max out all CPU cores like some other software. However, with DNxHD it should be possible. Example: doing a video mixdown inside Avid with DNxHD uses about 70% of my total CPU power (8 core xeon). So… nearly all my cores are being used, just not maxing them out.
I’ve done transcoding tests on several codecs, and the strange thing is that while DNxHD doesn’t use as much CPU power, it often still completes faster than other codecs which do utilize my cores. What I’m trying to say is that CPU usage and transcode time do not have a linear relationship.
-
[Bouke Vahl] “were one frame longer than the AMA ones…”
Well, funny enough that was exactly the issue that I reported to Avid (and they confirmed it) — that AMA clips are sometimes cut off 1 frame short. I’ve mostly seen this with audio, but have heard reports about some quicktime files as well.
Not necessarily related but eerily similar…
-
Nope.
-
I run mc6 and pt9 on the same system. Mc6 is just a serial number and Protools is dongled. Works fine.
-
Can you do me a favor please:
Import one of your MKIII files WITHOUT AMA into whatever flavor of DNxHD. Then AMA link the H264 file. Check to see if the timecode start and end is identical.I mention this because I recently reported a bug to Avid where I encountered inconsistencies between timecode of quicktime AMA’d clips and their MXF counterparts.
As a second note: I do remember that a recent Premiere Pro update (6.01 or something) said that they had addressed some incorrect timecode issues with the 5D Mark III. So… maybe it’s Canon’s problem after all and Adobe simply put a band-aid fix on it… not sure. Please report back.
-
Hmm, well I can’t speak for this other editor or the surrounding circomstances, but I’ve done this many from working in the animation industry.
That being said, I would have fired up ProTools most likely since it fits the job better.
Edit: Doh, I think you’re right about MC6. Well then…protools it is!
-
Sucky situation to be in. Feel free to export an AAF anyways and ask one of your fellow Avid/Protools editors (including me) to convert to OMF for you. Avid or Protools can both do this.