Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • 9. April 2021 at 14:50 #51119

    I’ll check the plugin builder and see if I can turn my manual install into a max2play-plugin.
    Since you didn’t comment, I’m assuming max2play doesn’t contain a browser-based text editor, which could be used from the web-GUI to edit the (optional) config file. I’ll see …


    7. April 2021 at 17:05 #51098

    OK – thanks.
    But since I do not experience missing functionality, I’m assuming it’s about the acceess point mode of the WiFi for initial configuration, right?

    7. April 2021 at 13:00 #51091

    A really strange problem. A day after network-access is back again.
    Since reboots didnÄT solve the issue, I suspect that the problem is caused by the router or somewhere else.

    We’ll see if it happens again.

    29. Januar 2021 at 19:12 #50690

    Well, I finally found the time to instal and configure vsftpd on my PI3. And the outcome is quite the opposite compare to FritzOS.
    ftp transfer is way slower compared to SMB. Here’s the ranking.
    1) SMB (3.5MB/s)
    2) scp (2 … 2.5 MB/s)
    3/4) ftp and sftp (1 … 1.5MB/s)

    Maybe this data is of use for others.

    12. Februar 2019 at 12:31 #44439

    thanks for all your help. My DAC is back and running. I probably messed up stuff while working temporarly without a license. Now I’ve re-licensed for the next two years and was able to get everything back running without afresh install.
    I hesitated to go this route, not becausue the max2play setup is so complicated, but because copying 50GB of Music to the SD card after a fresh install takes so much time!
    Do you think it’s possible to support a multi-partition setup (separting media from system) out of the box?
    I mean to make it easier to do a full reset to your defaults without deleting everything on disk.

    This time I performed it manually (mounting your image, copying system as well as boot partition on file system level onto my existing SD with everything removed but media data, and fixing the boot-loader afterwards), but it was cumbersome (but still faster than copying 50GB of data).

    Can you image supporting something like a „back to start“ or „update to vanilla“ functionality without wiping the SDcard completely?

    1. Februar 2019 at 1:09 #44310

    Hi Heiner,
    I’m still having trouble with my Allo DAC. Maybe I’ve mixed two things. My license expired (meanwhile I’ve relicensed), and I’ve updated the kernel, which bumped to rpi-4.14.y linux tree. Does the Allo driver work wih this kernel, or is this the source of my defunct Allo DAC?


    30. Januar 2019 at 9:01 #44235

    Hi Heiner,
    Thanks for your feedback. I gave it a try, but it didn’t work. Config.txt looks ok, but the dmesg boot log doesn’t look promising, as I guess the kernel driver cannot find the Allo DAC (LEDs are on. It’s turned on). There are only error messages.
    I’d expect at least one „positive“ log entry, but have no old log available to compare. Do you happen to know the log entry which indicates the detection of a Allo DAC?


    1. Mai 2018 at 21:47 #35400

    Heiner, what’s the status of the Jivelite power button (top left corner) on the official stretch based image 2.46? Is it already supposed to turn off the audioplayer and blank/turn-off the screen, or is this still an open issue?
    I’ve tried it on Pi 3B, and 2B .. no luck.


    12. April 2018 at 15:57 #35151

    Thanks for this feedback. Good to hear !
    I’m going to get the Pi3 replaced immediately („Gewährleistung“ ;-).
    Then we’ll see ..

    12. April 2018 at 10:42 #35141

    Meanwhile, I’ve tested my Boss Allo on a RaspPI 2B, and the indentical software stack (=sdcard) run’s very stable for days now. No issues.
    I’m suspecting a hardware issue on my Rasp-PI 3B, as it’s very unlikely that there a still kernel clock issues on 3B like this one
    open and unresolved. On the the other side, the Allo BOSS running in I2S master mode is kind of an exotic card …

    Can anyone confirm Allo Boss Rev 1.1 is running stable for more than a week on Rasp-PI 3B?


    12. April 2018 at 9:42 #35139

    Hi Heiner,
    I haven’t switched to current strech based 2.45. I’m still running the latest jessie based system (incl. online updates).
    Hardware is Rasp-PI3B, 7“Display, Allo BOSS Rev1.1, and the 5V/3A power supply suggested/sold by Allo (and other shops, too).

    Currently, I’ve switched to a Rasp-PI2B, as I’m having serious trouble with the I2S link between Rasp-Pi and Allo BOSS [appearing after hours/days of operation > differetn thread]. On this combination now everything runs stable.

    The reason for my question about pulseaudio is the following:
    Everything executues as described by yourself. The Allo Plugin sets output device for the Jive player directly to the card (no pa) and even sets the hardware mixer (option -V … but to „Digital“ whereas my card comes with „Master“ … but that’s mentioned somewhere and had been easy to fix). According to the webinterface settings, there’a absolutely no pulseaudio involved. But when checking for running processes, there a pa daemon, and it locks the alsa control device of the sournd card.

    Is this expected behaviour, an unknown issue, or maybe a leftover from the BT plugin I had installed for testing and uninstalled again? (ended up with a lot of stuttering for BT audio and had no time for further debugging … save some work for later). And if yes, how can I get rid of pulseaudio manually to fix this?


    5. April 2018 at 13:16 #35001

    Hi Heiner,

    my Allo BOSS is rev 1.1 without USB-C.
    I’ve followed the suggested procedure to re-install the Allo card, but no success. It still disappears from the system after some hours of (successful) use/playback. And as observed before, this is happening silently in idle state.

    I’m still puzzled about the basic question: Hardware (defect) or software issue?
    What’s required to happen to get ALSA forget about a I2S sound card?
    And even if there’s an issue on the I2C control link (loose cables, instable voltage supply, I2C clock issue as addressed by this patch, a soft reset/reboot should bring everything back, shouldn’t it?
    But it’s required to unplug and perform a cold reboot to get everything back running.

    Is there a debug mode for the Allo Boss device driver to get more insight what’s happening?


Viewing 12 posts - 1 through 12 (of 12 total)