SFZ Designer Project (0.25)

[davidv@plogue]

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

That would be us.

[mildonm]

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

Hi, thanks. I'm excited to release it too. I was supposed to be ready today to share with you guys an early beta since I've finished most of my initial goals, but I wanted to add a few more features that I think would be really useful.

Also, I realized that I haven't added all the opcodes yet. So maybe a couple more days.

[himalaya]

Don't rush. Take your time and make it good.

[mildonm]

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

That would be us.

You guys are awesome.

[mildonm]

Don't rush. Take your time and make it good.

[davidv@plogue]

You guys are awesome.

A good editor is really what SFZ needs. If you set your executable so that it can open an sfz file by double clicking on one, (making your editor the system's default), then it could easily be used with sforzando. Just save in your editor, and sforzando will get a warning that the file has changed, updating it instantly, and validating content.

We are looking forward to it!

Cheers

[mildonm]

A good editor is really what SFZ needs. If you set your executable so that it can open an sfz file by double clicking on one, (making your editor the system's default), then it could easily be used with sforzando. Just save in your editor, and sforzando will get a warning that the file has changed, updating it instantly, and validating content.

We are looking forward to it!

Cheers

Thanks for the tip David. In the current version, I only have an export-to-sfz option because I thought I would be saving a bunch of non-sfz data in the project file. I also haven't built a parser yet, which I'd have to build before I can have an automap feature.

Now I think it's a cool idea to save/open directly to/from sfz file.

Are there any sforzando-specific opcodes/values that I should include?

[davidv@plogue]

Thanks for the tip David. In the current version, I only have an export-to-sfz option because I thought I would be saving a bunch of non-sfz data in the project file.

Gotcha. In any case, if you save to SFZ, open that same SFZ in sforzando, do some edits in your editor and resave, sforzando is going to pick up the changes.

Are there any sforzando-specific opcodes/values that I should include?

Would need to take time to look at what you have so far. If you stick with Dimension Pro SFZ 2.0 support level, we are fine. We really only "plugged holes" in the spec so that we could do stuff other samplers did. Would take all day to go through them, but we do list them on our sites.

Cheers

[mildonm]

Are there any sforzando-specific opcodes/values that I should include?

Would need to take time to look at what you have so far. If you stick with Dimension Pro SFZ 2.0 support level, we are fine. We really only "plugged holes" in the spec so that we could do stuff other samplers did. Would take all day to go through them, but we do list them on our sites.

Cheers

Alright, thanks. I'm still in the process of gathering info on the latest spec. I think it will be fine with just the 1.0 opcodes at least initially.

I'll look forward to your feedback once the beta is out. Thanks very much!

[ThomasHelzle]

Thanks for the tip David. In the current version, I only have an export-to-sfz option because I thought I would be saving a bunch of non-sfz data in the project file. I also haven't built a parser yet, which I'd have to build before I can have an automap feature.

Now I think it's a cool idea to save/open directly to/from sfz file.

Yeah, sounds really good to be able to edit on the fly with live-update
But maybe it would be good to directly implement some kind of backup solution then?
So in case something goes wrong while saving or editing, a fallback is available?
Like automatically creating a subfolder "backups" and on each save, copy the previous version there, with date and time added to the filename.
SFZ is very small so the footprint shouldn't be a problem...

I agree that a visual editor should do a lot of good for the SFZ community.

Cheers,

Tom

[mildonm]

Yeah, sounds really good to be able to edit on the fly with live-update
But maybe it would be good to directly implement some kind of backup solution then?
So in case something goes wrong while saving or editing, a fallback is available?
Like automatically creating a subfolder "backups" and on each save, copy the previous version there, with date and time added to the filename.

Hi thomas. You know, nice idea, that actually crossed my mind. Auto backup should be available but optional.

But let's think this through...

The main advantage of having a separate format for saving the project is you can be sure everything is intact. loading an sfz directly would make it subject to parsing, which is not a problem. But if somehow you edited the sfz file in notepad before loading it in the editor you might see some changes, whereas loading it from a project file will guarantee it stays exactly the same. Plus, other things like settings, which windows/tabs/panels are open, etc., can be saved in a project file and not in an sfz file.

How about this: when you double-click an sfz file, it will open in the app but the app will say "Do you want to import this SFZ file?". To save the changes you can click export-as-sfz. Clicking 'save' or 'save-as' will still save it as a project file.

So it's still direct loading and saving, and it's clear that sfz files are parsed and generated, and project files are simply loaded and saved.

[ThomasHelzle]

Makes a lot of sense to me - best of both worlds

Cool stuff - looking forward to your editor!

Cheers,

Tom

[Asoretzu]

Hi.
I can help you whit the Linux version.
Cheers.

[mildonm]

Hi.
I can help you whit the Linux version.
Cheers.

Hi, welcome to the forum. =)

I will begin the linux version beta testing after I've released the first non-beta of the Windows version. Then after that, osx beta testing.

[mildonm]

I added a new feature to the opcodes panel that allows you to apply a group's opcodes to all opcodes in 4 different ways (see screenshots):

1. Modify - will modify the values of opcodes that also exist in other groups but will not add them if not present. Useful if you don't want the other groups to have an opcode specific to the current group.

2. Add - will add opcodes that are missing in other groups, but will not modify existing opcodes. Useful if you don't want to change the values of the opcodes in other groups, but want to add something new.

3. Modify and Add - will modify existing opcodes and will add missing ones. Combination of the 2 above.

4. Conform - will replace the entire opcodes/values list of a group with the current one. Like #3 but will also remove opcodes that don't exist in the source group.

Screenshots:

opcodeapply.png

opcodeapply4.png