-
Disclaimer: This Vendor's Forum is a paid-for commercial area. Unlike the rest of diyAudio, the Vendor has complete control of what may or may not be posted in this forum. If you wish to discuss technical matters outside the bounds of what is permitted by the Vendor, please use the non-commercial areas of diyAudio to do so.
Support for Botic Linux driver
- Thread starter miero
- Start date
If TidalConnect is working into Jack, then let's try eliminating Jack and direct the output of TidalConnect to your default Alsa plug instead of creating a virtual device. The syntax is either:
Code:
(-X or whatever the TidalConnect output option is..) alsa plug:default'
Code:
plug:default
Code:
pcm.!default {
type plug
slave {
pcm "botic-split" # added quotes, which works for me inside brackets
channels 2 # this line should be optional but probably doesn't hurt
rate "unchanged" # same comment as line above
}
}
pcm.botic-split {
type route;
slave {
pcm "hw:0,0"
channels 4
}
ttable.0.0 -1;
ttable.1.1 -1;
ttable.0.2 1;
ttable.1.3 1;
}
pcm.plughw.slave.rate = "unchanged";Obviously, best to not specify any output sample rate in the tidalconnect configuration.
If directing to your default plug doesn't work, then perhaps we can create a new virtual 'card'.
Good luck,
Frank
Tidalconnect does not see "default" and "sysdefault"
Requires hardware emulation of the audio device.
Tidalconnect only sees real devices. Therefore, without loopback, cannot solve this problem.
Code:
Could not find device: 'default'. Fallback to default device
Valid devices are: 'Botic: - (hw:0,0)' 'sysdefault'
Could not find a default playback deviceRequires hardware emulation of the audio device.
Tidalconnect only sees real devices. Therefore, without loopback, cannot solve this problem.
OK then, loopback it is.
Creating a loopback is quite simple. Here is a good link:
Playing with ALSA loopback devices | Playing with Systems
Simply use 'modprobe snd-aloop'. Then use 'aplay -l' to display the card groups available. When things are working to your satisfaction, you can add 'modprobe snd-aloop' to one or another boot script. To list all of the options within each card group, use 'aplay -L', which is also good for debugging the alsa plugs.
To begin, I suggest you direct TidalConnect to plughw:... or dmix:... Once that works then you can try hw:...
One other important suggestion - *never use tabs in alsa plugs*. Only indent using spaces!
Good luck,
Frank
Creating a loopback is quite simple. Here is a good link:
Playing with ALSA loopback devices | Playing with Systems
Simply use 'modprobe snd-aloop'. Then use 'aplay -l' to display the card groups available. When things are working to your satisfaction, you can add 'modprobe snd-aloop' to one or another boot script. To list all of the options within each card group, use 'aplay -L', which is also good for debugging the alsa plugs.
To begin, I suggest you direct TidalConnect to plughw:... or dmix:... Once that works then you can try hw:...
One other important suggestion - *never use tabs in alsa plugs*. Only indent using spaces!
Good luck,
Frank
I really like the minimalistic approach!
no donations are required.
Just flashed an sd and running initial testing with spotify connect over usb. Works really well.
Excited to try this with hermes and cronus.
Probably wrong clock speeds configured. The firmware assumes that you are running higher speed clocks whereas the mounted clocks have lower frequency or you have the clock divider active... Either set the clock divider to 1:1 / off or (if that is already done) try to adjust the frequency settings for the clocks in the firmware. There should be some parameters probably in bootEnv.txt or similar file.
Thanks for the reply coroner21. Yes, the clock divider needed to be set 1:1 then it played music. I preferred the sound of the Gentoo Player though. I did not expect a difference but the sound of the Pure firmware was thin and lacking in the mid bass. Perhaps I will try to contact the developer.