loading HH2 workspaces into HH3

[parityflux]

Hello,
I am planning to upgrade my HH2 to HH3/4 and am wondering if I might encounter difficulties in loading in my old workspaces. I did a few searches and did not find any relevant info. Can I import OK, or should I "start over"? I would like to at least bring in my last workspace used in HH2, as I put considerable work into it. It is not overly complicated by any means, but there are a lot of subtle things related to my devices that I may want to retain. Just checkin! I'm all in regardless.
-John

[nay-seven]

Hello,
depends of your workspace, but yes try first to import in HH3, cause i'm afraid you'll need to work on them obviously for HH4

[x.iso]

basically some modules might have changed, so if something doesn't work, check inputs/outputs of the modules, if everything is preset and wired correctly. for instance moving from HH3 to HH4 I had to fix a little bit my complex patch that used Video to Array colors, as inputs have changed (for the better).

[SylvainT]

Hello,

As I can remembre, you don't will encounter many problems from HH2 to HH3.
It will be certainely the same with HH4, except with the grid, and maybe with Plugins.
The grid was completely rebuilt, so you'll find your patches/racks and presets (from HH3) in the grid, but the curves disappear, so any automations will be lost.
HH4 is now 64bits only, so on Mac, you'll need to update your OS into 64bits, and your 32bits plugins won't be reconized in HH4 (be really careful with Catalina, not sure it is a good OS, High Sierra works definitively fine for me, I suppose Mojave also). It is the same on PC I presume, but HH3 was allready available into 64bits.
Regarding wires in the patch, it seems that everything is now in order, there was some conflicts, wires not connected at the right inlet, but it is adjusted now.
No problem with devices at all, it must be transparant.

All the best

Sylvain

[parityflux]

Thanks for the great replies. I really appreciate it as well as the confidence. I let ya know how it goes.
-John

[parityflux]

Well, I thought my workspaces were simple enough, but there were issues loading v2 workspaces into v3. Among them, these struck me as important:

1) I had two MIDI busses on two of my inputs to handle sending massaged data to all of the other racks. The customized components of the input devices are there, but the busses I created near the "Midi to Usine" outputs disappeared and I lost MIDI functionality in most racks. The busses were critical to my entire design because they carried specially filtered / translated MIDI
2) patch presets that were present in the old workspace now give an error when changing presets (SetPreset access violation); so those won't work at all.
3) some VSTi's needed refreshing, others did not. I did reinstall my OS and all VSTs a few months ago and I'm just getting back into HH, so this doesn't surprise me too much.

I'm gonna poke around some more tomorrow. I don't mind rebuilding a lot of this.

[nay-seven]

and have you try to import your HH3 workspace in HH4 ?
if your encounter reproducible errors, feel free to send report to support@brainmodular.com

[x.iso]

1) I had two MIDI busses on two of my inputs to handle sending massaged data to all of the other racks. The customized components of the input devices are there, but the busses I created near the "Midi to Usine" outputs disappeared and I lost MIDI functionality in most racks. The busses were critical to my entire design because they carried specially filtered / translated MIDI

if you mean that you edited device patch instead of using patch in a rack, then it makes sense that it would disappear. but, have you tried 'import old setup' option in general settings? that might also import device patches.

[parityflux]

and have you try to import your HH3 workspace in HH4 ?
if your encounter reproducible errors, feel free to send report to support@brainmodular.com

I wanted to get a working HH3 workspace before trying HH4. I'll get it going eventually. I will try to observe for reproducible errors and report them as appropriate.
-j

[parityflux]

if you mean that you edited device patch instead of using patch in a rack, then it makes sense that it would disappear. but, have you tried 'import old setup' option in general settings? that might also import device patches.

I'm going to do just that, next. I'll start with a clean space and import saved devices and racks as needed. I want to build a new environment for a gig anyway, so this is a great way to do it.

Just to be clear, most of the devices elements were intact, it was just any midi busses were missing. Everything else was there IIRC.

Thanks x.iso.
-j

[parityflux]

Loading into HH4 beta was a much more successful venture. HH4 just works so much better and there is greater clarity throughout. I was up against internal device-id and VST plugin-id conflicts due to my rebuilding of the Windows box, and it was pretty clear in HH4 where the issues were. Thanks so much. It just gets better and better.
-j

[nay-seven]

Good news ! glad you like it