Dear Mr. Raspi ,

[hitsware]

Would You please fix the new PiOS ( 32 bit )
so that Sonic-Pi produces sound ?
Thank You ,
Michael Mller

[pidd]

Its not just you.

I don't get sound either, Chromium has sound, sonic-pi doesn't. Using Pi4 3.5mm jack.

Not got round to looking into it yet.

[fruitoftheloom]

Would You please fix the new PiOS ( 32 bit )
so that Sonic-Pi produces sound ?
Thank You ,
Michael Mller

You have an open post on this issue, no need to regurgitate:

viewtopic.php?f=38&t=276866

[hitsware]

You have an open post on this issue, no need to regurgitate:

Sorry .... Figured this a better place for it .....

[fruitoftheloom]

You have an open post on this issue, no need to regurgitate:

Sorry .... Figured this a better place for it .....

If you want your post moved report to Moderator, do not multi-post.

[jamesh]

We do not maintain Sonic Pi.

We have now moved to a more standard Linux sound system setup, if Sonic PI does not work with it, then its likely that Sonic Pi will need some work.

I'll flag it up to a guy who might be able to help.

[hitsware]

O K

[jamesh]

O K

So, this is a known problem in SP. We have told the SP author how to fix it. He refuses to do so. Another dev is willing to fix it, so we have sent full instructions on the fix and how to package to them, and hopefully this will be released soon.

[bensimmo]

That depends how you look at it of course.
But here is a working version, it's newer than the the RPiOS versions.

Over at the SonicPi website/forum.
https://in-thread.sonic-pi.net/t/v3-2-2 ... lable/3976

This release replaces the existing v3.1 release of Sonic Pi which ships on Raspberry Pi OS which apart from being over 2 years old has a number of known issues including missing MIDI and OSC functionality and lack of headphone jack support.

