Re: [mistserver] Digest for mistserver@googlegroups.com - 1 update in 1 topic

13 views
Skip to first unread message

Bart Jenniskens

unread,
Jul 3, 2025, 3:58:07 PMJul 3
to mists...@googlegroups.com
Hi Vietor,

Much appreciated for the swift response and advice. I now understand the Process part also better. 

I've moved the command to the Push panel part. The only change I see is that "Date transferred" stops growing after 14.4 Mibytes is reached. Also the file on the FTP server won't grow anymore. This was not the case when I configured it wrong as a Stream Process, the file kept growing until the stream started. 

Are there any limits that may cause this? What may cause it to stop pushing data over 14.4 Mibytes? 

Trial 1:
image.png
Trail 2:
image.png

Regards, 
Bart

On Thu, Jul 3, 2025 at 12:58 AM <mists...@googlegroups.com> wrote:
Balder Vietor <balder...@ddvtech.com>: Jul 02 12:55PM +0200

Hey Bart,
 
You're close, but at the wrong place to set this up.
Instead of using a stream process you'll want to set this up as an
"Automatic push".
Automatic pushes are meant to start when a stream comes online and if no
start/end is given stay active for as long as the stream is active.
Stream processes are meant to ingest back whatever the process is starting
as Matroska and then add this to the stream. So MistServer is not doing
anything there as it's ingesting the log messages of FFmpeg and determining
this is not video.
 
At the Push panel to the left, create an automatic push:
[image: image.png]
 
mkv-exec will work in a similar fashion as the stream process version of
mkv-exec. It will send Matroska stream data to the standard in of whatever
application is launched right after the :. So you'll most likely want to
use the following push target:
 
mkv-exec:ffmpeg -loglevel quiet -hide_banner -fflags nobuffer -i - -c:v
mpeg2video -b:v 50M -minrate 50M -maxrate 50M -bufsize 1M -c:a pcm_s16le
-ar 48000 -ac 2 -f mxf ftp://IPADDRESS/output.mxf
<ftp://ipaddress/output.mxf>
 
Note that there's currently an issue that bash-styled argument quoting
isn't implemented. This will be in the upcoming release and development
builds already support it. This roughly means that if you're using a ' or "
it will fail unless you use a script that then runs the command. You'd have
to do:
mkv-exec:/path/to/script
in that case.
 
Best,
 
*Balder Vietor* | Supreme tester
*e:* balder...@mistserver.org
 
 
 
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to mistserver+...@googlegroups.com.

Balder Vietor

unread,
Jul 4, 2025, 6:30:59 AMJul 4
to mists...@googlegroups.com
Hey Bart,

There shouldn't be anything from our side limiting the the upload, so perhaps it's best to double-check a few things. 
One thing of note though: The bytes transferred is not how much is pushed out. It's how much has been pushed into the FFmpeg process. For MistServer the output is the FFmpeg process, whatever FFmpeg then pushes towards the FTP server is not something we can measure, I would after all severely doubt that  ~40seconds worth of the settings you're recording in your script would only be 14mb. I'd expect that to be much much higher.
So this is hinting that the FFmpeg process isn't getting stream data from MistServer because either FFmpeg or MistServer ran into an issue.

- Are there any messages from the FTP server in the log? Perhaps it's reporting a rejection or a time-out? That could explain whether ffmpeg stopped as the output is no longer active.

- Using manual pushes will also possibly shine some light on where the issue is.
   - You can do this with the following command in a terminal (do note that you need to be the same user as MistController, so root if you're running it as a service): 
MistOutEBML -g 6 -s STREAMNAME "mkv-exec:ffmpeg -loglevel quiet -hide_banner -fflags nobuffer -i - -c:v mpeg2video -b:v 50M -minrate 50M -maxrate 50M -bufsize 1M -c:a pcm_s16le -ar 48000 -ac 2 -f mxf ftp://IPADDRESS/output.mxf"
This command would start the same push, but raises the debug level allowing for more information in the terminal. So there's a good chance you'll see something that might explain the sudden stop. If the debug information is too spammy try changing the "-g 6" part to "-g 4". If messages suddenly stop or you're seeing a log of FAIL/Warn messages or something that mentions disconnected (possibly at INFO) that would be something to look out for. When in doubt you can always log all the output towards a log file and pass that along, but note that your FTP server, possibly your server address and stream names that you want to keep private would be in there, so remove any such information before sharing!
(To write it to a log fill add 2> /tmp/mist.log to the end:
MistOutEBML -g 6 -s STREAMNAME "mkv-exec:ffmpeg -loglevel quiet -hide_banner -fflags nobuffer -i - -c:v mpeg2video -b:v 50M -minrate 50M -maxrate 50M -bufsize 1M -c:a pcm_s16le -ar 48000 -ac 2 -f mxf ftp://IPADDRESS/output.mxf" 2> /tmp/mist.log
)

You can also see if it's the FFmpeg process giving an error, that would be slightly different syntax:
MistOutEBML -s STREAMNAME - | ffmpeg -fflags nobuffer -i - -c:v mpeg2video -b:v 50M -minrate 50M -maxrate 50M -bufsize 1M -c:a pcm_s16le -ar 48000 -ac 2 -f mxf ftp://IPADDRESS/output.mxf"
This will throw the ffmpeg messages in your terminal as well, so if ffmpeg gives an error you'll be able to see it.

- The last thing to check would be whether you see any changes if you tell ffmpeg to record locally. Simply change the "ftp://ADDRESS/output.mxf" part to something like "/tmp/test.mxf" and see if that stops around the same mark.
If this works it would hint the problem being between FFmpeg and the FTP server, but somehow not logged by either.

Best,

Balder Vietor | Supreme tester



--
You received this message because you are subscribed to the Google Groups "Mistserver.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mistserver+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/mistserver/CAAuYGW%2BkzhTTMpDELMisrarZWaJBd2-G-pPboOtFFnREvJnSYg%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages