-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
No auto start, unless ssh? #355
Comments
Hello. I will try to fix that in future updates, for now try this workaround. |
So I looked at that yes, where would i find the crontab? |
Type: |
Thanks bro u respond so quickly |
Just press CTRL + C |
Ok |
Socket listening on: 192.168.1.185:8765 |
Am i missing a requirement? |
Are you trying to run script manually now or are those logs from the start-on-boot script? |
Start on boot |
Then don't worry about it. If it's the same case as in the other issue, then it's an error caused by the script trying to run before getting a wifi connection. It can be temporarily fixed by adding a delay to the script's start. |
Ohhh, it could possibly be from the sudo python3 /home/piano etc. start script that i left in profile |
Yea thats what it was |
I have a idea, i was using a synthizer that was for raspi and it was headless, it would be awesome if you could combine the synth with the plv, and have a soundfont menu, the installation was one command and was fast, i can send you a link |
Hello, I have created a specific systemctl service in /usr/lib/systemd/system like this one and it works fine on my side: pi@raspberrypi:/usr/lib/systemd/system $ cat piano-visualiser.service [Install] [Service] and then enable it :
|
Hello! In the new PlV 1.3 update, the autostart is no longer working, i know how to manually start it and it works, but when i put the sudo python3 /home/Piano-LED-Visualizer/visualizer.py & in etc profile, it does not start, but when i ssh into it, it automatically starts up and the menu is shown with no commands entered, and if i close the ssh window, it stops working, how can i fix this?
The text was updated successfully, but these errors were encountered: