|
Sharing samples with collaborators (pg. 2)
|
View this Thread in Original format
| EddieZilker |
I'd read your license agreement but my own interpretation says that as long as you're not copying the entire library over to person B's hard disk, and you're using samples you hold the license to on your own equipment to create something which will be transferred to his, the samples, in question, are then your intellectual property.
Hence, if person A and B are both using Sonar 8.5 files and Person A loads up a song with Session Drummer Three and some soft-synths to transport to Person B's home, and SD3 happens to be loaded with the samples from company A, Person A hasn't committed any infraction. |
|
|
| cryophonik |
| quote: | Originally posted by EddieZilker
Hence, if person A and B are both using Sonar 8.5 files and Person A loads up a song with Session Drummer Three and some soft-synths to transport to Person B's home, and SD3 happens to be loaded with the samples from company A, Person A hasn't committed any infraction. |
That's exactly what I was getting at when I mentioned the samples being part of the project file in my OP. Another example is if the wav files are simply placed into audio tracks and arranged as part of the song, saved as a bundled project file and shared with my collaborator. I don't think most license agreements get down to that sort of hair-splitting.
I guess that really the question becomes: at what point does a collaborative project become a commercially viable product? |
|
|
| TranceLover007 |
| quote: | Originally posted by EddieZilker
I'd read your license agreement but my own interpretation says that as long as you're not copying the entire library over to person B's hard disk, and you're using samples you hold the license to on your own equipment to create something which will be transferred to his, the samples, in question, are then your intellectual property.
Hence, if person A and B are both using Sonar 8.5 files and Person A loads up a song with Session Drummer Three and some soft-synths to transport to Person B's home, and SD3 happens to be loaded with the samples from company A, Person A hasn't committed any infraction. |
This make really sense, this is the way I was envisioning this scenario.
Thanks EddieZ. |
|
|
| EddieZilker |
| quote: | Originally posted by cryophonik
That's exactly what I was getting at when I mentioned the samples being part of the project file in my OP. Another example is if the wav files are simply placed into audio tracks and arranged as part of the song, saved as a bundled project file and shared with my collaborator. I don't think most license agreements get down to that sort of hair-splitting.
I guess that really the question becomes: at what point does a collaborative project become a commercially viable product? |
Exactly. |
|
|
| Subtle |
| Its the same as sharing mp3s, there is no way to control it and everyone does it. |
|
|
| EddieZilker |
| quote: | Originally posted by Subtle
Its the same as sharing mp3s, there is no way to control it and everyone does it. |
Uh, no. Not really....
...Damn you! :whip: |
|
|
| RichieV |
| quote: | Originally posted by EddieZilker
Hence, if person A and B are both using Sonar 8.5 files and Person A loads up a song with Session Drummer Three and some soft-synths to transport to Person B's home, and SD3 happens to be loaded with the samples from company A, Person A hasn't committed any infraction. |
yes they have because those programs will no doubt save the wave somewhere on the new person's drive and the liner notes surely say usage as well as having a copy. |
|
|
| EddieZilker |
| This reminds me of the time BT got sued by some idiot maintained he used a loop out of his sample collection. BT proved, in court, that the loop the guy was claiming to have been his was actually made by BT in Reason. |
|
|
| Subtle |
| quote: | Originally posted by EddieZilker
Uh, no. Not really....
...Damn you! :whip: |
You have been missed Eddie. :) big hugs |
|
|
| EddieZilker |
| quote: | Originally posted by Subtle
You have been missed Eddie. :) big hugs |
Not as much as I've missed you guys. |
|
|
| cryophonik |
| quote: | Originally posted by RichieV
yes they have because those programs will no doubt save the wave somewhere on the new person's drive and the liner notes surely say usage as well as having a copy. |
Good point. What if they're bounced to a new format, say a 4/floor acidized 1-bar loop? Is it now an original piece of work that can be shared with a collaborator?
Or, maybe I should follow tehlord's lead and create an original masterpiece called "228 Different Vengtekki Drum Sounds" and make it available as a free download (in pristine 16/44.1 .wav format for superior listening pleasure, of course)? :p
OK, so now it's starting to sound like I'm looking for ways to cheat companies, but that's really not the case at all. I just find it a bit ridiculous, from a legal standpoint, that both parties should have to buy one sample set to create one song. I mean, as Darek alluded to, we don't both have to own the same synths - only one of us does and that person just shares the output from the synth as a .wav file. It would seem that one could make the case that, in Eddie's example, I'm not sharing the actual sample so much as I'm sharing the .wav output from my drum VST? |
|
|
| TranceLover007 |
Let's start this over (maybe I'm missing something), here is my scenario:
You and me are both working on the same project/track, you save everything (for this track) to one folder, compress it and send it to me. I uncompressed/unzip it on my computer, than open this project in Ableton/any other VST, from specific location and work on it. When I'm done, I will save it to the same folder, compress and send back to you. On the end I have to delete this folder.
What is wrong with this scenario?
Cheers |
|
|
|
|
