<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 9, 2020 at 3:27 PM Linux ROUEN Normandie <<a href="mailto:linux.rouen@free.fr">linux.rouen@free.fr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div>Yes, it has by default <a href="https://cdn.arstechnica.net/wp-content/uploads/2020/11/PXL_20201102_161143562-1440x1009.jpg" target="_blank">a
      big passive radiator</a> (the size of the keyboard) on top of the
    ARM CPU.<br></div></blockquote><div><br></div><div>Ok, I see. Looks like this is good enough to even run the cpu at a higher default clock speed, so it should be fine. This was a problem that plagued the original Pi4 which is why you see so many 3rd party cases with active cooling solutions on the market; I have one of those as well.<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
    
    Okay. I will need to check if the Raspberry Pi OS delivered with the
    rPi 400 is a 32 or 64-bit OS. Currently on the download page of the
    Foundation it's a 32-bit.<br></div></blockquote><div><br></div><div>Yep, that's the official distribution, it used to be called Raspbian before.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
    In the meantime I'm learning that now <a href="https://manjaro.org/downloads/arm/raspberry-pi-4/arm8-raspberry-pi-4-kde-plasma/" target="_blank">Manjaro</a>
    (20.10) and <a href="https://ubuntu.com/download/raspberry-pi" target="_blank">Ubuntu Desktop</a>
    (20.10) are official versions for the rPi 4 / rPi 400, but both are
    only in 64-bit. So based on above they will not be compatible with
    the current Purr Data for rPi.<br></div></blockquote><div><br></div><div>No, they won't. But the OBS has aarch64 build targets for both Manjaro and Ubuntu. I'm not sure whether these will work, but if anyone is willing to test them out, just let me know and I'll enable these targets.</div><div><br></div><div>Albert<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
    <blockquote type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <div> <br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <div>Based on my reading, it seems we need to blacklist
                the internal Audio for being able to properly use the
                external one.<br>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>You don't have to do any of that. Just plug the USB
            device into the Pi, configure it as the ALSA (or Jack) audio
            I/O and you should be set. That way you can keep using the
            built-in soundcard for other purposes. If you disable the
            built-in soundcard then may run into trouble because Purr
            and other applications will fight over access to the device.<br>
          </div>
        </div>
      </div>
    </blockquote>
    Well noticed.<br>
    <blockquote type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <div> <br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <div> I'm currently using either <a href="https://www.amazon.fr/dp/B01BNQERRQ/ref=pe_3044141_185740131_TE_item" target="_blank">CSL-1</a> or <a href="https://www.amazon.fr/dp/B07MPBVRNF/ref=pe_3044141_185740131_TE_item" target="_blank">CSL-2</a> when
                I need to have a second Audio device under GNU/Linux /
                ALSA / JACK2</div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Yeah, those will work fine, just as well as pretty much
            any of those cheap USB audio devices.</div>
          <div><br>
          </div>
          <div>Good luck, and let us know how Purr works on your Pi400
            when you get it!</div>
        </div>
      </div>
    </blockquote>
    I will do it.<br>
    Thanks. Joseph<br>
    <blockquote type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <div><br>
          </div>
          <div>Albert</div>
          <div><br>
          </div>
          <div> <br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <div>Now, I will need to wait at least 4-5 weeks before
                getting my Raspberry Pi 400 Kit (AZERTY) as it's
                currently (already) in stock shortage.<br>
                <br>
                Best, Joseph<br>
                - - - - - - - - -<br>
              </div>
              <div><br>
                Le 08/11/2020 à 23:50, Albert Graef a écrit :<br>
              </div>
              <blockquote type="cite">
                <div dir="ltr">
                  <div>Hi Joseph,</div>
                  <div><br>
                  </div>
                  <div>Last time I tested Purr on the Pi4, it worked
                    fine there. That was quite some time ago, though
                    (probably around Purr 2.9/2.10), so you'll have to
                    give it a go yourself to see how well the latest
                    version works there.</div>
                  <div><br>
                  </div>
                  <div> The only issue I remember was with the rather
                    lousy built-in soundcard of the Pi4, which can be
                    overcome with a cheap external USB audio device
                    (e.g., <a href="https://www.amazon.fr/UGREEN-Adaptateur-Compatible-Raspberry-Microphone/dp/B01N905VOY" target="_blank">https://www.amazon.fr/UGREEN-Adaptateur-Compatible-Raspberry-Microphone/dp/B01N905VOY</a>
                    is the one that I often use, but any half-decent USB
                    sound device should do the trick).</div>
                  <div><br>
                  </div>
                  <div>Good luck!</div>
                  <div>Albert<br>
                  </div>
                  <div><br>
                  </div>
                </div>
                <br>
                <div class="gmail_quote">
                  <div dir="ltr" class="gmail_attr">On Fri, Nov 6, 2020
                    at 8:20 PM Linux ROUEN Normandie <<a href="mailto:linux.rouen@free.fr" target="_blank">linux.rouen@free.fr</a>>
                    wrote:<br>
                  </div>
                  <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                    <div> Hello to the List,<br>
                      <div><br>
                        I'm looking for an additional, very affordable
                        but enough powerful PC under GNU/Linux for CAM
                        (computer-aided music), Programming, Home
                        automation, etc.<br>
                        <br>
                        Currently my choice is going for the <a href="https://www.raspberrypi.org/products/raspberry-pi-400/?resellerType=home" target="_blank">very
                          new Raspberry Pi 400</a> with Raspberry Pi OS,
                        a Raspberry Pi 4 that has been integrated into a
                        keyboard, with a complete kit priced at ~ 100 €
                        here in Europe (106.50 € Tax incl. in France).<br>
                        <br>
                        Questions:<br>
                        - Has anyone tested Purr Data with the Raspberry
                        Pi 4 (Debian or other distros)?<br>
                        - If yes, what was your experience, pros and
                        cons?<br>
                        <br>
                        Thanks a lot.<br>
                        - - - - - - - - - - - - - - - - - - - -<br>
                        Best,<br>
                        Joseph Gastelais<br>
                        <a href="https://www.linuxrouen.fr/wp/" target="_blank">LINUX ♥
                          ROUEN ♥ Normandie</a><br>
                        - - - - - - - - - - - - - - - - - - - -<br>
                      </div>
                    </div>
                    _______________________________________________<br>
                    L2Ork-dev mailing list<br>
                    <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
                    <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a></blockquote>
                </div>
                <br clear="all">
                <br>
                -- <br>
                <div dir="ltr">
                  <div dir="ltr">
                    <div>
                      <div dir="ltr">
                        <div>
                          <div dir="ltr">Dr. Albert Gr"af<br>
                            Computer Music Research Group, JGU Mainz,
                            Germany<br>
                            Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>,
                            web: <a href="https://agraef.github.io/" target="_blank">https://agraef.github.io/</a></div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
                <br>
                <fieldset></fieldset>
                <pre>_______________________________________________
L2Ork-dev mailing list
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a></pre>
              </blockquote>
            </div>
            _______________________________________________<br>
            L2Ork-dev mailing list<br>
            <a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
            <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a></blockquote>
        </div>
        <br clear="all">
        <br>
        -- <br>
        <div dir="ltr">
          <div dir="ltr">
            <div>
              <div dir="ltr">
                <div>
                  <div dir="ltr">Dr. Albert Gr"af<br>
                    Computer Music Research Group, JGU Mainz, Germany<br>
                    Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>,
                    web: <a href="https://agraef.github.io/" target="_blank">https://agraef.github.io/</a></div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
L2Ork-dev mailing list
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a></pre>
    </blockquote>
    <br>
  </div>

_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a></blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Dr. Albert Gr"af<br>Computer Music Research Group, JGU Mainz, Germany<br>Email: <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>, web: <a href="https://agraef.github.io/" target="_blank">https://agraef.github.io/</a></div></div></div></div></div></div></div>