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

Usb grabber does not work most of the times. #742

Closed
GhostgamesDHG opened this issue Jan 21, 2024 · 6 comments
Closed

Usb grabber does not work most of the times. #742

GhostgamesDHG opened this issue Jan 21, 2024 · 6 comments

Comments

@GhostgamesDHG
Copy link

Y

Hyperhdr doesnt see the USB grabber and I can see it in the ssh screen. So whats going on?

LOG
--> https://pastebin.com/qTdD1t5r

Steps to reproduce

What is expected?

For the system to find the usb graber normally

What is actually happening?

Most of the times it cant find my usb grabber. And in the ssh log I can find the grabber, but in the hyperhdr web interface not.

System

HyperHDR status:
On
Platform:
Linux (V4L2)
Video device
Video mode
Controller type:
wled
Instance:
hometv
Your HyperHDR version:
20.0.0.0beta1
Latest HyperHDR version:
v20.0.0.0beta1

@GhostgamesDHG
Copy link
Author

apparently if I restart hyperhdr it shows.
LOG https://pastebin.com/qbm4dT4V

How can I get this automaticly, because this system will not be for me so I cannot leave it like this.

@awawa-dev
Copy link
Owner

Hi
1 normally such a message means that the user does not have permissions, but if it works later, it is probably not the case
2 Your SD card/disk is dying which is causing a very slow loading of a key OS module (v4l)
3 You are using a grabber that is causing problems in this module

You can find more in dmesg. This is not a HyperHDR problem and diagnosing it in each specific case is a nightmare (a similar issue comes back once a year, last time it was probably caused by some fake UTV 007): I am not taking up this topic.

@GhostgamesDHG
Copy link
Author

Hi 1 normally such a message means that the user does not have permissions, but if it works later, it is probably not the case 2 Your SD card/disk is dying which is causing a very slow loading of a key OS module (v4l) 3 You are using a grabber that is causing problems in this module

You can find more in dmesg. This is not a HyperHDR problem and diagnosing it in each specific case is a nightmare (a similar issue comes back once a year, last time it was probably caused by some fake UTV 007): I am not taking up this topic.

Hi, me again I want to inform you about this topic. I have now 3 raspberry pi zero ws running hyper hdr. I have 2 captures. The thing I noticed was that none of the raspberry pis found the 2 grabbers. It did only find it when I disable and enable usb capture. Then it was there. Now I have 1 system running hyperion and It found both instantly. No problems with hyperion. So how can it be my hardware thats the problem. If I need to believe you I have 3 raspberry pi zero`s that will die. And that both of the grabbers are fake. How can It be that hyperion uses it instantly? This means that this is a software issue on yor software. So please reconsider. Maybe the usb grabber scanning needs to be delayed a little time.

@awawa-dev
Copy link
Owner

Not planned. The main key is to start HyperHDR as soon as possible, without any delay. Similar to shut it down. If some other software takes longer to start-up (and it's actually an unwanted side-effect and not intentional) then maybe it might actually work in your case. You can always delay service start-up by modifying the HyperHDR service file and adding any delay you want.

@awawa-dev
Copy link
Owner

Service file:
/etc/systemd/system/hyperhdr@.service
add to service section:
ExecStartPre=/bin/sleep 30
Apply changes:
sudo systemctl daemon-reload

@GhostgamesDHG
Copy link
Author

Service file: /etc/systemd/system/hyperhdr@.service add to service section: ExecStartPre=/bin/sleep 30 Apply changes: sudo systemctl daemon-reload

Thank you, I will try this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants