-
Notifications
You must be signed in to change notification settings - Fork 496
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
Packager stops packetizing from live sources in live profile #93
Comments
The issue is likely to be a networking issue. One of the multicast-aware routers between the packager host and the UDP stream source may be discontinuing the stream after a predetermined amount of time. Does failure occur after roughly the same amount of time each time? |
Hi, |
Hi,
This instance command line is: Meanwhile, tcpdump on this interface shows:
netstat -tupan shows, that the sockets receive queue of 3 from 4 input streams is full.. hm. Nobody reads from them:
|
You mean that the MPD keeps getting updated, including references to mp4 I am at a loss to think of an internal state which might cause that On Tue, Mar 1, 2016 at 4:33 AM, peyoh notifications@github.com wrote:
Thomás Inskip | Software Engineer | tinskip@google.com | +1 650 241 9697 |
That is indeed weird. Just to confirm, is the mpd file actually being updated, other than the publishTime? Do you see any error messages on the console? |
Hello,
About warning messages, I've redirected them to /dev/null. Will restart the services with logging enabled. BTW, |
Hello,
|
Yes, it can definitely help if you give us ssh access. Btw, just to rule out, do you have any cron job running that removes out-dated segments periodically? |
No.I have no cronjob for removing segments. |
Hi peyoh, From the thread info,
There is only one RemuxJob exist. Looks like the other packaging threads have exited. It is unknown yet what was causing these threads to exit. Likely some media parsing error. Can you run with debug code at https://github.com/kqyang/edash-packager, which contains slightly more debug messages? Then capture all logs. Let's analyze the logs later to see if we can figure out what is causing those threads to exit. |
Hi kqyang, |
Just use default if v=1 is too much. (no verbose level) |
Hi kquang,
This profile is definitely not processed:
|
Thanks for the new log, so there is a parsing failure. It seems like some problem in the content. Can you apply the below patch and run again:
You may also just sync and use the code at https://github.com/kqyang/edash-packager. This will collect additional debug message to help confirm what is wrong. |
Hi, |
I believe this is content problem. Here is the data from failure_1.txt: This is an IDR Slice NAL unit. Apparently it is incomplete, which caused the parsing failure.
The NAL unit is extracted from the below stream:
I think the problem is that start code emulation prevention was not applied properly to the source content causing NAL unit parsing problem. It might be possible to workaround it in edash-packager, but it will be better to solve the root cause. How is the content transcoded? Can you look into why the start code emulation prevention was not applied properly? |
Hm, |
Ok, that is a good argument to have more robust handling of NAL unit and start codes in edash-packager - which is difficult though. We'll think about how to tackle it. |
Hello,
I'm using edash-packager ver. 1.3.1. But sometimes, it just stops.
On the ethernet interface I'm able to see the input sources. The multicast groups are joined and the UDP streams comes to the interface.
After restart it continues to work.
Command line is:
Debug/packager --udp_interface_address=10.0.8.33 input=udp://239.204.6.121:7000,stream=audio,init_segment=/storage/web/dash/662/edash-audio.mp4,segment_template=/storage/web/dash/662/edash-audio-$Number$.mp4 input=udp://239.204.6.121:7000,stream=video,init_segment=/storage/web/dash/662/edash-video-576.mp4,segment_template=/storage/web/dash/662/edash-video-576-$Number$.mp4 input=udp://239.204.6.122:7000,stream=video,init_segment=/storage/web/dash/662/edash-video-512.mp4,segment_template=/storage/web/dash/662/edash-video-512-$Number$.mp4 input=udp://239.204.6.123:7000,stream=video,init_segment=/storage/web/dash/662/edash-video-384.mp4,segment_template=/storage/web/dash/662/edash-video-384-$Number$.mp4 input=udp://239.204.6.124:7000,stream=video,init_segment=/storage/web/dash/662/edash-video-288.mp4,segment_template=/storage/web/dash/662/edash-video-288-$Number$.mp4 --profile live --mpd_output /storage/web/dash/662/662.mpd -time_shift_buffer_depth 86400 -dump_stream_info -availability_time_offset 10
Manifest is:
GDB shows:
Please tell me how I can help to detect what the issue is.
BRS
The text was updated successfully, but these errors were encountered: