[AudioI] AudioInjector Octo on Buster Lite

[cx b]

Sure..

In the config file, it states:
dtoverlay=audioinjector-addons

Is there another area where AudioInjector should appear?

As for the dmesg, no mention of AudioInjector - although I did notice this:
[    8.501524] bcm2835_audio soc:audio: card created with 8 channels

What I've learned is that in the current build of Raspian Lite, Pulse
Audio and LXDE panels are not included.
I can try to flash the card with the full OS and run the "easy
install", just to see if that works.. but I would really like to run
it headless and use the optimizations described on the SuperCollider
page, if possible.



On Sun, Jun 20, 2021 at 6:26 PM Matt Flax <matt at audioinjector.net> wrote:
>
> hi there,
>
> Indeed it seems that your soundcard isn't being found.
>
> Can you show the excerpt of the config.txt which mentions audioinjector ?
>
> Also can you run dmesg and look for the audioinjector section.
>
> One way to bypass pulseaudio's default manging with ALSA is to do the
> following :
>
> ########## BEGIN ~/.asoundrc ###################
> @hooks [
>      {
>          func load
>          files [
>              "~/.asoundrc"
>          ]
>          errors false
>      }
> ]
>
> pcm.!default {
>          type hw
>          card 0
> }
>
> ctl.!default {
>          type hw
>          card 0
> }
>
> ########## END ~/.asoundrc ###################
>
> Matt
>
> On 19/6/21 4:15 pm, cx b via People wrote:
> > Also, here's what happens with Speaker-Test..
> >
> > pi at raspberrypi:~ $ speaker-test
> >
> > speaker-test 1.1.8
> >
> > Playback device is default
> > Stream parameters are 48000Hz, S16_LE, 1 channels
> > Using 16 octaves of pink noise
> > ALSA lib pcm_hw.c:1822:(_snd_pcm_hw_open) Invalid value for card
> > Playback open error: -2,No such file or directory
> >
> > On Sat, Jun 19, 2021 at 2:13 AM cx b <clistburnham at gmail.com> wrote:
> >> Hi there -
> >>
> >> I'm currently trying to get AudioInjector up and running on a
> >> Raspberry Pi 4, using Buster Lite and running headless.
> >>
> >> I'm a little new to this stuff, so I apologize for lacking clarity.
> >>
> >> My understanding is that PulseAudio is the default driver currently
> >> and direct access to ALSA has been hidden, which seems to be creating
> >> problems. In any event, as of now, I am unable to get Octo identified
> >> and running.
> >>
> >> Going by the manual install on the Git, here is my log:
> >>
> >>
> >> pi at raspberrypi:~ $ sed -i 's/\=volumealsa/\=REMOVEvolumealsa/'
> >> ~pi/.config/lxpanel/LXDE-pi/panels/panel
> >> sed: can't read /home/pi/.config/lxpanel/LXDE-pi/panels/panel: No such
> >> file or directory
> >> pi at raspberrypi:~ $ sudo apt remove pulseaudio
> >> Reading package lists... Done
> >> Building dependency tree
> >> Reading state information... Done
> >> Package 'pulseaudio' is not installed, so not removed
> >> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> >> pi at raspberrypi:~ $ echo updating the kernel
> >> updating the kernel
> >> pi at raspberrypi:~ $ sudo rpi-update
> >>   *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
> >>   *** Performing self-update
> >>   *** Relaunching after update
> >>   *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
> >>   *** We're running for the first time
> >>   *** Backing up files (this will take a few minutes)
> >>   *** Backing up firmware
> >>   *** Backing up modules 5.10.17-v7l+
> >> #############################################################
> >> WARNING: This update bumps to rpi-5.10.y linux tree
> >> See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=288234
> >> 'rpi-update' should only be used if there is a specific
> >> reason to do so - for example, a request by a Raspberry Pi
> >> engineer or if you want to help the testing effort
> >> and are comfortable with restoring if there are regressions.
> >>
> >> DO NOT use 'rpi-update' as part of a regular update process.
> >>
> >> ##############################################################
> >> Would you like to proceed? (y/N)
> >> pi at raspberrypi:~ $ echo check the device tree overlay is setup
> >> correctly in the file /boot/config.txt ...
> >> check the device tree overlay is setup correctly in the file
> >> /boot/config.txt ...
> >> pi at raspberrypi:~ $ sudo bash -c "sed -i
> >> \"s/^\s*dtparam=audio/#dtparam=audio/\" /boot/config.txt"
> >> pi at raspberrypi:~ $ cnt=`grep -c audioinjector-wm8731-audio /boot/config.txt`
> >> pi at raspberrypi:~ $ if [ "$cnt" -eq "0" ]; then
> >>>          sudo bash -c "echo '# enable the AudioInjector.net sound card
> >>> dtoverlay=audioinjector-addons' >> /boot/config.txt"
> >>> fi
> >> After this, I reboot.
> >>
> >> pi at raspberrypi:~ $ aplay -l
> >> aplay: device_list:272: no soundcards found...
> >>
> >> I'm not sure where else to identify or test the install.
> >>
> >> My goal is ultimately to run this interface with SuperCollider and my
> >> following steps were to use this tutorial:
> >> https://madskjeldgaard.dk/posts/raspi4-notes/
> >>
> >> Ultimately, though, SuperCollider could not identify Jack or the Octo.
> >>
> >> Any advice would be greatly appreciated.
> >>
> >> Thanks.
>
> --
> Checkout the community email list :
> https://lists.audioinjector.net/mailman/listinfo/people
>
>