You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello ,
I think there is a bug with the newer version of srt and nginx .
after nginx build accourding to the guide below we get error on the nginx side - Do you know why maybe ?
Hi, you can try to capture the data after the SRT->TCP conversion, and then I can check it out and see if it looks like a valid TS or not. For example, you can start a local TCP server using netcat - nc -l 1234 > dump.ts, and configure nginx-srt-module to proxy to the netcat port, instead of the nginx-mpegts-module port.
Hello ,
I think there is a bug with the newer version of srt and nginx .
after nginx build accourding to the guide below we get error on the nginx side - Do you know why maybe ?
Guide
MPEGTS/SRT
Sample ffmpeg command: ffmpeg -re -i test.mp4 -c copy -f mpegts "srt://localhost:7045?streamid={channel}_{stream}"
Supported codecs:
Video: h264 / AVC, h265 / HEVC
Audio: AAC, MP3, AC3, E-AC3, OPUS
FFMPEG Command :
ffmpeg -re -i 1.mp4 -c copy -f mpegts "srt://192.168.0.134:7045?streamid=bb_hd"
Error :
![Image](https://private-user-images.githubusercontent.com/40965289/408099299-294f7791-3b6b-4551-801e-dd84afcf91b6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNjk2NTQsIm5iZiI6MTczOTE2OTM1NCwicGF0aCI6Ii80MDk2NTI4OS80MDgwOTkyOTktMjk0Zjc3OTEtM2I2Yi00NTUxLTgwMWUtZGQ4NGFmY2Y5MWI2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDA2MzU1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTU2ZjViODAwZDUzMzJjNzJlZjAyNjY4MjNkN2Q4YmE2ZDZkMGQ3Mjc1MWU3NzZmZTQ4Y2Y2YjZjM2E2N2U5NDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.7I2ZX-I6nSHkpee09-ehW7hTO80N8-paQz93kAKm6zM)
[error] 792#792: *1035 invalid TS sync byte while reading data, client: 127.0.0.1, server: 0.0.0.0:8002
The text was updated successfully, but these errors were encountered: