New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PES packet size mismatch - Invalid stream specifier: C01 #2
Comments
The problem is "Invalid stream specifier: C01" - ffmpeg doesn't recognise or like this stream. The first thing to do is run ffprobe on the file like so, and post the result of the stream info: ffprobe -show_streams -i "/data/tv/alte_Musik/Alte_Musik..../00001.ts" The PES mismatch is a common warning, usually can be ignored |
May be worth mentioning that I'm at a German TV cable. Here is output - sorry, lots of stuff... For a radio programme:
And this is tv:
|
Does it work with other files? Both should work, but I don't like the look of "WARNING: library configuration mismatch". This suggests your ffmpeg libraries, avutil, avcodec etc might be out of sync with your version of ffmpeg. This can have bad effects, possibly including what you're seeing. Can you ensure you have a complete ffmpeg with matching libraries? File1: Without video, only podcast mode is of any great use. I don't think AC3 is supported in podcast mode, I'd have to check. Ideally I need a sample to test this unusual stream combination. My other thought is that I haven't ever seen a file with a DVB teletext stream (file 2), which may be an issue (I've not tested it). All the other streams I've tested with. Please share a 2 minute section of each file with me, so I can check. You can make excerpts like this, and post them somewhere I can download them (https://wetransfer.com/ etc). If there's a very long continuity announcement at the start, make the file 3 or 4 mins long, but including the continuity is useful for test.
|
Even better, use this to capture as much as possible: |
Happy new year. Sorry for the delay, I was a few days off. Here are the files requested: |
Great thanks. -f opus doesn't work for me also as that's not a valid file format (-f flag) for normal transcodes, its a stream format that partially supported for podcasts - if the opus code is enabled. Podcast mode is only designed to work on a file with 1 audio stream, so it rejects the AC3+MP2 file for podcast, I tested manually with ffmpeg: AC3 -> opus and it fails pretty badly - ffmpeg doesn't like channel layout, If converting the non-AC3 stream to opus or AAC is an important use case, I could look at it, but opus has limited profiles and only accepts 48kHz samples AFAIK. I captured my output on the video file below for ref. Please check again your codec mismatch warning, and try another build of ffmpeg. You could copy my long command line from below and see what message you get. Check also AC3 support in your ffmpeg build (I think it's built-in as standard but worth checking again). ffmpeg -codecs lists what's supported in your build.
|
Yes, looks as if it's a ffmpeg issue at MLD. Unluckily, I do not really know what to do, neither does Claus from MLD, who really does his very best to please his customers. AFAIK, I cannot try "another build", because these things are fixed in MLD repo. Here is ffmpeg -convert output: `MLD> ffmpeg -codecs
|
That's a very complete ffmpeg build! I include mine below, based on the SuSe/Packman config. You could ask for a a build that's much smaller, configured like this for test, but it's a bit of a long shot. Your example files also convert on the stock Suse/Packman ffmpeg build (4.4.4). One thing I notice is that my build doesn't contain libzvbi which is used to decode by dvb_teletext - the thing that's unusual about your samples. I can't build ffmpeg with libzvbi for some compatibility reason atm, but the stock version includes it, and your files convert with that version, I can't conclude anything from this, sorry.
|
Hello,
on a MLD, I tried:
3MLD> vdr-convert -f opus -i "/data/tv/alte_Musik/Alte_Musik/2023-12-20.21.28.168-0.rec"
log says:
Is there something I can do?
The text was updated successfully, but these errors were encountered: