Hello,
I have the soekris dac and the rpi3 as the source of the signal. What do you think, should I buy the kali i2s reclocker or FIFO in soekris is enough to solve the problem of the rpi's jiter ?
I have the soekris dac and the rpi3 as the source of the signal. What do you think, should I buy the kali i2s reclocker or FIFO in soekris is enough to solve the problem of the rpi's jiter ?
Well, the doc that they have released today confirms that they are routing Kali MCLK to pin29 on the header. But what they are calling GPIO5 is actually GPIO21. 5 is the BCM pin numbering. But anyway, we are all talking about the same thing, albeit referring to it differently.
@cdgames......
How many Kali hardware variants are now in the wild, and how do we tell them apart? ie. there was a 22/24 version, then a 44/48 version? Is there something silk-screened on the board, a revision number, that enables us to identify the variant?
With regard to Kali firmware..... How do we identify which version of firmware is currently installed on a Kali?
How many Kali hardware variants are now in the wild, and how do we tell them apart? ie. there was a 22/24 version, then a 44/48 version? Is there something silk-screened on the board, a revision number, that enables us to identify the variant?
With regard to Kali firmware..... How do we identify which version of firmware is currently installed on a Kali?
There are 2 versions 22/24 and 44/48Mhz...
Regarding firmware , paying customers have only latest firmware. Testers have a few versions. I don't think you can check the firmware but I sent an email to our team.
Regarding firmware , paying customers have only latest firmware. Testers have a few versions. I don't think you can check the firmware but I sent an email to our team.
Yes, I know that. What I am asking you is how we tell them apart? Is there something silk-sreened on the board, a revision number or something?????
This latest firmware... Is this firmware resolving the bugs.... The popping on sample rate change and the loop from buffer (after pause) issue?
I asked manufacturing ..but I don't think so since PCB is same, just oscillators are changed
I've bought a Kali with buffer loop problem, but have not received any news/mail how or when this problem will be fixed, is this correct?
Did you ask this question on the Volumio forum? The guy over there who represents Allo, (called Andre, I think), replied....
So, if you bought a Kali with the "buffer loop bug" it seems they will be sending you a new board.
I have tried this with promising, but so far mixed results. Especially if you have a Rev 1 or 2 Soekris before he added HW reclocking after the FPGA, it should be useful.
Mine is a Rev 1 DAM1021
I hope to get back to this over the weekend and will update afterwards.
Greg in Mississippi
I've received a pm from Ioan, they will sent a new Kali, sorted.
By the by, very disappointing to hear, clivem, that your efforts for the Rpi kernel have come to a halt. Keep up the good work, I think it is much appreciated by many.
Glad to hear it!
From what Ioan has said, publicly and privately, their "plus" advanced driver for the Piano is ready and they are just waiting for TI to let them know this week, which license they should use to release the PurePath created miniDSP binary firmware, for the Piano 2.1/2 (sub and active crossover) functionality. That's what is important, that the software/firmware gets released to allow people to fully utilise the Allo Piano hardware, with the functionality that was described in the marketing materials. I'm going to refrain from commenting on the reasons for my actions until after that driver is released. That's what is important, that the driver and firmware gets released.