Uploaded image for project: ' AGL Development'
  1. AGL Development
  2. SPEC-1610

raspberrypi3: bug on internal sound card

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • None
    • Flounder
    • Kernel/ OS

      There is an issue with 'dmix' when using rpi3 soundcard that make impossible to mix sound. Furthermore, it is impossible to use 4a-softmixer for this soundcard.

      Instruction to reproduce the issue (trying to use dmix with rpi3 soundcard) :

      • Replace your board's '/etc/asound.rc' file by the attached 'asound.rc' file.
      • Run an 'aplay -l | grep -i bcm2835' to get rpi3 soundcard alsa device id (a number between 0 and 31).
      • Modify the freshly replaced '/etc/asound.rc' to replace the '1' in the line 'slave {pcm "hw:1"}

        ' (l. 10) by rpi3 soundcard alsa device id.

      • Copy attached 'tone-440-stereo-48000-16bits.wav' sound file to you board '/home/0' directory.
      • Open two terminals on your platform :
      • In the first one, run : aplay -D Emergency_Main /home/0/tone-440-stereo-48000-16bits.wav
      • In the second one, run : aplay -D Warning_Main /home/0/tone-440-stereo-48000-16bits.wav

      On the second terminal, an error will be returned :
      ALSA lib ../../../alsa-lib-1.1.6/src/pcm/pcm_dmix.c:1156:(snd_pcm_dmix_open) unable to open slave
      aplay: main:828: audio open error: Invalid argument

      In attached files, you can find outputs of the error using rpi3 soundcard and the expected behaviour using a csl-cm106 soundcard.

        1. asound.rc
          0.6 kB
        2. rpi3_soundcard_output.md
          2 kB
        3. tone-440-stereo-48000-16bits.wav
          1.83 MB
        4. usb_soundcard_output.md
          2 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            leonanavi Leon Anavi
            sdesneux Stephane Desneux
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: