Jonas Bendsen
5
COW Coins
5
Premiere Pro Coins
Forum Replies Created
-
The response I received from Adobe over at their boards was basically “don’t worry about it.” Pretty great, huh?
[eye roll]
The error is basically left over from testing before release, and while “Droverlord” sounds incredible menacing, it’s just a name they gave a common error for quick identifying.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit… -
Using the “external file” method we finally got the OMF opened in ProTools today (AAF out of Premiere into ProTools was a no go). There were a few clips that ProTools couldn’t figure out how to hook up, but for the most part it was good.
So while we got the external media OMF working, I’m still wondering why I can’t generate an “encapsulated” OMF.
Frustrating.
Thanks for testing for me, Pentti.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit… -
Note that you can set “scale to frame size” in your preferences menu, so you don’t have to click it for each clip each time you bring one in. You can also select multiple clips (i.e. all the clips in a sequence) and do the “scale to frame size” in one right-click command.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit… -
You shouldn’t need to mess with the RED file source settings at all. Premiere is always going from the original RED source, and will resize from within the program, depending upon how you set up your sequence and if you right-click “scale to framesize” on your clips.
We probably need a little more information, but if your sequence is set up correctly, the first thing I’d check is whether or not your Program Monitor is set to “fit” in the size/zoom drop down (magnification). That’s really the only setting other that’s going to change the size of what you see. If it is set to fit, and you click “scale to framesize” in your right-click menu from any clip in your RED formatted sequence, it should show correctly.
You should also be running the RED plug-in on CS4.1 (I realize this could be a stupid statement, but better to cover all bases than overlook the obvious).
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit… -
Yep, that’s why I put the phrase, “(not even the original, untrimmed audio file)” in the part about the single clip, but thanks for checking to see if that could be it.
I’ve tried exporting AAF instead of OMF now, so I’ll find out later today if ProTools will deal with that format. Fingers crossed.
I’d still like to know why Adobe Premiere Pro is showing this “2 Gig” error no matter how big the project is. I even tried creating a new project with just one small audio file, and I still got the 2GB error on OMF export.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit… -
Just got the same thing working in Premiere CS4.1, but it brought up a Windows Taskbar Tab that said “DroverLord – TabPanel Window” and then froze and crashed.
WTF?
I thought it was some sort of malware or virus, but this is a clean (legitimate) version of Adobe Creative Suite Production Premium 4 and I’ve run several anti-virus and malware sweeps and nothing was found.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit… -
A couple of the posts in this thread aren’t legible, but the subject is important information, so hopefully the thread stays alive until an answer is found. I’m having the same problem right now, but it has to do with trying to author a DVD with 24p (23.976) footage.
I have no trouble creating a DVD with my footage when I export at 29.97 using Premiere’s MPEG-2DVD preset. However, when I try to export at 24p, I get the “gap” error in Encore.
I think this has something to do with flag frames? Perhaps the GOP settings need to be changed (though I tried changing my “N frames” to 12 (a multiple of 24) and it didn’t do me any good –but I wasn’t really sure what I was doing)?
Anybody with some information as to how to correct the “gap” error, please chime in!
Thanks.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit… -
When encoding to 23.976 out of Premiere (so Encore isn’t doing the transcoding), most often I get errors stating that there must be a space of “0” or greater than “0.4” in the time line. I think this has something to do with flag frames? I haven’t hammered out the kinks yet, but from poking around on the web, there seem to be ways to make this work.
Just be aware that you have to do some tweaking to get 24p to work correctly with authoring a DVD in Encore. DVD’s have to be 29.97fps, and then “magic” happens with the decoder (your DVD player) to make the DVD display 24p.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit… -
The answer is actually “yes.” As long as the only thing that’s changed with the clip name is the “.mov” you can use any text editor with “find/replace” functionality.
Open the Premiere project file with your text editor (or Adobe Dreamweaver for added ease) (the Premiere file is in XML format) and do a “replace” with “.mov” in the find field and “[whatever the file extension should be]” in the replace field.
You should be good to go. I do this all the time going back and forth between FCP and Premiere, changing the .mov extension (Final Cut proxies) to .r3d (original RED).
DON’T FORGET to back up your original Project file in case you screw something up editing it at the code level.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit… -
I’m experiencing a similar problem cutting a trailer.
I’ve got some .aif files that simply won’t play in a sequence (they scrub, and with ours they actually do play in the source pane. The weird part is, if I drag them to a different sequence, they work just fine.
I’m wondering if this might be the case with your scenario as well?
I would just create a new sequence, drag the audio files into that sequence, and be done with it, but the files won’t play in the current sequence or a newly created one. They only play in “already created” sequences.
Very strange.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit…