Internal Server Error
Is this correct about my previous question
thankyou
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Hendrik Schreib... on 20 May, 2014 10:18 AM
I'm not exactly sure what you are referring to... Could you please add further messages to the discussion thread you are relating to?
In that thread I asked: Do you still see those Internal Server Errors?
Thanks.
2 Posted by Adyn Rhodes on 20 May, 2014 10:38 AM
yes I still have those internal server errors
what else can I try to fix this problem
Support Staff 3 Posted by Hendrik Schreib... on 20 May, 2014 10:40 AM
If you can, please turn "use online resources" off during the next analysis - most algorithms do not require to contact the server.
Does this help?
-hendrik
4 Posted by Adyn Rhodes on 21 May, 2014 07:18 AM
how come when these songs analyse this error appears in nearly every song ? is there a place online all the tracks can be analyse and corrected to there title and bpm ?
From: [email blocked]
To: [email blocked]
Subject: RE: Internal Server Error [Questions #2608]
Date: Wed, 21 May 2014 17:16:49 +1000
when I do this there isn't as many songs that turn up with the error . what I really want from this program is to analyse all the tracks I have on my computer and put there correct titles of the tracks and correct bpm to each song . anything else I can do to get these results
thanks
Support Staff 5 Posted by Hendrik Schreib... on 21 May, 2014 04:25 PM
Hm,
I checked the logs and it seems there was something wrong with the server, when looking up songs without taking existing metadata into account. I believe this is now fixed.
That aside, I noticed that you are using the Import Meta Data task and are replacing existing meta data. When using solely the acoustic fingerprint to identify a song, it is impossible to pick the correct release, if it was released multiple times (because the audio data is identical). Please be very careful with overwriting good existing data - it may cause more harm than good.
Also, if you haven't done so already, please adjust your memory settings to something like
900m, as described in http://www.beatunes.com/beatunes-outofmemoryerror.html - otherwise, beaTunes will be slow, show error messages, and the internal database might break. All things you'd like to avoid ;-)Cheers,
-hendrik