-
Notifications
You must be signed in to change notification settings - Fork 516
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
UDP parser error #1447
Comments
Without assigning blame, a parser error means that the parser doesn't understand the content as formatted. It's possible for the content to be malformed, and it's possible for the parser to be buggy. Can you please share your Packager command line and some information on the source of the UDP stream? |
'packager', 'input=udp://10.0.90.38:5002,stream=video,init_segment=/var/opt/live/test_1/video_1/video_init.mp4,segment_template=/var/opt/live/test_1/video_1/video_$Number$.m4s,drm_label=VIDEO,hls_name=video_1,iframe_playlist_name=/var/opt/live/test_1/video_1/iframe.m3u8,hls_group_id=video', 'input=udp://10.0.90.38:5002,stream=audio,init_segment=/var/opt/live/test_1/audio_tr1/audio_init.mp4,segment_template=/var/opt/live/test_1/audio_tr1/audio_$Number$.m4s,stream_selector=1,language=tr1,hls_name=tr1,hls_group_id=audio,playlist_name=/var/opt/live/test_1/audio_tr1/audio_tr1.m3u8,drm_label=AUDIO', '--segment_duration=2', This is the packager cmd I am using. |
Can you share information about the transcode? Are you using FFmpeg, or something else? What version? What command? |
i am using GStreamer for the transcode don't know much about that I will share what I know |
Could gstreamer have a bug that creates malformed TS packets? Can you update it to the latest release and try again? Can you also try taking some of those TS that failed to parse and checking them against another parser, such as https://thumb.co.il/ ? |
I am also using Gstreamer and also getting the same error. |
E1119 05:46:23.075434 8 h264_parser.cc:1011] Interlaced streams not supported Any one explain this? Is this related to same bug from above |
As I said, could you try taking some of those TS that failed to parse and checking them against another parser, such as https://thumb.co.il/ ? If they are parsed successfully by other software, that could help someone understand the problem and improve the parser in Shaka Packager. If they fail there, too, then please report the bug to gstreamer: https://gstreamer.freedesktop.org/documentation/contribute/index.html?gi-language=c#how-to-file-issues-and-request-for-enhancements |
In UDP input, how can I get TS packets for the parser test? |
I'm also seeing the same error on a passed through HEVC stream from ffmpeg to shaka 3.4.0. If i start shaka after say 10 seconds, all is fine What i get: I dont have an analyzer handy but i'm guessing shaka does not like some of the initial packets sent by ffmpeg. I'll try to capture and run an analysis when i find some time :) |
The TS file is parsed fine by https://media-analyzer.pro/app which also has a bitstream analyzer I can provide both source stream samples as well as ffmpeg passthru stream samples in private |
hi @joeyparrish while packaging directly through ffmpeg can't get any parser error ffmpeg -i udp://224.0.10.15:3030 -map 0:v -c:v copy -f hls -hls_time 4 -hls_segment_filename /opt/var/5002/video_%03d.ts /opt/var/5002/video.m3u8 -map 0:a -c:a copy -f hls -hls_time 4 -hls_segment_filename /opt/var/5002/audio_%03d.ts /opt/var/5002/audio.m3u8 -master_pl_name /opt/var/5002/master.m3u8 -var_stream_map "v:0 a:0" i tried for m4s and also didnt get an mp2t mpeg2t parser error using ffmpeg |
Also while just using this without +genpts flag also getting parser error |
E1108 08:40:14.781702 8 mp2t_media_parser.cc:122] Parsing failed for pid = 101, type=3
I1108 08:40:14.781818 8 status.cc:76] 8 (PARSER_FAILURE): Cannot parse media file udp://192.168.50.4:3501
E1108 08:40:14.781987 7 packager_main.cc:628] Packaging Error: 8 (PARSER_FAILURE): Cannot parse media file udp://192.168.50.4:3501
in between packaging, the error appeared , but the udp is transcoded with mpe-ts correctly , whats the main problem here
The text was updated successfully, but these errors were encountered: