<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Life After Giga: A Call for Open Source Sampling Development</title>
	<atom:link href="http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/</link>
	<description>The latest gear, software, and techniques for electronic music production and performance</description>
	<pubDate>Tue, 02 Dec 2008 03:30:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Darren Landrum</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-532603</link>
		<dc:creator>Darren Landrum</dc:creator>
		<pubDate>Tue, 29 Jul 2008 00:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-532603</guid>
		<description>@Vladimir: You're right, of course, and my apologies. My contact with the LinuxSampler group has been through Benno and Christian, who are both in Germany.

However, I'm not the one who was accusing open source software of stealing from the commercial world. I did make the point, though, that I do have a few original ideas of my own concerning the overall design for a sampler. These ideas will apply for other types of music software as well, I think. I don't want to give too many details just yet, because I want to flesh out ideas and run them past people I trust first. I actually agree with you about implementing popular functionality and open file formats.

I've also been called worse things than a dung beetle. :-)</description>
		<content:encoded><![CDATA[<p>@Vladimir: You&#8217;re right, of course, and my apologies. My contact with the LinuxSampler group has been through Benno and Christian, who are both in Germany.</p>
<p>However, I&#8217;m not the one who was accusing open source software of stealing from the commercial world. I did make the point, though, that I do have a few original ideas of my own concerning the overall design for a sampler. These ideas will apply for other types of music software as well, I think. I don&#8217;t want to give too many details just yet, because I want to flesh out ideas and run them past people I trust first. I actually agree with you about implementing popular functionality and open file formats.</p>
<p>I&#8217;ve also been called worse things than a dung beetle. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vladimir Senkov</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-532167</link>
		<dc:creator>Vladimir Senkov</dc:creator>
		<pubDate>Mon, 28 Jul 2008 13:51:33 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-532167</guid>
		<description>Darren,

Linuxsampler doesn't get around anything and not all developers are in Germany. Linuxsampler is based "prior art" to any of those patents and I believe this is why it wasn't sued by Tascam. Although, of course, anyone can sue anybody these days for just about any reason. Btw, not looking up the patent isn't going to make you infringement less willful :)
I'm not sure i understood your point about opensource simply copying commercial software. Surely you aren't talking about copying as in stealing code, are you?
If you are talking about implementing compatible software then i must protest. If nobody implemented open software that does essentially the same thing that closed software did, having the similar form-fit-function, e.g. opening the same file formats, etc. then there would not be many users of open software. I use open software but i must interact with others who do not all use open software. It would be difficult for me to work in the office w/o an openoffice, for example. So there is nothing "uncool" about implementing something that already exists, especially if you can do it better.
You are essentially saying that you would do something different implying that it doesn't already exist. Why are you so sure that it does not? How well did you do your research? If so, does it not exist because there isn't much of a demand for it or because it's impossible to implement properly?</description>
		<content:encoded><![CDATA[<p>Darren,</p>
<p>Linuxsampler doesn&#8217;t get around anything and not all developers are in Germany. Linuxsampler is based &#8220;prior art&#8221; to any of those patents and I believe this is why it wasn&#8217;t sued by Tascam. Although, of course, anyone can sue anybody these days for just about any reason. Btw, not looking up the patent isn&#8217;t going to make you infringement less willful :)<br />
I&#8217;m not sure i understood your point about opensource simply copying commercial software. Surely you aren&#8217;t talking about copying as in stealing code, are you?<br />
If you are talking about implementing compatible software then i must protest. If nobody implemented open software that does essentially the same thing that closed software did, having the similar form-fit-function, e.g. opening the same file formats, etc. then there would not be many users of open software. I use open software but i must interact with others who do not all use open software. It would be difficult for me to work in the office w/o an openoffice, for example. So there is nothing &#8220;uncool&#8221; about implementing something that already exists, especially if you can do it better.<br />
You are essentially saying that you would do something different implying that it doesn&#8217;t already exist. Why are you so sure that it does not? How well did you do your research? If so, does it not exist because there isn&#8217;t much of a demand for it or because it&#8217;s impossible to implement properly?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren Landrum</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-531068</link>
		<dc:creator>Darren Landrum</dc:creator>
		<pubDate>Sun, 27 Jul 2008 01:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-531068</guid>
		<description>In all honesty, I'm not too worried about it. I'm sure an option will present itself by the time I get that far. There's plenty to do between here and there. :-)</description>
		<content:encoded><![CDATA[<p>In all honesty, I&#8217;m not too worried about it. I&#8217;m sure an option will present itself by the time I get that far. There&#8217;s plenty to do between here and there. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Davis</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-530875</link>
		<dc:creator>Paul Davis</dc:creator>
		<pubDate>Sat, 26 Jul 2008 18:29:32 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-530875</guid>
		<description>Darren, I don't personally believe that the patent will stand if challenged in court. Pre-caching is a common OS technique, and in fact on *nix-style OS'es, you get about 50% of what their patent describes just by reading from the file. That is, the OS reads more than you asked for into a "buffer cache" and the next time you read it, its already in RAM and ready to be fetched very rapidly. The amount that is "read-ahead" is somewhat configurable, but not quite enough or as precisely as one would want get giga-like behaviour. There also appears to be some precedents for the patent that may or may not provide clear prior art.

Another way to look at this is that Halion was developed after the giga patent was taken out. I am about 98% certain that Steinberg did not license the patent, and did not feel under any threat of a lawsuit (based on personal communication with Steinberg employees).</description>
		<content:encoded><![CDATA[<p>Darren, I don&#8217;t personally believe that the patent will stand if challenged in court. Pre-caching is a common OS technique, and in fact on *nix-style OS&#8217;es, you get about 50% of what their patent describes just by reading from the file. That is, the OS reads more than you asked for into a &#8220;buffer cache&#8221; and the next time you read it, its already in RAM and ready to be fetched very rapidly. The amount that is &#8220;read-ahead&#8221; is somewhat configurable, but not quite enough or as precisely as one would want get giga-like behaviour. There also appears to be some precedents for the patent that may or may not provide clear prior art.</p>
<p>Another way to look at this is that Halion was developed after the giga patent was taken out. I am about 98% certain that Steinberg did not license the patent, and did not feel under any threat of a lawsuit (based on personal communication with Steinberg employees).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren Landrum</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-530775</link>
		<dc:creator>Darren Landrum</dc:creator>
		<pubDate>Sat, 26 Jul 2008 15:33:55 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-530775</guid>
		<description>Here's the problem as I see it:

The core technology of GigaStudio is that patent on on-demand sample streaming from disk. It's a real possibility that all of the other commercial samplers on the market license that patent. That makes the patent worth a lot more than the product.

If they do release the product open source, it will be minus the code that the patent covers, at the very least. That would leave you with a neutered product. Creating your own streaming sample code then becomes a patent violation. This ends up leaving you in the same boat that I'm in.

Because it's the patent that's worth the real money, getting them to sell that to a bunch of open sourcers will be a chore, and incredibly expensive, assuming they don't just laugh us out of the metaphorical room.

Now, it could be I'm wrong, and that there is a way around these issues, and other companies have found it. But for now, I think it's best to assume the worst possible scenario until we know more.

Personally, I'm looking to use 64-bit addressing and letting people really load up the RAM. I've also thought about seeing if I can get a version of FLAC that works on 24-bit waves, to save memory. These are just off-hand ideas for now, though.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s the problem as I see it:</p>
<p>The core technology of GigaStudio is that patent on on-demand sample streaming from disk. It&#8217;s a real possibility that all of the other commercial samplers on the market license that patent. That makes the patent worth a lot more than the product.</p>
<p>If they do release the product open source, it will be minus the code that the patent covers, at the very least. That would leave you with a neutered product. Creating your own streaming sample code then becomes a patent violation. This ends up leaving you in the same boat that I&#8217;m in.</p>
<p>Because it&#8217;s the patent that&#8217;s worth the real money, getting them to sell that to a bunch of open sourcers will be a chore, and incredibly expensive, assuming they don&#8217;t just laugh us out of the metaphorical room.</p>
<p>Now, it could be I&#8217;m wrong, and that there is a way around these issues, and other companies have found it. But for now, I think it&#8217;s best to assume the worst possible scenario until we know more.</p>
<p>Personally, I&#8217;m looking to use 64-bit addressing and letting people really load up the RAM. I&#8217;ve also thought about seeing if I can get a version of FLAC that works on 24-bit waves, to save memory. These are just off-hand ideas for now, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel Hamburger</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-530691</link>
		<dc:creator>Joel Hamburger</dc:creator>
		<pubDate>Sat, 26 Jul 2008 13:28:01 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-530691</guid>
		<description>It's always nice to see level headed discussion about open source projects.

Though gigastudio is on the scrap heap, I doubt that tascam will be willing to forgo the fee for salvage.  It's clear that they have a significant investment in the IP. 

I assume there are companies that are considering taking up the gigastudio mantle. They will probably be doing the same market analysis that Tascam is doing and will likely come to a similar conclusion, it's not very viable. However, there is another option.

How about forming a cooperative which will attempt to raise the necessary funds to purchase the IP.   Once the cooperative owns the code they would be free to make it open source as they wish.

Rather than a petition for Tascam to give the software away we should start collecting pledges from putative coop members.  A solid goal would be to gather 2000 $100 pledges. Though 200k is not a huge number it would be enough of start to be taken seriously by Tascam.

At the very least make tascam and or other developers realize that there still is a small market for the product.  

If the co-op actually succeeds in raising capital and purchasing the IP there are a number of possible business models that could lead to sustainable development support and maintenance of the product. 

Ideally, the coop members would pledge with the full understanding that the resulting product would be open source.  This would make the product essentially donation/shareware.  I do think that there are enough professional users who would be willing to risk $100-$500 just for a reasonable chance to not have to port libraries !

Once the code is open sourced, development could continue in the "usual" open source manner.  However it would be wise to use the cooperative funding model to leverage the existing knowledge base, i.e. hire members of the current product team ( I believe there are a half dozen or so coders).

A knowledgeable product manager could then designate which tasks code be handled by the existing coders and which could be crowd sourced.

Testing and bug reporting would be handled by the coop members. Once a stable release is generated feature requests could accumulated and ranked. Another round of funding could then be raised for the next version.

It's obvious that Tascam did not feel that there was enough of a commercial market to warrant the continued development and and support costs.

With a cooperative open source model I think gigastudio could at least be sustained for the next 5-10 years.  If something like this actually worked it might be possible to expand the product along the lines discussed above.

If there is any interest in this idea I'd be more than happy to work on it.

joel [ATTTT]  godelstring [DOOT] com</description>
		<content:encoded><![CDATA[<p>It&#8217;s always nice to see level headed discussion about open source projects.</p>
<p>Though gigastudio is on the scrap heap, I doubt that tascam will be willing to forgo the fee for salvage.  It&#8217;s clear that they have a significant investment in the IP. </p>
<p>I assume there are companies that are considering taking up the gigastudio mantle. They will probably be doing the same market analysis that Tascam is doing and will likely come to a similar conclusion, it&#8217;s not very viable. However, there is another option.</p>
<p>How about forming a cooperative which will attempt to raise the necessary funds to purchase the IP.   Once the cooperative owns the code they would be free to make it open source as they wish.</p>
<p>Rather than a petition for Tascam to give the software away we should start collecting pledges from putative coop members.  A solid goal would be to gather 2000 $100 pledges. Though 200k is not a huge number it would be enough of start to be taken seriously by Tascam.</p>
<p>At the very least make tascam and or other developers realize that there still is a small market for the product.  </p>
<p>If the co-op actually succeeds in raising capital and purchasing the IP there are a number of possible business models that could lead to sustainable development support and maintenance of the product. </p>
<p>Ideally, the coop members would pledge with the full understanding that the resulting product would be open source.  This would make the product essentially donation/shareware.  I do think that there are enough professional users who would be willing to risk $100-$500 just for a reasonable chance to not have to port libraries !</p>
<p>Once the code is open sourced, development could continue in the &#8220;usual&#8221; open source manner.  However it would be wise to use the cooperative funding model to leverage the existing knowledge base, i.e. hire members of the current product team ( I believe there are a half dozen or so coders).</p>
<p>A knowledgeable product manager could then designate which tasks code be handled by the existing coders and which could be crowd sourced.</p>
<p>Testing and bug reporting would be handled by the coop members. Once a stable release is generated feature requests could accumulated and ranked. Another round of funding could then be raised for the next version.</p>
<p>It&#8217;s obvious that Tascam did not feel that there was enough of a commercial market to warrant the continued development and and support costs.</p>
<p>With a cooperative open source model I think gigastudio could at least be sustained for the next 5-10 years.  If something like this actually worked it might be possible to expand the product along the lines discussed above.</p>
<p>If there is any interest in this idea I&#8217;d be more than happy to work on it.</p>
<p>joel [ATTTT]  godelstring [DOOT] com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Downpressor</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-529204</link>
		<dc:creator>Downpressor</dc:creator>
		<pubDate>Fri, 25 Jul 2008 04:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-529204</guid>
		<description>Peter,

Fair `nuff.</description>
		<content:encoded><![CDATA[<p>Peter,</p>
<p>Fair `nuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Kirn</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-529145</link>
		<dc:creator>Peter Kirn</dc:creator>
		<pubDate>Fri, 25 Jul 2008 03:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-529145</guid>
		<description>Downpressor, exactly. My point was just to prompt discussion -- the simple fact is, open source software tends to have a longer life cycle than proprietary software. (That CAN be an advantage of proprietary software for some things; it's why I think often you have a balance.) So, in other words, this was an appropriate jumping off point for a separate discussion.

The open source software I know and use isn't simply copying proprietary software. If it were, I wouldn't be using it. OSes are a bad example, because there's so much that people ask of an OS -- Mac, Windows, Linux, etc. are constantly accusing each other of copying, but that could also simply be responding to user needs. In music and audio, what I've seen from open source is very much distinct from what the proprietary software is doing. End of story.

GIGA CONNECTION --
I made the connection here, so to whatever extent I muddied the waters by doing that, sorry.

But then, the point here was we have a choice:
* hope that a petition convinces a big corporation to open source a giant, app OR
* build some simple frameworks that would make these things easier to develop

Might the simple frameworks issue become much harder than people expect? Might you wind up with something *nothing* like Giga? Might it be something idiosyncratic and unrelated to commercial products? Absolutely. I think that's a really good thing. </description>
		<content:encoded><![CDATA[<p>Downpressor, exactly. My point was just to prompt discussion &#8212; the simple fact is, open source software tends to have a longer life cycle than proprietary software. (That CAN be an advantage of proprietary software for some things; it&#8217;s why I think often you have a balance.) So, in other words, this was an appropriate jumping off point for a separate discussion.</p>
<p>The open source software I know and use isn&#8217;t simply copying proprietary software. If it were, I wouldn&#8217;t be using it. OSes are a bad example, because there&#8217;s so much that people ask of an OS &#8212; Mac, Windows, Linux, etc. are constantly accusing each other of copying, but that could also simply be responding to user needs. In music and audio, what I&#8217;ve seen from open source is very much distinct from what the proprietary software is doing. End of story.</p>
<p>GIGA CONNECTION &#8211;<br />
I made the connection here, so to whatever extent I muddied the waters by doing that, sorry.</p>
<p>But then, the point here was we have a choice:<br />
* hope that a petition convinces a big corporation to open source a giant, app OR<br />
* build some simple frameworks that would make these things easier to develop</p>
<p>Might the simple frameworks issue become much harder than people expect? Might you wind up with something *nothing* like Giga? Might it be something idiosyncratic and unrelated to commercial products? Absolutely. I think that&#8217;s a really good thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren Landrum</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-529143</link>
		<dc:creator>Darren Landrum</dc:creator>
		<pubDate>Fri, 25 Jul 2008 03:18:35 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-529143</guid>
		<description>The framework I propose is just to give a base point for the development of other apps. It would contain things like classes for interfacing with JACK for audio and MIDI, the ability to process DSP graphs, and a few other things. It's not going to be a final app unto itself. Rather, it would provide things every synth or sampler app would need in a way that I feel makes sense. One of the guys I'm working with already has a JACK audio and MIDI class written, and he's testing it now. I'm currently working out the digraph one.

I also wish people would stop assuming that just because my inflamed sense of self coincides with this whole GigaStudio fiasco, that all I want to do is clone it. I have many idea of my own for a sampling workstation that bear no resemblance to anything on the market. Whether they're any good or not remains to be seen, but hey, it's worth a try. I sent a link to Peter something I had written on one of my main ideas, though I did ask him to keep it under his hat for now. I'll email you a link to it, if you'd like, Paul, as I know I can count on some good feedback from you. ;-)

There are other ways of approaching the same problem, to achieve interesting results.

And you're right, Olga is much smaller in scope than a huge sampling workstation, but it pains me to say that nothing on Linux comes even close to sounding as good as it does. I want to solve that.</description>
		<content:encoded><![CDATA[<p>The framework I propose is just to give a base point for the development of other apps. It would contain things like classes for interfacing with JACK for audio and MIDI, the ability to process DSP graphs, and a few other things. It&#8217;s not going to be a final app unto itself. Rather, it would provide things every synth or sampler app would need in a way that I feel makes sense. One of the guys I&#8217;m working with already has a JACK audio and MIDI class written, and he&#8217;s testing it now. I&#8217;m currently working out the digraph one.</p>
<p>I also wish people would stop assuming that just because my inflamed sense of self coincides with this whole GigaStudio fiasco, that all I want to do is clone it. I have many idea of my own for a sampling workstation that bear no resemblance to anything on the market. Whether they&#8217;re any good or not remains to be seen, but hey, it&#8217;s worth a try. I sent a link to Peter something I had written on one of my main ideas, though I did ask him to keep it under his hat for now. I&#8217;ll email you a link to it, if you&#8217;d like, Paul, as I know I can count on some good feedback from you. ;-)</p>
<p>There are other ways of approaching the same problem, to achieve interesting results.</p>
<p>And you&#8217;re right, Olga is much smaller in scope than a huge sampling workstation, but it pains me to say that nothing on Linux comes even close to sounding as good as it does. I want to solve that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Downpressor</title>
		<link>http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-529115</link>
		<dc:creator>Downpressor</dc:creator>
		<pubDate>Fri, 25 Jul 2008 02:52:34 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmusic.com/2008/07/23/life-after-giga-a-call-for-open-source-sampling-development/#comment-529115</guid>
		<description>Johnny Horizon,

I dont disagree with you, but in my limited experience guys who build their own stompboxes have always been seeking something unique rather than just trying to replicate the successes of the commercial world. YMMV.</description>
		<content:encoded><![CDATA[<p>Johnny Horizon,</p>
<p>I dont disagree with you, but in my limited experience guys who build their own stompboxes have always been seeking something unique rather than just trying to replicate the successes of the commercial world. YMMV.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
