Brian Rice
Forum Replies Created
-
Does anybody know if this has been fixed? I am in the process of switching over from FCPX to Resolve, but I am currently encountering the exact same issue (with Resolve 15.3). I’ll select all the clips I want to multicam, and it only uses a few of them while leaving the others out, and even with the ones it uses, it’s still out of sync. I had to individually bring in the remaining clips and sync it manually, which was a hassle, but then I decided to just do the multicam in FCPX—which usually nails it every time—them exporting it as an XML. I guess that’s acceptable because it doesn’t take very long, but the point is kind of completely move everything over to Resolve.
-
I can’t find a “No Input” option in Premiere…
-
Just another update:
I did go back to the current version, 9.2, and it seemed fine with an old project that had previously been problematic with playback, but when I began a new project, the choppiness returned, albeit with 4k footage. Now, before you say it’s probably about my system settings etc…I subsequently rolled back to 9.0, and it’s all fine, now. I also reinstalled the latest Cuda driver (7.5.25) and it’s not causing any problems with 9.0 (and when I had it removed, 9.2 was still problematic).
So, the gist of all this is that, for some reason, Premiere CC 2015 9.2 has something buggy that’s causing it to not run properly on my system. I’ll wait and see how 9.3 turns out before upgrading again.
-
Also, I’ve looked at the Preferences/Audio Hardware and I don’t see an option for Default Input, so I can’t even switch that to None…
-
4K footage from a GoPro DJI Inspire 1 drone, and dSLR footage (Nikon D800, D600, and D750). Media is located on my laptop’s solid state drive. But the important thing to understand is that all of this was fine until the cc 2015.2 update in January.
-
Thanks. What I did that seems to have gotten it to work “normally” again was to rollback to CC 2015.0, as well as managing to remove the Cuda driver from my computer. I hadn’t worked on any video since December, but the update to 2015.2 was late January, and I didn’t resume video work until last week when I discovered the issues I discussed (I also added the Cuda driver last month). For the time being, I think I’m content to leave it at that.