(12-19-2020, 05:15 PM)Tim Curtis Wrote: @the_bertrum, the issue is specific to Allo Usbridge SIG board and us caused by some issue in the 32-bit ASIX driver that we just started compiling. Swapping in Allo's compile of the driver fixes the issue :-) I posted link to the patched image.

Plan is to wait a bit and see if any more bugs are identified, fix them and then publish a bugfix release. Pretty much how every major release unfolds.

(12-18-2020, 09:32 PM)Gabster 2000 Wrote:

(12-18-2020, 06:30 PM)Tim Curtis Wrote: Hi,

Post all bug reports and questions concerning moOde 7.0.0 in this thread. Please paste log output, scripts, etc in code boxes for readability.

-Tim

Can not seem to load Ver 7.0  on Allo Usbridge Signature ver 6.7.1 was loading fine seems to hang on a black screen or this screen attached
flashed card a few times no go same card works on Pi3B+
anyone else have this issue ?

(12-20-2020, 10:09 AM)Rexalex Wrote:

(12-18-2020, 09:32 PM)Gabster 2000 Wrote:

(12-18-2020, 06:30 PM)Tim Curtis Wrote: Hi,

Post all bug reports and questions concerning moOde 7.0.0 in this thread. Please paste log output, scripts, etc in code boxes for readability.

-Tim

Can not seem to load Ver 7.0  on Allo Usbridge Signature ver 6.7.1 was loading fine seems to hang on a black screen or this screen attached
flashed card a few times no go same card works on Pi3B+
anyone else have this issue ?

Hi,

yes, I have the same problem! I`ve installed ver. 700 on Usbridge only after installintg memory card on Raspberry 3B+, then translocated the card in Usbridge.

(12-19-2020, 12:25 PM)Tim Curtis Wrote:

(12-19-2020, 11:14 AM)adrian311 Wrote: Hi Tim/Team

MoOde 7 installed well, and looking very nice - thanks!
One small issue - RPi2 with Suptronics x400 Dac/amp doesn't output any sound even though the source is playing, and gives the following error message:

MPD error

Failed to open "ALSA default" (alsa); Failed to open ALSA device "hw:0,0": No such file or directory

If I set the Dac to something like HiFiBerry DAC + (which uses same 5122 chipset) all is well, and also gives access to the same chip options - filters, on chip hardware volume etc. I'm guessing the Suptronics setting is not finding the overlay or something?

Regards
Adrian

I just ran a quick test and after setting I2S device to Suptronics x400 the iqaudio-dacplus overlay is added to config.txt. I don't recall changing anything for the Suptronics device in the SQL table but if it should be using the Hifiberry overlay I can change it.

Is there a link to Suptronix product info that states which overlay to use?

Code:

pi@rp2:~ $ cat /boot/config.txt
disable_splash=1
disable_overscan=1
hdmi_drive=2
hdmi_blanking=1
hdmi_force_edid_audio=1
hdmi_force_hotplug=1
hdmi_group=0
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=audio=off
dtoverlay=iqaudio-dacplus
#dtoverlay=disable-wifi
#dtoverlay=disable-bt

(12-20-2020, 06:11 AM)DRONE7 Wrote: Bump....

How to remove the little white animation that appears next to the currently playing track..??