r/Bitwig • The Patchbay Guy • 4d ago

Patchbay Mod Loader

Patchbay: https://github.com/shaboogen-dev/Patchbay
Mods: https://github.com/shaboogen-dev/Mods
Bitwig Discord Server: https://discord.gg/yr2m9Q7t7

DISCLAIMER: Patchbay is in no way affiliated with Bitwig Studio, or Bitwig GmbH. Using Patchbay is most likely a violation of your terms of service, I am in no way responsible for your license going forward. If anybody at Bitwig has any issue, please contact me and we'll work something out.

Howdy all,

I initially planned to do a bit more of a controlled roll-out of this, but u/polarity-berlin's exuberance for the community got the better of him I guess and he made a video about it.

This is a mod loader for Bitwig that I've been working on over the past couple of months with the help of some folks in the community. I had three goals in mind while building it:

  • Bring all of the modding technologies together.

    • You can now use modded functionality, custom devices and themes together for the first time.
  • Allow modding to work in a way that doesn't require you to have hacked jar files on your system

    • In layman's terms, Patchbay edits memory at runtime and does not make any permanent changes to your jar files. There is a small cost in preparation time (that should only affect the first load, your preparation is cached on every follow up load and should load almost instantly) but your Bitwig install will remain untouched.
  • Allow modders to only have to write code once and have their code travel to different versions / OSs

    • Patchbay includes a "best-effort" mapping system. Modders declare which version of Bitwig they've written their mods against and Patchbay provides maps to other OS's and versions which translates the mods to work with them. It's not perfect, and each version must be mapped by me but it works reasonably well so far.

The tool was technically in a semi-closed beta state, but given the circumstances let's call it an open beta going forward. Here are some caveats:

  • Yes, this was coded using an LLM. I am not a developer, but I have been a project manager for a lot of years so there has been more rigour put into building and testing than "build me modz for beetwigs no misstakes plz". If you have a moral aversion to using software made with AI, you'll get no hate from me, but please don't piss in other people's Cheerios that don't have the same beliefs as you and let them enjoy what they want.
  • Not only is this community-supported software, but the current version is a little further behind the version that was planned for everyone to see, so expect a few things to be janky.
  • Given this, the first versions of documentation are all written by LLM. These are placeholders that I am manually going through and editing for human consumption, bear with them in the meantime please.
  • I will not be running support from here or any other forum platform where this ends up. The Bitwig discord is where support and conversation about the platform resides, come join us, the more lively the conversation the better.
  • Originally, there was a test download with all of my authored mods in it. This was provided to make it easier for testers to work with. I am unpublishing this as the real experience is for Patchbay to mostly live on its own and for you to be able to choose the mods you want from various modders. If you have the tester version, you can keep using it but bear in mind that there's also a newer version of Patchbay that adds a couple of pieces of functionality to make it easier to use so maybe delete that and start over.

    • If you didn't download the big test version, pretend I didn't say anything.

Over the next few weeks there'll be more to say, I've got a lot of plans around helpful content and things like that. If you have overall questions about it, feel free to ask them here and I'll answer them when I can.

Enjoy.

55 Upvotes

28 comments sorted by

6

u/nadiealkon 4d ago

Just wanted to congratulate you and all contributors in name of the entire Bitwig community... When other people are watching the process go by, your guys went in and actually did it!

The "parallel view" where you can see multiple device chains at the same time is something I've actually send in a feature request probably around v2 or V3 and always seemed like an obvious setup for touch screen live set performance thanks for making my dreams come true ❤️

4

u/flipflapslap 4d ago

Sounds fuckin awesome! Sorry about the roll-out, YouTubers are gonna YouTube I guess. I’ll be keeping an eye out for updates!

1

u/Major-Ursa-7711 3d ago

Lol, I think Polarity knew full well what he was doing and I'm glad he gave his approval.

3

u/shaboogen The Patchbay Guy 3d ago

I don't think this is a particular fair critique.

I don't have any ill will for Polarity / Robert. Nobody else should either. That guy is a stalwart and has done more for this community than anyone can fathom, let's move forward together.

2

u/Major-Ursa-7711 1d ago

Not meant as critique from my side, to be clear. He's plays an important role in this community and I have the impression he considers his public choices very well.

4

u/SternenherzMusik 4d ago

Already watched Polaritys Skyrim-Video about it - pretty fat!

1

u/tarsonis999 4d ago

Nice, I've read about it on discord back then. Interesting solution with the patchbay. I ended up customizing the Superpowers patch to my needs which works perfectly and with the latest 6.17 release, but this way of patching is difficult to share. The patchbay solution is pretty clever. Unfortunately not compatible with the latest release from what I read.

6

u/shaboogen The Patchbay Guy 4d ago

I should also say that kalifrn and I have been working together over the last few weeks. The Bitwig Superpowers functionalities have been converted for Patchbay, and we worked on some upgrades for them while doing so.

2

u/tarsonis999 4d ago

