Problems with Quicktime plugin: corrupt memory

Deadline
1

Hello,

We’re getting some strange errors with the quicktime plugin.

Error: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.(System.AccessViolationException)

This doesn’t happen with all the quicktime renders but it does happen consistently on certain jobs. I thought maybe it was a mis-reported out of memory error but the machines handling it have 12GB of RAM and it’s only a 300frame 1080HD render so it can’t be that surely?

It does seem to happen on large numbers of frames. I’m not sure what the limit is because so far our renders have been mainly 25 frame rotations. This is the first batch of longer renders we have done with the plugin.

Has anyone come across this?

2

What’s the format and average file size of the input frames? Have you tested other formats to see if the problem is specific to the format that you’re using?

Also, which OS are you rendering these QTs on?

Thanks!

  • Ryan
3

Hi Ryan,

The average frame size is 4mb rendering on Windows using h.264. I haven’t tried other settings but I will do now and see what I get.

Thanks,

Dan

4

It was the settings. H.264 seems a bit flaky. I tried Photo-JPEG and it was fine.

Photo-JPEG should be fine from a quality/size point of view so I’ll switch over to using that codec instead.

Thanks,

Dan