5 Free piano instrument in SFZ, Decent Sampler format

[luiscameron]

Just release another Yamaha C3 piano instrument (from pianobook) today, enjoy

https://apiano.co.uk/free-piano-instrum ... mpler-sfz/

[kinwie]

-deleted-

[enroe]

Just hope my things on sfzinstruments could be useful for people.

You can be sure about that!

Your SFZs are and will remain unique! Thank you for those!

I think I've been ripped off, hahahh.
...

I don't understand you.

Also Mr. Cameron creates SFZ-files - what is wrong with that?
He has his own concept, his own controller selection, etc. So there
is simply a second, completely different SFZ definition to use
certain multisamples.

You, on the other hand, have your way of creating SFZ files -
also very sophisticated and refined and much appreciated!

What can be so wrong with that?
Or did you think that the sfz format belongs to you alone?

Though, a bit sad to see even a free mapping can be ripped off so easily.
(Maybe that's why pro sample devs don't want to do sfz stuff)

Haha, yeah: A free mapping cannot be ripped off, if the naming
of the author is always supplied - due to creative commons "by
attribution" - and due to the usual normal understanding.
Everyone I know respects this principle!

And yes, Kinwie, with the great SFZ format - and the free
downloads here - you are a prominent member of the
"Free Cultural Movement" and thus - as pathetic as that
sounds - someone who does indeed improve the world.

[enroe]

Just release another Yamaha C3 piano instrument (from pianobook) today, enjoy

https://apiano.co.uk/free-piano-instrum ... mpler-sfz/

Thank you Luis, good job!

[kinwie]

-deleted-

[luiscameron]

Thanks. Ours was a collaborative project and most of the actual SFZ mappings have been done by Kinwie, who deserves credit if you base your enhanced version on his work (something like "original SFZ mapping done by kinwie"). I mainly supported the project logistically and by contacting some of the original sample library developers to obtain permissions / clarify license conditions.

Thanks Kazi7 for the clarification. Agree, I have added the credits to kinwie to show our respect to him!

[luiscameron]

What can be so wrong with that?
Or did you think that the sfz format belongs to you alone?

Ahh yeah sorry, my bad. Sfz format belongs to the world.
Anybody can do anything to it. I forgot that.
Enjoy...

@kinwie, we respect your work! Without your work, the open source musical instrument like SFZ and Decent Sampler can not grow! As enroe said, your SFZ is unique, it is a great piece of work!!

BTW, we updated the credits in the Yamaha C3 Headroom piano page to show our respect to your work!

[luiscameron]

Just release another Yamaha C3 piano instrument (from pianobook) today, enjoy

https://apiano.co.uk/free-piano-instrum ... mpler-sfz/

Thank you Luis, good job!

Thank you for your encouragement!

[kinwie]

Well, I don't think you need to put my name for credit, please remove it.

I just want to clarify one thing. The author of Headroom Piano samples, Bengt, allowed me to convert his samples to other format (sfz-flac) with this condition :
with the author's permission as long keeping the original instrument name

It's written in the readme. It's free but originally not a CC licensed library. So you can't use your own instrument name for it. And for other format (wav, decent, etc) I think you need to ask his permission directly if you want to redistribute his modified samples on your site.

Funnily, I'm a bit shock to see other person rip off my sfz to make another sfz of it that another person said it is his sfz...amazing...

[enroe]

Kinwie, I now understand very well why you are so upset.
I hope and assume that this is all an oversight.

The author of Headroom Piano samples, Bengt, allowed me to convert his samples to other format (sfz-flac) with this condition :
with the author's permission as long keeping the original instrument name

It's written in the readme. It's free but originally not a CC licensed library. So you can't use your own instrument name for it. And for other format (wav, decent, etc) I think you need to ask his permission directly if you want to redistribute his modified samples on your site.

@ Luis Cameron: In this case you should contact the author as soon
as possible and ask. You might have to rename the sample set -
depending on what Bength Nielsson said.

And yes, I see, you already added some text. But maybe this is not enough.

By the way: There are different CC-variations. You can also specify
within CC that no changes to the samples and / or the name may
be made.

Funnily, I'm a bit shock to see other person rip off my sfz to make another sfz of it that another person said it is his sfz...amazing...

Yes, that is not so funny.

Were you able to contact this person and clarify the matter? You
should definitely try that, because such a thing is rarely malicious.
Most of the time it's just carelessness.

