New free SFZ player from Plogue

[davidv@plogue]

So, did you answer about a Linux version ? Open source or not open source, but working.

Not currently in the agenda for a full product.

[Kriminal]

Does it show sample names in the piano roll?

You can see the name of the last sample triggered on the Info tab of sforzando when you load a bare SFZ.

If you have ie a drumkit sfz and you want to step program in the PR with the mouse, its good to see whats where. Essentisl really. Lots of drum machines do this.

[davidv@plogue]

Lots of drum machines do this.

Are they all free??

[Kriminal]

Lots of drum machines do this.

Are they all free??

Whats that got to do with it?

[pljones]

If you have ie a drumkit sfz and you want to step program in the PR with the mouse, its good to see whats where. Essentisl really. Lots of drum machines do this.

I've never found it of the slightest interest when programming a drum kit to have this. What am I missing?

[Chad@PA]

Speaking of sfz drumkits... would you guys want more free sfz kits? or other instruments?

[Kriminal]

Speaking of sfz drumkits... would you guys want more free sfz kits? or other instruments?

Yes please

[Kriminal]

If you have ie a drumkit sfz and you want to step program in the PR with the mouse, its good to see whats where. Essentisl really. Lots of drum machines do this.

I've never found it of the slightest interest when programming a drum kit to have this. What am I missing?

if you have to ask, prob nothing.

personally i find it makes for a very fast work flow (and also easy to see if things are mapped how i want them)

[Chad@PA]

I always program my drum kits to follow GM mappings so never had to worry about PR names. But those are my tastes, GM mapping is always a good thing to start with. Don't see the need for PR naming if kits follow that consistency.

[Kriminal]

I always program my drum kits to follow GM mappings so never had to worry about PR names. But those are my tastes, GM mapping is always a good thing to start with. Don't see the need for PR naming if kits follow that consistency.

What if a kit contains just 20 samples of glitch drums or other unconventional sounds?

[pljones]

How would I get the labelling in Kontakt, by the way? You mean like in the group / piano roll grid layout? If so, I've always found the groups aren't single keys and overlap each other in obscure ways in the kits I've seen done for Kontakt.

(And that brings out a point -- you're not editing in the sampler: you're editing in a text editor and can put your own comments in and organise your sfz files (yes, that's plural - you can easily put different parts of one mapping in different files) logically. I find it much easier than Kontact. Which could be why I've never wanted the piano roll labelled.)

[David Else]

I would *REALLY* like to see a portable version, ie .DLL (and accompanying files if needed) only for the VST! A lot of people don't like to run a .exe for many good reasons.

Making a portable version would mean locking a particular build of ARIA engine inside a separate DLL, which would lead to major support issues for us.

On the PC, if i wanted to extract the .dll from an installation and then just copy it to my DAW PC, does it need any additional files or registry changes? CHEERS!

[declassified]

This is great software. Really. It loads even gigabyte multisamples quickly, consumes literally no CPU and has a nice interface.

I just found out that it supports FLAC as sample format. FLAC really does wonders on the file size of sustained notes etc. Awesome!

[billcarroll]

Not sure if somebody has mentioned this yet, but ...

I wanted to create a drum kit for a project in Pro Tools (the DAW is pretty irrelevant) and found a way to create a self-contained sfz file and sample set that I could upload with the DAW project for another producer so it would just work when they open the project on their end. This assumes both people are using Macs, and I haven't tested on Windows.

On the Mac you can quickly make an sfz patch and associated sample(s) portable with a project by:

1. create an sfz subfolder in your DAWs project folder (use any folder name you want)

Code: Select all

/?/your-amazing-project/sfz/

2. drop your sfz file(s) into that folder

Code: Select all

/?/your-amazing-project/sfz/drum_kit.sfz

3. for this example I created a subfolder in sfz named samples, and dropped the samples in

Code: Select all

/?/your-amazing-project/sfz/samples/your_sample.wav

4. Edit the sfz file and set sample location

Code: Select all

sample=./samples/your_sample.wav

* Make sure to change path and file names to fit your setup

Essentially the "period + forward slash"

Code: Select all

./

indicates current directory where the sfz file is located, and sforzando is able to recognize this to locate the samples.

Once you have the sfz file and samples in place in the project, you can insert sforzando on a track and drag the sfz file onto the interface to open the kit.

Now when you save your project the sforzando kit is saved in the project folder, and you can hand off the project folder self-contained.

If there is a better way to do this please let me know


* edit - turns out you can simply put the sample name in the SFZ file if the samples will be in the same folder as the SFZ file.

Code: Select all

sample=your_sample.wav

[davidv@plogue]

On the PC, if i wanted to extract the .dll from an installation and then just copy it to my DAW PC, does it need any additional files or registry changes? CHEERS!

The ARIA Engine is a separate DLL from the VST/AU/RTAS/Standalones which are merely wrappers. All products use the same common engine. So if you keep the main engine updated, you keep all products updated, without patching each and every single VST in your various DAW plugin folders.

Plus all the GUI assets are external and need to be referenced.