-
Notifications
You must be signed in to change notification settings - Fork 18
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
ERROR: FFmpeg exited with code 1 #65
Comments
This means your ffmpeg is unable to stream. Could you post your log here? |
{ i cant retrieve my log info atm, it said something like ffmpeg type 1 or something like that. It gave an error code. |
Ok, first of all "videoProcessor": should be "ffmpeg" as this is the binary that is used to stream (and not "High-Performance Embedded SOC Processor"). |
[6/9/2020, 12:44:20] [Video Doorbell] Snapshot from Front Door at 480x270 ive changed the "videoProcessor" to "ffmpeg" BTW |
Ok, I am assuming that your snapshots work. As you are using h264_omx codec please make sure that your user that is running homebridge is allowed to use grafix hardware. |
it says that there is a snapshot but i do not get one in the home app. Also please explain to me what you mean about the grafix hardware. What is it ? etc Thanks for helping BTW, sorry for any inconveniences caused im a bit of a noob! |
As h264_omx codec uses gpu to increase performance the user that is running homebridge has to be allowed to use the graphic hardware of your system. Many cams provide a url to get a pic from the cam. This url can be tested by opening in your web browser. Optional "stillImageSource" parameter should point to this snapshot url of your cam. Also, after changing config parameters it is better to remove the doorbell and add it as a new doorbell with a different name to your home as homekit remembers configuration parameters and changes may not be recognized. |
I am experiencing the same issue. Could this be related to a recent Raspberry pi OS update? Maybe a recent ffmpeg update?? If not a recent plugin update impact. I am using the following config with my camera:
I am getting the following when running
|
@dikodahan I found that error was due to the version of ffmpeg being used. The plugin uses a packaged version that comes with it instead of the system version. I was able to resolve by uninstalling system version and the plugin, and re-installing just the plugin. Also @dikodahan were you able to somehow get notifications working with your August doorbell? |
I have no clue why, but I'm having the same issue. I never installed FFMPEG with HomeBridge, as I knew this plugin had it built-in. It will work for a few minutes, then constantly crash with code 1. And notifications when the button pressed don't work. If I manually click the button accessory platter inside the home app it will work, but not when the doorbell button is physically pushed. |
I have the same problem. Using "homebridge-videodoorbell" there is FFmpeg exited with code 1 error. I have the same stream's URL and vcodec for "homebridge-camera-ffmpeg"- everything works perfectly. Part of my config |
Please make sure that you are using the same ffmpeg version. |
Ummmm what? I never installed FFMPEG only your plugin so make sure I have the same version installed compared to what? |
@spiderguy84, homebridge-camera-ffmpeg comes with a version of ffmpeg. What @Samfox2 suggests is to use that ffmpeg (as it works with homebridge-camera-ffmpeg) in homebridge-videodoorbell as well. In my case I added Beware that my path is under a MocOS system. I do not know if on other systems, it will be the same. |
But what I am saying is that I don't have any other version of FFMPEG to use, so why would I need to tell it to use its own plugin version? |
On which operating system are your homebridge running ? If it is a Linux flavour, you could have some version (not the one used by homebridge-camera-ffmpeg) of ffmpeg installed (in a location referred to by PATH) and this version is used by homebridge-videodoorbell but does not work anymore for some reason. |
Guys. which shows dummy switch for doorbell so fighting with this plugin at this moment is pointless. |
Could you use some English that makes sense? We are talking about FFMPEG, and you bring up dummy switches? |
Synology DS 218+ |
I am also suffering occasional type 1 errors from ffmpeg. Using this plug-in with a HIKvision DS-HD1 and snapshots are showing OK, but live video is dreadful. Any movement in the field of view creates blocks on screen in that area and that can spread to most of the screen. But when first trying to view Live, the window sometimes just stays black and the HomeBridge log shows ffmpeg failed with Type 1 error. These cameras have a strange 1536x2048 resolution, but whatever I put in the config, Homebridge logs show it is trying to stream 1280/720@299kbps. I need to be able to stream at the full resolution but cannot seem to be able to achieve that and half the time ffmpeg just crashes. I have the latest stable version of ffmpeg on the Homebridge server (Mac) and neither this plug-in nor the ffmpeg-camera plug-in (also installed) seem to contain ffmpeg, so presumably it must be using the 'system' one on the PATH (usr/local/bin in fact). If not, which is it using? And why is it crashing and how can I obtain full quality video from this camera? |
Those are the resolutions supported by homekit (from hap-nodejs): All other resolutions can cause issues and need to be transcoded. |
Ok thanks. Looks like I need to figure out the ffmpeg settings to do that. What ffmpeg does this plug-in use? I couldn't find one built-in. Does it just use whatever is available on the PATH? |
Yes, the first ffmpeg binary that is found is used. |
Thanks. I'm presuming I can supply ffmpeg with options to transcode to what I need? |
All this time later and still keep getting ffmpeg crashing with Type 1 error. Nothing I have tried seems to make any difference. But… I set up the same doorbell/camera in 'homebridge-camera-ffmpeg' with minimal configuration and it just works. Try that same config. for this plug-in and again 'Type 1 error'. Since neither plug-in has 'video processor' specified, they must both be using the same ffmpeg (although this plug-in doesn't report the version whereas 'homebridge-camera-ffmpeg' does). So, same config, same ffmpeg, but this plug-in crashes and 'homebridge-camera-ffmpeg' doesn't. Which means this plug-in is throwing options (that we cannot control) at ffmpeg which cause it to crash. Is it still being maintained? Any possibility of looking at what this plug-in is doing to cause this 'currently insurmountable' problem. |
how can I connect a Ezviz dp1c? |
what does this mean?
The text was updated successfully, but these errors were encountered: