This project has moved. For the latest updates, please go here.

Conversion Failure(s)

Mar 7, 2016 at 1:10 AM

I have a couple files that seem to keep failing to convert - so upgraded to the newest (2.4.4) build today, retried them -> still failing ... :-(. The message in the log seems to be around the following (snippet from the file). Thoughts?

ERROR> 2016-03-06T20:06:10 MCEBuddy.Engine.ConversionJob --> Unhanded error during conversion, conversion cancelled
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MCEBuddy.Transcode.Convert.GetConversionExtension(ConversionJobOptions conversionOptions)
at MCEBuddy.Engine.ConversionJob.GetDestinationFilename(ConversionJobOptions conversionOptions, VideoMetaData metaData, String originalFileName, Log jobLog)
at MCEBuddy.Engine.ConversionJob.Convert()

Mar 7, 2016 at 11:52 AM
Please upload your log to the mcebuddy server

Mar 7, 2016 at 2:23 PM
Sure! Done, stored in "Discussion 652153" folder.

Mar 7, 2016 at 6:16 PM
Just FYI - 2 more files failed today ... same recording. Very odd. But it seems it's not just a bad file.
Mar 7, 2016 at 7:46 PM
You've written a custom profile and there's a mistake somewhere in your profile. I can't see from the logs. Check your profile again possibly while defining the extension of the converted file etc (something to do with that)

Mar 7, 2016 at 7:54 PM

It's not a custom profile - rather generated from the GUI, by changing the target resolution. Could the resolution change cause this?

Mar 7, 2016 at 7:56 PM
No, post the profile (using code brackets please)

Mar 7, 2016 at 10:30 PM
OK, sorry, slight sidetrack - my fault!

My conversions were failing (2 of them at least), so I figured I'd better update to the latest version, it had been a while. So ... I upgraded yesterday, but it seems that in the process a few of my settings were lost / changed - like the profile ... :-). So, I re-added it back, now failing for a different reason (like before).

New / corrected logs updated (now 45 MB, not 29 kB ... ;-)).

Mar 7, 2016 at 11:53 PM
Your source video is heavily corrupted is why you're seeing all these issue (including potential audio sync). In this case
> 2016-03-07T17:25:10 MCEBuddy.AppWrapper.FFmpeg --> [ac3 @ 00000209ebb11a40] frame sync error
2016-03-07T17:25:10 MCEBuddy.AppWrapper.FFmpeg --> Error while decoding stream #0:1: Invalid data found when processing input
2016-03-07T17:25:10 MCEBuddy.AppWrapper.FFmpeg --> [libfdk_aac @ 00000209e8cc1020] Queue input is backward in time
2016-03-07T17:25:10 MCEBuddy.AppWrapper.FFmpeg --> [mp4 @ 00000209e93558c0] Non-monotonous DTS in output stream 0:1; previous: 58299565, current: 58299053; changing to 58299566. This may result in incorrect timestamps in the output file.
2016-03-07T17:25:10 MCEBuddy.AppWrapper.FFmpeg --> Input stream #0:0 frame changed from size:704x480 fmt:yuv420p to size:544x480 fmt:yuv420p
2016-03-07T17:25:10 MCEBuddy.AppWrapper.FFmpeg --> [Parsed_crop_1 @ 00000209ebfe0f00] Invalid too big or non positive size for width '704' or height '352'
2016-03-07T17:25:10 MCEBuddy.AppWrapper.FFmpeg --> [Parsed_crop_1 @ 00000209ebfe0f00] Failed to configure input pad on Parsed_crop_1
2016-03-07T17:25:10 MCEBuddy.AppWrapper.FFmpeg --> Error reinitializing filters!

Your file is corrupted. I.e. whatever recording device you're using (TV tuner) has bad drivers and it's generating non compliant files.

Specifically in this case the cropping is failing. Try turning off cropping from expert settings and see it helps but your long term solution is to fix/update your tuner driver or fix the recording source.

Mar 8, 2016 at 12:50 AM
What's odd is - I converted several other files also, they are fine. And the video plays back just fine ... it's only this show.

I did disable cropping - fixes the issue! Trying to understand why of course ... ;-). This video is lower input resolution, 704x480 - is that somehow causing grief?

With no cropping the log is clean (and much smaller). What is the downside of leaving cropping disabled?

Mar 8, 2016 at 1:29 AM
not really, the cropping is profile specific and codec specific. Some codes can't handler certain resolution, it looks at SAR/DAR and aspects ration including pixel ratios. Some codes are very picky. In this case it's your nvenc codec which can't handle that resolution or pixel ratio. hence disable cropping. You can write a custom profile to handle it but you'll have to dig through ffmpeg commands to take care of it. In our profiles we have a few examples of where we've take care of it for some picky codecs.

Mar 8, 2016 at 1:32 AM
Makes sense - thanks for the help!
Mar 8, 2016 at 3:46 PM
If you look at this:
> 2016-03-07T17:25:10 MCEBuddy.AppWrapper.FFmpeg --> Input stream #0:0 frame changed from size:704x480 fmt:yuv420p to size:544x480 fmt:yuv420p

Your video appears to be changing size in between, I think it may be an advertisement and looks like the nvenc codec can't handle changing video resolutions within a stream yet

Mar 9, 2016 at 1:02 AM
Makes sense - thanks again for all the help!