Stephane Clavel
Ok due to the number of mp3 that seem to make vdj crash, I'll give the b14 anyway, even if the sound configuration is not finished.
I have corrected the problem with the mp3 rick sent to yanx (faithless), so now I want to know if there are still other mp3 that won't work with the b14.
If it is the case, please send them to me so I can correct the mp3 engine.
beta14
------
- record auto play fixed
- wma engine fixed
- record infos fixed
- mono/headphone configuration mode done
- pitch change shown during automix
- pitch value display fits in its hole
- bad mp3 fixed
- improved 4/4 phase detection
I have corrected the problem with the mp3 rick sent to yanx (faithless), so now I want to know if there are still other mp3 that won't work with the b14.
If it is the case, please send them to me so I can correct the mp3 engine.
beta14
------
- record auto play fixed
- wma engine fixed
- record infos fixed
- mono/headphone configuration mode done
- pitch change shown during automix
- pitch value display fits in its hole
- bad mp3 fixed
- improved 4/4 phase detection
Inviato Sat 17 May 03 @ 4:16 pm
DJ Rick
I'm launching into the same extensive analysing process that I did with beta 13. So far of the 17 tracks the were locking VDJ up durring analysis I have re-tested 6. 2 of them scanned fine, 2 reported fatal errors, and let me click ok and continue working within VDJ... however 2 of them still caused a lock up.
I'm also noticing that I'm getting "fatal errors" with 14 (the report of a fatal error still allows me to click OK and continue working) on tracks that were fine in 13.
One more thing (this might be important) On several of the tracks, (not all) that locked up, or reported a fatal error, I launched Atomixmp3 and found audible probelms with these files. (small clicks or skips) However, if a bad file slips through the cracks and I try to play it at work, I'd hate for VDJ to lock up over it. Maybe VDJ needs to be a little more tolerant of imperfect files...
I'm also noticing that I'm getting "fatal errors" with 14 (the report of a fatal error still allows me to click OK and continue working) on tracks that were fine in 13.
One more thing (this might be important) On several of the tracks, (not all) that locked up, or reported a fatal error, I launched Atomixmp3 and found audible probelms with these files. (small clicks or skips) However, if a bad file slips through the cracks and I try to play it at work, I'd hate for VDJ to lock up over it. Maybe VDJ needs to be a little more tolerant of imperfect files...
Inviato Sat 17 May 03 @ 6:02 pm
Homeboy
Wanted to add to Ricks problem even though I posted in bugs area there is more info about this.... After a fatal error sometimes VDJ will continue to report fatal errors to tracks that it actually can scan. But you need to restart. Rick and I are currently working together to report the FE tracks.
Inviato Sat 17 May 03 @ 6:06 pm
DJ Rick
I know this is a bug, but I'm afraid this post was going to be too long for the bugs list.
I have completed the scan of the same 1730 songs now with 14 that I did with 13. There is a bit of difference in the result. Some of the tracks that were causing the lock up scanned fine this time. There were 17 of them, now there are 3 (I think) However, 14 other tracks have some different problems with track analysing. I have (besides the 3 that cause the complete lock up) 13 others that report a fatal Error durring analysing. In this case, I can generally just hit OK, and VDJ will continue. However if one of these tracks was a part of a batch for analysing, each subsequent track would also report a fatal error. For instance, if I had 10 tracks selected and the first track reported a fatal error, if I just clicked OK, it would continue, but report a fatal error on each of the next 9 tracks unless I stop the analysis and shut down VDJ, and re-launch it. Then the rest of the 9 tracks would scan and be fine. Of the 16 total tracks that either lock VDJ up, or cause a fatal error to be reported. If I load one of them to be played, the scan ends abruptly, and a exception error is reported in the "scan thread". Of course if I choose recover from that error, VDJ reopens and imediately begins the scan process again on the bad track and reports the same error. I can't get another track to replace the bad track before the error is reported. The result is that VDJ must be shut down and re-launched.
To summarize, only 3 of the same 17 tracks that locked up VDJ in 13, cause the same problem with 14. But there are now 13 other tracks (that were fine with beta 13) that cause a different problem altogether. I have identified the probelm tracks, and would be happy to supply whatever further information you feel I can to get us past this problem.
Thanks!!
Rick
I have completed the scan of the same 1730 songs now with 14 that I did with 13. There is a bit of difference in the result. Some of the tracks that were causing the lock up scanned fine this time. There were 17 of them, now there are 3 (I think) However, 14 other tracks have some different problems with track analysing. I have (besides the 3 that cause the complete lock up) 13 others that report a fatal Error durring analysing. In this case, I can generally just hit OK, and VDJ will continue. However if one of these tracks was a part of a batch for analysing, each subsequent track would also report a fatal error. For instance, if I had 10 tracks selected and the first track reported a fatal error, if I just clicked OK, it would continue, but report a fatal error on each of the next 9 tracks unless I stop the analysis and shut down VDJ, and re-launch it. Then the rest of the 9 tracks would scan and be fine. Of the 16 total tracks that either lock VDJ up, or cause a fatal error to be reported. If I load one of them to be played, the scan ends abruptly, and a exception error is reported in the "scan thread". Of course if I choose recover from that error, VDJ reopens and imediately begins the scan process again on the bad track and reports the same error. I can't get another track to replace the bad track before the error is reported. The result is that VDJ must be shut down and re-launched.
To summarize, only 3 of the same 17 tracks that locked up VDJ in 13, cause the same problem with 14. But there are now 13 other tracks (that were fine with beta 13) that cause a different problem altogether. I have identified the probelm tracks, and would be happy to supply whatever further information you feel I can to get us past this problem.
Thanks!!
Rick
Inviato Sun 18 May 03 @ 5:20 pm