bb.linuxsampler.org

Just some proof that I'm actually still working on it...

dahnielson wrote:Just some proof that I'm actually still working on it...

Nice to hear that. I think it's time to move on and start working on another formats and sfz looks like a very good choice.

grishata wrote:

dahnielson wrote:Just some proof that I'm actually still working on it...

Nice to hear that. I think it's time to move on and start working on another formats and sfz looks like a very good choice.

Yes, it's a runner up on the feature poll. Will take a look at my code and see if I can push a patch or something in the near future.

Yay!

I've managed to compile and register my new empty SFZ engine.

Of course LS now segfaults when Fantasia launch... due to the fact i haven't implemented anything yet.

I would recommend everyone interested in the SFZ format to get the book I'm holding in the picture above. Chapter 17 (p.337--370) provide an overview of the SFZ format. Appendix A (p.377--416) contain the listing and documentation of all opcodes. While most of the book is dedicated to synthesizers from Cakewalk, hence its name, the second and third chapter about general synthesizer programming and synthesis techniques might also be of interest. So it's of good value and Simon Cann is a great author.

WONDERFUL !!!!

man you are gonna be my HERO !!!

Hard to guess but if you provide a patch we can help.

grishata wrote:Hard to guess but if you provide a patch we can help.

That's my intention!

I'm going to flesh it out a bit first so you all can see where I'm going with it.

My new .plan:

1. Make a carbon copy of the GIG engine, search and replace GIG -> SFZ;
2. Modify my libsfz code (sfz.h/.cpp) to match the libgig API abit and modify the engine were it can't;
3. Implement a subset of SFZ opcodes that match the GIG engine capabilities;
4. Hopefully end up with a rudimentary prototype that work as an initial goal.

I'll submit a patch when it compiles.

Gah!

I'm back to square one (by reminding myself of the differences between GIG and SFZ). I'm just going to finish writing a hopefully well-designed and documented libsfz and let you guys figure out how to implement the LS engine using it.

dahnielson wrote:I'm back to square one (by reminding myself of the differences between GIG and SFZ). I'm just going to finish writing a hopefully well-designed and documented libsfz and let you guys figure out how to implement the LS engine using it.

One step at a time is a good approach

BTW, I'm working on an implementation chart:

http://docs.google.com/Doc?id=dfzz98xt_45cnk2wvfj

Nothing new yet. Intend to cover opcodes that should be implemented and documenting additional comments/notes about them. Also so far corrected one small error (the start_locc/stop_locc opcodes) in the book.