<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Top Dj Companies Create Universal Standard</title>
	<atom:link href="http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/</link>
	<description>A Complete Resource for Digital DJ Information and Technology</description>
	<lastBuildDate>Sun, 12 Feb 2012 14:54:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: signaturex</title>
		<link>http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/comment-page-1/#comment-16019</link>
		<dc:creator>signaturex</dc:creator>
		<pubDate>Sun, 11 Jan 2009 05:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.djtechtools.com/?p=1001#comment-16019</guid>
		<description>[quote comment=&quot;&quot;]i was trying to get someone to write a script for opening different versions of my traktor home folder based on what version of traktor i was opening. &lt; hard to do...[/quote] </description>
		<content:encoded><![CDATA[<p>[quote comment=&quot;&quot;]i was trying to get someone to write a script for opening different versions of my traktor home folder based on what version of traktor i was opening. &lt; hard to do&#8230;[/quote]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: signaturex</title>
		<link>http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/comment-page-1/#comment-16018</link>
		<dc:creator>signaturex</dc:creator>
		<pubDate>Sun, 11 Jan 2009 05:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.djtechtools.com/?p=1001#comment-16018</guid>
		<description>i was trying to get someone to write a script for opening different versions of my traktor home folder based on what version of traktor i was opening. &lt; hard to do... </description>
		<content:encoded><![CDATA[<p>i was trying to get someone to write a script for opening different versions of my traktor home folder based on what version of traktor i was opening. &lt; hard to do&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corax</title>
		<link>http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/comment-page-1/#comment-15714</link>
		<dc:creator>Corax</dc:creator>
		<pubDate>Wed, 24 Dec 2008 14:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.djtechtools.com/?p=1001#comment-15714</guid>
		<description>i think id3-tag way is right. but in version we have now &#039;mp3-file&#039; have not space for wave form overviews... and some apps has some &quot;look&quot; on waveform basics. aaam, cue,loops -maps, bpm standart in mp3-cont are not bad. it will be very usefull...</description>
		<content:encoded><![CDATA[<p>i think id3-tag way is right. but in version we have now &#8216;mp3-file&#8217; have not space for wave form overviews&#8230; and some apps has some &#8220;look&#8221; on waveform basics. aaam, cue,loops -maps, bpm standart in mp3-cont are not bad. it will be very usefull&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/comment-page-1/#comment-15656</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Sat, 20 Dec 2008 09:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.djtechtools.com/?p=1001#comment-15656</guid>
		<description>ID3 tags that are not suitable because it is limited to the MP3, but dj may apply different file formats (WAV, AIF, FLAC, OGG, AAC, ...). Database in XML format is the right solution. Each song in the database uniquely identifies (SHA1 hash function of the music data in files). Thanks to the openness of XML is then possible to add any more text data (BPM, CUE, LOOPS, Artist, Label, ...) and binary data (Image, Wave Data, ...). When I want to transfer the data to another computer to move music files to another directory to back up the reinstallation of operating system, etc., only to make a backup and restore of a local XML file database. Such information on file in a database can add any program, but can be supplied to download and import for the purchase of songs, or imported from the global internet database. Because each progarm can calculate the BPM and other information differently, for each song in the database was created by default, but each program would be able to add their own value.
   128.26
   127.83 </description>
		<content:encoded><![CDATA[<p>ID3 tags that are not suitable because it is limited to the MP3, but dj may apply different file formats (WAV, AIF, FLAC, OGG, AAC, &#8230;). Database in XML format is the right solution. Each song in the database uniquely identifies (SHA1 hash function of the music data in files). Thanks to the openness of XML is then possible to add any more text data (BPM, CUE, LOOPS, Artist, Label, &#8230;) and binary data (Image, Wave Data, &#8230;). When I want to transfer the data to another computer to move music files to another directory to back up the reinstallation of operating system, etc., only to make a backup and restore of a local XML file database. Such information on file in a database can add any program, but can be supplied to download and import for the purchase of songs, or imported from the global internet database. Because each progarm can calculate the BPM and other information differently, for each song in the database was created by default, but each program would be able to add their own value.</p>
<p>   128.26</p>
<p>   127.83</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ko1N</title>
		<link>http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/comment-page-1/#comment-15643</link>
		<dc:creator>ko1N</dc:creator>
		<pubDate>Fri, 19 Dec 2008 18:38:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.djtechtools.com/?p=1001#comment-15643</guid>
		<description>[quote comment=&quot;15635&quot;]Ian --
One approach could be to create a centralized system that could abstract the data formats of different applications into a common interface to which any DJ application could plug into - a proxy of sorts, basically what Fractal Earth was getting at. My employer produces a product that incorporates this design to manage an entirely different type of data than what we are discussing here but the high-level problem (incompatible data formats) and the solution (abstraction) match up.
There is an open-source audio server named JACK that follows this paradigm as well --&gt; http://jackaudio.org/
A standard would be *much* easier but with companies not exactly wanting to sing Kumbaya with each other - this could be a workaround.[/quote]
Well I thought of something different here. You could create a library (.dll in windows and .so in unix) that exports certain symbols (which link to functions). Each function could retrieve a certain information of a given track. On top of that there could be an editor that makes use of this library in some way to edit information for certain tracks. Such a system could make use of ID3 Tags for general informations (that is ASCII based) and advanced information like waveforms. On top of that the API should hold functions for writing the track information.
This is just an idea that came up in me. The problem is that program developers would need to include these libraries or atleast install the application that holds these libraries to use them! So imho a GPL&#039;d library would be the way to go here! Everyone could use the library for free and put his own ideas into it!
Regards, Patrick.</description>
		<content:encoded><![CDATA[<p>[quote comment="15635"]Ian &#8211;</p>
<p>One approach could be to create a centralized system that could abstract the data formats of different applications into a common interface to which any DJ application could plug into &#8211; a proxy of sorts, basically what Fractal Earth was getting at. My employer produces a product that incorporates this design to manage an entirely different type of data than what we are discussing here but the high-level problem (incompatible data formats) and the solution (abstraction) match up.</p>
<p>There is an open-source audio server named JACK that follows this paradigm as well &#8211;&gt; <a href="http://jackaudio.org/" rel="nofollow">http://jackaudio.org/</a></p>
<p>A standard would be *much* easier but with companies not exactly wanting to sing Kumbaya with each other &#8211; this could be a workaround.[/quote]</p>
<p>Well I thought of something different here. You could create a library (.dll in windows and .so in unix) that exports certain symbols (which link to functions). Each function could retrieve a certain information of a given track. On top of that there could be an editor that makes use of this library in some way to edit information for certain tracks. Such a system could make use of ID3 Tags for general informations (that is ASCII based) and advanced information like waveforms. On top of that the API should hold functions for writing the track information.</p>
<p>This is just an idea that came up in me. The problem is that program developers would need to include these libraries or atleast install the application that holds these libraries to use them! So imho a GPL&#8217;d library would be the way to go here! Everyone could use the library for free and put his own ideas into it!</p>
<p>Regards, Patrick.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Empolo</title>
		<link>http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/comment-page-1/#comment-15636</link>
		<dc:creator>Empolo</dc:creator>
		<pubDate>Fri, 19 Dec 2008 04:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.djtechtools.com/?p=1001#comment-15636</guid>
		<description>Ahh, shoot.
sed s/Ian/Ean/g in my last post.
:) </description>
		<content:encoded><![CDATA[<p>Ahh, shoot.</p>
<p>sed s/Ian/Ean/g in my last post. </p>
<p>:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Empolo</title>
		<link>http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/comment-page-1/#comment-15635</link>
		<dc:creator>Empolo</dc:creator>
		<pubDate>Fri, 19 Dec 2008 04:24:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.djtechtools.com/?p=1001#comment-15635</guid>
		<description>Ian --
One approach could be to create a centralized system that could abstract the data formats of different applications into a common interface to which any DJ application could plug into - a proxy of sorts, basically what Fractal Earth was getting at. My employer produces a product that incorporates this design to manage an entirely different type of data than what we are discussing here but the high-level problem (incompatible data formats) and the solution (abstraction) match up.
There is an open-source audio server named JACK that follows this paradigm as well --&gt; &lt;a href=&quot;http://jackaudio.org/&quot; rel=&quot;nofollow&quot;&gt;http://jackaudio.org/&lt;/a&gt;
A standard would be *much* easier but with companies not exactly wanting to sing Kumbaya with each other - this could be a workaround. </description>
		<content:encoded><![CDATA[<p>Ian &#8211;</p>
<p>One approach could be to create a centralized system that could abstract the data formats of different applications into a common interface to which any DJ application could plug into &#8211; a proxy of sorts, basically what Fractal Earth was getting at. My employer produces a product that incorporates this design to manage an entirely different type of data than what we are discussing here but the high-level problem (incompatible data formats) and the solution (abstraction) match up.  </p>
<p>There is an open-source audio server named JACK that follows this paradigm as well &#8211;&gt; <a href="http://jackaudio.org/" rel="nofollow">http://jackaudio.org/</a>  </p>
<p>A standard would be *much* easier but with companies not exactly wanting to sing Kumbaya with each other &#8211; this could be a workaround.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dj Nvidia</title>
		<link>http://www.djtechtools.com/2008/12/17/top-dj-companies-create-universal-standard/comment-page-1/#comment-15632</link>
		<dc:creator>Dj Nvidia</dc:creator>
		<pubDate>Thu, 18 Dec 2008 20:00:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.djtechtools.com/?p=1001#comment-15632</guid>
		<description>Ya,
I am to knew to this digitial djing thing to really have an opinion.  I am still trying to learn and practice everything I can about Traktor Pro...and switching software seems way out of the question because its already out of my price range to buy one, let alone two.
But I do admit the concept does seem logical, and new-aged.  The big thing is cross-platform and opensource (or shareware). With Digital djs being as tech-savy as we are, there no reason why the companies shouldn&#039;t be able to meet the needs of the smart customer base.
Good Post... </description>
		<content:encoded><![CDATA[<p>Ya,</p>
<p>I am to knew to this digitial djing thing to really have an opinion.  I am still trying to learn and practice everything I can about Traktor Pro&#8230;and switching software seems way out of the question because its already out of my price range to buy one, let alone two.</p>
<p>But I do admit the concept does seem logical, and new-aged.  The big thing is cross-platform and opensource (or shareware). With Digital djs being as tech-savy as we are, there no reason why the companies shouldn&#039;t be able to meet the needs of the smart customer base.</p>
<p>Good Post&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

