What happened to Soundux? Updates?

[D3SOX]

We are currently in the progress of rewriting the whole application.

Name	Required Portion Done	Reference	Overall-Progress (%)
Mock-Ups		https://drive.google.com/file/d/1PiwXaEFdvMU77PaZTKR38R3pQ5cumz31/view?usp=sharing	80%
Frontend		https://github.com/Soundux/soundux-ui-next	80%
Frontend-Renderer		https://github.com/saucer/saucer	55%
Backend Audio-Manipulation¹		https://github.com/Soundux/rohrkabel	100%
Backend Code		Not yet available	85%
Website		https://github.com/Soundux/website	1%
Ereignis		https://github.com/Soundux/ereignis	100%

¹ The library required for creation of virtual microphones and audio/application-passthrough

Overall-Progress is not required to be 100%. We already use the Frontend-Renderer despite it not being 100% complete, the next Soundux-Version will most likely also ship without the Frontend-Renderer being 100% complete.
Overall-Progress refers to all planned features that may come as a new feature addition in future releases, for example macOS support for the frontend-library will be released at a later date

[Curve]

Just to post some additional updates, we're making good progress right now ^^

The Patchbay-Portion of the backend is usable and mostly stable already and the new audio playback-backend is to follow soon

As soon as we reach a state where the new update is easy to use for users we'll publish the first beta

[Curve]

Another Update: The new playback-backend also made some nice advancements today, basic playback works now and is able to play basic remote files (no ytdlp Integration yet tho)

[pr8x]

When can we test the beta?

[Curve]

When can we test the beta?

As soon as it's usable

[thatguy4194]

I understand that with open source projects time is inconsistent and deadlines are hard to set, but can you provide an ETA? I'm a huge fan of this project and am curious how long the next release will take.

[Curve]

I understand that with open source projects time is inconsistent and deadlines are hard to set, but can you provide an ETA? I'm a huge fan of this project and am curious how long the next release will take.

As I've implied yesterday, we can't provide any ETA as we don't know how long we'll need ourselves

[thatguy4194]

That's reasonable, Thank you. May I also ask why the reference for backend code is listed as not yet available? If there isn't a git repo for it yet, why? Sorry if this is already specified elsewhere.

[Curve]

That's reasonable, Thank you. May I also ask why the reference for backend code is listed as not yet available? If there isn't a git repo for it yet, why? Sorry if this is already specified elsewhere.

The repository for the new backend code is in a private repository and will be merged into this repo once it's production ready.

[thatguy4194]

Alright, Thanks.

[Visne]

Any update? Would be cool if the backend could be open sourced

[Curve]

Any update? Would be cool if the backend could be open sourced

Currently the frontend progress is a little stale, which is why there have been barely any update posts.

I still have some things to clean up and will then hopefully just merge the backend repo into the main repo

[thatguy4194]

Any update? Would be cool if the backend could be open sourced

Currently the frontend progress is a little stale, which is why there have been barely any update posts.

I still have some things to clean up and will then hopefully just merge the backend repo into the main repo

I think that's the play right now. Easy to set up soundboard options are limited right now on linux, at least in my experience. I think if you can just get the backend to a working state with a fair amount of bugs, you would see a lot of support and commits from people excited to finally see an update to the project. I think that will drum up some support for the frontend as well. Maybe add some more details to the page for the new UI to streamline the process of getting started with commits and such. I'm a huge fan of this project and I want to see it succeed, Thank you!

[ranenvious]

Any update? Would be cool if the backend could be open sourced

Currently the frontend progress is a little stale, which is why there have been barely any update posts.
I still have some things to clean up and will then hopefully just merge the backend repo into the main repo

I think that's the play right now. Easy to set up soundboard options are limited right now on linux, at least in my experience. I think if you can just get the backend to a working state with a fair amount of bugs, you would see a lot of support and commits from people excited to finally see an update to the project. I think that will drum up some support for the frontend as well. Maybe add some more details to the page for the new UI to streamline the process of getting started with commits and such. I'm a huge fan of this project and I want to see it succeed, Thank you!

