sischo
VDJ 5.0 v.5 crash like precedent version
Crash ID=004999d0 (date=710242025, version=5.0 rev.5, build=505, thread=Main, dump=8b1383c3, excode=c0000005 (0,376fe70))
Crash ID=004999d0 (date=710242025, version=5.0 rev.5, build=505, thread=Main, dump=8b1383c3, excode=c0000005 (0,376fe70))
geposted Wed 24 Oct 07 @ 8:55 pm
djcel
Can you give us more details about this crash (describe what you did) among the ones you listed here:
http://www.virtualdj.com/forums/78215/PC_version_bugs_report/crash_with_VDJ_5_v4__VST_problem_.html
Do you still use the option "Safe mode" ?
http://www.virtualdj.com/forums/78215/PC_version_bugs_report/crash_with_VDJ_5_v4__VST_problem_.html
Do you still use the option "Safe mode" ?
geposted Wed 24 Oct 07 @ 9:20 pm
sischo
I don't use Safe Mode; only Overclock is actived!
The other options active are Quality with simple algorithm; Master Tempo=Fast; low pass filter isn't active.
My crash is always the same that I described in my other post
The other options active are Quality with simple algorithm; Master Tempo=Fast; low pass filter isn't active.
My crash is always the same that I described in my other post
geposted Thu 25 Oct 07 @ 10:52 pm
djcel
sischo wrote :
VDJ 5.0 v.5 crash like precedent version
Crash ID=004999d0 (date=710242025, version=5.0 rev.5, build=505, thread=Main, dump=8b1383c3, excode=c0000005 (0,376fe70))
Crash ID=004999d0 (date=710242025, version=5.0 rev.5, build=505, thread=Main, dump=8b1383c3, excode=c0000005 (0,376fe70))
After investigation, it seems to be a crash due to the beatlock use.
Can you tell us how you can reproduce it by using this function.
geposted Sun 28 Oct 07 @ 10:39 am
djcel
We have finally found the bug:
It is due to the use of the function "sync(auto)" (right click on the button SYNC of the skin) or "sync_nocbg()" in the 1s zone before the beginning of the song
(In clear, it appears when you ask a synchronysation on Beats instead of on CBGs in the 1s scratch zone)
It will be corrected in the next version.
Thank you again for your help.
It is due to the use of the function "sync(auto)" (right click on the button SYNC of the skin) or "sync_nocbg()" in the 1s zone before the beginning of the song
(In clear, it appears when you ask a synchronysation on Beats instead of on CBGs in the 1s scratch zone)
It will be corrected in the next version.
Thank you again for your help.
geposted Sun 28 Oct 07 @ 11:55 am
sischo
I hope this problem will be fixed in the next version!!
When the new version will be out, I'll test again about this problem and I'll tell you about it.
Thank you!!!
When the new version will be out, I'll test again about this problem and I'll tell you about it.
Thank you!!!
geposted Sun 28 Oct 07 @ 2:46 pm
sischo
djcel wrote :
It is due to the use of the function "sync(auto)" (right click on the button SYNC of the skin) or "sync_nocbg()" in the 1s zone before the beginning of the song
(In clear, it appears when you ask a synchronysation on Beats instead of on CBGs in the 1s scratch zone)
It is due to the use of the function "sync(auto)" (right click on the button SYNC of the skin) or "sync_nocbg()" in the 1s zone before the beginning of the song
(In clear, it appears when you ask a synchronysation on Beats instead of on CBGs in the 1s scratch zone)
After several tests I noticed the problem that you have underlined is correct.
Good work to fix it!!
geposted Sun 28 Oct 07 @ 7:00 pm
djcel
It was solved in v5.0 rev.6
geposted Mon 03 Dec 07 @ 2:04 am