David Dobson
Forum Replies Created
-
Sometimes it does seem like auto save doesn’t work – even in CS4 – especially when rendering the timeline.
Ctrl-S as often as you can think of it. -
David Dobson
January 24, 2009 at 9:49 pm in reply to: why is premiere pro cs4 rebuilding media cache files everytime open a project?The problem with the media preference settings (for those of switching hard drives) is that they are global, so for instance, if you set the media files specifically to go to a folder, then that setting will be true for all projects an any drive. So when you go back to the first Hard Drive and open that project and the program looks for you files in a drive that doesn’t exist, it creates new files in the default location (adobe/common). Then if you change the settings to the folder on the drive you want the next time it runs it sees that the info has changed and creates new files in there – again – it won’t even recognize the files it created in earlier attempts, I guess because they don’t match the file names in the Media Cache database.
So what I have done is as follows: Leave the Database in the Adobe/common folder so all your projects can access it, and then for the Media Cache itself, select the check mark that says something like “put the cache next to to the source files.” I don’t have the program in front of me. That should permanently solve the problem. It did for me anyway. Basically, you should never change the media preference settings once the are set.
-
David Dobson
January 24, 2009 at 2:09 am in reply to: why is premiere pro cs4 rebuilding media cache files everytime open a project?Where are the media cache files being saved?
Where are the media cache databases being saved?
PPro will rebuild the cache for files when it can thinks that it has not already done so – so perhaps the location of the cache database is changing locations. Check your preferences>media -
I do think the way you DO things is the WHOLE point – that the final result can be achieved either easily or by jumping though hoops does matter.
-
Yes – if by that you mean earn a living using Premier Pro.
I work on both platforms regularly, but I own CS4 and run it on two machines. I can afford the hardware upgrades.
In my experience, FCP crashes too – sometimes as often in a day as CS3 did. CS4 is better, though I have plenty of issues with it I hope they fix.
One extreme advantage of PPro is that you can do some pretty sophisticated audio mixing IN THE TIMELINE. FCP audio mixing capability is really, well, amateurish.
I also like that PPro CS4 works natively with a lot of files. I have a regular need for AVCHD, HDV, DVCProHD (.mxf) and have used XDCAM (.mp4). And I do this without a special video card or raid drives. (SATA-II drives have sufficed even for the XDCAM-ES HQ footage.) I don’t know about the latest version of FCP, but the last I heard, P2 files had top be converted — AND — in order to do that you had buy a third party app. (I’m sure if I got that wrong someone will let me know.)
The title tool in PPro is much better than in FCP (I’ve never understood why the title tool in FCP was so bad.)
Also, Running Vista on a Dell might be your crash problem, not PPro. I’d also be suspect of anything using SCSI.
-
Well I’ve got CS4 and Encore is better but PPro has crashed 10 times today while I was just doing very normal editing tasks like scrubbing though clips or – you know- making an edit. I will say the crashed have mostly occurred with one project that is DVCProHD 720p24. My HDV and DV projects don’t crash. But load times for eveything are long – especially projects with lots of clips.
I’ve never see Vegas and I used to work with Avid a lot and PPro CS4 is really nice – when it doesn’t crash. I’ve sent in about 100 crash reports since I got it.
-
Have you tried exporting the video from AE as DV AVI rather than Uncompressed? Still though – it shouldn’t happen.
-
In fact – if you put a 768×432 solid into a PAL widescreen comp (in AE) it has to be blown up to 138% to fill the frame – and THAT alone is going to make the video look just plain awfull. If the source is already highly compressed, then it it’ll look even worse.
-
Fields – the short version: Half of a frame – every other line on the screen. The opposite of Progressive scan in the video world. If you want the full story, you can look it up in Wikipedia.
You can use the button in the effects window that jumps to the next keyframe to get to the exact keyframe. I think holding shift while dragging also snaps to keyframes…
Don’t know if you can turn that on or off – doubt it. I’ve actually never noticed that key frames could be put in between frames till you mentioned it.
-
PAL is 720×540 non-square pixels (wide screen?) You should be editing in a sequence set to PAL DV if you want to export to PAL DVD. Put your edit in the correct timeline and adjust that accordingly. 768×432 is what?