Another late-addition to sfz that is really useful when you're experimenting with various sets of waves is the #include directive . This allows you to tell the player "I want you to read in the contents of another sfz text file right here".
It works just like a #include statement in C source code (which is why it looks exactly the same -- starting with a #).
And like in C, you follow the #include with the name of your second text file, in doublequotes:
Code: Select all
#include "My_Second_File.sfz"
That second sfz file should be in the same folder as your first
I haven't experimented with enough sfz players to make a statement about how many of them support naming multiple directories like so:
Code: Select all
#include "My_Files\My_Second_File.sfz"
That's legal in the C language (although C uses a forward slash). And since this sfz addition mirrors the C statement, I would think that some player(s) probably supports it. But you'd best avoid using that feature.
So too, I can't make a statement about what happens if you precede the #include with a default_path. It's conceivable that a player may look for the other script there. But it seems just as likely to me that it would reserve default_path for your sample files only.