tag:help.beatunes.com,2009-07-24:/discussions/questions/9947-analysis-resultsbeaTunes: Discussion 2018-08-18T21:02:31Ztag:help.beatunes.com,2009-07-24:Comment/458874662018-08-13T15:54:02Z2018-08-13T15:54:02ZAnalysis results<div><p>Hey Richard,</p>
<p>I will get back to you about this and your other questions later today.</p>
<p>Thanks for your patience.</p></div>hendriktag:help.beatunes.com,2009-07-24:Comment/458874662018-08-13T16:01:38Z2018-08-13T16:01:38ZAnalysis results<div><p>Thanks! No rush. I know I posted a lot over the weekend.<br>
One update: for some reason, the h2.db file shrunk to 1,266,616 KB. I didn't realize it could dynamically get that much smaller. I might have had beaTunes open when I reported the larger size.</p>
<pre>
<code> From: hendrik <tender+d261b165ac@tenderapp.com></code>
</pre>
<p>To: <a href="mailto:pattonre@yahoo.com">pattonre@yahoo.com</a> Sent: Monday, August 13, 2018 10:54 AM Subject: Re: Analysis results [Questions #9947]</p>
<p>#yiv6234881673 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv6234881673 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}</p></div>Richardtag:help.beatunes.com,2009-07-24:Comment/458874662018-08-13T16:12:29Z2018-08-13T16:12:29ZAnalysis results<div><p>Did you restart beaTunes?<br>
beaTunes may compact the database when it shuts it down.</p>
<p>BTW: the database size should not lead to bad runtime behavior. With growing size only insertions and updates may get slower, but lookups should remain fast (because of indexing).</p></div>hendriktag:help.beatunes.com,2009-07-24:Comment/458874662018-08-13T16:16:35Z2018-08-13T16:16:35ZAnalysis results<div><p>Yes, I did restart beaTunes.</p>
<pre>
<code> From: hendrik <tender+d261b165ac@tenderapp.com></code>
</pre>
<p>To: <a href="mailto:pattonre@yahoo.com">pattonre@yahoo.com</a> Sent: Monday, August 13, 2018 11:12 AM Subject: Re: Analysis results [Questions #9947]</p>
<p>#yiv8378883152 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv8378883152 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}</p></div>Richardtag:help.beatunes.com,2009-07-24:Comment/458874662018-08-18T21:02:29Z2018-08-18T21:02:29ZAnalysis results<div><p>Just to comment about a couple of the other points you've raised:</p>
<ul>
<li>Danceability: This is either reading a value set by MixedInKey, a value computed by AcousticBrainz or using the algorithm by <a href="http://www.academia.edu/download/30167921/dfa.pdf">Streich and Herrera</a>. Of these values, I assume the MixedInKey value is actually the best.</li>
<li>Lyrics: beaTunes does a glorified web search. If it's not easily found on the web, beaTunes cannot import it.</li>
<li>Acoustic/Electric/Neither: beaTunes pays attention to a couple of sources, but depends on third party information. This is why there isn't always a value</li>
<li>BPM and Key: This is either imported from online resources or calculated depending on the audio portion of your files (depends on your settings). The method is not optimized for classical music, but rather for popular music.</li>
</ul></div>hendrik