Activity › Forums › Adobe Premiere Pro › Premiere CS5 Choppy/Skippy Render Issue
-
Premiere CS5 Choppy/Skippy Render Issue
Saad Raahim replied 9 years, 2 months ago 15 Members · 44 Replies
-
Dragan Negovanovic
March 23, 2011 at 5:05 pmTim, the stalls are consistent. However, when you import the rendered file into a fresh CS5 Premiere project it plays perfectly fine. Then I render out again and the stalls happen in two different places :-((( Each new render causes a skip on a different place.
-
Tim Kolb
March 23, 2011 at 6:45 pmWhat is the computer configuration?
Where is your scratch disk set?
How much hard drive space for scratch? For Video storage?
Exact framerates/datarates you’ve tried.
EVERY setting in the MPEG export…
Formats you’ve attempted to export to…and any differences in behavior in various players.
What happens if you export to something crazy like uncompressed or QT Animation or even DVCProHD and THEN compress it to MPEG?
AND…as I asked you, have you imported the original project into a fresh project to see if the project itself is simply corrupted?
TimK,
Director, Consultant
Kolb Productions, -
Dragan Negovanovic
March 23, 2011 at 7:55 pmWhat is the computer configuration?
I have a Intel Centrino Dual Core 2.53mghz per core, 4gb of ram, and 256mb Nvidia card. The hard drive is 500gb 5400rpm, 300 being available.
Where is your scratch disk set?
I am sorry I am not sure what this means. I am new to videoHow much hard drive space for scratch? For Video storage?
I have 300 gb available on the hard drive, I am not sure how I would allocate the space. Sorry.Exact framerates/datarates you’ve tried.
I tried exporting, 30mbs target rate with target high 36mbs..MPEG 2 upper field first for NTSC with frame blednig and max rendering quality setting
I also tried 7mbs target with 9mpbs high. MPEG2 upper field NTSC, frame blending , max render quality
I tried 25mbs target and 30 high, and rendered as pal 25frames, upper field first into MPEG2
I tried 7mbs target with 9mbps high MPEG2 for PAL upper and lower field frame blending max render quality on all of these tries.
I also exported as WMA but that was awful
I also rendered as h264 with the 1080/60i preset and it stalled as well
What happens if you export to something crazy like uncompressed or QT Animation or even DVCProHD and THEN compress it to MPEG?
I did not try this yet, but I can try that as well
AND…as I asked you, have you imported the original project into a fresh project to see if the project itself is simply corrupted?
Hmm, no I have not tried this yet. However I will try.
I know I should probably upgrade my machine as well, but I don’t know if that is the cause.
Thanks for your patience with this.
-
Todd Perchert
March 24, 2011 at 2:47 pmDragan – I’ve been experiencing something similar with exporting to mpeg-2 through AME. I think the issue for me is something with AME or the mpeg-2 component. I am able to render out uncompressed avi files from PPro fine, but when I then take those and render through AME as mpeg-2 I will still get the short ‘stall’ or quick ‘freeze’ in the video on simple :30 TV spots. I’m still trying to narrow down the problem. Unfortunately, it’s not all the time, and if I adjust the bit rate for the mpeg-2 render it may be fine or the freeze may be in a different location. For me it usually happens once, occasionally twice, in a :30 spot. Like you said, importing that same mpeg-2 back into PPro will play fine, but I can’t rely on that for the TV stations – who knows what they will be using and if it will play fine or not.
I recently reinstalled Adobe Prod Prem and that didn’t take care of the issue.
TCPC specs: EVGA Classified SR-2 mobo, 2 x 3.33 Ghz Xeon 6 cores each liquid cooled, 24GB 1333 DDR3 RAM, Quadro4000, 700MBps external RAID, Win 7 64bit, Adobe Prod Prem CS5.
-
Dragan Negovanovic
March 24, 2011 at 4:53 pmTodd it is good to see that I am not the only one with this problem. You definately have a high end system, unlike me, and we are having the same issue. This leads me to believe that it is not my system. I am exporting into the AVI format now to try as Tim suggested and I will then try to convert into MPEG2 to see if there are issues still.
Just FYI, my system is Inter Centrino Dual core 2.53ghz, 4gb of ram and 500gb 5400 rpm. Your typical everyday computing machine, it redners for a while, but it renders it out.
Thanks for your input..
-
Tim Kolb
March 24, 2011 at 5:58 pmYes, Dragan…your system is excruciatingly limited on power. I now see that you mentioned your system specs in an earlier post and I apparently skipped over them.
A 5400rpm harddrive is a severe limitation…I’m not in the least surprised that you’d have playback problems on a large HD file. Your processor is also very limited. When you’re decoding, that will affect it. It’s likely that PPro is dropping the clip to 1/2 res decode when you re-import it and that’s why PPro can play it while an outside player (like Windows Media Player or whatever) is trying to play it back at full resolution.
Now…why these files are a problem for the TV station is a mystery to me…
I assume you’ve tried to delete the source clips at the “glitch” points from the edit timeline and tried a full export to see if it implicates a bad source file?
TimK,
Director, Consultant
Kolb Productions, -
Dragan Negovanovic
March 24, 2011 at 11:55 pmTim, once again thanks for your response. I completely agree that my machine is very limited now for HD Editing. I will purchase a new most powerfull laptop very soon. However, I don’t know if that will fix the problem.
Two reason why I am saying that:
1. Todd in the upper post has an excellent machine and he is having the same issues
2. I have rendered 45 min AVCHD to MPEG2 before on this machine without a glitch.
I am taking your recommendation now to take import the project into a new one and export out an uncompressed AVI first, then i will import into new project and render to MPEG2. I will post the results. Thanks again.
-
Todd Perchert
March 24, 2011 at 11:57 pmDragan – I’m working on a theory here… Try exporting your project. When you get it into AME, try something. Before hitting render, hit ctrl-alt-del and start Task Manager. Click on the Applications Tab, Right-Click on Adobe Media Encoder, select Go To Process. Right-click on the Adobe Media Encoder exe process. Select Set Affinity. Uncheck a couple of cores and hit okay. Then go to AME and start que. Tell me if it works.
When you shut down AME after its done rendering and restart it, it should go back to all processors selected – you can always go back and double-check.
Like I said, a theory I am working on here. If it works I’ll tell you what I’m thinking…
TC -
Dragan Negovanovic
March 25, 2011 at 5:51 amOk, when you say uncheck a couple of cores do you mean one core because the options I show are
All Processors
CPU0
CPU1DO I leave just CPU1 and let it render?
-
Todd Perchert
March 25, 2011 at 2:00 pmyes sir. Uncheck one and leave the other checked.
I thought your specs had an i7… Must be someone elses post I was reading with an i7… Anyways, your render will take longer, but I’m interested in the final result.
I discovered that my system may have a power supply going or a bad 12v rail to one of the cpus. I’ve run several tests with half the cores and have gotten clean mpeg-2 renders every time. I’m just wondering if you could be having a power supply issue or lack of power from the power supply.
TC
Reply to this Discussion! Login or Sign Up