Dave Fleming
Forum Replies Created
-
OK, I did actually find my old presets. When I try to import them in the export settings dialogue, I get an error “The selected preset is not a valid MPEG2 preset. No exporter found for this preset.”
Any suggestions?
-
Matt, Dave,
Thanks for the responses! Dave nailed it – it was the motion path on the incoming keyframe that had been adjusted that was causing the overshoot/recoil look. I had wasted a fair bit of time poking around the timeline and playing with the keyframes there.
Thanks again,
Dave
-
I did read through that workflow but must admit to being a bit intimidated by all the steps involved.
So, with these two workflows side by side, you see a noticeable quality jump with the longer workflow?
df
-
Thanks Jeff,
This definitely did get me on track. I stuck with 5.5 and was very close with menu room.
You know, I now feel bad about all those one-off DVDs I did using dynamic link “send to Encore.” For all of the convenience that afforded, the final result looked like trash by comparison. Why can’t Adobe handle that downconvert better?
Dave
-
Me too – unless it’s not recent…then I have to dig for it.
df
-
Dale,
Reference the post above with the link to the bug report site:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Maybe if we fill that thing up something will happen!
I, too, have no immediate plans to go to the cloud version.
Dave
-
Hi Kevin,
Yes, the camera is up to date. I’m pretty sure this is a PPro issue. Guess I’ll be waiting on CC…
df
-
Well, a heck of a long time after this original post, but…a few weeks ago I had a EUREKA moment when working with some XDCAM EX 4-channel audio footage that had been “mis-handled” in Windows Explorer. I felt like I owed a follow up to you guys who had responded back then.
I noticed that the file structure of the botched footage in the CLPR folder was “1001_01″, for example. But, correct footage that contains all 4 discreet audio channels was named ” 1001_01″ (notice the 4 blank spaces prior to the file name). So, basically what is happening is that when XDCAM EX files in the CLPR folder get moved with Windows Explorer instead of Sony XDCAM Browser, Windows collapses the file name and removes the 4 blank spaces and you lose your 4 discreet mono channels.
Not to be outdone, my crack IT guy whipped up a batch file that re-inserts the 4 blank spaces in ALL the files names in the CLPR folders (and subfolders). He used the batch file solution since the problem can’t be corrected within a Windows environment, and because there are so many stinking files to correct!
Once he did that, VOILA, the file structure is restored and the 4 mono audio channels return! After all that, all I can say is Take that Sony and Microsoft and your ridiculous proprietary file structure…
-
I would highly recommend Pond 5 for stock footage. They have very affordable footage and were easy to set up a terms agreement with. Plus, there’s a Pond 5 extension that runs within Premiere or Bridge or some such (I guess I don’t use it very much!). I researched all the other stock houses before settling on them.
Dave Fleming
WPTZ -
Thanks for all of your testing. It is very appreciated!
I had sort of suspected early on that having a too small font size would be a problem. So, I stuck to sizes 75 points or larger.
My title word is “EDITORIAL” (in all caps) in a white rectangle. The specific font I was trying to work with is Helvetica Neue Medium Condensed – Heavy at around 100 points. That never worked for me.
I can’t remember all the test fonts I tried, but I remember trying Bank Gothic, which didn’t work. That really sucked, because Helvetica Neue Medium Condensed and Bank Gothic are our two main station fonts.
I tried Adobe Caslon Pro, which worked. My out-of-state buddy suggested than one, since it was an Adobe font! Ironically, it is a heavily serifed font, and so would have more complex shapes than a simple sans serif. Interestingly, Myriad Pro also worked in my system (I’m on a PC). Odd, since that didn’t work on one of your boxes…
But, thank God, I got approval on the Brandon Grotesque version late this afternoon! But, there’s just been so much craziness with this problem that I’m going to submit it as a bug report on Adobe’s site.
Thanks again,
Dave