Good afternoon can anyone tell me how to use https://github.com/quiniouben/vban, i have got it sat in the downloads folder on a brand new raspberry pi3 and really want to be able to do it before I do my next filming next monththanks hex_1

I won't answer for the Voicemeeter author, but the application you downloaded is (probably) written by a different person. You have to approach them (or the community associated with them) for support for that open-source program. Some communities are really good and will help you as best they can, and the software looks like a good idea.

If the actual situation is different, then the VoiceMeeter author can correct me. (I'm used to that... heh.)

Hi all, @hex_1 : this is a correct place, or alternatively, you can open an issue in the github project.To have a better idea of the trouble, you could try to add -l4 option to your command line.That you have an alsa_read error may tell us the configuration you are trying to use, your device cannot support (48kHz, mono, 16bit (default)).Could you check if you can open this device with aplay and same configuration ?That you reach a Seg fault is very unexpected : have you cross-compiled or compiled directly on the raspberry pi ?Anyway, we will find a solution.

i compiled on the same pi i have added -l4 and it is giving this error [ Info: socket_open: opening socket with port 6980Info: socket_open with port: 6980Info: audio_init: config is direction in, backend alsa, device , buffer size 1024Info: audio_backend_get_by_name: found backend alsaInfo: audio_set_map_config: new map config is nb channels 1Info: audio_set_stream_config: new stream config is nb channels 1, sample rate 48000, bit_fmt 16IFatal: alsa_open: open error: No such file or directoryError: audio_set_stream_config: could not open backend with new config]hope this means something to youthanks hex_1

Sorry for delay, I forgot to enable notifications.Well, at least, it is more fair, it tells you it cannot open the device. Then it could be something like there is no device defined as default in your alsa configuration.One way to test this idea would be to use the exact device name with option -d.To get the device name "arecord -L" is a good tool.

Hi,So, it seems to confirm the lack of defined default device, as if I do the same on my PC I have the following at the bottom of this message, where default is having a description and says which is default.I would start trying with "-d sysdefault"