-
Notifications
You must be signed in to change notification settings - Fork 39
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
Raveloxmidi on raspberry pi zero w #68
Comments
Sorry you're having problems. Can you attach the debug log output for when this happens? There are a couple of possible explanations. Secondly, and this is something I'm working on trying to fix, the MIDI messages are coming in quickly but get split between 2 packets. This can cause raveloxmidi to go into a tight loop and that locks everything up. Thanks Dave |
Hi Dave, Cheers, |
Hi Dave, I played with the minimum delay between the midi messages sent to Raveloxmidi and managed to find a reasonable latency with sleep(0.007). I also added the heartbeat message (once a minute) I send from my python controller to iOS and Macbook apps via Raveloxmidi and so far it was working for 5 hours without dropping the connection. Thanks a lot for Raveloxmidi again! Cheers, |
By the way, thank you |
Right now, inbound MIDI messages to raveloxmidi are written to the file defined by the "inbound_midi" configuration option. What application are you thinking of sending the messages to? |
Hi Dave, network.control.port = 5004 ff . ff . 43 C 4b K e5 . 3d = 9b . 3b ; |
Thanks for that. I've just pushed a fix in the master branch. Version number should now be 0.8.2 |
Hi Dave,
I was using the older version of Raveloxmidi with the old version of my controller for couple of years with no issues at all as far as I remember.
I put raspberry pi zero w inside of the fcb1010 foot controller and convert the incoming midi messages into mapped midi signals for 4 different processors running on my macbook and iPad.
I decided to make things better and wrote the new version of my controller. I saw you message about the new improved version of Raveloxmidi and installed it on Raspbian Buster.
Unfortunately now with the new version both of my devices got disconnected from Ravelox every few minutes and I can't see any reason for that in a log file when running Ravelox in debug mode.
Did you try to run Ravelox on Raspbian Buster ?
I saw your post about raspberry pi zero w but for me when it's working there is no much latency at all. The MIDI messages for Volume pedals reach the processors with the amazing speed.
The only problem is with the dropped connection. Both my devices loose the connections at the same time when it happens.
Could you please help me to find the solution for my problem ?
This is the response for the status of the Ravelox service after both my devices lost connection
sudo systemctl status raveloxmidivp.service
● raveloxmidivp.service - RaveloxMidi.VP
Loaded: loaded (/etc/systemd/system/raveloxmidivp.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-03-06 21:55:37 AEDT; 31min ago
Main PID: 793 (raveloxmidivp)
Memory: 492.0K
CGroup: /system.slice/raveloxmidivp.service
└─793 /usr/local/bin/raveloxmidivp -N -c /usr/local/bin/raveloxmidi.conf
This is the response to running Ravelox in debug mode:
sudo /usr/local/bin/raveloxmidivp -N -d -c /usr/local/bin/raveloxmidi.conf
network.control.port = 5004
network.data.port = 5005
network.local.port = 5006
network.socket_timeout = 30
network.max_connections = 8
service.name = raveloxmidivp
service.ipv4 = yes
service.ipv6 = no
run_as_daemon = no
daemon.pid_file = raveloxmidivp.pid
logging.enabled = yes
logging.log_level = debug
security.check = yes
readonly = no
inbound_midi = /dev/sequencer
file_mode = 0640
discover.timeout = 5
sync.interval = 10
network.read.blocksize = 2048
config.file = /usr/local/bin/raveloxmidi.conf
network.bind_address = 0.0.0.0
The text was updated successfully, but these errors were encountered: