MSF Online Preset Exchange—Discuss

[arachnaut]

Hmm - yeah, I see that. I'd never kept Sort on before, since I prefer to stick with my dragged arrangement (can't really see any use for alphabetizing, except maybe to find something). I'm about to send a crash report; will mention this, too.

Simon always provides a list of his presets with descriptions, macro modulations, etc. in alphabetical order in a PDF with his products.

So I go through his list, but if the presets are random, that makes it hard. It also makes it easy to known when you are done with a longish list.

If I make Sort be ON and save the presets, they are not saved in a different order, the order is the way they were made, I guess.

I can use my XML editor to sort lines If I can get the sort field into fixed columns, so with some effort, and possible mistakes, I can edit the presets if I wanted.

I have done things like this in the past, for example, before Falcon had the batch processing for sample keys, I would use my editor on it's presets more easily than replicating in the GUI.

Since the editor is programmable, I have rules files for SFZ files and stuff like that which make sample editing easy.

As you might guess, I prefer ascii readable files over binary formats for program resources. It also might explain why I am so interested in the XML files in Appdata and ProgramData folders.

[David]

Makes sense:) And sort not sticking definitely doesn't—we'll see what Vojtech thinks!

[David]

what Vojtech thinks:
"the sort thing is the way it is, it's only visual settings for the preset window. "

Sorry!

[MeldaProduction]

Yep, sorry folks, it would be too problematic... I actually have an easter egg there, which allows me to sort stuff permanently, then it works with the arrows too, but you know it's permanent, so I don't think it's the best thing to have

[arachnaut]

Is there a way for us mere mortals to enable the Preset Management Window?

preset-management-window.png

[arachnaut]

One issue I am thinking about, at least I was a while ago, was to use the FX Matrix row and column as a parameter to an FX array processor.
The idea was that every module in the FX grid was identical, but it used it's x y position as a parameter to modulate something inside.
As a simple example, imagine a 32-band parametric eq whose center frequency is set by it's x position in the Modular32 grid. The y parameter would not be used here.

I don't think this is possible, is it?

[David]

Grid [matrix] position isn't modulatable, that I'm aware of. Nor can it be a mod source. Interesting idea, though—Maybe the new Order MP type could be leveraged for something like this…? Though AFAIK, it's not modulatable, either.

[arachnaut]

It doesn't need to be modulatable. I would use the grid number in a MATH expression (for example to calculate the center band of box N) - then the rest can modulate around that frequency.

[David]

I figured it was unlikely that I actually understood; now I'm sure:)

[arachnaut]

I'll be a bit more precise.

I want to make N modules, where N may be a small number from, say 8 to 32. These are frequency band modules.
If there are 8 these would represent octave bands, if 32, they would be one-third octave bands.
The band range would be set by means of using the grid number in an expression or transformation graph.

That way, there is only one actual module made and it is parametrized for any number of bands (pass bands).

Next I want a delay line set to a delay based on 1/(square root of frequency).

This is also parametrize with the same grid number.

So with one block or module, I can make identical pass bands. This uses the grid X position.

Now make a row of 32 of these. They are 1/3 octave bandpass filters with a delay line set proportional to the center frequency of that band.

This implements an N-band acoustic dispersion unit.

Now copy that whole row and paste in another row. That is a two-stage acoustic dispersion unit.

Do this until you run out of cpu and realize an M-stage acoustic dispersion unit.

Now we can use the grid Y position to enable the rows.

We set a parameter from 1 to M where M is the number of stages. This is compared inside the module to enable or disable the stage. If stages is set to say, 5, all the rows above the fifth will be disabled.

The end result is that I have made an N band M stage acoustic dispersion device from a single module using the grid N, M position as an input parameter. If arrays or tables are available, these parameters could be pre-calculated.

[arachnaut]

Here is a mockup of one way to do it, using a crossover to split the bands.

Clipboard 1.png

[David]

A really interesting new Device has been uploaded to the MSF Exchange: The Belladonna by Tyler Dedera.

It's interesting in at least these ways:
1. It sounds great.
2. It's a full-fledged Device, with a very rich Easy Screen.
3. There's an excellent Bars section showing off direct drawing from the Easy Screen into a Rhythmizer volume preset. I suggest popping up the R preset in Edit mode then going back to the EScreen to watch how the Bars actually affect the R preset screen as you adjust them.



AND…4. It includes Device Presets! Tyler's built a bunch of diverse presets and worked them all into an incredibly massive Banks MP so you can select between them right from the Easy Screen, without using any sort of standard Melda Preset Browser. Brilliant idea.



By all means check this one out!

[David]

Here is a mockup of one way to do it, using a crossover to split the bands.
Clipboard 1.png

Sorry this cool idea has been languishing here un-responded to (like everything else!) But in this case I really think you should make a new topic just for it, so that Vojtech is more likely to see it. His default reaction is of course "sorry, no time". But not always; definitely worth a try.