I hope that helps and sorry for taking so long to get back to you!

all the best,

Vashi

Thank you.

Does CS5.5 PP internally up-convert h.264 to 422 8 bit, or 444 10/12 bit natively in 64 bit machine?

In either case would the addition of transcoding using ProRes on an iJOBS box or CineForm on a PC, make the eventual rendered output “better”?

The base format is Nikon’s HDslr’s, D7K and soon D4.

Thanks in advance for your reply, I was unable to search an answer to the conditional aspects that resolved my question.

Great forum regardless, always a lot to learn.

Rob

I’ve had this happen on larger projects (20+ hours of footage). There are numerous reasons or possibilities for this to happen. To try to help you I would need more info on your computer, version of Premiere, codec of the project you are working on and other essential info about your system. Usually this problem can by caused by a corrupt file so think back to the last files/images you imported before this started. You mentioned that you had a 6.5 hour timeline (!!!!) in your project and that could also cause Premiere to choke on the load. I’ve used 2 hour timelines for feature films but even that is a huge amount for Premiere to cache and open. I was curious why you were rendering before exporting videos as if you are on CS5 of CS5.5, the Mercury Playback will allow real-time playback in most cases…again not knowing your CS version or sequence preset doesn’t allow me to help you. Also, pulling hard drives out of your computer to exit Premiere may not be the best idea and could damage the contents of your drive and further corrupt files. On export, Premiere will create new render files for the final video file so there usually is no need to render before that point.

I would suggest the first thing to do is go into your Auto-Save vault and try to open the last saved version of your project BEFORE you did the export that is locking up Premiere. I set mine for 5 minute intervals so you should find a date-stamped version that occurred at some point before you initiated the render. You can also trash references for Premiere to see if that un-boggles the project. I’ve also tried cancelling the load before it goes to far and getting the project to open that way. You can then copy the current sequence and copy/paste that into a new project with the same settings. This has saved the day for me in the past.

I hope this helps and you get back up and running on your project. Also, don’t be afraid to go to the Adobe Premiere forums or Google this problem as there are literally thousands of people who have posted and discussed this exact issue. It is not uncommon but usually stems back to something very simple and easily reversible.

All the best,

Vashi Nedomansky

I have a HUGE problem right now. I have been using FCP for a while now but I am new to Premiere cs 5 but I started using it because I shot with a new HD camera and Final Cut was having trouble viewing the footage. Anyways, this project is byfar the biggest I have worked on in terms of footage. I have somewhere around 6 1/2 hours in the timeline but my editing system seemed to be handling it just fine. I hit a major milestone in my editing after around 30 hours of editing and I let it render as I went to work. After I got home, there was still 2 hours of rendering but I needed to start exporting some videos so I cancelled the render… I believe that is where everything went wrong. I was some test exports when I noticed that Premiere was running a bit slow so I rebooted the system. After rebooting, I tried to reopen the project and now Adobe Premiere is stuck in the “Load Project” screen. I had about 20% left to render when I stopped it and it seems like that is where the load bar stops. What can I do??? I can open up any other file in Premiere but when I try to open this one, it seems like it freezes Premiere and then I can’t safely remove the harddrive that I have the files on and I can’t shut down my computer unless I just pull the harddrive out of the computer. I have also tried waiting out the “load Project” menu and I saw no progress after an hour.

If anybody can offer any ideas as to what is going on, I would be extremely grateful.

[...]Little Things Make the Big Difference – Editing in Adobe Premiere CS 5.5 | Hurlbut Visuals[...]…

The alt key. If you hold alt while making a selection, all clip linking and grouping is ignored.

I use it to make J/L cuts, delete audio in one fell swoop, or even make edits to grouped clips without ungrouping them.

[...]Little Things Make the Big Difference – Editing in Adobe Premiere CS 5.5 | Hurlbut Visuals[...]…

Good question and definitely a very important one when dealing with feature film size projects that easily push into the hundreds of hours range. I’ve cut feature films on all 3 NLE (Avid, FCP and Premiere) and would agree that Avid deals quite well with huge amounts of footage.

That said, I feel Premiere is more then up to the challenge and equal to FCP 7 performance levels. There is always an extended launch time as the media is located/checked and loaded, but once that is complete…I’m off and running. A good amount of RAM (12+) will keep you running smoothly and make dynamic link with After Effects, Photoshop and Audition more seamless. I’m so glad I don’t have to export quicktimes, open them in AE, render out another quicktime and reimport it as I had to in FCP.

If you feel like a project is getting bogged down, you can always save the project into reels of 20 minute chunks or even into just 2 projects as needed. Again I havent had too much of a lag or slow responsiveness but even in FCP (not so much in Avid) we would chunk out the projects for better performance.

With digital formats being so easy to capture and with multiple cameras being normal on most film productions, the sheer amount of footage has spiralled into a mountain of Terabytes. With Adobe CS6 around the corner, i’m very confident that the Adobe workflow will continue to plow through footage and allow us as editors to just edit instead of wait for the NLE to play catch up.

Just as an illustration to the amount of footage in projects….the hockey movie Miracle (2004) that I worked on had 240 hours of raw footage. To contrast that…No Country for Old Men (2008) had 45 hours of footage and won the Academy Award for Best Film. A short film I just completed that comes out November 3…had 18 hours of raw footage and a final running time of 10.5 minutes.

I don’t think you should have any problems using Premiere for your feature film…just keep your project organized and clean on the way in so that you can easily find the footage you need!

all the best,

Vashi

How does PPro handle large projects like a feature film? Does it bog down with huge amounts of edits in the timeline like FCP sometimes can? Media Composer seems to handle that part with more ease. Curious if you’ve had experience along these lines?
Thanks!

One thing I noted – when you want to set your default video transition there is a typo above: (CMD+Q makes any transition you highlight in your video transition folder the default)

CMD+Q, I found that you can CTRL+click the transition you’d like, such as Film Dissolve, to set the default transition. Then you just select at least two of your frames, hit Q once you have the keyboard shortcut setup and you’re off to the races.

I’m curious, what is your preferred audio transition default?

Make sure you have at leas 16GB of RAM — because in spite of the enhanced CPU & GPU multithreading less ram will cause a bottle neck. I think the technical term is “through put” — and 16GB or more is what increased your through put so that your main hard drive running the app can function smoothly while editing multiple HD clips.

You’ll also want to split the scratch disk tasks, so you’re not over utilizing any one of your extra hard drives. I’m assuming you have at least 3 total internal drives. And if so, you might want to consider setting them up as RAID 0 – which is actually a non-redundant RAID with double the processor strength, so be sure to have external back ups.

Hope that helps. …I had to figure all of it out the hard way.