HDV rendering error

[kwshaw1]

If you get Speed Encoder to do anything, can you print the encoded file back to your Sony? (my latest beef)

Ah, interesting question. I haven't tried that because I can just take the M2T files and play them directly on my Playstation 3. I don't have any reason to go back to tape, especially now that hard drives are cheaper per hour of storage...

[Khoi Pham]

Sounds like a job for Procoder.

If you get Speed Encoder to do anything, can you print the encoded file back to your Sony? (my latest beef)

Rusty

I also have some beef with Speed Encoder right now, I can use it to encoded and print to tape, but the same file will not playback on the timeline, it will freeze my computer.

[Rusty]

Sounds like a job for Procoder.

If you get Speed Encoder to do anything, can you print the encoded file back to your Sony? (my latest beef)

Rusty

[kwshaw1]

Okay, here's the error I'm getting. This happens consistently when I try to render directly from an HDV clip to HDV output using Speed Encoder.

"Failed in Grid Encoder. It might be out of memory. Please send the log file below to Rhozet corporation."

Should I go ahead and send the log file to someone?

P.S. I've posted a screen shot of the error which I'll leave up for a few days so you can see the full details:

http://www.videomem.com/speed_encoder_error.jpg

recur the error is helpful for the developing team to modify it:)
in fact, users are the best tester:)

[Rusty]

Sounds like Speed Encoder is up to its' old tricks again!

Rusty

[kwshaw1]

What error are you getting?

I'm having trouble recreating the error because now Edius just crashes when I try to render from HDV clips to HDV output. Something about the encoder failed - sounds like a memory issue or like that.

[GrassValley_BH]

What error are you getting?

[kwshaw1]

I'm getting an error when trying to render from an HDV timeline to HDV output and have only been able to avoid it by pre-rendering to the HQ format first. Has anyone else encountered this, and what is the most likely culprit? I'm working in Windows XP on a dual-core laptop with 2 GB of RAM, and I've turned off my virus software plus some other processes which might slow things down -- but I still get the error.