From a purely legal point of view, this would be a clear case of
plagiarism - and also easily and clearly verifiable. So, you should
email this "person" asking for clarification.

[kinwie]

Kinwie, I now understand very well why you are so upset.

That one case above not upsetting me, I just point out the polite way regarding originally non-CC libraries redistribution. Not just take it and put it on a new website with a new name. It's like stealing, alas that's what CC license allowed to for the one we put at sfzinstruments github. I should be careful next time if I ever make other sfz for public again, lesson learned.

What really upset me is, he destroyed my Headroom Piano sfz program. I made it, so I know all details. There are hanging opcodes leftover, which he probably not understand and not deleted, like "width_oncc" curve ID without the curve index. I will be happy if it really get improved and more useful but rather than improved, it's got destroyed.

Like Kazi7's first good question, what the scope of this project. I see this is as a scammer. Maybe today thread title will be updated to "6 Free piano...". Tomorrow will be "7 Free piano..." and so on.

OTOH, Headroom Piano on sfzinstruments already a free well-programmed sfz and reflects its original kontakt version. If it needs update or enhancement, it can be forked and make a Pull-request. I think that's what sfzinstruments project is intended for. Again, alas its CC license allowed things to be stolen...I should be more careful next time...

[luiscameron]

Guys, based on your conversation, we make some changes in our website for this intrument, please check it out.
https://apiano.co.uk/free-piano-instrum ... oom-piano/

Thank you all for pointing out the potential issues related to the above instrument. Sincerely thanks!

[enroe]

It's like stealing, alas that's what CC license allowed to for the one we put at sfzinstruments github. I should be careful next time if I ever make other sfz for public again, lesson learned.

... Again, alas its CC license allowed things to be stolen...I should be more careful next time...

Yeah, I hear you! This case is a bit confused.
Why? Let's take a closer look at this:

Bengt Nilsson has made his sample set available under
"Creative Commons - by". This CC means that the only
condition is: Name mention. Otherwise someone can
do pretty much anything with the samples. You have
now - probably more subconsciously - placed your SFZ
under this CC license. Maybe that wasn't so glorious.

"Lesson learned" should therefore mean: Next time - or
already now - I'll put my SFZ under a slightly different
CC license, namely under "Creative Commons - by - nd".
Because that would mean: Attribution and the SFZ may
NOT be changed. Because these "changes" are exactly
what annoys you now.

By the way, it would be even better to choose "Creative
Commons - by - nd - nc". Because then any
commercial distribution would be excluded.

-----------------------------------------------------------------------

So ... I would appreciate it if you continued to create
your ingenious SFZs - you can do that really best - and
if you would always add the license "CC - by - nd - nc".

Then you are on the safe side as a freelance creative.
And it is precisely for this "safe side" that Creative
Commons was made.

[kinwie]

What can be so wrong with that?
Or did you think that the sfz format belongs to you alone?

Sfz format belongs to the world, so let more other people create and share sfz mappings...
I'm done for the moment. This issue scares me away.
I've deleted my unnecessary comments in this thread.
I just point out that anybody else could be ripped-off too.
All your sfz and samples suddenly available at this guy website with new name without you knowing.
Yeah...it's free world...Anybody can do anything to it...

[MTorn]

Part of what makes things so complex with SFZ instruments (and several other formats) is that every instrument has two distinct components: the sample set, and the SFZ text file.

The sample set is fairly fixed, and can generally be attributed to one person or company, the one who recorded and edited the original samples.
However, for any given sample set an infinite number of SFZ files can be made. They can span from the bare minimum (basic key range assignment) to something quite creative and complex. In many cases an SFZ can even be produced though automation, so no human at all can be attributed with creating it.

So who made the SFZ instrument?
The person who recorded the samples? Those samples may not have been intended for an SFZ in the first place. Maybe recorded 30 years ago.
Or did the SFZ author make the instrument? If I find a set of samples on some sharing site, and make a quick SFZ mapping, did I make this instrument?

When it comes to sharing free instruments, there has to be a certain amount of throwing caution to the wind. Most people don't understand, or care, about the intricacies of a creative commons license.
When you have "free" software, and "free" instrument sets, it's almost inevitable that people will use them without too many thoughts about usage rights. If you want to retain full control and credit for your work, it's probably best to avoid the "free" environment altogether.

I'm in the process of producing a massive library that intend to share when it's complete. I'm hoping that a lot of people will have use for it, but I have no expectations that it will remain unaltered for very long.