Paul Donahue
Forum Replies Created
-
Thanks. 90% width and height I believe is the action safe area, is it not?
-
Paul Donahue
August 25, 2015 at 1:34 pm in reply to: Exception: failed to get the sample temporal offset from the AMA Plug-in messageHi Aynsley,
The advice I received on the Avid Forum was not to use AMA, but to use LINK and then transcode/consolidate the footage. I also received advice that I should link directly to folders, not to individual MXF clips.
I ended up transcoding the sequence, deleting the corrupt clips, linking to them and working them back into bins, and was able to complete editing the film.
I hope this helps.
Paul
Paul Donahue
Media Eye
vimeo.com/pauldonahue/videos -
Paul Donahue
November 19, 2014 at 7:38 pm in reply to: AMA Plugin Error Message Causing Avid MC 8.1.0 to constantly crashHi Hadas,
I did receive some assistance on the Avid forum, such as:
when AMA linking your footage, bring the footage in as folders, not individual MXF files
after you have your AMA link footage in, transcode it all to DNxHD 185. this way your footage is already all transcoded and you can edit, color correct then export without any problems
I ended up moving the entire project to a Promise Pegasus hard drive form the Lacie Rugged hard drive, then transcoded the sequence I was working on in a separate bin, after duplicating the sequence, and working with that version. This basically worked. I have started to think that the Lacie cannot handle full HD footage so well and will use that drive just as an archival backup drive
The next project I do I will do AMA link to the folders rather than to individual files and see if this does away with the issue.
I had a very curious thing happen which was that footage shot on different days, which was stored in separate bins, started appearing in other bins, replacing the footage that was there. I am hoping that linking to folders will prevent this.
Robert, I looked for your post dealing with Resolve on the Avid Forum and couldn’t find it.
Paul
Paul Donahue
Media Eye
vimeo.com/pauldonahue/videos -
This has now worked out fine. What I did was to export a QT reference file, import then into Squeeze and then applied the Preset. Everything worked fine without an error message.
Paul Donahue
Media Eye
http://www.mediaeyemedia.com -
Hi,
I am using 6.5.2 and am also just getting a black screen when I export a QT reference file. Any suggestions?
Paul
Paul Donahue
Media Eye
http://www.mediaeyemedia.com -
Hi,
It has exported to Squeeze ok, but whenever I encode it and send it out of Squeeze for some reason it always cuts off the end of the video. Do you have any idea why this would be happening?
Paul
Paul Donahue
Media Eye
http://www.mediaeyemedia.com -
Hi,
It has worked after the mixdown. Thanks for the advice!
Paul
Paul Donahue
Media Eye
http://www.mediaeyemedia.com -
Hi, I haven’t done a video mixdown and will do this and export it again.
Sincerely,
Paul
Paul Donahue
Media Eye
http://www.mediaeyemedia.com -
Paul Donahue
October 25, 2013 at 11:26 am in reply to: the edit rate of the clip (50.000000) does not match the project edit rate site (25.000000)Hi,
Thanks for this advice. That explains perfectly what I would like to do.
Sincerely,
Paul
Paul Donahue
Media Eye
http://www.mediaeyemedia.com -
Paul Donahue
October 24, 2013 at 8:40 pm in reply to: the edit rate of the clip (50.000000) does not match the project edit rate site (25.000000)i’ve now opened up a new project and i can choose 720/50. Thanks!
Paul
Paul Donahue
Media Eye
http://www.mediaeyemedia.com