Personally if I check a repo that looks like it might solve my problem and it's last update was more than 6 months ago I avoid it, so I'd imagine your right. No-one wants to start relying on software that's already unmaintained, and no-one wants to maintain software they don't think anyone actually uses, so it wouldn't be surprising if a lot of people got turned off from contributing because of the silent development. From a developer standpoint it does make sense to not want things that are in-progress to be visible to everyone since you kinda just want to work on it solo without having to deal with ideas constantly being thrown around, but a repo that gets too stale can lose favour fast. It's a pretty hard act to balance but it's kind of just the unfortunate reality of rewrites/refactors a lot of the time.

[Curve]

Any update? Would be cool if the backend could be open sourced

Currently the frontend progress is a little stale, which is why there have been barely any update posts.
I still have some things to clean up and will then hopefully just merge the backend repo into the main repo

I think that's the play right now. Easy to set up soundboard options are limited right now on linux, at least in my experience. I think if you can just get the backend to a working state with a fair amount of bugs, you would see a lot of support and commits from people excited to finally see an update to the project. I think that will drum up some support for the frontend as well. Maybe add some more details to the page for the new UI to streamline the process of getting started with commits and such. I'm a huge fan of this project and I want to see it succeed, Thank you!

Personally if I check a repo that looks like it might solve my problem and it's last update was more than 6 months ago I avoid it, so I'd imagine your right. No-one wants to start relying on software that's already unmaintained, and no-one wants to maintain software they don't think anyone actually uses, so it wouldn't be surprising if a lot of people got turned off from contributing because of the silent development. From a developer standpoint it does make sense to not want things that are in-progress to be visible to everyone since you kinda just want to work on it solo without having to deal with ideas constantly being thrown around, but a repo that gets too stale can lose favour fast. It's a pretty hard act to balance but it's kind of just the unfortunate reality of rewrites/refactors a lot of the time.

