Jeff Bellune
Forum Replies Created
-
NTSC is also lower-field first for DV and DVD.
-Jeff
-
Have you tried the Draft Quality setting in the Program panel’s wing menu?
Also, the longer the length of the DL clip, the slower it will perform. Consider what you have available when you RAM preview in AE.
-Jeff
-
If you are exporting from AA as a QT reference movie, try a self-contained quicktime. You said you tried “other formats”, but you didn’t specifically mention QT.
PS – I estimate your chance of success using my suggestion at about 5% – 10%.
If you haven’t done so already, I recommend spending as much time tweaking project and export settings in Avid as you have in Premiere.
-Jeff
-
Tim,
IMHO, until you figure out why PPro 1.5 is misbehaving on your client’s system, don’t even think about upgrading. Your experience with PPro so far is rare. Not completely unheard of, but very rare. In most cases, hardware/software conflicts are responsible for the problems, and in some cases, operator error. There are times when the conflicts are not resolvable, and changing systems and/or software is the only solution.
Until you pin down exactly what’s going on with Premiere and your client’s system, upgrading may be futile. You don’t want to push the upgrade only to find that the same conflicts that existed in 1.x also affect 2.0.
-Jeff
-
See my response to your other post.
-
I’m not familiar with the output format/codec of the Miranda box, so I’ll start with some general Premiere-type troubleshooting tips based on the info you’ve given.
1. Make sure the codec used to create the video files for use in PPro does not temporally compress the video. No DivX, MPEG, etc. Higher-end codecs like DVCPro 50 are not native to PPro, so if they are not available to Premiere at the system level or as a plugin then you will have problems.
2. Make sure your project settings in Premiere match the properties of your source video. If you need, say, web output from DV sources, then set up a DV project and output for web when you export.
3. Kill all background processes and other applications that could interfere with PPro’s access to memory or disk. Packet-writing software, media players, live virus scanners and the like could be problems. Other graphics or fx apps shouldn’t be a problem. Emphasize “shouldn’t”.
4. Consider length of program. If you’re trying to work with 2+ hours of source video and effects at the same time then there may be memory management issues with PPro. Try breaking up the project into smaller projects (not just different sequences within a single project) or cut down on the number of effects in use at one time.
5. Third-party plugins. Make sure they are all compatible. Check with the vendor’s web site and/or support channels.
6. Windows hard disk settings. Start>My Computer>View System Information>Hardware>Device Manager>Disk Drives. Double-click each drive in turn. For each drive, select the Policies tab and put a check next to Enable write caching on the disk. This will seriously improve drive I/O performance and should improve Premiere’s stability. The warning associated with this setting should be heeded – use a UPS and make sure a recent disk image has been created for backup purposes. However, don’t let this warning scare you. Power outages and equipment (hardware) failures are rare, and reliable power supplies and good backups are essential in any computing environment.
7. An abundant resource for all things Premiere is the Premiere Pro Wiki.
That should keep you busy for a while. 🙂
-Jeff
-
You’re welcome. I forgot to ask you in my first response – did you try burning a test RW disc (or an R disc) and see how the menu –> timeline transition worked in a finished disc? If you were only using Encore’s preview before it might be worth re-creating your old transition to see how your hardware/software players handle menu –> timeline.
-Jeff
-
You’re welcome. I was glad to help.
-Jeff
-
I just quickly created 3 Test buttons. They all said “Test”. Now when its in Encore and I preview it the “T” is lined up perfect and the “e” is close but when you look at the “s” and last “t” it is off and looks like a drop shadow because it is slightly off.
I need to test your issue on my system a bit more to see if I can duplicate exactly what you are experiencing. While you wait for me to do that (if you want to wait :-)), I have to ask one question:
On your test menu, did you animate at all in AE? Or just bring it directly to Encore from PS? If you are seeing mis-aligned layers when you bring the menu straight to Encore from PS, then something is wrong in Photoshop. I just duplicated your test menu in PS7 and Encore 2.0 without animating in AE and it worked correctly.
Also, in Encore, try hiding the text layer on your real menu by poking out the eyeball instead of deleting the text layer. I don’t think this will fix the problem, but it is one less variable to consider.
I’m trying to recreate this issue using my own assets. This may go faster if you can email me a copy of the PS menu. My web site is listed in my profile, and the site has a contact email address at the bottom of the home page.
-Jeff
-
1. If you are using the 1.0 version of Encore, update free to 1.01. I think the 1.01 update fixed this issue.
2. Make sure you buld your menu in Photoshop on a 720×534 canvas. PS7 uses square pixels. Likely the frame grab from Premiere was 720×4880 with rectangular pixels. Once all of your menu elements are set the way you want in PS, resize the 720×534 image to 720×480 inside of PS. Ignore any distortions that are created during the resizing. Then save your menu.
3. Now if you use the menu in AE and Encore, it will be recognized as 720×480 rectangular pixel document (even though it’s not) and the distortions that were created when you resized in PS will go away.
4. For more info about PARs, find Rick Gerard’s tut here on the Cow.
-Jeff