search

cannonbeach / ott-packager

OTT/ABR streaming encoder (H264/HEVC) and packager for DASH and HLS
GNU General Public License v2.0
228 stars 42 forks source link

No Source Signal #20

Closed marciocamello closed 5 years ago

marciocamello commented 5 years ago

SESSION:1 (TSRECEIVE) WARNING: NO SOURCE SIGNAL PRESENT (SOCKET:3) 127.0.0.1:4000:lo (142

I cant receive signal in my server.

cannonbeach commented 5 years ago

Please make sure you have a transport stream signal on the loop back interface (lo) going to port 4000.

You can verify your signal is present using tcpdump as follows: sudo tcpdump -n udp -i lo

What are you using as your source?

On Tue, May 21, 2019 at 5:41 PM MarcioCamello notifications@github.com wrote:

SESSION:1 (TSRECEIVE) WARNING: NO SOURCE SIGNAL PRESENT (SOCKET:3) 127.0.0.1:4000:lo (142

I cant receive signal in my server.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cannonbeach/ott-packager/issues/20?email_source=notifications&email_token=ABJ3YIID2YVQBNZCSNXQYXTPWR3B5A5CNFSM4HOPIT22YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GVCPTXA, or mute the thread https://github.com/notifications/unsubscribe-auth/ABJ3YIN2B5B6OSVHUZHJ5RDPWR3B5ANCNFSM4HOPIT2Q .

marciocamello commented 5 years ago

ffmpeg -re -i input -c:v copy -c:a copy -f mpegts "udp://ip:4000"

tcpdump output

tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes

cannonbeach commented 5 years ago

Please make sure you re-stream to the loopback interface (which 127.0.0.1) otherwise the traffic may end up on a different interface such as eth0.

Here is the command line I used to test: ffmpeg -re -i input.ts -c:v copy -c:a copy -f mpegts udp://127.0.0.1:4000?pkt_size=1316

marciocamello commented 5 years ago

Thank you, works, my interface is esn3, so i sendo to remote IP and works now.

marciocamello commented 5 years ago

Whats this LOG?

-------------- dumping out frame data ------------ DONE WITH SYNC LOCK WAITING FOR SYNC THREAD TO STOP: 1 -------------- dumping out frame data ------------ -------------- dumping out frame data ------------ SESSION:1 (MAIN) STATUS: LEAVING SYNC THREAD - DISCONTINUITY DONE WAITING FOR SYNC THREAD TO STOP STATUS: RESTARTING FRAME SYNC THREAD SESSION:1 (MAIN) STATUS: STARTING NEW SYNC THREAD STATUS: RECEIVE_FRAME (H264/HEVC : 0): TYPE: 2 PTS: 2197124460 DTS: 0 KEY:

If show this log, dont generate ts files anymore.

cannonbeach commented 5 years ago

I'd have to see the full log to really understand the issue, but from what I can tell it looks like there is a discontinuity in your source stream that is causing the core sync thread to restart. The core sync thread is supposed to restart on an unrecoverable discontinuity, but it should continue to process frames after that event. Did the application exit or hang?

If you're still having trouble, please send me a short capture of your source and I can debug the issue.