Eric Jurgenson
Forum Replies Created
-
If shooting progressive was just to achieve a film look (not for graphics elements or layback to film) you should use a standard NTSC (interlaced) preset, perhaps even DV NTSC. The progressive look will be maintained in an interlaced project, and broadcast or DVD use typically require interlaced video.
-
Each timeline (sequence) has a tab that you click on to bring it to the foreground. These tabs are lined up along the top of the sequence window (qabove the timeline). Each tab has the sequence name and a little X to close it.
-
Now what I’m thinking is that you have a corrupt clip. When Premiere opens, it starts a DLL program called ImporterProcessServer, whose job it is to link the project elements to the actual media elements, creating picons, etc. during startup.
If it encounters a file it doesn’t like, it will lock up (crash), especially in CS4 (Adobe really needs to fix this). This will stop the import process, accounting for only some of the clips importing into the project. The remainder remain offline.
You may be able to fix the problem by locating the problem clip. It may be that the last clip to import is the problem, or the next clip in line to import is the problem. I would also suspect any elements that aren’t the same format as the project (sequence) format (DV NTSC, for example). You can try to take everything offline (unlink), restart Premiere, and relink the files you consider safe. Restart Premiere, and make sure the project loads normally. Then start importing the suspect clip(s) one or a few at a time, and restart Premiere, watching for clips not importing properly. Perhaps by using this method, you can identify the problem clip, which could perhaps be recaptured or transcoded with another program.
-
Click the little X on the sequence tab. This closes the sequence, but it remains in your project bin. You can reopen it by double clicking the particular sequence icon you want to open in the bin (list mode, not picon mode). You have to restart Premiere to actually clear out the memory.
-
What version of Premiere are you on? This may be an indexing problem. Premiere has to scan long GOP files to determine the proper frame cadance (called indexing) that it needs to properly edit the files. Not sure where these index files live, but perhaps someone could chime in with a method for making Premiere reindex the clips (maybe by deleting the original index files).
-
Try making the original clip offline, then putting it on the timeline. Then load the MP4 into the source viewer. Right click on the offline clip on the timeline,ad select “replace with clip from source viewer – match frame” (not sure it is worded exactly this way – I’m away from my system). This seems to get around the matching audio tracks issue. I’m not sure if this relinks in the bin or only on the timeline.
-
Another tip: Close the sequence you aren’t working on (and restart your project). This saves memory. Also, make sure “Optimize for memory” is selected in preferences.
-
Sounds like you may have a corrupt project file. I’d start looking at my auto-save projects (in the auto-save folder). Start with the highest number (usually 5), which is the most recent version. (Premiere generates this auto-save backup when it closes). When (if) you find a version you can work with, you will probably want to rename and save it back in the root of your project folder alongside the original version.
Another option that sometimes works with corrupt project files is to create a new project, and import the original project into it. It will show up as a folder in your bin. Open it, and you should see your sequences. Double click the sequence icons (in list mode) to open the timelines.
-
Yeah, Premiere is going through a rough patch right now. Frankly, this is just sloppy code writing – the import and export DLLs should be adequately trapped to prevent crashing at the very least.
I was helping a friend with a Premiere edit the other day on CS2, and it was like coming back to an old friend. Imagine being able to burn a DVD in the actual editing application!
One of my two systems is still on CS3, and I’m keeping it that way for the time being.
There is no question in my mind, though, that Adobe will ultimately fix these issues. I’m not at the point yet where I’m ready to jump ship – too many years invested in Adobe at this point.
-
I don’t know about the registration thing, but your laptop should work for editing HDV. I would recommend obtaining an ExpressCard e-SATA adaptor, and storing all your project files (including captured video) on an e-SATA capable desktop drive. This is much faster than FireWire. Don’t capture video on your system drive.
Also I’m going to guess that Vegas captures can be imported directly into Premiere. Both applications capture HDV natively. But I have not actually tried it.