FFmpeg (RTMP, SRT) - Githubissues

rse / vingester

Ingest Web Contents as Video Streams

https://vingester.app

GNU General Public License v3.0

187 stars 16 forks source link

FFmpeg (RTMP, SRT) #67

Open ievgeniilarin opened 2 years ago

ievgeniilarin commented 2 years ago

I've tried the current version of VIngester (WIndows 10) and I've not managed to send neither RTMP nor SRT.

I haven't found the FFmpeg console output for more specific errors.

rse commented 2 years ago

I've not tried FFmpeg output for some time myself, so I've to check this.

rse commented 2 years ago

I can confirm that FFmpeg support is currently broken. I'm also not able to record or stream with FFmpeg. I'm already debugging it, but it looks strange: FFmpeg is started and gets data, but doesn't write or stream anything. I've to dig deeper...

rse commented 2 years ago

Ok, I've already found out an issue: if the FFmpeg configuration has an audio stream, but the Web content does not deliver any audio, FFmpeg waits forever for the interleaved audio fragments and as a result does not write anything at all. By disabling the audio streams (OUTPUT 2 / Headless / AUDIO / Channels: 0) FFmpeg correctly seems to work.

rse commented 2 years ago

Ok, the FFmpeg support will be now fixed in the new Vingester 2.8.0. Please re-open this issue if you still have problems with FFmpeg even in this or higher versions.

ievgeniilarin commented 2 years ago

I'm still having issues with ffmpeg. Vingester becomes unresponsive after activating ffmpeg.

2022-04-13 13_36_00-Window

rse commented 2 years ago

This problem is under Windows?

ievgeniilarin commented 2 years ago

Yes, I'm running the app on Windows 10.

rse commented 2 years ago

I've currently no more Windows 10 available, but under my Windows 11 PC where I do regular Vingester tests, your exact configuration worked just fine and did not made Vingester unresponsive (at least with the latest snapshot from HEAD):

Hmmm...

rse commented 2 years ago

Oh, I at least see one part of your problem: when I try to stop the browser, it does not stop and I have to stop it twice. So, yes, there is something under Windows which I do not see under macOS (where I develop Vingester). I've to investigate further...