Cliff's Notes:
In my case, it looks like mvpmc's vlc_control.c is sending VLC a command
that no longer functions with ffmpeg.  I changed mine to always force 25 fps
and it works fine.

Full Detail:
Mythdora 10 (FC10) upgraded from Mythdora 4 (FC6) attempting to stream mp4
video to my mvpmc using VLC.  Would get the VLC errors:
[00000403] [Media: mvpmc] avcodec encoder warning: MPEG1/2 does not support
2997/100 fps (mpeg2vi...@0x9bcf240)
[00000403] [Media: mvpmc] avcodec encoder error: cannot open encoder
[00000403] [Media: mvpmc] main encoder warning: no encoder module matching
"ffmpeg" could be loaded
[00000403] [Media: mvpmc] main encoder debug: TIMER module_Need() : 4.573 ms
- Total 4.573 ms / 1 intvls (Avg 4.573 ms)
[00000388] [Media: mvpmc] stream_out_transcode stream out error: cannot find
video encoder (module:ffmpeg fourcc:mp2v)

My initial searches came up with tons of stuff about ubuntu removing
libraries and ffmpeg not working anymore, etc.  Even though I was on Fedora,
I assumed it was ffmpeg's fault.  I removed ffmpeg rpms and compiled
ffmpeg's latest release from source.  Same error.  OK, maybe it's VLC then.
Removed VLC rpms and compiled VLC's latest release from source.  Same
error.  Obviously I was on the wrong track.

I was looking for new leads, and I wondered if the "MPEG1/2 does not support
2997/100 fps" warning was a little more than a warning.  I reencoded my mp4
files to 25, 29, and 30 fps.  Same error every time, which meant to me that
mvpmc was always forcing 29.97 fps.  I did some searching and found that you
could pass startup commands like "--sout-transcode-fps 25.0000" to VLC that,
I assume, are supposed to override whatever command mvpmc sends.  They
didn't work, even when setting "--vlc-vopts none" in my mvpmc config.  The
last route I could think of was to compile my own mvpvc.  I added "fps =
"25.0000";" after line 666 (heh) in vlc_control.h and compiled.  Moved new
files to tftp, cold booted, and it works!

I'm not anywhere near an expert on this stuff, but based on my experience,
ffmpeg has changed their requirements.  Unless this is a mistake on ffmpeg's
part, mvpvc will need to be changed output frame rates that ffmpeg will
accept.
------------------------------------------------------------------------------
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to