BrainModular

which is the suggested routine to move from 5.x to 6.x while recovering workspaces and patches?
Previous versions needed the entire existing Config folder to be copied in the new one, is this still ok?
thank you

th good routine would be to import old setup in the Setup tab :
https://brainmodular.com/manuals/hh6/en ... tab-global

ok, thanks

generally the config folder is not compatible from a version to the next major version (ie. 5 --> 6)
I recommend to configure Usine from scratch...

I've uploaded the demo of 6.xx and scanned the plugins locations.
When on 6.xx all the plugins in the workspace originally made with 5.xx are showing "invalid" on all connections, while when I drag them from the plugins navigator into the patch they appear just fine.
Another thing worth of note is how different the graphic presentation of the patch is. In the image you see the patch buttons of the Aether plugin: on top is the one imported from the 5.xx and at the bottom the one loaded into the patch from the plugin list.
As Olivier wrote he wasn't sure that 5.xx was working with M series processors I was hoping the reason of the inactive connections was because of that.

I saw this just after sending my previous post.
Well, when you have a complex workspace, rebuilding it from scratch is quite a problem Olivier...

senso wrote: ↑

25 Feb 2025, 08:30

generally the config folder is not compatible from a version to the next major version (ie. 5 --> 6)
I recommend to configure Usine from scratch...

I saw this just after sending my previous post.
Well, when you have a complex workspace, rebuilding it from scratch is quite a problem Olivier...

In general, it is not necessary to reconfigure the workspace. But only the general Factory setup: scan of plugins, personal folders, language and other details in the Factory setup
Devices often need to be reconfigured. But you can try saving them in the old version and loading them in the new version.

The other thing is the event classes in the sdk have changed so some user modules may need to be recompiled - one of my user modules needs to be recompiled to work on hh6.
Basically a null event pointer used to be filled in automatically and it does not on hh6. This is accomplished using the new event class instead.

sm_jamieson wrote: ↑

30 May 2025, 19:05

The other thing is the event classes in the sdk have changed so some user modules may need to be recompiled - one of my user modules needs to be recompiled to work on hh6.
Basically a null event pointer used to be filled in automatically and it does not on hh6. This is accomplished using the new event class instead.

Hi !
The UsineEvent is simply deprecated but still working sofar. that is fortunate as I don't have the motivation to update 200 modules !

as for the null pointer error, it's just that HH6 is more picky than HH5, ie the error was present in HH5 but didn't trig an error.

Curious to see your user modules by the way

Olivar

It's a module that creates events from scratch and sdkCreateEvent on an empty event pointer does not seem to work in hh6. Not finished recoding yet with the new event class so there might be another error. The other module works with the old event pointer from hh3 sdk.

I have 3 user modules.
1. ParamMux that sends events of every type down the same wire. Some overlap with new Usine features.
2. A patch browser module
3. The other is a massive midi zone type module I use for live playing, a bit like Mainstage. I'll post a screenshot.

Well - there was another error !
When I get a chance I'll continue the sdk discussion in the SDK forum.

Here are screenshots of my big module:
In the wiring, the Mux outputs go to channel strips via my ParamMux module - the midikeyboard module writes directly onto the wire many types of events (2 levels of mux) that are extracted by ParamMux modules at the other end to operate the faders etc.

I was thinking of using Usine Objects for some of the control, but its slow and there is no fast feedback path for changing values - so its good for sending but not for receiving changes to events.