Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Won't export

Christoffer Glans

Christoffer Glans

Well-known member
Joined
Jun 11, 2007
Messages
4,993
Reaction score
36
Points
48
Age
42
Location
Stockholm, Sweden
I'm trying to export a ProRes from a 6K Dragon file with D.E.B and A.D.D on. It's not a long clip, just around 1 minute. But the export time just keeps increasing and after a while it's at 20 hours and counting with the export percentage at 0%. Tried on my Desktop PC and then on my Macbook Pro, it's the same every time.

What is going on?
 
ADD can take up to 45 second per frame as its using pre and post frames to calculate.

(25x60) x45/60/60. About18.75hours.

sounds correct
 
But, when switching it off, it does the same :001_unsure:
 
David Battistella said:
ADD can take up to 45 second per frame as its using pre and post frames to calculate.

(25x60) x45/60/60. About18.75hours.

sounds correct
Click to expand...


David my pc is 7 second for frame! A.d.d and Deb.
45 seconds is tooooooo much.
 
Björn Benckert said:
I would try DPX or some image sequence to see if that speeds it up.
Click to expand...

Tried that too, nothing... it's like if the program get stuck in an endless loop. Tried the beta release as well, same result.
 
I have the same problem you are describing, Progress 0% and ETA keeps ticking up. In both the current release and beta builds, it's unbelievably frustrating. In the release build I have seen this happen in H.264 & DPX export, and in the beta build I have seen it happen in H.264, Prores, DPX. The worst part is this problem comes and goes intermittently, making it hard to track down. I have occasionally been able to get past zero, at which point the export goes through relatively quickly (no A.D.D.) and successfully.

Export logs often have this error : ICMCompressionSessionEncodeFrame() failed (-6682), which seems to be related to the QuickTime API. Once this occurs RedCine-X, doesn't seem to be aware of the failure, and sits there spinning.

I basically gave up trying to figure this out months ago, but I'm glad to have found someone else experiencing this.
 
Yeah, it started rolling after a while. It's like when this happens, it doesn't matter if you close the program or the Redcine-X process in application manager, it's like the error persist until random and then it works again. I don't think it's related to quicktime directly because the error is still there when changing to a DPX or TIFF export, but Redcine might get stuck with quicktime locking all exports until it sorts that process out. Ian, did you try force quitting any quicktime related processes and reopen Redcine-X?
David, I can't seem to find a log that relates to the problem, there isn't anything in them that pinpoints something wrong. Which log is it that would be sent in?

And what would I need to be able to render A.D.D faster? Is it only the RedRocket-X that enables that or does it use GPU acceleration (new card, better performance?)
 
Christoffer Glans said:
It's like when this happens, it doesn't matter if you close the program or the Redcine-X process
Click to expand...

I experienced this recently too with lastest redcine.

A 6K 90-ish frame clip in redcine on a mac running 10.8.5
export to prores never moved past 0% and the estimate climbed to something like 20 hours then the estimate disappeared.

tried a couple other clips, same results.

It used to export to prores just fine...
 
Christoffer and Daniel,

Thats ok -- just do a "Save Report" from the help menu and send me the zip file. Please have verbose enabled and then attempt some exports first. The logs may not have errors but they might provide a hint to me as to where things are hanging up. Also anything else you can tell me that might be relevant to recreating the issue is also appreciated. Once we can recreate the problem, it will get fixed.

Thanks,
David
 
Did this issue ever get resolved? I'm having the same problem myself in Build 35 and 36. Working with the Red team now to try to replicate, but wondered if anyone else has encountered this issue.

Win7 64-bit | Build 35 and 36
 
Hi Craig,

Can you please enable verbose logging and do a Save Report from the Help menu? Please run a few exports before saving the report so it can capture the failure.

Thanks,
David
 
Hi David:

(Reference RED Support #37368.)

Thanks for looking into this. This exported report will show you the issue:
https://app.box.com/s/7jlrmdtxrbfp4j0cnheleam47s8g74iu

The 4 most recent exports went like this:

1) Tried to export all clips in a project to H264. Gets stuck on first export, time counts up to 10+ hours, 0 byte file is created, percent never moves beyond 0%. Had to close, manually kill redexport.exe.
2) Re-opened Redcine-X. Tried to export all clips in a 2nd project to H264. Gets stuck on first export, time counts up to 10+ hours, 0 byte file is created, percent never moves beyond 0%. Had to close, manually kill redexport.exe.
3) Re-opened Redcine-X. Tried to export "selected clips" this time instead of full project. Redcine-X crashed entirely on the first video. First time I have seen this behavior.
4) Re-opened Redcine-X, did the same type of export. The first video encoded successfully, then the second one got hung up, just like in test #1.

If there's anything else you need, please let me know.

(Please note: Note that I upgraded to Win10 for these examples, hoping that might solve the issue, but same behavior was exhibited as with Win7.)
 
Last edited:
What's the mai for sending reports again...

Having all sorts of things with 35/36 on yosemite.

Went back to 33 for a while. All fine. Tried the new 36. Crashes all over the place, independently of CUDA/OpenCL/web-driver/OSX driver
 
Hi Gunleik,

You can send them to redcinex at red dot com.

A few people have been having weird issues like this, and we are still trying to get to the bottom of it. If you can reproduce crashing please let us know.

Thanks,
David
 
You must log in or register to reply here.
Back
Top