We have sent this new release to Raspberry Pi, but unfortunately they decided not to accept and distribute it, preferring to continue to ship their v3.1 build... (continue at the forum for why RPi didn't)

But then hitsware already knew all of this.


I am guessing that debian source is needed as there is now/soon a 64bit OS to support and would that also help out with RPiOS-AMD64/X86 too?

[jamesh]

That depends how you look at it of course.
But here is a working version, it's newer than the the RPiOS versions.

Over at the SonicPi website/forum.
https://in-thread.sonic-pi.net/t/v3-2-2 ... lable/3976

This release replaces the existing v3.1 release of Sonic Pi which ships on Raspberry Pi OS which apart from being over 2 years old has a number of known issues including missing MIDI and OSC functionality and lack of headphone jack support.

We have sent this new release to Raspberry Pi, but unfortunately they decided not to accept and distribute it, preferring to continue to ship their v3.1 build... (continue at the forum for why RPi didn't)

But then hitsware already knew all of this.


I am guessing that debian source is needed as there is now/soon a 64bit OS to support and would that also help out with RPiOS-AMD64/X86 too?

Sonic Pi's comment above is disingenuous to say the least.

We need a .deb package that is rebuild-able - the one referenced is apparently not, and tbh, it's a bit of a hack together job (The Sonic PI build process is, I've heard, a bit of a nightmare). There are number of bugs in it a SP developer is looking in to, for which we are very grateful. Once they are all fixed, then we are more than happy to accept the deb. It's actually our preferred approach, so it's not like we are being deliberately obstructive - we just need something that works to our required standard.

I do not know if this has anything to do with 64-bit.

[fruitoftheloom]

.
Actually as a point of interest it has already been discussed, so do not know why HITS has made 2 posts

viewtopic.php?f=38&t=254157

[hitsware]

That depends how you look at it of course.
But here is a working version, it's newer than the the RPiOS versions.

Over at the SonicPi website/forum.
https://in-thread.sonic-pi.net/t/v3-2-2 ... lable/3976

This release replaces the existing v3.1 release of Sonic Pi which ships on Raspberry Pi OS which apart from being over 2 years old has a number of known issues including missing MIDI and OSC functionality and lack of headphone jack support.

We have sent this new release to Raspberry Pi, but unfortunately they decided not to accept and distribute it, preferring to continue to ship their v3.1 build... (continue at the forum for why RPi didn't)

But then hitsware already knew all of this.


I am guessing that debian source is needed as there is now/soon a 64bit OS to support and would that also help out with RPiOS-AMD64/X86 too?

Yes , hitsware is sadly aware of an apparent " fallout "
( for lack of a better term ) ......
Unfortunately there is a problem with screen sizing on the
new SPi .deb version ( ( on Rpi 3B+ ) not sure about 4 )
Sonic Pi is the main reason I started using RPi to begin
with . If I must , I can ( hopefully ) continue to use older
versions of RPiOS , but I prefer to be able to use
Noobs to refresh my system .

[jamesh]

That depends how you look at it of course.
But here is a working version, it's newer than the the RPiOS versions.

Over at the SonicPi website/forum.
https://in-thread.sonic-pi.net/t/v3-2-2 ... lable/3976

This release replaces the existing v3.1 release of Sonic Pi which ships on Raspberry Pi OS which apart from being over 2 years old has a number of known issues including missing MIDI and OSC functionality and lack of headphone jack support.

We have sent this new release to Raspberry Pi, but unfortunately they decided not to accept and distribute it, preferring to continue to ship their v3.1 build... (continue at the forum for why RPi didn't)

But then hitsware already knew all of this.


I am guessing that debian source is needed as there is now/soon a 64bit OS to support and would that also help out with RPiOS-AMD64/X86 too?

Yes , hitsware is sadly aware of an apparent " fallout "
( for lack of a better term ) ......
Unfortunately there is a problem with screen sizing on the
new SPi .deb version ( ( on Rpi 3B+ ) not sure about 4 )
Sonic Pi is the main reason I started using RPi to begin
with . If I must , I can ( hopefully ) continue to use older
versions of RPiOS , but I prefer to be able to use
Noobs to refresh my system .

I'd be very cautious when reading anything about us written by the Sonic PI author. I've just read a Sonic PI thread I won't link to, and there are a LOT of inaccuracies in what has been written. For a start, we have not changed our acceptance policy - it's been the same for paid contributors (and non paid) since we started - deliver stuff to our standards (which basically means packaged and rebuildable), and deliver on time. Everyone else seems to able to cope with both of those.

[hitsware]

> We have now moved to a more standard Linux sound system setup

Would You please elaborate on that ?
Or refer me to an ( the ) article .
Thank You & Mega Regards ,
hitsware

[jamesh]

> We have now moved to a more standard Linux sound system setup

Would You please elaborate on that ?
Or refer me to an ( the ) article .
Thank You & Mega Regards ,
hitsware

IIRC, the previous setup made all three output possibilities subdevices of a single device. (HDMI0, HDMI1, headphone) Now each device is regarded as a separate device (although all part of the same driver code). which is how it's usually done in Linux. Apparently, SonicPi uses some sort of hardcoded data which needed to be fixed up to work as you would normally expect something using Linux sound to work. So, a hacky bit of code needed to be updated to something more appropriate. We told the SP devs exactly what needed to be done, along with how to package it all up.

For reference the driver source is here. You can check its history to see what changed.

https://github.com/raspberrypi/linux/bl ... /bcm2835.c

IIRC, the module parameter to change the way is work is enable_compat_alsa.

[B.Goode]

> We have now moved to a more standard Linux sound system setup

Would You please elaborate on that ?
Or refer me to an ( the ) article .
Thank You & Mega Regards ,
hitsware

The sort of thing that ought to be documented in a Blog post when a revised release of the Operating System is released.


Ideally flagged up with an introduction like

One particular change which it is worth pointing out is that we have made a small change to audio...

Ref: https://www.raspberrypi.org/blog/latest ... -may-2020/

(of course, you might feel it isn't a small change... )

[hitsware]

The sort of thing that ought to be documented in a Blog post when a revised release of the Operating System is released.

Ref: https://www.raspberrypi.org/blog/latest ... -may-2020/

Thank You ! .... SPi works fine through HDMI
I thought I'd tried that, but evedently not.

[jamesh]

> We have now moved to a more standard Linux sound system setup

Would You please elaborate on that ?
Or refer me to an ( the ) article .
Thank You & Mega Regards ,
hitsware

The sort of thing that ought to be documented in a Blog post when a revised release of the Operating System is released.


Ideally flagged up with an introduction like

One particular change which it is worth pointing out is that we have made a small change to audio...

Ref: https://www.raspberrypi.org/blog/latest ... -may-2020/

(of course, you might feel it isn't a small change... )

As code changes go it was pretty minor. Most of the functionality was already there but not enabled - I just fixed up the driver for two HDMI, and we enabled the correct mode as default.

The fact Sonic Pi used hardcoded settings for sound is the issue in this particular case.

[goTouch]

That depends how you look at it of course.
But here is a working version, it's newer than the the RPiOS versions.

Over at the SonicPi website/forum.
https://in-thread.sonic-pi.net/t/v3-2-2 ... lable/3976

This release replaces the existing v3.1 release of Sonic Pi which ships on Raspberry Pi OS which apart from being over 2 years old has a number of known issues including missing MIDI and OSC functionality and lack of headphone jack support.

We have sent this new release to Raspberry Pi, but unfortunately they decided not to accept and distribute it, preferring to continue to ship their v3.1 build... (continue at the forum for why RPi didn't)

But then hitsware already knew all of this.


I am guessing that debian source is needed as there is now/soon a 64bit OS to support and would that also help out with RPiOS-AMD64/X86 too?

Hi, does everyone get it run with sound successfully? I tried but still don't get sound from headphone jack.
I need the sound from headphone jack because I don’t have HDMI device on it.

First thing I found is the UI to change default sound device doesn't work for me. Either the speaker icon on top corner or the raspi-config tool doesn't work. Old command like amixer cset numid=3 1 doesn't work either (because the sound device is different in latest Raspbian now).

I had to create a /etc/asound.conf to set default sound device to the headphone jack. Not sure if Sonic Pi is supposed to work on such config automatically. At least Chromium (youtube) works for me now. Any idea on the exact steps to change the default output to headphone jack?

Thanks.

Code: Select all

pcm.!default {
  type hw
  card 1
}

ctl.!default {
  type hw
  card 1
}

[goTouch]

The 64bit beta seems not using the new sound devices. It is still the old one single device with multiple output.

I installed 64bit via BerryBoot v2 and not sure if it grabbed the latest beta from:

https://downloads.raspberrypi.org/raspi ... -arm64.zip

[DougieLawson]

The 64bit beta seems not using the new sound devices. It is still the old one single device with multiple output.

That's because it's a BETA test on a different fork of the firmware. It'll get merged soon enough.

If you're part of the beta testing group then before reporting problems on here you MUST run sudo rpi-update & sudo rpi-eeprom-update (with the beta settings in /etc/default/rpi-eeprom-update) to ensure your system is running with the latest firmware and kernel (or you may be reporting a re-discovery of a known bug).

[goTouch]

We do not maintain Sonic Pi.

We have now moved to a more standard Linux sound system setup, if Sonic PI does not work with it, then its likely that Sonic Pi will need some work.

I'll flag it up to a guy who might be able to help.

Hi there, I tried building debian source package from sonic-pi github and is able to do it with some small changes.
What is the process to get someone to review and submit to raspian repository? Do I need to make it into debian sid as well?

It is minimum change to make it build debian package, though not perfect. The code base has some external software packed in. Ideally those software should be in separate package but then this would require the sonic-pi code to call them from system wide /usr/bin,lib etc, instead of containing them in one .deb package and installed under /opt/sonic-pi/....

[jamesh]

We do not maintain Sonic Pi.

We have now moved to a more standard Linux sound system setup, if Sonic PI does not work with it, then its likely that Sonic Pi will need some work.

I'll flag it up to a guy who might be able to help.

Hi there, I tried building debian source package from sonic-pi github and is able to do it with some small changes.
What is the process to get someone to review and submit to raspian repository? Do I need to make it into debian sid as well?

It is minimum change to make it build debian package, though not perfect. The code base has some external software packed in. Ideally those software should be in separate package but then this would require the sonic-pi code to call them from system wide /usr/bin,lib etc, instead of containing them in one .deb package and installed under /opt/sonic-pi/....

The changes really need to be supplied to SonicPi themselves, unless you are willing to take on the ongoing maintenance of the changes you have made. We would then take the entire buildable package from Sonic Pi and build that in to our distro's.

We are very reluctant to take on any more burden in regard to creating PiOS- its hard enough to keep on top of it as it is.

[goTouch]

The changes really need to be supplied to SonicPi themselves, unless you are willing to take on the ongoing maintenance of the changes you have made. We would then take the entire buildable package from Sonic Pi and build that in to our distro's.

We are very reluctant to take on any more burden in regard to creating PiOS- its hard enough to keep on top of it as it is.

Understood totally. I also contacted the author and will see what's feasible right now. They probably can take the simple Makefile I created, but it is a little far stretch whether they are willing to keep debian files in their repo.

The best way for this maybe is to make it part of Debian repository. Then PiOS gets from Debian as is and hassle free.
There is always need for someone to maintain the packaging anyways. Author won't be interested to maintain multiple forms of packaging for deb, RPM, arch, etc. Debian also relies on community effort for the packaging effort, particularly to add new packages. Then it could be rebuilt somehow automated but still needs human help to supply new version.

My concern is the current sonic-pi repo contains a snapshot of other software (like QScintilla). It is of course convenient to them but it would be best to separate the packaging. This then requires some change of the building script. I am also asking the author about this.

[jamesh]

The changes really need to be supplied to SonicPi themselves, unless you are willing to take on the ongoing maintenance of the changes you have made. We would then take the entire buildable package from Sonic Pi and build that in to our distro's.

We are very reluctant to take on any more burden in regard to creating PiOS- its hard enough to keep on top of it as it is.

Understood totally. I am also contact the author and see what's feasible right now. They probably can take the simple Makefile I created, but it is a little far stretch whether they are willing to keep debian files in their repo.

The best way for this maybe is to make it part of Debian repository. Then PiOS gets from Debian as is and hassle free.
There is always need for someone to maintain the packaging anyways. Author won't be interested to maintain multiple forms of packaging for deb, RPM, arch, etc. Debian also relies on community effort for the packaging effort, particularly to add new packages. Then it could be rebuilt somehow automated but still needs human help to supply new version.

My concern is the current sonic-pi repo contains a snapshot of other software (like QScintilla). It is of course convenient to them but it would be best to separate the packaging. This then requires some change of the building script. I am also asking the author about this.

Good luck! We've been asking for a working packaged version for some time. I believe someone at SP has been working on it.