Steve Pankow
Forum Replies Created
-
Wouldn’t be the first time people have had issues with Avid marketing. Wasn’t Adrenaline touted as being upgradeable?
-
With Avid, you’d import the HD material and check Resize on the import menu. That generates letterboxed SD material. Alternatively, you could create a HD project and export the finished project as SD or change the project settings to SD (I suppose that depends on the system).
While I understand the freedoms afforded by being able to move HD shots around in a SD frame with FCP, I suppose Avid’s argument would be that the shots should have been properly composed in the field rather than fudged in post. If your end product were HD, you wouldn’t be able to do what you’re desiring anyway unless you shot 4K or something.
-
Spoke with Mukesh and tried his idea of uninstalling AMP Font Viewer and deleting the Red .ini without any luck.
Next, I copied the entire Symphony font directory into my Media Composer (only copying in new fonts and not overwriting) and that took care of it. Even reinstalled AMP and there was no conflict with Red. Another bonus is that Red now starts faster.
With the font folder now up to 1,865 fonts and 277MB I figured Photoshop would once again not display all the fonts in its list, but it appears to be holding up for the moment.
Do you have any solution for the LightZoom serial? UPDATE: LightZoom still appears to work in Red standalone, so I guess it’s not needed.
-
Yep. Need a number?
-
Did a remove/reinstall and got back up to 3.0.4 but the problem remains when trying to generate title media. It’s Invalid Menu Handle MenusImp.cpp 65.
Did find out I no longer have the serials for LightZoomFilter.exe and RED3GLFilters.exe though. Any chance of getting those?
-
This is a new problem. And of course after I said it wasn’t a problem locally, the error surfaced. Seems related to any time I attempt to generate title media.
Going to rebuild the font style palettes, reboot and see what happens.
Avid is Media Composer v2.2.10 with Quicktime Pro 7.1.
Only other thing I can think of is that I ran Piriform’s CCleaner. Maybe it nuked something it shouldn’t have.
-
If that’s the “RED3.0.0_3.0.4.exe” file, then we still have it. What info are you curious about getting on my end?
Just to clarify, RED is working fine with locally created projects – I’m in one right now. It’s just this one out on the network that’s acting up.
-
I figured it was a long shot, but I was curious as to what in general the error message was suggesting.
Perhaps it’s related to the fact that the .red project and media live on a Avid Unity share and not on a local host. The Symphony Nitris next door can access this project without issue and it runs the same 3.0.4 version. Only recent change was to delete many fonts off of my system, but as far as I can tell the fonts that the project wants are still on board.
I have yet to see if bringing everything local fixes it, but I rendered out what I needed via the Symphony.
-
I think your only choice is to twirl down into the Transformations track and dink around with the bezier handles on whatever you’re looking to alter. Never had much luck with that myself. I’d kill for an automatic “easy eaze” that makes smooth movements between keyframes. Maybe this exists now as I’m still on ver. 3.
-
Oh, so you mean the tracks on the timeline are part of the transition itself and those probably change all the time. Yeah, if your editors don’t know how to step into FX and relink files, that could be a killer.