I don't have a problem with making the backend repo visible, however I don't want to deal with people trying to compile something that's in progress and then complaining that it's not working (which will be the case here, as due to soundux' structure, frontend and backend have to be tightly integrated for them to work properly together).

Also, as can be seen historically, barely any people have contributed, and that's absolutely understandable as, especially the backend, uses many low level and in house libraries, which aren't really well documented (especially my libraries, i.e. rohrkabel don't have really good documentation as they're primarily developed for soundux) and thus it may be hard to get an overview of the code since many parts depend on other in house libraries and for some seemingly small changes big parts of those in house libraries have to be adjusted.

Progress of soundux is not only tracked in this repo, many of our in house libraries (some even part of other github organizations, i.e. saucer are currently being developed for the new soundux version.

TLDR: Progress on soundux is tracked in many smaller repositories which are in house libraries specifically built for the next soundux version, where you can partially track progress, since the new version will need all of those libraries to function properly. As there's seemingly high demand for me to make the backend-rework repo public I'll make it visible soon but don't complain that you can't even use the thing as it's not integrated with the Frontend at all yet.

---

Edit: If having no commits for some time looks "off turning" for some, I can embed the progress tracker into the readme and peridodically update it to reflect progress.

Edit2: Also, for people to be able to contribute it would be helpful if the new version is even runnable, that's not the case though, as frontend and backend are developed independently from each other, the backend currently only implements most features of the new version, however those features aren't used anywhere yet, as we first have to build the communication bridge from backend to frontend.
So when someone wanted to contribute at the current stage they would need to know exactly how we want to implement certain parts of the software and would also need to know how we then want to use and extend that in the future, which - at least in my eyes - doesn't sound like something anyone apart from Nico and me would know

---

Sorry for the text dump, just wanted to share my opinion on this.
I know you guys are waiting really long for the update now, I promise its coming, just wait a little longer and we'll publish the new stuff ^^
In case Nico isn't able to make rapid progress on the frontend I'll update this repo to work with the new backend while still having to old frontend just to get rid of some bugs in the meantime.

[LTS-Colonel]

If having no commits for some time looks "off turning" for some, I can embed the progress tracker into the readme and periodically update it to reflect progress.

Can't speak for everyone but that's more than just how I operate on Github...it's half the beauty of FOSS. If the majority of commits down the date column are over a year ago I go straight to the fork network.

Looking forward to Soundux updates when ready

[Curve]

There's been some changes lately which will lead to me taking over the Frontend development as well, which will greatly simplify the development process (no more syncing with team members + explaining how certain parts work).

I'll create new branches in the frontend and backend repository respectively over the next few weeks and begin implementing / finishing the rework ^^

For those interested, current blockers are:

• saucer

  The library which powers soundux' GUI
  I don't expect the update to take too long anymore, the currently missing features are:

  • modules support
  • documentation updates
  • updated examples ✅
  • updated command line utility ✅

[LTS-Colonel]

@Curve great to hear; thanks for your work! So many open source projects die on the vine (and understandably so) but I trust the vocal community of Soundux users is reassuring that you've built something useful to many. 💯

[Curve]

There's been some changes lately which will lead to me taking over the Frontend development as well, which will greatly simplify the development process (no more syncing with team members + explaining how certain parts work).

I'll create new branches in the frontend and backend repository respectively over the next few weeks and begin implementing / finishing the rework ^^

For those interested, current blockers are:

* [saucer](https://github.com/saucer/saucer)
  > The library which powers soundux' GUI
  > I don't expect the update to take too long anymore, the currently missing features are:
  
  
  
  * `modules` support
  * documentation updates
  * ~updated `examples`~ ✅
  * ~updated command line utility~ ✅

I'll probably post-pone module support for saucer and get started on soundux this week

[Curve]

There's been some changes lately which will lead to me taking over the Frontend development as well, which will greatly simplify the development process (no more syncing with team members + explaining how certain parts work).

I'll create new branches in the frontend and backend repository respectively over the next few weeks and begin implementing / finishing the rework ^^

For those interested, current blockers are:

* [saucer](https://github.com/saucer/saucer)
  > The library which powers soundux' GUI
  > I don't expect the update to take too long anymore, the currently missing features are:
  
  
  
  * `modules` support
  * documentation updates
  * ~updated `examples`~ ✅
  * ~updated command line utility~ ✅

I'll probably post-pone module support for saucer and get started on soundux this week

Sorry for the small delay, I took a quick detour and finished saucer v2.0.0.

This will tremendously improve the windows experience as there were some unsolved windows related bugs remaining ^^

[Curve]

I have started work on the frontend yesterday :)

[Funtimes909]

Hey, I love that you guys are still putting effort into this project, as someone else already mentioned the options for soundboards on linux as of right now are extremely limited so losing soundux to being unmaintained would really suck, however I was wondering if the new frontend is going to support being run on (X)wayland?
Great work on the project and really looking forward to the next release whenever its ready!!

[Curve]

Hey, I love that you guys are still putting effort into this project, as someone else already mentioned the options for soundboards on linux as of right now are extremely limited so losing soundux to being unmaintained would really suck, however I was wondering if the new frontend is going to support being run on (X)wayland?
Great work on the project and really looking forward to the next release whenever its ready!!

The Frontend has nothing to do with that, but yes, the backend will support Wayland

[kjcole]

If having no commits for some time looks "off turning" for some, I can embed the progress tracker into the readme and periodically update it to reflect progress.

It should be like voting 😉 -- Commit early, commit often. Wee commits for wee changes show progress and, should you ever get hit by the proverbial bus, makes it easier for others to follow in your footsteps without needing the grandiose vision of the entire masterpiece. Just one brushstroke at a time is enough.

[mansman12]

How is the update progressing?

[Curve]

How is the update progressing?

I have exam month currently, but am enthusiastic about continuing the work once I'm done with them ^^

I've also battle-tested the patchbay a lot as Venmic shares most of the patchbay code, and it seems like almost all bugs are ironed out right now and the code base is fairly clean :)

The hotkey code logic is also currently underway and will be "tested" with Vesktop in advance

[mansman12]

How is the update progressing?

I have exam month currently, but am enthusiastic about continuing the work once I'm done with them ^^

I've also battle-tested the patchbay a lot as Venmic shares most of the patchbay code, and it seems like almost all bugs are ironed out right now and the code base is fairly clean :)

The hotkey code logic is also currently underway and will be "tested" with Vesktop in advance

Good luck with exams and thanks for letting us know how things have been progressing.

[Curve]

Thanks! :)

[Hellscaped]

domain expired better renew

[Curve]

domain expired better renew

We are transferring the domain over to me

[OmriOn]

Whats the status of the app rn?

[PolyCatDev]

Yeah. How is stuff going? If the team wants contributions, they could link to a public repo for the app itself.

[Curve]

Yeah. How is stuff going? If the team wants contributions, they could link to a public repo for the app itself.

I'm still on the hotkey logic, currently fiddling around with how to get them to work with the xdg-desktop-portals.

Not looking forward to any contributions yet, but will happily review them once the project is in a stable state :)

[owosoup]

Oh about hotkeys, are random sounds per key planned in the next release? I could really use binding multiple sounds to one key and have one random pick at each press. It's fine if it isn't on the roadmap though.

[Curve]

Oh about hotkeys, are random sounds per key planned in the next release? I could really use binding multiple sounds to one key and have one random pick at each press. It's fine if it isn't on the roadmap though.

As mentioned in the discord, this is not planned as a core feature but will be possible to implement with the plugin API (however, I'm not sure if it will be ready for the first beta)

[Nebula-0-System]

i've been keeping an eye on this and i gotta say i'm really excited especially as it seems like you're getting a lot closer, especially in 2024, those progress meters keep ticking onward and upward. when there's a beta out, put my name down as i'd LOVE to be a tester for Linux Mint + Cinnamon, ping me when that door's open because i love Soundux and i'm excited to get the update installed and testing! also kicked 3€ your way on Ko-Fi. keep rockin!

[EmersonBiggons]

+1

[PolyCatDev]

Yeah. How is stuff going? If the team wants contributions, they could link to a public repo for the app itself.

I'm still on the hotkey logic, currently fiddling around with how to get them to work with the xdg-desktop-portals.

Not looking forward to any contributions yet, but will happily review them once the project is in a stable state :)

I don't know how to implement hotkeys properly with XDG Portal but I did find a workaround for OBS. It uses the OBS WebSocket to toggle stuff from a cli app I built. You hook up that app to your system shortcuts and toggle shortcuts from there. It's far from perfect and it needs a WebSocket but it's something.

https://github.com/PolyCatDev/obs-waykey

[Curve]

Yeah. How is stuff going? If the team wants contributions, they could link to a public repo for the app itself.

I'm still on the hotkey logic, currently fiddling around with how to get them to work with the xdg-desktop-portals.
Not looking forward to any contributions yet, but will happily review them once the project is in a stable state :)

