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
Hi, I have been using DVBLast in a production environment for the last few years, great software and super stable.
I am demultiplexing a MPTS udp source and sending the individual demuxed programs to local ffmpeg instances for further processing via udp, all works ok and it has been working fine for the last few years. The problem I always have had is that whenever I have to restart the ffmpeg instances the log is full of messages like this:
error: couldn't writev to 192.168.3.201:2500/udp (Connection refused)
The messages are produced at a rate of 5 per second, so, since the MPTS has 6 channels and the ffmpeg takes a few seconds to restart whenever that happens the log is filled with 100 to 150 log lines with the same message, I have tried all -quiet options and the message always appear.
Is there any way to avoid "error: couldn't writev to....." messages being produced or decrease the frequency of them?
Thanks in advance.
Salva.
PS: DVBLast versión being used is DVBlast 3.4 (release) and OS is raspbian (Ubuntu) on a Raspberry PI 3B+
The text was updated successfully, but these errors were encountered:
salvaaod
changed the title
Avoid messages "error: couldn't writev to 192.168.0.10:1234/udp (Connection refused)"
Avoid messages "error: couldn't writev to local_ip:local_port/udp (Connection refused)"
Oct 12, 2020
The way you are currently doing it, when there is nothing listening on 192.168.3.201:2500 you are getting the errors.
A better way is to send the output to multicast address. An additional extra by using multicast is that you can have multiple subscribers and even if there are no subscribers dvblast would be able to output the stream.
Hi, I have been using DVBLast in a production environment for the last few years, great software and super stable.
I am demultiplexing a MPTS udp source and sending the individual demuxed programs to local ffmpeg instances for further processing via udp, all works ok and it has been working fine for the last few years. The problem I always have had is that whenever I have to restart the ffmpeg instances the log is full of messages like this:
error: couldn't writev to 192.168.3.201:2500/udp (Connection refused)
The messages are produced at a rate of 5 per second, so, since the MPTS has 6 channels and the ffmpeg takes a few seconds to restart whenever that happens the log is filled with 100 to 150 log lines with the same message, I have tried all -quiet options and the message always appear.
Is there any way to avoid "error: couldn't writev to....." messages being produced or decrease the frequency of them?
Thanks in advance.
Salva.
PS: DVBLast versión being used is DVBlast 3.4 (release) and OS is raspbian (Ubuntu) on a Raspberry PI 3B+
The text was updated successfully, but these errors were encountered: