I am only getting the following error multiple times just after rebooting:
Is this something I should ignore?
Using Debian Strecth, latest rpi-updated version and latest Allo firmware.
Is this something I should ignore?
Using Debian Strecth, latest rpi-updated version and latest Allo firmware.
Last edited:
piCorePlayer it's been updated to 3.22 with Kernel 4.9.50, master volume control and glb_mclk toggle.
So far looking good, waithing @soundcheck opinion.
So far looking good, waithing @soundcheck opinion.
Hi Everyone, I'm new here.
I've read through this entire thread and I haven't seen anyone talking about the piano 2.1 with JRiver. I have my piano up and running in 2.1 setup on a fresh Raspbian install, I've downloaded all of the firmware files so I can configure the paino is alsamixer.
I'm hoping to use some of JRiver's DSP functions to add delay and EQ but JRiver seems to only see the Piano as a 2 channel DAC (even though it correctly functions as a 2.1 channel DAC).
I've asked the same question at the JRiver forum but has anyone here messed around with the Piano 2.1 with JRiver? Or do you have any suggestions how I might get the DAC presented as multichannel to JRiver?
Thanks for the help.
Matt
I've read through this entire thread and I haven't seen anyone talking about the piano 2.1 with JRiver. I have my piano up and running in 2.1 setup on a fresh Raspbian install, I've downloaded all of the firmware files so I can configure the paino is alsamixer.
I'm hoping to use some of JRiver's DSP functions to add delay and EQ but JRiver seems to only see the Piano as a 2 channel DAC (even though it correctly functions as a 2.1 channel DAC).
I've asked the same question at the JRiver forum but has anyone here messed around with the Piano 2.1 with JRiver? Or do you have any suggestions how I might get the DAC presented as multichannel to JRiver?
Thanks for the help.
Matt
@Matt
It's a two channel (stereo) input DAC.
All DSP work (crossover) is done on the DAC chip itself.
How it's done is defined by Allo (through custom firmware).
JRiver has no cards in the game! You can't do the crossover stuff
on the PC.
It's a two channel (stereo) input DAC.
All DSP work (crossover) is done on the DAC chip itself.
How it's done is defined by Allo (through custom firmware).
JRiver has no cards in the game! You can't do the crossover stuff
on the PC.
Thanks gang.
It looks like I might be able to do some of what I want using the TI software (if they'll ever grant me access).
Matt
It looks like I might be able to do some of what I want using the TI software (if they'll ever grant me access).
Matt
Thanks. I managed to get an approval once I emailed them.
Is there any way to take a look at the purepath files used for the standard setups? It might make it easier to understand how to tweak.
Matt
Is there any way to take a look at the purepath files used for the standard setups? It might make it easier to understand how to tweak.
Matt
I've played around with the TI suite at Raspberry Pi with Piano2.1 DAC DSP and Volumio2
The block diagrams show what I trying. I was also able to get starter files from Allo.
Last edited:
Come on cdsgames!!!! 😡
4.9.53 is online now and you still havn't managed to update the driver!
4.9.53 is online now and you still havn't managed to update the driver!
Allo finally uploaded the corrected driver!
Great work! It's a pleasure to work with a company such as Allo,
that listens to our wishes! ( NoNo. There's no sarcasm in the air 😉 )
Basically you all need a 4.9.56 kernel on your OS of choice.
Yep. I know. There are not many of them around yet.
It still might take a little while to get going. 🙄
Enjoy.
there is only one way to get the best sq out of the raspberry: you have to slim the kernel. i e.g. Play my Music in autoplay only. anything else is away from the kernel. e.g. Network Video, Tastatur, mouse, usb, just everything that is not connected to Music. even though i use an allo kali the increase in sq is huge, especially regarding Timing.
os activity makes the sq worse. basta.
os activity makes the sq worse. basta.
Interesting to see Codaca inductor in place. 😀 Will there be PFFB and an external SE2Diff stage implemented as well? From our measurement, we have seen that using an external SE2Diff stage (even without PFFB) gives an advantage of nearly 20dB regarding k1/k2 and k1/k3 margin. PFFB then pulls another 10-20dB better performance. With an overall system gain of 32dB THD+N hits 0.0077% while pure THD is at 0.0022%. At 1kHz k1/k2 is 108dB, k1/k3 is 120dB. These values are for 10W into 10R.
Last edited: