Upcoming pulseaudio 15.0 does have bt codecs switching aswell. itās already merged, but release isnāt out yet. Also pa 15.0 will have support for higher quality backchannel/microphone via mSBC/WBS (Wide Band Speech).
6 Likes
There is a platform target release for aarch64 but none of the tooling yet, so at least today I can not build pipewire for Xperia 10 II outside of the phone. If I had 2 phones I could consider just building it in the other one. If pipewire were to be added IMO it should be on aarch64 only, so your device would go on working.
No need to convince anyone, I use it everyday so I am convinced and that is enough for me.
Opening this thread in Platform Development section of Sailfish OS seems quite appropriate. You are allowed to experience things your way. Lastly the only thing worth bothering Sinterklaas with is world peace. 
2 Likes
What do you mean? You need tooling matching your host (x86) and target matching the device (aarch64) to build packages for the device.
[jwnz@ordinaattori ~]$ sdk-assistant create SailfishOS-latest-aarch64 http://releases.sailfishos.org/sdk/targets/Sailfish_OS-latest-Sailfish_SDK_Target-aarch64.tar.7z
Creating target [SailfishOS-latest-aarch64]
Using tarball [http://releases.sailfishos.org/sdk/targets/Sailfish_OS-latest-Sailfish_SDK_Target-aarch64.tar.7z]
Do you want to continue? (y/n) y
Downloading 'Sailfish_OS-latest-Sailfish_SDK_Target-aarch64.tar.7z'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 151M 100 151M 0 0 1982k 0 0:01:18 0:01:18 --:--:-- 1772k
INFO: md5sum matches - download ok
Unpacking target ...
No suitable tooling found for this target
Note that while SDK targets are target-cpu specific, SDK toolings are always i486 which is the only supported host platform.
I meant what I said.
Ah, yeah, thatās different I think. I think itās usually caused by mismatch of version between tooling and the target you downloaded.
grep VERSION= /srv/mer/toolings/SailfishOS-latest/etc/os-release
VERSION="4.0.1.48 (Koli)"Oh, wow, there is a tooling folder but it is empty. 
So it literally was missing, just in a different way than I expected.
[mersdk@SailfishSDK SailfishOS-4.1.0.23EA-armv7hl]$ ls /srv/mer/toolings/SailfishOS-
SailfishOS-3.3.0.16/ SailfishOS-4.0.1.48/ SailfishOS-4.1.0.23EA/
[mersdk@SailfishSDK SailfishOS-4.1.0.23EA-armv7hl]$ ls /srv/mer/toolings/SailfishOS-4.1.0.23EA/etc/os-release
/srv/mer/toolings/SailfishOS-4.1.0.23EA/etc/os-release
[mersdk@SailfishSDK SailfishOS-4.1.0.23EA-armv7hl]$ grep VERSION= /srv/mer/toolings/SailfishOS-4.1.0.23EA/etc/os-release
VERSION="4.1.0.23 (Kvarken)"
I used the SDKMaintenance tool to install the targets - I managed it from 2nd try
Using SDKMaintenanceTool is fine, if one likes graphical tools, clicking with mouse etc.
If one does not want to move the hands from the keyboard, installing targets is also possible with sfdk. E.g.
sfdk tools install SailfishOS-4.1.0.23EA-aarch64
2 Likes
as discussed earlier PA 15.0 is progressing aswell, and 15.0-rc1 has been released now, including support for multiple bluetooth A2DP audio codecs, and also higher quality HFP mode using mSBC (Wide Band Speech / WBS) codec.
https://lists.freedesktop.org/archives/pulseaudio-discuss/2021-May/032082.html
Just read it. Thanks!
Summary, not up to par with Jack yet, but getting there. As a long time Jack (and core audio) programmer, Iām keen to see where this goes.
But I also have rock steady pulse / jack integration (mostly for dynamic audio installation stuff with super collider). Might be a thing, eh 
2 Likes
Little bit off topic, but I had to respond to thisā¦
I have a lot of linux software that doesnāt work anymore. Buy some software, and just 3 years later, it isnāt compatible anymore. Backwards compatibility is a bitch on linux. On windows, just by comparison, most XP software is still able to run on windows 10. Linux software must be actively maintained or you are screwed.
So yeah, without sarcasm: Yipee, flatpacks. Flatpacks solve this and many more problems. Ok, I could get older dependencies (if the repos are still online) and put them into a folder, set the variables and chroot into it, but flatpacks are a lot easier and nicer.
I see your name now and then on this forum and in the stores, and I got a lot of respect for your skills and contributions. But donāt let those blind you to other peoples problems. Flatpacks solve big problems.
2 Likes
Well, I know what you mean, in theory. And I have no credibility by virtue of being here.
But, big but, as a person who sunk a lot of money into apple software and went from 8080 to powerpc, bought the upgrades and finally gave up on ābackwardā compatible (wasnāt, it was upgrade or die) I have to agree to disagree. Over the course of 30 years (first mac 1986, last mac 2007)ā¦ I put 10s of thousands into mac hardware and software. That I regret.
There are linux systems I built 10 years ago which i still use. They are kinda āair gappedā media machines but they ājust workā ā¢. So I froze them in time in the awareness that āchange is not always goodā. I have a mulitrack recording system that still runs on linux. Although, to be honest, I switched to hardware for āall thatā (Tascam multi-track).
Flatpak is fine under two conditions.
- Desktop with lots of space (for 2 apps, I have 3.5G being used, thatās just for io.github.mirukana.mirage and io.github.NhekoReborn.Nheko).
- you have the time to spend doing security updates āoutsideā the usual channels (apt update, etc).
I used to do Mac OSx development and have some experience with the āfreedomā of just packing all your dependancies in a directory ā¦ And sometimes there really is āno other wayā. But it is just as much a burden. At the moment, for me that burden is knowing that I donāt have debian, ubuntu, arch or redhat security teams auditing what is happening with my crypto messengers.
So you tell me. Make it possible/easy to install mirage even on an older Ubuntu (say 18). Now, I communicate over channels where security is, well, paramount. With flatpak installs, I have extra responsibility to make sure I donāt compromise them. thatās ok for me, cause itās my job anyway. But Iām not sure itās such a good idea for people who ājust want it to workā. Iām not saying thatās you, but I do know a lot of people even in Linux Land who are that way.
So, in summary, Iām not against flatpak, per se. I just find it dangerous. Iām willing to live with that. On the Sailfish front, I canāt imagine using it, because it would swamp my root partition in no time.
Update: so, I think that flatpak uses so much space because it doesnāt remove installed dependencies
correctly:
no way that the two apps in question require:
org.freedesktop.Platform.GL.default/x86_64/19.08 system,runtime
org.freedesktop.Platform.GL.default/x86_64/20.08 system,runtime
org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08 system,runtime
org.freedesktop.Platform.VAAPI.Intel/x86_64/19.08 system,runtime
org.freedesktop.Platform.VAAPI.Intel/x86_64/20.08 system,runtime
org.freedesktop.Platform.html5-codecs/x86_64/18.08 system,runtime
org.freedesktop.Platform.openh264/x86_64/2.0 system,runtime
org.kde.KStyle.Adwaita/x86_64/5.12 system,runtime
org.kde.KStyle.Adwaita/x86_64/5.14 system,runtime
org.kde.KStyle.Adwaita/x86_64/5.15 system,runtime
org.kde.Platform/x86_64/5.12 system,runtime
org.kde.Platform/x86_64/5.14 system,runtime
org.kde.Platform/x86_64/5.15 system,runtime
Seems like at least one too many?
1 Like
Thatās a completely different sound than the message I quoted. Not that it matters, but I agree with most you said right now. Iāll keep it at that, to not sidetrack this topic any further.
To get on topic: When I first heard about pipewire I was thrilled. I really dislike pulseaudio, and jack is not supported by some apps I most use, so a better alternative is very welcome.
For SFOS I think it is not necessary. I never do much advanced audio configuration on my phone, and it is not what the device is meant for.
I hope in a few years pipewire will gradually replace pulseaudio everywhere, with applications dropping PA support. By that time, I hope sailfish will be ready to make the switch as well.
Yeah, Iām āall over the placeā. I like to think itās human, but sometimes Iām just tired. And I dislike redhat. And systemd, for that matter. But Iām just a kranky old guy. I flip between rabid revulsion and enlightened reflection. sorry.
I think I made it plain, above, that Iām also interested in the development of pipewire. But Iām a jack poweruser so Iām fine with alsa+jack. My next project for Sailfish is an SDL2 based softsynth. Sailfish needs a softsynth. and a proper rythm generation thing ā¦
Yeah, jack is great. Iāve yet to make ardour work with pipewire.
Why does SFOS need a softsynth? And is pipewire not a better jack alternative than PA?
I often (well, before the pandemic home office) make music on my commute to the office. Usually i use one of my small synths or a pocket operator. But Iād like to also be able to do some sound design/synthesis on the way to work. I have a two hour daily commute, three times a week.
I do not know if pipewire is better than PA. PA has been suck but as pasik put it above, improvements keep being made. On the machine Iām typing with I have ardour running with jack and pulse streaming into jack from the webbrowser. Although I donāt do that very often. Jack syncs with pulse started working reliably about 3 or 4 years ago, but I admit itās more a novelty thing.
As I mentioned, I have frozen in time machines for ārealā audio work and a dedicated multi-track tascam. I also use mostly home built hardware based on Axoloti, my own analog designs and the Mozzi lib running on arduino clones. Oh. And saxophones, drum kits (2), guitars, trombones, etc.
So, I donāt have an OS dependency for audio production anymore. I did 8 channels (with bob/firewire a presonos device) for about 3 years on linux but that was a period where I couldnāt focus on music enough anyway).
Now Iām derailing this thread. Sigh. Sorry.
Big problem is comparing the two Windows and Linux. Perhaps you upgrade too often. There is a rule: do not touch a running system
1 Like
You might find these interestingā¦ Sporth
and GitHub - thi-ng/synstack: Modular soft synth & Forth based VM for audio DSL experiments
Bloody weird. Iām just implementing a stack machine on Arduino. Started this morning. Thatās weird timing. Thanks a bunch! I hadnāt seen this!