BrainModular

Hi, I am not sure if this is a bug or something more global.
I use Usine Hollyhock 64 Bit (several older versions and the latest upd8 1.02.012k (OS: windows8 , i7)).

However, since I use hollyhock there was always the problem that important settings of a workspace are partially lost. If a workspace (made with Holly7) is re-opened with a newer version of hollyhock (e.g. Holly8) there is not 100% recovery of settings but additionally, there appear some changes that have never been entered. The list is really long (midi settings are partially lost, input channels that where not stored in a rack appear, midi control settings do not work properly although the setting is displayed correctly, the setting of plug-ins are partially lost - file paths are lost - input and output settings are lost. I would appreciate, if the settings (midi and audio and grid and plug-ins etc.) could be stored and re-called after re-opening with a different (latest) version.

Please tell me, if there exists a way how, a former hollyhock (64 bit) workspace can be translated to a newer version without building up everything once more (midi-grid-audio-plugin etc) - this takes more than hours because I use a lot of tracks and vst plug-ins.

I was really happy with your new and exciting software, but It is the first time for me that I observed something like this and it is really strange and I hate software that behaves unpredictably. In a live performance you need something more reliable - we started at the beginning of this year and now it is NOVEMBER and I don`t have a software that I could use - but probably I am the only one experiencing such problems !
Please, do not get me wrong I really want to use Hollyhock because of its open and creative aspects but if I cannot solve these problems it is useless for me.

At the moment I stopped at hollyhock version 7 because the translation to version 8 is to much time consuming for me - and it is really annoying if you save something and if you re-open the workspace it is lost or overwritten in a peculiar way. I am really not happy with this situation, but if there is any advice, how I could do it better please tell me.

Thanx for your support
Gerd

Are you copying your configuration files between previous and new installed versions?

I can confirm that I've experienced connection shifts, where an inlet is now connecting to a different outlet than it had in a previous version. The Sequins patch is broken by default for me in the (k) beta, where it was fine in (a). This happens in old workspaces and new ones, so the config folder should not be an issue.

To make it work I need to reset the polyphony. Luckily I've gotten really good at this over the development of the patch. But it still means moving crap around, resetting values, all that busywork. Frankly I haven't had the motivation because it was just too disheartening to be loading up the new beta and my (finally) 'finished' patch, only to have to turn to my collab and say "well, it used to work".

Part of me wonders, what's the point of fixing it if when there is no guarantee that it won't just break immediately? When stuff like this happens I feel like it is often treated as the user's own fault and what sounds like a serious issue is left in silence. I think this is wrong.

Be sure we listen carefully to our users ceasless, but our main problems is generally to reproduce the issues.
If we don't receive an example patch or a complete description where we can reproduce the bug, it's impossible to find .
That's also why we always encourage users to send bug report with the most possible elements.