-
Notifications
You must be signed in to change notification settings - Fork 119
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
Wyze V3 go2rtc frame link fails #632
Comments
from what I can tell from the go2rtc docs, |
According to this comment on go2rtc, as of v1.5 it should automatically transcode to jpeg from the first stream, it doesn't have to be an mpeg source.
|
our ffmpeg is compiled without jpeg support, i'll take a look |
ok this seems to be fixed in the latest go2rtc, i'll update it soon. |
Great! I'll wait for the next release to test further. |
latest master includes the new version of go2rtc. |
@vfilby can you confirm this is fixed? |
So, it doesn't seem to be working for me. When I try to hit the jpeg frame link, here is the logs from go2rtc. I have included the go2rtc logs and some version sanity checking below to make sure I am not doing something completely wrong.
go2rtc config:
Couple checks to make sure I updated the software correctly:
|
go2rtc updated to 1.8.5, is this still happening? |
I can't check I had to reuse this camera elsewhere offsite and I won't have access to it for a few months. |
I am running go2rtc 1.8.5 and the frame.jpeg does not work for me |
** ignore |
Using go2rtc, the links to get a jpeg frame return a 500 error, and the following error in the go2rtc log. Reading up on go2rtc it looks like it should just grab the first stream and transcode, but I am not knowledgeable enough about either go2rtc or ffmpeg to start tweaking values.
Te error message suggested increasing the analyze and probe durations so I tried 500 instead of 50 and that didn't change the results.
Anyone else experiencing this problem? Any potential solutions or leads?
Relevant wz config:
The text was updated successfully, but these errors were encountered: