Mark Thompson
Forum Replies Created
-
Tero, thanks. That works
-
Mark Thompson
February 22, 2016 at 6:37 pm in reply to: Quicktime movies suddenly stopped pllaying in PremiereHi,
I had a similar problem on windows. It seems that Premiere has trouble starting up some component of QuickTime (that other nle don’t have). Although its not obvious that a win problem could appear on mac, I would guess it is (due to similar architectures).
My workaround is to look at that media in DaVinci Resolve and then try again in Premiere. If it will work then media browser can view them first, eventually they will play on your timeline. It is as though DaVinci can start he QuickTime component up and then Premiere can use that component.I don’t worry about it any more. The error looks dire, i.e. says you have lost your audio and video tracks, but they do come back before too long.
I don’t know if that will work for you. -
thanks very much for that.
-
this problem has gone away.
It may have been user error.
IT may have been something to do with QuickTime start-up.
Either way things are back to normal. -
Mark Thompson
November 27, 2015 at 2:55 pm in reply to: C100 on premiere Pro CORRECT WORKFLOW – upper or progressive?Hi,
I would conform first so that you edit with everything as close as possible. Even if that means running the clip through premiere in order to align it as close as possible to your other footage. But seek other opinions.Here is a blog post by Matt Davis: https://mattdavis.pro/2013/12/30/canon-c100-psf-the-fix/
I had never heard that Premiere is unstable with MTS.
mark
-
Mark Thompson
November 27, 2015 at 1:58 pm in reply to: Mercury Engine Hardware Accelleration sometimes works, sometimes doesn’t. CC2015.1 GTX670Hi,
I found the exact same problem, I reported it here: https://forums.creativecow.net/thread/3/971432.Someone suggested updating the NVidia driver, someone else suggest reverting to an older one.
I never did find a solution, however it seems to have sorted itself out, on my system at least I seem to have the Engine there most of the time.Even when Premiere could not find CUDA I found that Photoshop and Audition could find it. It is most odd.
-
Mark Thompson
November 27, 2015 at 1:41 pm in reply to: C100 on premiere Pro CORRECT WORKFLOW – upper or progressive?Hi,
I have something for you to try. So take a copy of one of the clips from the C100 and from Media Browser add it to your project. From the project window right click on the clip and select “Interpret Footage”. On that dialog you will have the option to conform it to progressive. Then try your test again and see if it better.So what’s going on? The C100 shoots in a funny format. It is recorded as Progressive (if that is what you selected) but some NLE think it is interlaced. Conforming to Progressive is reported to be the best solution for Premiere.
Once upon a time I would have said the C100 is PsF for progressive segmented format. Google that and allow at least a day for all the discussion. However I understand that PsF is only for HD-SDI, so I’m unsure as to what to correctly call the footage from the C100.
Let us know how you get on and always take a backup of the source clip.
-
I’ve figured this out myself. It is to do with “source patching”.
Make sure source patching is selected for your track. 🙂 -
Mark Thompson
November 5, 2015 at 11:01 pm in reply to: Mercury playback engine unable to find CUDA and then it doesthe upgrade of the driver did no good.
It still seems to take some time to recognize the driver is there.
-
Mark Thompson
November 5, 2015 at 6:43 pm in reply to: Mercury playback engine unable to find CUDA and then it doesDavid,
good point, I think I am release behind.
Actually, there is a newer release than I have 358.87I’ll put that on an try again.
thanks
mark