Have a bunch of multimedia on a NAS drive that I play over smb.
Today did a a tumbleweed update - if I remember correctly the update was dated (2020-03-07)
Since then I am no longer able to play videos (using smpalyer/mpv) over smb.
I get the error . . .
Warning: option --input-file is deprecated and might be removed in the future (use --input-ipc-server).
[ffmpeg] Protocol not found. Make sure ffmpeg/Libav is compiled with networking support.
Failed to open smb://ls210/share/TV/TVShowname/s01e01.mkv.
Exiting... (Errors when loading file)
I noticed during the update that a bunch of smb files were updated as well as ffmpeg
Anyone have any ideas?
Should I file a bug report?
Have used snapper to rollback the system to before the update and can play over smb just fine again.
I did notice that several “libav” packages were updated during that update. I suppose I could check, but I’m guessing that some of them may have reverted to openSUSE repos instead of the packman repo (I do allow vendor change here). So perhaps you just need to wait a day or two for packman to catch up, and then move those packages back to packman.
I have encountered the exact same problem today. All ffmpeg/libav* packages are from Packman.
I have also tried to open the mp4 file from the commandline with mpv, it says “Protocol not found.”
My guess is that Packman ffmpeg/libav* has some compiling issues. If you have filed a bug, please let me know the BOO id so that I can follow.
$ mpv smb://admin@192.168.0.100/share/movie/1.mp4
[ffmpeg] Protocol not found. Make sure ffmpeg/Libav is compiled with networking support.
Failed to open smb://admin@192.168.0.100/share/movie/1.mp4.
I’ve actually closed the bug as it is clearly an issue with packman’s version of ffmpeg and not mpv
Hopefully they get ffmpeg compiled with smb support into packman shortly
a fix for this has now been added to ffmpeg-4
however, I’ve now shifted to running Leap 15.2 (beta) which appears to currently be using ffmpeg-3
Will 15.2 be getting an update to ffmpeg-4 any time soon and is there any particular reason it is still on ffmpeg-3?