Selur's Little Message Board

Latest Hybrid on macOS Big Sur 11.7.10 (20G1427)

Input file is an avi capture file with HuffYUV.
One filter only to test QTGMC to generate ProRes422 output file.

Job aborts with :

Seem to be a problem with ffmsindex utility returning an error code.

Maybe I am asking too much from Hybrid to transcode HuffYUV based input file to ProRes ?

Or maybe a problem with ffmsindex ?

I ran ffmsindex from Terminal and it throws an error :

...and then ran it again with real parameters that Hybrid was using:



Incompatible version of libffms2.dylib included in Hybrid ?
See attached debug file.
Thanks

UPDATE:
@selur,
I found one of your old posts here and from your Mediafire server, downloaded version 6.0.0 of libffms2.dylib and copied that over 5.0.0.
Now the errors shows:

 
Conclusion: HuffYUV codec not supported by Hybrid ?

Seems like there is an issue with the ffms2 version.
Try whether using one of the ffms2 versions from:
If none of the ffms2 versions from https://www.mediafire.com/folder/wvdlnja...cajx3o6114 works, here sadly is nothing I can do to help.

Cu Selur

That's the link I used to get the version 6.0.0 of libffms2.dylib.
There's a version of ffmsindex in that link too but it does not make a difference.

There are two separate problems (and workarounds).

Problem 1:

Hybrid ffmsindex fails to load libffms2.dylib version 5.0.0 for HuffYUV input files

Workaround 1:
Replace version 5.0.0 of this

with version 6.0.0 (attached)

Maybe next version of Hybrid can contain this new version

Problem 2:

ffmsindex does not like the input AVI file.
The reason seems to be with the dimensions of the Horizontal and Vertical pixels.
The input file was CROPPED during capture to 690x562.
Apparently these dimensions are not multiples 4 so ffmsindex fails with : "Indexing error: Could not open video codec".
In the debug file (almost at the beginning) there's a message from ffmpeg about this:


Workaround 2:
If I capture without cropping so that the input file contains dimension 720x576 then there's no problem.
Or, capture and crop but make sure the dimensions are multiple of 4.

Happy you found a workaround.
Thanks for sharing!

Cu Selur

Thanks.

I have one old 3 hours capture file with this wrong  resolution

I tried FFMPEG crop option to convert it to 688x560 but FFMPEG fails because the input file is wrong resolution 

Any suggestion for how to convert this 3 hour capture (without actually recapturing it again) ?

688x560 sounds like a valid resolution,..
What is the ffmpeg call you used?
What is the exact error message ffmpeg gives you?
What formats and container does your file use?

(11.11.2023, 15:25)Selur Wrote: [ -> ]688x560 sounds like a valid resolution,..
What is the ffmpeg call you used?
What is the exact error message ffmpeg gives you?
What formats and container does your file use?

688x560 is my desired resolution but the existing file has 690x560.
Here's MEDIAInfo of the problem file:


When I use FFPROBE to check the file, I get:


This is the same error as FFMSINDEX ("width must be a multiple of 4 for this combination"......blah blah..}

The FFMPEG command line I used was:


Where I am trying to shave off 2 pixels off the X-Axis to change it from 690 to 688 and leaving the Y-Axis at 0 change.
But FMPEG complains with the same error:


Basically it's a catch-22 situation where FFMPEG will not allow to to fix the file because there's a fault with the file.

I did manage to PLAY the file with command line version of windows Mplayer (but of course that does not help be).

How did you capture it?
If you used something that uses vfw, you can probably use VirtualDub to open the file.

Cu Selur

It was captured on a PC using Virtualdub (using Matrox MXO2 Mini capture).
Even virtualdub cannot open the file as I think it too uses FFMPEG internally so cannot read it.

VirtualDub (not VirtualDub2) should not use ffmpeg, but try to use the vfw codecs on your system.

So the main problem might be to figure out what vfw codec really was used when this file was created.

Cu Selur