I tried to render an Avid MC6 Qt. Ref. file in Sorenson Squeeze 8.5 and everytime I do, I got this error.

I posted this error on Sorenson site but seems no one knows. I am using Vimeo and Youtube preset and both got this same error.

Try duplicating your sequence and making a Video mixdown. Edit that mixdown into the duplicate sequences V1 with all other video tracks active. (so you end up with a mixdown on V1 and no media on any other Video tracks.

When exporting this duplicate time line to QT reference select the option to create an Audio Mixdown during the export.

Then open SS 8.5 and add this new QT reference as your source.  If your timeline is more than 10 minutes I would try what I just suggested on a 30 second section of your timeline to check it all works

I think this is a Sorenson/MainConcept codec issue as against an MC problem.

I successfuly exported from MC6.5 to DNxHD 36 1080P50.

Imported to Squeeze and applied mp4/H264 - MainConcept CUDA.

Failed at the very end with the same error.

It seems to happen if the video is long. This one is 50 minutes.

Didn't happen on a short 3-5 minutes video.

No problem encoding the very same video to VP8.

Additional tests:

- In the very same Sorenson project where the ManiConcept h264 CUDA codec failed I:

- copied the preset that failed

- changed the codec to x264

- added the preset to the very same movie that failed and

- rendered it.

No problem, worked just fine. Then I:

- cleared the previously failed render and

- re-rendered it

It has failed again with the same message.

I think this proves that the problem is with the MainConcept h264 CUDA codec.

I have lodged a report with Sorenson.

Bill -- did you get a response from Sorenson?  I'm having the same exact issue.  Any help would be appreciated.  Thanks.

Sorry for the late reply, i was filming off the map.

stevehj:

did you get a response from Sorenson?

Yes and no.

I worked out, the compression fails if Stream-type is set to 'Streaming(hinted)'.

It worked when i set it to Non-streaming.

I told it to Sorenson and they reply was that they are "happy" that i found a workaround.

Quickly I advised them that I was expecting a thankyou for carrying out free Alpha-testing for THEM to solve a bug and a report that they fixed it.

Didn't hear from them since.

Cheers,

Bill

Well I'm getting the same error at random here. However, I'm not coming right out of Media Composer. I have rendered master files that I'm now running through Squeeze 9 Pro. About a third of my renders (I have about 20 files in front of me) are coming up "MPEG4IP Hinter Failed." Nothing on the Sorenson threads. Yes, these are for Vimeo. I'd selected the "hinted" because, well yes, these are for streaming. Guess I'll try it with hiniting off and see what happens. I'm using x.264 instead of Main concept and running these at 15,000 Kbps for HD on a Vimeo Pro account.

Robb Harriss:

...I have rendered master files that I'm now running through Squeeze 9 Pro. About a third of my renders (I have about 20 files in front of me) are coming up "MPEG4IP Hinter Failed." Nothing on the Sorenson threads. Yes, these are for Vimeo. I'd selected the "hinted" because, well yes, these are for streaming...I'm using x.264 instead of Main concept and running these at 15,000 Kbps for HD on a Vimeo Pro account.

Same settings as Robb, same problem. Four years and three versions later, Squeeze developers and support are just as unresponsive. However, turning off "hinting" did the trick. Whatever  that "Hinter" is, it just doesn't take the hint! Coming straight out of MC 8.6.5 Mixdown works as well as QT export. Squeeze has always given me good results when it does work.

In the hope it helps someone:

I master as MyMovie_DNxHD.mov.

I now use ffmpeg (still on Windows 7) to convert/compress to mp4/x264. (Yes, I have Squeeze but i need testing ffmpeg - I am migrating all editing to linux)

Windows: Avanti interface is minimalist. There must be better ones - up to you.

The GTX 1080 has some two-thousand-how-many Cuda cores. Sorenson reports 640 ... hmmmm ... but, forget about the Cuda cores anyway. Nvidia does not provide properly for H264 encoding meaning the render may be inferior quality compared to CPU render. (ffmpeg has a 'hardware accelerate'  switch but it has the same issues as all other softwares) Back to the CPUs.