Automatic push of stream writes no more than 620 or 621 bytes

[Michel Hageman]

Hello all, 

I'm using Mistserver 3.3 with an automatic push on a stream when active, that is pushing to a directory on the same server as Mistserver is running on. Previously there was no problem and the pushes/recordings were fine. But now it only writes 620 or 621 bytes and then quits the push. The stream is happily running, but no push anymore! 

What to do?

Thanks in advance!

Michel

[Balder Vietor]

Hey Michel,

I think I'll need a bit more information:

- What is your input protocol? (rtmp push, rtsp pull, srt pull, srt push, etc)

- What are the incoming push codecs? 

- What format are you recording in?

- Do you get any specific log messages about your stream/recording?

You should be able to get the log messages with the following command if it's running as a service:

journalctl --since=-1d -u mistserver |grep STREAMNAME

I'm not aware of any issues with recording, but it sounds like we might've missed something. I assume it also doesn't auto-restart?

With kind regards,

Balder Viëtor
Head of Testing

MistServer

--
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 on the web visit https://groups.google.com/d/msgid/mistserver/981638a6-70e3-4322-9b2c-b5d3bdef4dban%40googlegroups.com.

[Balder Vietor]

Hey Again,

I think I actually found it, you're most likely receiving a RTMP push stream and recording in MKV?

It seems we introduced an issue if a JSON track is present and with RTMP streams now showing the AMF data that seems to be most rtmp pushes. I'll see if I can figure this one out. 

In the meanwhile you should be able to bypass the issue by adding "?meta=none" to the end of your record path, that should tell MistServer to ignore the metadata track.

Example, instead of:

/tmp/my_stream_recording.mkv

use

/tmp/my_stream_recording.mkv?meta=none

With kind regards,

Balder Viëtor
Head of Testing

MistServer

[Michel Hageman]

Thank you so much Balder! I'll give it a try!

Op do 18 apr 2024 om 10:13 schreef Balder Vietor <balder...@ddvtech.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/mistserver/CAKPFDa0iRLb2c%2B-LR9%3DUBRsCXMmo75erBYgi5Q8cbgEgGxd10A%40mail.gmail.com.

[Michel Hageman]

And yes! These are indeed my settings. RTMP-input and a push from the stream to *.mkv. If I append the ?meta=none then everything is working again!!

Op do 18 apr 2024 om 14:35 schreef Michel Hageman <mhag...@gmail.com>:

[Balder Vietor]

Hey Michel,

Yeah sorry about that. I'll get that fixed for the next release, you wouldn't need the ?meta=none after that again. It's a bit of a silly mistake on our end 😅

With kind regards,

Balder Viëtor
Head of Testing

MistServer

To view this discussion on the web visit https://groups.google.com/d/msgid/mistserver/CAEb0UUAHJjsvwE%2BnboL_ojxBiuHYJPY%3DWdhAn3RL4nPZiMfi8Q%40mail.gmail.com.

[jammin radio]

I’m using Push 3 streams to multiple push destinations - 

How do I add SSL config for ngix please 🙏🏻 

To view this discussion on the web visit https://groups.google.com/d/msgid/mistserver/CAKPFDa2fxLBdmJB%3DUJYpq8LM4a9KPi-nMZK_rsdkqgJrTTu03Q%40mail.gmail.com.