Ted Potma comments

Results 99 comments of


                                            Ted Potma

No HSKV -Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.

@GreatWiz: I edit the plugin code on my laptop, then after an `npm run build` I deploy it to my rPi using scp. Note that on your rPi you'll need...

No HSKV -Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.

@iknowdjz : Any insight you can offer would help. I can't reproduce this issue myself, and I have no idea what the reason some people experience it is. ffmpeg supports...

No HSKV -Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.

@iknowdjz: That is odd. I don't know why that would be the case... I'm not sure if that's having an effect or not.

No HSKV -Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.

Try version 1.1.21 and see if it solves the issue. Thanks to @PatrickStankard for (hopefully) providing the solution.

No HSKV -Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.

@iknowdjz: Are you still getting the stdin error on the live streams?

No HSKV -Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.

@iknowdjz : Debug mode would definitely help, from when you try to view the live stream.

No HSKV -Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.

@iknowdjz : There are no errors in your logs, the plugin seems to be working fine. Looks like the packets are simply not arriving at your iPhone/Mac/etc. This can happen...

No HSKV -Failed to start stream: input to ffmpeg was provides as stdin, but the process does not support stdin.

Closing as the underlying issue about stdin seems to be resolved.

Raspberry Pi 5: FFmpeg exited with code: null and signal: SIGSEGV (Unexpected)

Try turning on debug mode in Homebridge settings. This is FFmpeg itself crashing because it's running out of memory or performing some illegal operation. Not sure what's causing it. Did...

Raspberry Pi 5: FFmpeg exited with code: null and signal: SIGSEGV (Unexpected)

Well, ffmpeg is there.... the HB RPi image should be fine. For some reason it's getting a segmentation fault and quitting.... I'm afraid from here I really have no idea...