-
CS6-Media Encoder Fails on long (1hr +) H.264 render
Windows 7 – 64 Bit. 8 GBs RAM
Adobe Pr and other programs on C: internal Plenty of hard disk space left 300+GBs
External high speed 7200 RPM RAID 1 where the media is stored.
External high speed 7200 RPM Non RAID drive for rendering to be written to.
Both drives are eSata.
CS6 Pr and Media Encoder 6.0.0.382Footage is a single capture of a lecture. 1 hr. 20 minutes.
Shot on Canon xf105 in MXF format at 1280×720 23.976p (US)
Footage goes together fine (many multiple file clips ‘chained’ or butted up against one another, as is done when you shoot a continuous take)
The footage plays fine in Pr in final form for export.
No special effects. one dissolve (intro title slide to lecture)Reproduceable problem:
I export to Media Encoder.
I choose H.264 and Vimeo Wide Screen SD 23.976
The file exports about 2/3rds of the way, not the same place each time, and fails with no definitive error message. Just something to the effect of “…. failed.” (I’m currently uploading the footage and can’t reproduce it at the moment)
Rendered file to external drive (have more than one, have tried it on two, with same results)
All drives have plenty of disk space on them.I tried cleaning the Media Encoder Media Cache. Same result.
I tried moving the cache files to an almost empty external disk. No change.
I broke the video into a 10 minute segment, it rendered just fine with the same settings.
This seems to be a bug in Media Encoder. Is there a fix for this? A workaround? My client would like a single long file of the presentation.
Could the 8 GBs of RAM be an issue? Not sure why it would. Or is this a known bug for Media Encoder?I will attempt to create a DVD for them as well, and see if things actually work at that length.
I also posted this on Adobe’s web site. But I figure that if this is a bug, we all should know it. It’s a rather simple thing to ask Media Encoder to do. Render an hour or more single camera shoot with no effects. Basic.
Al
-
3 Replies
-
This is not a bug.
Try exporting to another codec for one.
Try the Vimeo HD 720p/24 preset, not widescreen.
Try lowering the data rate some.Chris Tompkins
Video Atlanta LLC -
I believe I may have solved it, as I uploaded the update to 6.0.1.31 and it appears to have fixed the problem. I have multiple workstations so I had not updated the one that I was using. What I can report is that it went away during the first pass I made on it. I didn’t have time to do additional testing on it, since I’m under a bit of a deadline. But I did get through it once after the update, which was enough to get it out on the net for them to review.
I was under the belief I had been up to date on all machines, but this incremental update appears to have fixed that ‘bug’. (it appeared to only affect that particular render choice).
Al
-
I were facing the same problem like yours, even I am using a new update of Encoder.
I tried to export directly via Premiere CS6, and I got an amazing result. PPCS6 exports faster than Encoder CS6 does. While PPCS6 was working, I used GPU monitor to see what happening. Very surprised, the percentage of using GPU (CUDA) when PPCS6 was exporting was very high (from 27 to 80 percent load), and CPU was being used about 50 percent. This is opposite to the case of using Encoder exporting. It is usually using about 6-12 percent of GPU resource.
Reply to this Discussion! Login or Sign Up