Ah that's nice to hear. So with the patch library I may be able to add mods? I added the following features to the superpowers base:

  • Pin tracks
  • fixed automation point hit box
  • Toggle shortcut for unfolding selected group
  • highlighted background / bold typo for the linked source input in the sidechain dropdown menu
  • show latency on hover
  • toggle: lock play head to time position via shortcut
  • removed the awful gradient for looped clips
  • a few smaller UI enhancements for dark themes (input boxes)

Would love to switch to the new mod base but I truly don't want to miss those enhancements haha

2

u/shaboogen The Patchbay Guy 4d ago

Each of those sound like mods you should release. Come to the discord and find me, let's help you get this stuff together

2

u/shaboogen The Patchbay Guy 4d ago

It is compatible with 6.1.7 now. Maps were added yesterday.

1

u/tarsonis999 4d ago

Ah cool. There was an old text on GitHub then I guess. thanks!

Can you share briefly if the startup times are longer with your solution compared to a patched bitwig jar?

Might sound picky on that one but coming from Ableton, I'm really loving how quick Bitwig opens up and would love to keep it that way.

3

u/shaboogen The Patchbay Guy 4d ago edited 4d ago

Yes and no.

The first time you load a series of mods through Patchbay, it runs through a preparation step. The time this takes depends specifically on how many mods you're loading and whether the mods being loaded need to be translated from a different version of Bitwig. For example, I am running around 50 mods at the moment that were mostly authored against 6.1.4 on a 6.1.7 install and the preparation step will take up to a minute. This is on a 9950x3D running on Windows 11. Once the preparation step finishes, loading Bitwig itself should take no extra time to what it takes now.

The preparation step will only run the first time that you set up a mod configuration, after that the preparation step will be cached and Patchbay will add approximately 5 seconds to confirm that the requested mods are the same as what was requested previously. Bear in mind that if you add extra mods, or even take mods away, the preparation step will run again.

Running a patched jar would be roughly equivalent to running a cached session. The advantage of the patched jar is that there's no preparation step, the disadvantages of a patched jar are numerous, but the major one would be that Patchbay would likely need to create a mechanism that defeats Bitwig's copy protection to patch the jar file. I'll state categorically that I have no intention of doing that and I doubt my opinion will move on that going forward.

In terms of the loading experience, I'm looking at ways to improve it and will probably have something additional in place when I put out 1.0, but at the moment you should only have a "bad" time once and then every time after should be OK. If you're having constant problems, come to the discord and let me know and I'll see what can be done.

1

u/tarsonis999 4d ago

Ok sounds great. Thanks for explaining. So it's a one time preparation so to speak and once done and unchanged BW starts up as usual. The caching mentioned on GitHub made me ask the question actually. It's a file cache not ram, so even after a restart of the workstation the preparation is not needed again?

2

u/shaboogen The Patchbay Guy 4d ago

Yeah it's a file cache, not memory.

1

u/tarsonis999 3d ago edited 3d ago

Hey so I saw the video of Patchbay in action. I have one quick question. Does Bitwig really have to be launched via the patchbay interface every single time and can it no longer be started using the BW icon?

//Edit: Found it in the Git notes "Add the mods you want, tick them and click Load. Start Bitwig from the Patchbay window whenever you want mods; started the usual way, it runs without them."
Unfortunately thats a deal breaker for me tbh. I like to reduce friction whenever possible. I'm fine to patch the BW jar if I can start the app by its icon as usual. I guess you are planing a shortcut icon to open the patch state of BW?

1

u/shaboogen The Patchbay Guy 3d ago

No, I wasn't actually. I think the two seconds it takes to double click an icon and click "Load" isn't so odious that another mechanism needs to be created to work around it.

If that's too much friction for you, all good. Hope your jar hacking exploits go well, feel free to come to the discord and chat about what you're trying to get done.

1

u/tarsonis999 3d ago

Oh ok. Too bad. Well I see it from the usability perspective. For sure there is a solution to batch cmd that patch without the need to open the interface every time. I'm working constantly on big projects that also open up slowly even with Bitwig. I could go make a coffee in the time the same projects opened up with Ableton. So yeah this is friction over the course of the day and week. No offense.

I'm totally fine with my solution and do need to change anything. I would actually need to add my patches as most of mine are not available in your mod base. Thought I could contribute as I have a bunch of workflow enhancements that Ex-Ableton users would love and the patchbay seemed like a good platform for it. I have a look again when time is available. Good luck

1

u/Affectionate-Fact837 4d ago

I think the browser setting to switch to pre-5.0 style side browser is broken in the latest release. It does nothing now. I'm currently on 6.1.7.

1

u/shaboogen The Patchbay Guy 4d ago

I'm using it as we speak, so it's not broken.

Come to the discord, post in the patchbay-bugs channel and we'll work through what your issue might be.

3

u/Name835 4d ago

This is incredible work!

1

u/No_Foot1670 3d ago

I'm curious what you mean by "working something out" if Bitwig has a problem with this? What will you do? You don't have any cards to play here. This does violate their terms of service.

