Batch Importing SysEx FM Lab to Layers

I’ve just discovered (to my delight) that FM Lab’s Import feature supports V50 sysex files. However, it seems I can only import and save one patch at a time. Is there a way to import an entire sysex and save out all the sounds as separate Layers? Clicking a patch, then digging through the menus to find Save As Layer… option is very tedious.

Hi @tjbuege !
Do I understand it correctly, that after importing the folder, you want to save each of the presets as an individual layer preset?

Edit:
From here into layers?

What I want to be able to do is be able to create my own layer presets by importing them from sysex files. Right now, FM Lab comes with Program presets and Layer presets. For example, when I create an instrument track and select Halion 7, then in the Halion editor select FM Lab, There is a list of layers to choose from:

I’d like to be able to create my own Layer presets. When I use the import function from within FM Lab and select a patch from a sysex file, I see the settings change in FM Lab and I hear the sound change. What’s the proper way to save this as a new layer that I can then edit? I’ve been right clicking the locked FM Lab layer in the Program Tree and selecting Save Layer As… When I do that, the saved layer is no longer associated with FM Lab, It’s like a generic Halion layer. And when I load it, there is no macro page and no zone editor. No way to edit the layer I just imported from a sysex. Shouldn’t this be possible?

As another example, if I skip FM Lab all together, and initialize a new patch as an FM Synth, I can go to the FM Oscillator section in the Zone Editor and select the Import button. I save it out using the same steps as above. Again, it’s not associated with FM Lab (I don’t expect it to be), but the layer can be imported / opened, and it’s editable.

I guess ultimately I’d like to be able to import these sysex patches as standalone FM Lab layers that can be saved individually, then later edited. I can’t seem to be able to do that. I’m finding Halion 7 very powerful, but also not easy to grasp. So thank you for any help you can provide.

Sorry, I didn’t answer this: yes, from that import screen. I want to be able to save each of those patches listed as it’s own stand-alone layer preset.

1 Like

The locked FM Lab layers visible in HALion 7, lack the structure necessary to function inside HALion Sonic.
HALion 7 layer presets can contain whatever you want, they need no special structure.

If you export the layer preset from HALion Sonic, and open it in HALion 7, you can see the difference (Flex Phraser, 4 aux buses on the main bus, tagging, etc.):

In our sound design guideline, we ask designers to save HALion Sonic presets and layers from within HALion Sonic. This ensures the correct structure automatically.

For sysex imports. the flow would be:

  • load the Init FM Lab layer preset in HALion Sonic 7.
  • go to the import tab and import the bank
  • click the preset you want to save as layer (the fm lab settings adjust)
  • go to the PROGRAM tab
  • right click the Init FM Lab. layer and save it.

Make sure the tagging and filename are correct, or else you will not find it under the FM Lab tile of the media bay. Not all layers are automatically tagged correctly (Flux has none for example), for various reasons. Each sound is a labour of love, created by an individual. Everyone has their own interpretation of the guidelines :wink: So most stuff deviates after over two decades of evolution.

More information about the guidelines we strive for are here:
https://steinbergmedia.github.io/halion-script-api/HALion-Tutorials-Guidelines/pages/HALion-Tutorials-Guidelines.html

Here for HALion Sonic specifically:
https://steinbergmedia.github.io/halion-script-api/HALion-Tutorials-Guidelines/pages/HS-Preset-Guideline.html

3 Likes

Thank you for such a detailed response! There’s a lot here for me to ingest. I was not aware of those guideline documents. I’ll spend some time studying them, and respond back here if I have any questions. Again, thank you!

1 Like

Don’t dig too deep into those guidelines. They are mainly for commercial library and instrument creators. But there is also some good advice in there if you want to take things further.

1 Like

I had a chance to try the steps you outlined above, and it works perfectly.

This is very helpful in my understanding. Thank you again!

1 Like