SFZ Designer Project (0.25)

[mildonm]

what do you guys think of assisted manual opcode entry? I can make all opcodes available, and also validate and correct the user-supplied values. Maybe something like this:

[pljones]

There once was a tool called sfZed that provided a grid-based assisted manual entry of opcodes for SFZ1. The final version should still be available here.

[himalaya]

it is the workflow that I'm trying to address in the project.

Hi,

I'd love to improve my current SFZ-creating workflow with just one visual app, like yours.

Currently, I use the EMU X3 sampler to quickly create a multi-sample preset. Then, I create the actual SFZ in Extreme Sample Converter. The whole process is actually quick: EMU can auto-create the preset very quickly, pull the root note from the file name and then auto-stretch each key zone perfectly. Save it and open in ESC, which creates the SFZ in no time. The problem is, I've moved to Mac OS, and both EMU X3 and ESC are PC-only. This means I need to use one of my dying PCs (WinXP), which are on their last legs. So, I'd love a new program that would do it all with a quick workflow. I'd be interested in any auto-preset creation options especially.

Cheers,
R.

[mildonm]

... pull the root note from the file name and then auto-stretch each key zone perfectly.

In the current version I'm testing there is still no way to automate the importing of samples, but I'm gonna work on it after I add assisted opcode entry.

How do you name your samples? It's certainly easier for me if I can just force users to name them a certain way in order to use the batch import function.

Maybe something like rootkey_lovel_sequenceNumber (e.g. c4_90_1.wav)

[mildonm]

There once was a tool called sfZed that provided a grid-based assisted manual entry of opcodes for SFZ1. The final version should still be available here.

Yeah, thanks. Something like that.

I might provide a way for users to add new opcodes via a text file.

[1wob2many]

Hi Mildonm,

My use of a visual app would be primarily for creating/editing large drum/sound fx kits. So to be able drag and drop samples either individually or as a batch into the interface would be helpful.

[mildonm]

Hi Mildonm,

My use of a visual app would be primarily for creating/editing large drum/sound fx kits. So to be able drag and drop samples either individually or as a batch into the interface would be helpful.

Sure, noted. drag n' drop would be really convenient for a lot of people.

[mildonm]

I've added assisted opcode entry which shows matching opcodes/values as you type, and validates the values you supply. You can also enter opcodes that are not on the list and their values will not be validated and corrected.

The only thing left before the first beta release is the multi-file import (no automap and dragn'drop yet).

Here's a screenshot:

[himalaya]

... pull the root note from the file name and then auto-stretch each key zone perfectly.

In the current version I'm testing there is still no way to automate the importing of samples, but I'm gonna work on it after I add assisted opcode entry.

How do you name your samples? It's certainly easier for me if I can just force users to name them a certain way in order to use the batch import function.

Maybe something like rootkey_lovel_sequenceNumber (e.g. c4_90_1.wav)

I name my samples like this:

Sample Name C4.wav

[mildonm]

Maybe something like rootkey_lovel_sequenceNumber (e.g. c4_90_1.wav)

I name my samples like this:

Sample Name C4.wav

In case the other 2 'tokens' are not supplied in the filename, the program must assume default values. But I think I'm going with rootkey_lovel.wav (lovel optional)

Specifying the lovel in the filename is useful when you have multiple velocity layers. If it's not specified, then the program will assume 0. We only need lovel because the hivel can be interpolated from a higher lovel.

I realized that sequenceNumber is not necessary for parsing, but people will always add some sort of marker to indicate round-robin variations. I can just simply sort them alphabetically. =)

[himalaya]

I think your naming system is good. Mine is a bit simplistic as these were samples created for Alchemy which only had a rudimentary implementation of the SFZ format.

[bigcat1969]

Looks very interesting. Thanks for all your hard work. I might finally get something out of SFZ besides a headache.

[mildonm]

I think your naming system is good. Mine is a bit simplistic as these were samples created for Alchemy which only had a rudimentary implementation of the SFZ format.

It's been a while since I've done any testing with alchemy player/alchemy. I used to recommend it as the preferred player for my sfz's until I realized that it's only playing 3 round-robin samples max. Mine usually have at least 5 or 6. Is it still the case?

Now I recommend sforzando.

[mildonm]

Looks very interesting. Thanks for all your hard work. I might finally get something out of SFZ besides a headache.

Thanks, I hope it would be helpful.

[Burzukh_Studios]

I feel weak at the knees just looking at it. Best of luck with this amazing slice of code !

Now only if someone could make a multi-out version of sforzando .....