Ingresar:     


Forum: VirtualDJ 8.0 Technical Support

Tópico: scan bpm problem

Este tópico es antiguo y puede contener información incorrecta para la nueva versión.

Recently change my hd to fat32 for better performance on Mac. When i select songs to batch & analyze for bpm... run the analyze for a few songs and then froze and always shows the infos of the song frozen (such as Free your....(0%)) and need to restart VDJ to unblock.
Looking for a solution. Thank you
 

Mensajes Fri 18 Sep 15 @ 7:34 am
Does it always hang on the same song ?
If so, please upload a file that makes BPM scan to hang on a server and send us the link to check it.
 

Same Problem here!
 

its not always hang on the same song. The problem happened at any song
It always fail to scan over 10 songs.
I tryied many times and always had to restart Vdj !!!!
 

Hello, is there any new infiormation about that bug?
 

Did you upload one of the songs it hangs on and send a ticket to the support team as asked above?
 

Same problem here. Never the same song, if I restart it goes well. I think it's when I want to scan more directory's.
My MBP now also scans 1 song, where I think on previous builds it was 3 songs.
 

kradcliffe wrote :
Did you upload one of the songs it hangs on and send a ticket to the support team as asked above?


i upload 2 pics and a song

wait for an answer...
 

Warakurna wrote :
Same problem here. Never the same song, if I restart it goes well. I think it's when I want to scan more directory's.
My MBP now also scans 1 song, where I think on previous builds it was 3 songs.


i have problen even in one folder see pics
 

freeze at 58% (comand+alt pic)
 

correct pic
 

...
 

Have submitted a ticket as well. They asked for me to update to latest version - i did. Still same issue. Random songs. Random amount of songs analyzed. Doesn't matter file type or anything. Very annoying. I have several new songs I need to analyze and cannot.
 

There was a fix for a possible analyzing bug.
Please try again with the latest beta build 2479.
 

FYI - looks like the latest beta build fixes the issue (knocking on wood!!) :) :)
 

There was a fix with the latest beta build 2479.

Thank you all
 



(Los tópicos y foros antiguos son automáticamente cerrados)