I don't know how to implement hotkeys properly with XDG Portal but I did find a workaround for OBS. It uses the OBS WebSocket to toggle stuff from a cli app I built. You hook up that app to your system shortcuts and toggle shortcuts from there. It's far from perfect and it needs a WebSocket but it's something.

https://github.com/PolyCatDev/obs-waykey

I've seen that approach as well and as we'll have a REST-Api we should support that too.
However I'd still like to get the XDG-Implementation working, I'll probably get back to that soon :)

[Curve]

i've been keeping an eye on this and i gotta say i'm really excited especially as it seems like you're getting a lot closer, especially in 2024, those progress meters keep ticking onward and upward. when there's a beta out, put my name down as i'd LOVE to be a tester for Linux Mint + Cinnamon, ping me when that door's open because i love Soundux and i'm excited to get the update installed and testing! also kicked 3€ your way on Ko-Fi. keep rockin!

Love to hear, thanks a lot!!! Will put out an announcement as soon as the Beta is ready :)

[Nebula-0-System]

i've been keeping an eye on this and i gotta say i'm really excited especially as it seems like you're getting a lot closer, especially in 2024, those progress meters keep ticking onward and upward. when there's a beta out, put my name down as i'd LOVE to be a tester for Linux Mint + Cinnamon, ping me when that door's open because i love Soundux and i'm excited to get the update installed and testing! also kicked 3€ your way on Ko-Fi. keep rockin!

Love to hear, thanks a lot!!! Will put out an announcement as soon as the Beta is ready :)

fantastic!!! i'm excited, keep it up!!!

[bsvdoom]

Really cool, waiting for the stuff patiently, meantime, can we get maybe a fresh windows build of this "old" project, with the midi support included? Thanks-a-lot!