Missing Both Macro Page and Zone Editor When Opening Some Preset Layers

Virtual instruments HALion
1

I’ve been digging around with Halion 7 and FM Lab, trying to figure out the best way to import sounds from sysex files. I was looking at some of the preset layers, and found they don’t have a zone type associated when looking in the Program Tree. The icon looks like a lock. When selecting such a layer and opening the editor, there is no macro page and no zone page, so no way to edit that layer’s parameters. I tried browsing to the Preset layers for FM Lab using Media browser, and double clicking on a layer to create a new track. When opening the instrument, there is no macro page and no zones. Is this a bug? I know there is an FM zone supported by Halion, but it appears that FM Lab is not using it.

1 Like
2

Here’s what I see in the program tree when opening one of the FM Lab Preset Layers:

image
image590×384 22.1 KB

Note the Lock icon where I would expect to see an FM Zone icon.

3

Hi @tjbuege !
The lock is intentional. As an instrument designer, you can decide to lock layers.
The reasons are multiple, for example, layers containing proprietary code, samples only licensed inside an instrument but not individually (cough you could just bounce them cough) etc. etc.
If it would be up to me, all of this would be accessible and open. But on the other hand, it is cool to get some access to certain technologies and libraries and play them, even if I can’t rip them apart and fully mold to my own imagination.
In other words, it satisfies the needs of musicians, but not necessary sound and instrument designers.
Thanks for your understanding.

4

It is using it, but encapsulated in a script, see above.

5

Ok, yes I understand the reasons for locking the layer. I’d like to be able to import sysex patches as new layers that can be saved as layers, then edited later. It seems when saving a layer from within FM Lab “breaks” the link between that saved layer and FM Lab, and it can no longer be edited. See my other thread.

And I apologize for the two threads. At the time it seemed my questions were different enough that it warranted a separate discussion. Here’s a link to the other thread, for reference:

1 Like