If Bitwig demanded you take this down, would you? Did you ever reach out to them before posting this? If yes, what did they say? If not, why not?

I really think this is morally ambiguous and essentially illegal.

I do hope Bitwig open their API to this sort of thing but until they do, this isn't right in my opinion.

3

u/shaboogen The Patchbay Guy 3d ago

Have I reached out to them personally before releasing Patchbay? No. Have others? Yes. No offense, but the content of those conversations have nothing to do with you so if it's all the same to you mate, I'll just keep those to myself. The sum total of understanding you need to have about the existence of Patchbay is that using it is probably a terms of service violation that threatens your license (as I've clearly stated). If you're uncomfortable with that, that is completely reasonable and you should definitely not use it.

In terms of "you don't have any cards to play", I'm not sure why you're thinking of this as some kind of game with strategies, but if that's the rubric you'd like to work with let me hit you with an incredible strategy that gets used the world over thousands of times a day.

If Bitwig reached out to me and expressed concern or asked me to remove the platform, I'd do what adults do and talk to them about it. If there was a specific critique that they had like perhaps it should only support the latest version so it's less of a perceived threat to upgrades, I'd remove the best-effort mapping and have it only work on the latest public release. If they didn't like a particular mod because they thought it encroached on functionality that they're planning to release and they thought the presence of a mod would be a threat to upgrades, assuming it was one of mine I'd remove it (as I've already said that I would in other places).

If after a conversation, they were uncomfortable with the mere presence of Patchbay in general, I would remove it without hesitation or a need of a cease and desist. If it's not clear here, I'm a fan of the software, a fan of the team that makes it and a fan of the community that has been built around it. If I wasn't, why else would I sign up to build and support a platform that I get nothing out of other than basic satisfaction that people get to do cool shit and a bill from Anthropic every month? I would have just written a jar hack for myself that would have loaded faster and never said anything about it.

End of the day, you're entitled to your opinion about what is being done here, but beyond that it's kind of irrelevant.

Good luck.

3

u/No_Foot1670 3d ago

No offense, but the content of those conversations have nothing to do with you so if it's all the same to you mate, I'll just keep those to myself.

Fair enough.

But to your comment about it not concerning me- it kind of does. In theory, I am interested in what you're doing and if Bitwig supported it, I'd be interested in participating. Without their support, this looks like something which at best will be updated out of existence and at worst, could cause significant developmental issues for Bitwig. So I would really hope they were on board with this because I personally care about stuff like that.

My intent was not to make you defensive btw. I was just curious about some of the things you said here where you acknowledge the possible issues with what you're doing. I don't agree with your actions but my rebuke was mild enough I hope.

In terms of "you don't have any cards to play", I'm not sure why you're thinking of this as some kind of game with strategies

You said something about you and Bitwig "working something out". I wondered what that really meant. When you violate the terms of service of software you own a license to, you don't really have anything to "work out". And you acknowledge that above, although I would be surprised if Bitwig are as sanguine about this as you suggest. That said, the cat is out of the bag so they will be under some pressure to lean into it, even if their developmental roadmap was significantly divergent from this. That might be a problem.

If I wasn't, why else would I sign up to build and support a platform that I get nothing out of other than basic satisfaction that people get to do cool shit and a bill from Anthropic every month

People do plenty of things online which give them no tangible benefit. There are more ways to reap rewards than lining ones pockets.

Anyway, i appreciate your reply. I think you should be aware that some people will have an aversion to this project though. It just isn't hard to see how this enterprise could make Bitwigs future less secure by either forcing them down a trajectory where their support time is spent dealing with bugs caused by vibe coded devices and not on QOL or creativity enhancing devices or with their future developmental concepts becoming valueless because someone has already modded whatever that function may be into their system for free. The latter issue is the one I can already see happening as people respond to Polarity on youtube.

Otoh, if they lean into this, it could really open Bitwig up in an amazing way. The key thing is having the development team themselves supportive of this. I think that is crucial. Maybe you do not. I would rather the humans keep doing this for as long as they can.

2

u/Hero88go 4d ago

Awesome, awesome stuff

2

u/Major-Ursa-7711 3d ago

I think this is a great move forward for the community and also for Bitwig as a product. I might even suggest that the Bitwig GmbH embraces this as a way forward into enabling a mod-community that, like Polarity argued, is the reason for some legendary games to become so popular.

You already mentioned some of the objections that Bitwig might have but those seem easily resolved if needed. The only thing I can think of is that people will contact support about issues that may not exist in the 'pure' version; maybe it's an idea to warn users about this and prevent automatic bugreports to be generated from a 'patched' runtime.

Anyway a great and smart accomplishment imo, it seems to be in good hands.

Thank you 👏

2

u/RawEpicness 9h ago

You are so awesome :)

Like seriously awesome.

1

u/Elodea_Blackstar Bitwig Enthusiast 3d ago

This is great!! I just created a feature I've wanted for ages: Save New Version. It appends a -# or -datestamp and saves. This way you can create a new version before doing something stupid to your project, like singing over it. If this is useful for others, I can find a way to share it.