5 ms·
Don't go leaving it exposed if you connect it up to the venue's WiFi, if you're playing live. ;)
by mr_sturd 4y ago
Don't go leaving it exposed if you connect it up to the venue's WiFi, if you're playing live. ;)
- worik 4y agoDon't run wifi and real-time software at the same time.
- deleted 4y ago[deleted]
- zamnos 4y agoWhat wireless technology would you recommend instead then?
- worik 4y agonone, of course
- zamnos 4y agoLol ok. Meanwhile the rest of the industry is moving on. I mean, how do you even do an wired connection to a drone? A lot of times guitarists will perform on a stage and the clients wants aerial views without the cost of a crane. Do you just tell them you can't do it and have them go with a different company?
- pdntspa 4y agoWith special nonstandard proprietary wireless protocols is the answer you're looking for. The same shit wireless stage mics use. Or control over cellular data. I can guarantee you they aren't pairing them to a 802.11 router. Lol ok.
- bacon_waffle 4y agoI'm a little confused by this thread - it seems like you suggest that the drone should be controlled by the SBC in an effects pedal, that the guitarist is using to provide low-latency audio processing? As a techie and perpetual-intermediate musician, that seems a bit odd... But, incidentally, at my day job I'm working on an embedded Linux system where audio latency matters, and which may well wind up with a WiFi radio (where latency probably doesn't matter so much). So, I'd like to understand issues in this space.
- darkwraithcov 4y agoThe core audio driver does a pretty good job with this.
- mr_sturd 4y agoThe only signals going over WiFi here would be controls for the virtual pedals.
- jcelerier 4y agoJust the beacons you get from other routers around can be enough to create disturbances
- mattkrause 4y agoUsing wifi to trigger real-time software is often a bad idea, but using it to configure responses to future triggers isn’t necessarily so bad.
- rerdavies 4y agoThe Raspberry Pi 4 has separate USB hubs: one for WiFi and ethernet (an internal hub), and another for external USB ports. The USB port service loop will run with higher priority, so there doesn't seem to be any serious adverse affect. The same isn't true for SD card access, which does cause dropouts. I've seen a video that suggests that disabling power management for the SD card hardware will correct the problem -- specifically that changing power state causes a 3ms delay. But I'm not quite sure how to go about disabling that on a Raspberry Pi OS. . WiFi doesn't seem to affect audio latency. That's not true for Raspberry Pi 3, where WiFi and USB ports do run on the same USB hub.
- giantg2 4y agoAudience participation show.
- Our_Benefactors 4y agoI had sketched an idea for a web ui that would talk to a VCV instance, outputting signals to a real eurorack device with an expert sleepers module… need to keep hacking on that.
- deleted 4y ago[deleted]
- 867-5309 4y agoDefCon Big Band