androidi
Bug
1. Loaded a song and: (looks like same bug happened in rev4)
Crash ID=004c8523 (date=710152227, version=5.0 rev.4, build=504, thread=Main, dump=660f7f07, excode=c0000005 (1,0))
Crash ID=004cb213 (date=712070029, version=5.0 rev.6, build=506, thread=Main, dump=660f7f07, excode=c0000005 (1,0))
2. Play song, put it on reverse (mixstation skin has this atleast), listen, then seek to another position in the song with the reverse on, now the music gets chopped at regular interval regardless of the pitch. Normal audio: "hello" Normal reverse: "olleh" reverse after seek: "o l l e h"
3. The song length (mm:ss) of VBR MP3 files is somehow approximated immediately upon load before the entire file has been analyzed. On the first playback when nothing is in the database xml, the entire song can be played with the windows mp3 decoder (not the internal one that assumes all files are constant bitrate for determining the length).
However the approximation is smaller than the full length and is then stored into VirtualDJ Local Database v5.xml in the root of the drive of the song in question is. Next time the same file is loaded, the approximate value from VirtualDJ Local Database v5.xml is used to CLIP the song into that size so that you can't play the entire file anymore! WHOOPS! Song ends prematurely on next playback!
Workaround I found:
Edit the file VirtualDJ Local Database v5.xml by hand and change Infos SongLength="...." to larger value and next time the song is loaded it will be analyzed correctly to the full length.
However if the value is large like: SongLength="604714196" then it doesn't get analyzed at all...
1. Loaded a song and: (looks like same bug happened in rev4)
Crash ID=004c8523 (date=710152227, version=5.0 rev.4, build=504, thread=Main, dump=660f7f07, excode=c0000005 (1,0))
Crash ID=004cb213 (date=712070029, version=5.0 rev.6, build=506, thread=Main, dump=660f7f07, excode=c0000005 (1,0))
2. Play song, put it on reverse (mixstation skin has this atleast), listen, then seek to another position in the song with the reverse on, now the music gets chopped at regular interval regardless of the pitch. Normal audio: "hello" Normal reverse: "olleh" reverse after seek: "o l l e h"
3. The song length (mm:ss) of VBR MP3 files is somehow approximated immediately upon load before the entire file has been analyzed. On the first playback when nothing is in the database xml, the entire song can be played with the windows mp3 decoder (not the internal one that assumes all files are constant bitrate for determining the length).
However the approximation is smaller than the full length and is then stored into VirtualDJ Local Database v5.xml in the root of the drive of the song in question is. Next time the same file is loaded, the approximate value from VirtualDJ Local Database v5.xml is used to CLIP the song into that size so that you can't play the entire file anymore! WHOOPS! Song ends prematurely on next playback!
Workaround I found:
Edit the file VirtualDJ Local Database v5.xml by hand and change Infos SongLength="...." to larger value and next time the song is loaded it will be analyzed correctly to the full length.
However if the value is large like: SongLength="604714196" then it doesn't get analyzed at all...
Posted Thu 06 Dec 07 @ 6:19 pm
androidi
Better workaround:
Change the
FAME IsScanned="1"
to
FAME IsScanned="0"
before starting up VDJ :)
Change the
FAME IsScanned="1"
to
FAME IsScanned="0"
before starting up VDJ :)
Posted Thu 06 Dec 07 @ 6:41 pm
androidi
More permanent hack to get the large VBR files/mixes to finally load fully everytime.
1.Remove IsScanned="1" from VirtualDJ Local Database v5.xml in drive root for songs that don't load entirely or all songs.
2.Change mp3 decoder in settings to "General Window MediaPlayer audio decoder", see that it uses windows codec not FFDSHOW or other crap by configuring ffdshow audio decoder to Disabled for mp3.
3. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
4.Set max load to 15, ok, then set it back to Always if it doesn't load entire file!
1.Remove IsScanned="1" from VirtualDJ Local Database v5.xml in drive root for songs that don't load entirely or all songs.
2.Change mp3 decoder in settings to "General Window MediaPlayer audio decoder", see that it uses windows codec not FFDSHOW or other crap by configuring ffdshow audio decoder to Disabled for mp3.
3. XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
4.Set max load to 15, ok, then set it back to Always if it doesn't load entire file!
Posted Thu 06 Dec 07 @ 7:43 pm
djcel
androidi wrote :
Bug
1. Loaded a song and: (looks like same bug happened in rev4)
Crash ID=004c8523 (date=710152227, version=5.0 rev.4, build=504, thread=Main, dump=660f7f07, excode=c0000005 (1,0))
Crash ID=004cb213 (date=712070029, version=5.0 rev.6, build=506, thread=Main, dump=660f7f07, excode=c0000005 (1,0))
1. Loaded a song and: (looks like same bug happened in rev4)
Crash ID=004c8523 (date=710152227, version=5.0 rev.4, build=504, thread=Main, dump=660f7f07, excode=c0000005 (1,0))
Crash ID=004cb213 (date=712070029, version=5.0 rev.6, build=506, thread=Main, dump=660f7f07, excode=c0000005 (1,0))
Can you reproduce with the same file?
Posted Fri 07 Dec 07 @ 4:03 pm
androidi
Sorry I was flipping through various files quick and didn't pay attention to what was the file being loaded.
Addendum to the 2nd reverse playback choppiness after seek bug:
It seems to happen especially when the file hasn't been analyzed and you put it playing, reverse, then while it's still analyzing, seek beyond where the analyzing is going on (black/empty waveform display) and let it continue with reverse. Atleast on the VBR files I tried it plays like described in bug 2. That's most prone to happen when playing a the large VBR files where you can't get VDJ to analyze the file fully. Fixing bug 3 would make this more unlikely to happen.
Addendum to the 2nd reverse playback choppiness after seek bug:
It seems to happen especially when the file hasn't been analyzed and you put it playing, reverse, then while it's still analyzing, seek beyond where the analyzing is going on (black/empty waveform display) and let it continue with reverse. Atleast on the VBR files I tried it plays like described in bug 2. That's most prone to happen when playing a the large VBR files where you can't get VDJ to analyze the file fully. Fixing bug 3 would make this more unlikely to happen.
Posted Fri 07 Dec 07 @ 5:12 pm
djcel
androidi wrote :
Sorry I was flipping through various files quick and didn't pay attention to what was the file being loaded.
Could you try to reproduce the crash and if you find a suspicious file, do not hesitate to send it us.
Posted Fri 07 Dec 07 @ 5:44 pm