-
Notifications
You must be signed in to change notification settings - Fork 100
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
[Support request] Yi Pro 2K Home YFUS 12.0.51 #753
Comments
Please, send me a copy of the frame buffer. |
Please see the buffer attached. |
I can confirm that y623 should work. |
Hi, this image worked, thanks. I think you can add this camera version to the list of supported devices. |
I had the same problems with this cam, i have solve my problems after i have formated my sdcard with "EaseUS Partition Master" and use Fat32 and GPT, after that my cameras worked fine |
Hi, have same model but ZFUS, it seems to work, but it has many restarts during work, mostly when I try to access preview(rtsp/onvif). Does same firmware should work without issues on this device? UPDATE: |
Hello |
Which firmware version? |
Is this question for me..? :) |
Yes, tell me the fw version that appears in the app. |
Thanks. 12.0.51.0_202303091901 |
Try y623. |
well it works but gives me a fish eye image... so it is not really good |
Is the image different from the one in the app? |
it is the same.. :( I dont understand why. |
….now I am. not able to reach the admin site. Can this be because of the se card? |
Maybe |
Hello
I changed the card. Sometimes the picture gets pixel. At the same time I
get notification from home assistant and that photo is ok. The view in
motioneye is also pixeled. Then sometime it is ok. Any suggestion?
Thanks
|
If the image quality is the same as in the app it is probably a camera problem. |
Hi sorry for late reply, i Just used firmware for Y vesrsion but doing preview through rtsp or onvif I get pixels sometimes, need to either restart or open app few times.. |
Please. |
Base version is: |
Please, wait for the next release. |
There can be many reasons for this problem.
Please, try if this beta is better: |
Hey @roleoroleo I tried the one above with both 12.0.51.01_202303091901, 12.0.51.04_202311171457 and card formated through app but camera record is freezing a loot, same goes for RTSP stream. If there's anything I could provide to get this tuned, just let me know! Cheers. |
Please, send me a copy of the buffer /dev/shm/fshare_frame_buf |
count=1; version="12.0.51.04_202311171457"; model="YFUSY94"; while [ $count -le 9 ]; do cat /dev/shm/fshare_frame_buf > "/tmp/${version}_${model}_fshare_frame_buf_${count}"; count=$((count+1)); sleep 5; done fshare_frame_buf.zip (both fw) Size is different between firmware versions. Executed on both, 9 files each. |
The frame buffer is ok and supported, both for 12.0.51.01 and 12.0.51.04. The log shows a problem near time 1705403439422, but I don't understand the type of problem. |
Looks like the issue is present on both streams
|
very very strange. |
I don't remember exaclty but it's near the standard MTU ~ 1500 bytes.
|
@roleoroleo between cam and go2rtc. those are the packets sent from the camera |
Then the size of the packet should not be greater than 1500... |
@roleoroleo I just checked my openwrt router configuration and MTU is set to 1500. This is indeed strange, because the camera should have a MTU of 1500 for the wifi interface: That said i really don't think this is a network issue. The HD streams works, only the LOW stream is corrupted. Other then that, the issue is only visible when playing trough the web browser. Playing the stream through VLC doesn't show issues. Thank you for helping me investigating! |
ok I think that Windows TCP/IP stack is messing with the packets length by assembling multiple packages. I repeated the network capture by running tcpdump on the camera itself and no more strange frame sizes are present: I'm not seeing anything strange from a network point of view. Do you have other ideas? thank you |
Ok, now the dump is ok. When you play the stream with vlc, is the path of the packets the same? |
@roleoroleo yes absolutely. The only change is in the software, vlc instead of web player through go2rtc |
I don't understand... |
@roleoroleo fshare_frame_buf.zip Sure, here it is. Is the frame_buf the same for HIGH and LOW resolution? because HIGH resolution works. Thank you |
It's the same buffer for both streams. |
@roleoroleo do you want to connect to my PC to investigate in real time? I'm available today the whole day. I sent you an email, thank you |
@roleoroleo just tried with the "-s" option and it works!! |
Maybe your model uses a different framerate. |
I think so... Why the sps overwrite is on by default? Is there anything wrong with using the sps provided by the camera in the frame buffer? |
No, nothing wrong |
Great thank you! Why hidden though? |
thank you!!! any chance you can fire a build so I don't have to setup the building system? |
A new release is coming... |
Great thanks. If you still want to publish a beta I will be glad to test |
Too late :) |
ahah :D thank you!! |
You will find a new parameter in system.conf: |
@roleoroleo tested and it works like a charm! Thank you and have a nice weekend! |
Thank you for the update @roleoroleo. Wanted to test the new mode, but had a problem with it: If I change the RTSP Server Program to go2rtc, save i, reboot the cam and go to the config page it shows me that standard is choosen and not go2rtc. Is this only a GUI problem or can't I really change to the go2rtc program? Audio is choosen as aac with the current version 0.3.3 |
Try to clean the cache of the browser. |
Tried with 3 different browsers :/ Can I check the choosen program in the console? |
Hi, I have a Yi Pro 2K Home
For curiosity I tried to apply the hack with y623. It kind of works (Web Interface, SSH, ...) but I have some problems with the RTSP streams. Low quality stream sometimes works, but not very stable, the high res stream does not work at all. Is there any advice what I can try to get this model running? Thanks for this great work!
The text was updated successfully, but these errors were encountered: