Ricky Barrow
Forum Replies Created
-
I had a problem – same issue, I selected one file at a time to load or transcode and found some of the files were corrupt. Everything worked fine on non-corrupted files. Sounds like this may not be your issue but maybe worth looking at.
Ricky
-
My experience = pan & zoom is memory hog – only way to stop and clear trouble is to back out of app and come back in and also render effects even if they are not perfect yet to allow you to work longer before restarting app. Pan/Zoom is a pain in the cache.
Ricky
-
Ahhh, got it.
Ricky
-
Just a small point of clarification – AMA linking option shouldn’t be greyed out, I don’t believe – it should either be available or it should say P2 import options. You may already know that you can enable or disable AMA linking. It may not allow linking as Pat said, based on the source file, but the option itself shouldn’t be greyed out.
Ricky
-
As a test, copy a small MXF file to a folder on your hard drive and try AMA linking to that file and see if it works. I have had 3 things happen when AMA linking failed. 1) Drive on my system cannot be mounted as a “volume” drive (I am on Windows 7) 2) AMA has not worked for me in the past when it had to “navigate” through too many folders to link, such as a “STREAM” folder buried in 6 other folders. 3) make sure you have the correct AMA plugin available on Avid’s download website that matches your file codec.
other than those things, it is over my head – I’m not as experienced as most on here 🙂
Ricky
-
Typically transcoding a file vs. importing is about 1/4 realtime in my experience with ProRes Qt files
Ricky
-
If your version of Avid supports AMA linking, it will be MUCH faster to link to the file and transcode – this does not affect the original file.
Ricky
-
Thank you! This is extremely valuable information for me and explains a LOT. It is all making sense to me now – thank you again, very much!
Ricky
-
This is true about the DNxHD codec, but if QT Player on my computer will not even recognize the file, then it wouldn’t matter on the codec, it is a corrupt file, thus the best explanation so far is that his system is not powerful enough to handle real-time capturing to a file. The only time I have received files from him without error was when using ProRes 422 (LT) which might further explain that his system isn’t powerful enough to process higher res files in real time. I appreciate any feedback as I am still looking for answers. Thanks!
Ricky
-
Nevermind – TY, Found it.
Ricky