h2p ugly compressed binary?

[hakey]

Other than, eg, storing Zebra oscillator waveform data, what's the reason for the "ugly compressed binary" at the end of h2p files?

Deleting the section in Tyrell h2p files seems to have no untoward effect.

[Urs]

Other than, eg, storing Zebra oscillator waveform data, what's the reason for the "ugly compressed binary" at the end of h2p files?

Deleting the section in Tyrell h2p files seems to have no untoward effect.

There's the current preset path for when you open the gui, in ACE/Bazille there's information about which cables have been daisy chained, in Zebra there's the text and labels of the XY controls and the key/velocity scaling curves, but also the Grid information. Then there's MSEGs for MFM2 and Zebra. And custom LFO waveforms. ModMappers. Lotsa stuff like that, not so much in TyrellN6 or Podolski.

[hakey]

not so much in TyrellN6

So what does the compressed binary in Tyrell represent?

[Urs]

not so much in TyrellN6

So what does the compressed binary in Tyrell represent?

The last preset directory and such. Not 100% sure, there's a lot of things and services that are only needed by the "bigger" plugins.

[hakey]

Strangely, saving the same Tyrell preset in the same location gives a different string each time.

Just another of life's little mysteries, I guess.

[benj3737]

I use zebra a bunch in max msp and actually would love to be able to decipher the xy labels etc. This is probably a super-esoteric request, but that would help me out a ton. Is there any way to decode that binary info?

[Urs]

I use zebra a bunch in max msp and actually would love to be able to decipher the xy labels etc. This is probably a super-esoteric request, but that would help me out a ton. Is there any way to decode that binary info?

It's messy.

I'm contemplating to let people edit text portions directly. That is, the'd be right up there with the parameters such like

#XY1_l="My label text\nspanning two lines"

That's going to be important so people can find Zebra presets by XY-descripton.

[benj3737]

I use zebra a bunch in max msp and actually would love to be able to decipher the xy labels etc. This is probably a super-esoteric request, but that would help me out a ton. Is there any way to decode that binary info?

It's messy.

I'm contemplating to let people edit text portions directly. That is, the'd be right up there with the parameters such like

#XY1_l="My label text\nspanning two lines"

That's going to be important so people can find Zebra presets by XY-descripton.

That would rock!