James Brady
Forum Replies Created
-
When our company renames files, we usually leave the original out-of-camera file number as the last part of the name. Have you done this in your example–where “0095” in “Benin2019_0095.MP4” is the original number? If so, you could manually replace the files based on the number …it’s still manual, but at least you’re not working in the dark.
If no part of the original file name has been preserved, then all you have to go by would perhaps be file number order and your memory of which shots you used in the edit. You can leave the new file names, and manually re-link your edited clips to the files… but you’d have to visually confirm each of your replacement choices.
-
Good question. My tests have all been on Windows.
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
resultsvideo.com -
See for yourself:
https://forums.adobe.com/search.jspa?q=2015.3&place=%2Fplaces%2F1383596&depth=ALL
https://forums.creativecow.net/search.php?q=2015.3&f%5B%5D=3
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
resultsvideo.com -
Three weeks into testing Adobe Premiere Pro CC 2015.3 has revealed numerous issues–some are quite literally show-stoppers. Adobe’s Premiere forum is buzzing with similar reports. My advice for anyone employing Premiere in a business environment is to continue using 2015.2 until the next patch/release from Adobe. They’ve been good to us for a long time …they’ll fix it!
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
resultsvideo.com -
Thanks to Zac Lam at the Adobe Forum, I have the solution to the Sapphire problem–no uninstalling, CC Cleaner, or even re-booting necessary:
1) Move the Sapphire Plug-ins folder outside of the Adobe plug-ins folder where it is installed.
2) While holding down the Shift key (Windows), launch Adobe Premiere to clear the plug-in cache.
3) *KEEP HOLDING SHIFT* throughout the entire Adobe Premiere launch process (this was my problem before, I was only doing a “shift-click” to launch and then letting go of the key).
4) Close Adobe Premiere.
5) Move the Sapphire Plug-ins back into the correct plug-ins folder for Adobe.
6) Launch Premiere again, this time without holding the Shift key. The plug-ins re-added should be loaded incrementally into Premiere’s cache and should load successfully.This was a fairly easy way to fix the problem. Oddly, prior to Zac’s suggestion (and before I figured out the holding-shift-for-a-long-time trick), I stumbled on a more difficult workaround whereby if you rename ALL the sapphire effect files to begin with “AE.”, followed by their original filenames, voila! Both Premiere and After Effects recognize all the Sapphire effects. Not sure why that works, but it does!
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
resultsvideo.com -
Duke,
I just read in another post that Red Giant had an update for 2015.3 compatibility.https://www.redgiant.com/blog/2016/06/21/software-update-we-are-ready-for-cc-2015-3/
Hope it works for you!
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
resultsvideo.com -
Thanks, Chris. I’ll be troubleshooting this today so I’ll get back to you on the CC-Cleaner option. I understand that would completely remove the selected Adobe App, in this case Premiere. I’ll probably try some less-intrusive options first. Either way, I’ll keep the thread updated with any progress.
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
resultsvideo.com -
Updated last week and am having two major issues:
1) Adobe Premiere Pro loads all Genarts Sapphire effects plug-ins on the launch screen, but they are not available under the effects tab. It’s like Premiere simply cant find them anywhere (After Effects finds them just fine).2) Also in Adobe Premiere: If I apply Ultra Key to a clip and attempt to adjust the “Contrast” slider, the program monitor and all external video output goes black. Video playback is lost until Premiere is restarted… and lost again if the playhead touches the clip with the Ultra Key plugin.
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
http://www.resultsvideo.com -
I recently stumbled upon this identical thread on another forum. Here, Adobe’s Todd Kopriva states:
“Apple’s H.264 encoder has a severe bug that causes crashes in the encoder when 24 or more threads are used. So, people with computers with a large number of CPUs will hit this bug.”
It’s a 5-month old comment, and there’s not much further discussion, but here’s the link:
https://videohive.net/forums/thread/after-effects-codec-problem-quicktime-h264/138081James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
http://www.resultsvideo.com -
That didn’t work for my workstations. Odd.
James Brady
Senior Editor
Results Video, Inc.
El Paso, Texas
http://www.resultsvideo.com