Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FFmpeg (RTMP, SRT) #67

Open
ievgeniilarin opened this issue Mar 2, 2022 · 9 comments
Open

FFmpeg (RTMP, SRT) #67

ievgeniilarin opened this issue Mar 2, 2022 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@ievgeniilarin
Copy link

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
Copy link
Owner

rse commented Mar 22, 2022

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

@rse rse self-assigned this Mar 22, 2022
@rse rse added the bug Something isn't working label Mar 22, 2022
@rse
Copy link
Owner

rse commented Apr 3, 2022

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
Copy link
Owner

rse commented Apr 3, 2022

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
Copy link
Owner

rse commented Apr 4, 2022

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.

@rse rse closed this as completed Apr 4, 2022
@ievgeniilarin
Copy link
Author

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

2022-04-13 13_36_00-Window

@rse
Copy link
Owner

rse commented Apr 13, 2022

This problem is under Windows?

@rse rse reopened this Apr 13, 2022
@ievgeniilarin
Copy link
Author

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

@rse
Copy link
Owner

rse commented Apr 14, 2022

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):

image

Hmmm...

@rse
Copy link
Owner

rse commented Apr 14, 2022

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants