8.3.1 update confusing Allo Boss2 on bitrate?

[Skip Pack]

I just did the in-place update to 8.3.1 without apparent issue, but when I started to play a song, it was speeded up greatly.

I have been using SoX to upsample to 192/32 with 'adhere to base frequency', and it was working fine with 8.3.0. Since the input is 
redbook the output should be 176.4 and that is what 'Audio Information' reflects. However, the audio played by the system sounds like it is at 4X speed. Either the sample rate communication to the DAC Allo2 is failing or the DAC itself is the problem.

If I turn upsampling off entirely, the interface shows that the song is playing but there is no sound.

Any thoughts are most welcome, I'm happy to run suggested diagnostics.

Skip

[Tim Curtis]

I can repro "no sound" on Allo BOSS 2.

I suspect this is due to some sort of incompatibility between the custom Allo driver for the Boss 2 and the new 6.1.y Linux kernel branch. This would require Allo to troubleshoot but AFAIK their softwares are no longer being maintained.

Options:

1. Stay on moOde releases <= 8.3.0 which do not use 6.1.y kernels
2. Try downgrading to 5.15.84 kernel on moOde 8.3.1 using the commands below (untested). While this might work to resolve the specific Boss 2 issue it creates an 8.3.1 configuration that can't be officially supported and may have other breakage.

Code:

sudo apt -y install raspberrypi-kernel=1:1.20230306-1
sudo apt -y install raspberrypi-bootloader=1:1.20230306-1

I did a spot check on some other DAC's with custom drivers for example Allo Katana and Audiophonics ES9038 DAC and no issues under the 6.1.y kernel. Same for other DAC's like Allo BOSS, IQaudIO DACZero, ProtoDAC TDA1387 X8 and Allo Revolution DAC (USB).

[fdealexa]

I can repro "no sound" on Allo BOSS 2.

I suspect this is due to some sort of incompatibility between the custom Allo driver for the Boss 2 and the new 6.1.y Linux kernel branch. This would require Allo to troubleshoot but AFAIK their softwares are no longer being maintained.

Options:

1. Stay on moOde releases <= 8.3.0 which do not use 6.1.y kernels
2. Try downgrading to 5.15.84 kernel on moOde 8.3.1 using the commands below (untested). While this might work to resolve the specific Boss 2 issue it creates an 8.3.1 configuration that can't be officially supported and may have other breakage.

Code:

sudo apt -y install raspberrypi-kernel=1:1.20230306-1
sudo apt -y install raspberrypi-bootloader=1:1.20230306-1

I did a spot check on some other DAC's with custom drivers for example Allo Katana and Audiophonics ES9038 DAC and no issues under the 6.1.y kernel. Same for other DAC's like Allo BOSS, IQaudIO DACZero, ProtoDAC TDA1387 X8 and Allo Revolution DAC (USB).

Hi Tim,
I also encountered a crash with ALLO BOSS 2, after the last upgrade (8.3.1).
By downgrading, as you recommended, I solved it but the system asked me to add a couple of parameters in the commands:
--allow-downgrades
And
--allow-change-held-packages
So the commands I had to enter were:

Code:

sudo apt -y --allow-downgrades --allow-change-held-packages install raspberrypi-bootloader=1:1.20230306-1

sudo apt -y --allow-downgrades --allow-change-held-packages install raspberrypi-kernel=1:1.20230306-1

What do you recommend to do to have the right driver for the new version?

Thanks for the usual and fast solution and best regards,
Francesco

[Tim Curtis]

I don't have a recommendation because Allo does not appear to be supporting or maintaining any of their custom drivers for example the ASIX driver for the SIG has not been maintained since mid-2022.

[Skip Pack]

I tried the reversion to the older kernel as suggested by Tim and it failed, consistent with your note. I then did a clean install of 8.3.0, and i'm up and running. I don't think I'll try to get the 'mixed' version going as there is nothing I need in 8.3.1. Not sure what I'll do with my little blue box longer term. Use other outputs, or pull the Pi 4B.  The ProtoDac 1387 looks like a fun build.


Thanks to you both, Skip

[TheOldPresbyope]

My thought was you need to communicate directly to Allo but then I looked at their support forum on AudiophileStyle

A new post just this Sunday seems to identify the same issue, albeit running on DIetPi rather than moOde. There's no answer yet.

You still might add your findings as a way to increase the sense of urgency ... assuming they intend to support old products. I'm sure their profit margin is slim and long-term software maintenance is expensive.

Sadly, this isn't a new phenomenon. I could recite past experiences with hardware that was great in its time (or at least good enough for me to break down and buy it) but no longer works because the drivers haven't been updated ... but ... never mind.

Regards,
Kent

[DRONE7]

Sadly, this isn't a new phenomenon.

Though consistent with Allo product. They seem to build for one kernel version,  sell out of the run then abandon the product and updates.
One only has to recall the Allo Kali that has had no fix for the inability to reproduce 24 bit output since the kernel changed soon after its release.

[Tim Curtis]

I think more likely their business like countless others was ireparably damaged during the Pandemic and thus no money to pay their engineers.

[fdealexa]

My thought was you need to communicate directly to Allo but then I looked at their support forum on AudiophileStyle

A new post just this Sunday seems to identify the same issue, albeit running on DIetPi rather than moOde. There's no answer yet.

You still might add your findings as a way to increase the sense of urgency ... assuming they intend to support old products. I'm sure their profit margin is slim and long-term software maintenance is expensive.

Sadly, this isn't a new phenomenon. I could recite past experiences with hardware that was great in its time (or at least good enough for me to break down and buy it) but no longer works because the drivers haven't been updated ... but ... never mind.  

Regards,
Kent

Hi Kent,
Thanks for the answer. I already replyed to a similar thread (ALLO BOSS 2 Acrylic no audio in rAudio with kernel 6.1.x) and I tryed to submit a request directly to the Audiophile Founder.
Thanks again and best regards,
Francesco

[DRONE7]

I think more likely their business like countless others was ireparably damaged during the Pandemic and thus no money to pay their engineers.

Possibly, although covid seems to be a convenient scapegoat for almost any problem these days.

Here many manufacturers, growers, wholesalers, and retailers blatantly increase prices and blame covid even after it being proved that this is not the case. Greed will wear any hat even if it doesn't fit.

Recall too the Kali fiasco was several years prior even to the existence of Covid and the same lack of attention was given by Allo.