Dazmax
Sorry mate but I think you are going to have to bite the bullet and go through your files with the newer V6. I know its a pain in the butt.
Once its done its done. It might take you some time but it will be worth it. Any version post V5 will not suffer from this issue. THATS WHY it was changed.
Sorry mate I know this is not what you want to hear but that is, as they say " The way it is"
Daz
Once its done its done. It might take you some time but it will be worth it. Any version post V5 will not suffer from this issue. THATS WHY it was changed.
Sorry mate I know this is not what you want to hear but that is, as they say " The way it is"
Daz
Posté Thu 29 Oct 09 @ 5:48 pm
djcity
There has got to be a better way. I have about 300gb of music. I CAN'T re-analyze it all. I'll be out of business for the next two months. I'm an urban DJ spinning Hip Hop, R&B, and Reggae. The scan won't get even 1/2 of it right.
I'm depending on certian people to help me through this and have all confidence in them to see me through.
I'm depending on certian people to help me through this and have all confidence in them to see me through.
Posté Fri 30 Oct 09 @ 1:51 am
Charlie Wilson
City, this has arisen because your using an old version. Why don't you just use 6.2 be done with it and never have this issue again
Posté Fri 30 Oct 09 @ 3:41 am
djcity
I have been trying to upgrade to 6.0.2 on my gig machine but the database for some reason won't come over. I have been working on this issue. Until I get that resolved, I gotta use 3.4. It may be a mute point now though.
Posté Fri 30 Oct 09 @ 8:59 am
Dazmax
Could you beg or borrow a second PC , copy the files and re build your database while using your main machine for gigs. Once you finnish you could then transfer everything back but using V5+?
Daz
Daz
Posté Fri 30 Oct 09 @ 3:06 pm
djcity
I built the database for v5.2 that I will upgrade to 6.0.2 on Sunday. I have a party tonight and two shows tomorrow and I have learned better that to upgrade on my gig machine right before a show.
My issue now is that the new version sounds grainy. Thats the best way for me to describe the sound.
I did a test with the same track in 3.4 and in 5.2 and in 3.4 the sound is crystal clear while in 5.2, it's not. the sound is grainy.
Any advice?
O.k here is a better description of the sound...It sounds like static or a little bit like a short in a wire. I got that from stopping the platter and moving it slowly and just a very little.
I'm playing at Hood College tonight and am trying to get my database and sound correct before tonights show.
My issue now is that the new version sounds grainy. Thats the best way for me to describe the sound.
I did a test with the same track in 3.4 and in 5.2 and in 3.4 the sound is crystal clear while in 5.2, it's not. the sound is grainy.
Any advice?
O.k here is a better description of the sound...It sounds like static or a little bit like a short in a wire. I got that from stopping the platter and moving it slowly and just a very little.
I'm playing at Hood College tonight and am trying to get my database and sound correct before tonights show.
Posté Fri 30 Oct 09 @ 3:52 pm
mp3jrick
Click config/performance
Uncheck safe mode and over clock
Move the performance lever all the way to the left
Put the latency box on auto
Then try it again
Uncheck safe mode and over clock
Move the performance lever all the way to the left
Put the latency box on auto
Then try it again
Posté Fri 30 Oct 09 @ 4:14 pm
djcity
I have done that but it still sounds bad.
Fastest
No Safemode................No Overclock
Latency is set to Auto
Basic interpolation is checked
scratch is set to quality
Simple algorithm is checked
master tempo Fast is checked.
It sounds pretty bad almost like it's too loud.
Fastest
No Safemode................No Overclock
Latency is set to Auto
Basic interpolation is checked
scratch is set to quality
Simple algorithm is checked
master tempo Fast is checked.
It sounds pretty bad almost like it's too loud.
Posté Fri 30 Oct 09 @ 4:18 pm
Tear Em 'Up
Your mixer gain may be too hot for your new configuration. Try turning it down a tad.
Posté Fri 30 Oct 09 @ 5:19 pm
djcity
Thanks Terry. I tried that. Unfortunately thats not the problem. I may not be a computer guy but I am a sound guy. I gotta work on it at the party tonight. I have no other choice at this point.
Wish me luck.
Wish me luck.
Posté Fri 30 Oct 09 @ 5:22 pm
Dazmax
Hi City
The only setting I can see that you might want to mess with is Scratch. try setting to optimise for latency.
Daz
The only setting I can see that you might want to mess with is Scratch. try setting to optimise for latency.
Daz
Posté Sat 31 Oct 09 @ 12:08 pm
djcity
I had to do a party on Saturday night at Hood College.
I had a BAD night. Really weird stuff happened in VDJ last night. On virtual deck 1, I would stop the CDJ but the virtual deck in VDJ would still move forward slowly. There were times early in the night that virtual player 1 would stop responding to timecode all together. I had to shut VDJ down and restart it in order for VDJ to pick up the timecode again. Let me explain, I still had the timecode signal in VDJ, I still had 100%, it just would not control the deck. It was like I was in internal mode. I tried with the Maya44 USB, the NI Audio 4 and the Serato interface. Same distortion and same issues on all three. As far as my other laptop is concerned, the Vista, I have not been able to get it to sound good enough to really test it out. I get snaps crackles and pops. I was thinking it was a Vista thing but now i'm not so sure. Serato sounds great. Just like 3.4 sounded.
3.4 on my XP laptop sounds GREAT! Crystal clear, no distortion, no snaps,crackles or pops. I have played the same song, the exact same mp3 in v3.4 and it sounds perfect but that same mp3 in 5.2 sounds bad.
I still had the distorted sound but my sound system helped to mask it a little. The downside of that is that I blew both my compression drivers half way into the show. I had a pair of backup speakers so I was able to keep it moving. Power does not blow speakers, distortion does. I had no other choice but to play with what I had and to do the best I could do. I had all my levels adjusted properly, never even hit amber on my led's. Green all the way through my system.
Lastly, VDJ kept changing my bpm's. They would double when I loaded a track. Not all the time but it happened enough to give me a REAL hard time finding things and playing things. On top of that, the cbg's kept being incorrect even though I made sure all was correct before I left the house. I would load a track and watch bpm's double and / or watch the beatgrid move. For example, I load a track that's 80 bpm's and the large box is on the first downbeat that I have a cue point set for. I would see VDJ move the large box 1 beat over or chop it in half by moving it 1/2 beat over. Also, I noticed that even though the bpm's are correct and exact and I have the beatgrid correct, as the track advances towards the middle and end, the beatgrid is no longer syncing to the waveform. It's like the bpm is incorrect even though I KNOW it's correct. I can hit my 1st cue point and see that the beatgrid is correct at the beginning of the track but it's way off towards the end of the track. That has nothing to do with the times VDJ just changes the bpm of the track I loaded. A track that is 75bpm's and scanned to be 75bpm's, when loaded can change to 150bpm's.
Believe it or not, even with all those issues, I had a really good party. No one but me knew how hard of a time I was having. Those kids could not even tell that the horns blew. I just know that I struggled all through the night. REALLY struggled.
Any ideas or advice, I have to get this fixed somehow.
I had a BAD night. Really weird stuff happened in VDJ last night. On virtual deck 1, I would stop the CDJ but the virtual deck in VDJ would still move forward slowly. There were times early in the night that virtual player 1 would stop responding to timecode all together. I had to shut VDJ down and restart it in order for VDJ to pick up the timecode again. Let me explain, I still had the timecode signal in VDJ, I still had 100%, it just would not control the deck. It was like I was in internal mode. I tried with the Maya44 USB, the NI Audio 4 and the Serato interface. Same distortion and same issues on all three. As far as my other laptop is concerned, the Vista, I have not been able to get it to sound good enough to really test it out. I get snaps crackles and pops. I was thinking it was a Vista thing but now i'm not so sure. Serato sounds great. Just like 3.4 sounded.
3.4 on my XP laptop sounds GREAT! Crystal clear, no distortion, no snaps,crackles or pops. I have played the same song, the exact same mp3 in v3.4 and it sounds perfect but that same mp3 in 5.2 sounds bad.
I still had the distorted sound but my sound system helped to mask it a little. The downside of that is that I blew both my compression drivers half way into the show. I had a pair of backup speakers so I was able to keep it moving. Power does not blow speakers, distortion does. I had no other choice but to play with what I had and to do the best I could do. I had all my levels adjusted properly, never even hit amber on my led's. Green all the way through my system.
Lastly, VDJ kept changing my bpm's. They would double when I loaded a track. Not all the time but it happened enough to give me a REAL hard time finding things and playing things. On top of that, the cbg's kept being incorrect even though I made sure all was correct before I left the house. I would load a track and watch bpm's double and / or watch the beatgrid move. For example, I load a track that's 80 bpm's and the large box is on the first downbeat that I have a cue point set for. I would see VDJ move the large box 1 beat over or chop it in half by moving it 1/2 beat over. Also, I noticed that even though the bpm's are correct and exact and I have the beatgrid correct, as the track advances towards the middle and end, the beatgrid is no longer syncing to the waveform. It's like the bpm is incorrect even though I KNOW it's correct. I can hit my 1st cue point and see that the beatgrid is correct at the beginning of the track but it's way off towards the end of the track. That has nothing to do with the times VDJ just changes the bpm of the track I loaded. A track that is 75bpm's and scanned to be 75bpm's, when loaded can change to 150bpm's.
Believe it or not, even with all those issues, I had a really good party. No one but me knew how hard of a time I was having. Those kids could not even tell that the horns blew. I just know that I struggled all through the night. REALLY struggled.
Any ideas or advice, I have to get this fixed somehow.
Posté Mon 02 Nov 09 @ 10:01 am
GadgetMan
With all these problems I'd strip everything back and start again...
Backup your XP laptop (use the file/settings transfer wizard to back everything up to one of your exeternal hard drives)
Insert your XP recovery disc
Reformat the drive and start from scratch.
Install XP
Install the necessary drivers ONLY
Apply the necessary service packs (1,2 & 3) - depending on what rev your recovery CD is
Once you are at SP3, apply the remianing windows updates
Install SmartDeFrag from IOBit.com and do a Deep Optimize
Create a Restore Point
Install LATEST drivers for your primary device/soundcard - not all of them
Install VDJ 3.4 & 6.0.2 (not 5 - let's skip that!)
Now do your tests. You have no other intefering software/hardware - this should be your base system build.
Assuming all goes will Create Another Restore Point
If not start tweaking the VDJ settings until you get the desired sound
Install any other remaining software/drivers you need
Check the VDJ set up between each install - you may just find the offending software/driver that's giving you all this grief
Only install what you need to
Try Game Booster from IOBit.com as well to shut down unnecessary processes.
If you get problems with that device, go back to your first restore point and repeat the steps above.
You should not continue to to play live if your setup is damaging your equipment - You need to make time for this, you can't use each gig as a live test, you can't spend the hour before each gig trying to resolve problems. You need to put the time and effort in to get this sorted.
If it means leaving the lappy at home for a few shows and working purely from CD, then that's what you are going to have to do.
As so many of the threads state here, it's rarely VDJ that's the problem (otherwise we'd all be screaming). If it is VDJ then a fresh install normally sorts that out.
Laptops/PC's are like cars, they need servicing regularly, failure to look after the engine can result in nasty problems down the line.
A fresh install of any O/S is like changing the oil & filter, cleaning the air filter and cleaning your spark plugs. It's necessary to keep things running smoothly.
I rebuild my laptop on average once every 6 months, sooner if something goes wrong.
I'm even considering getting some image software so that the next time I re-build and have it running smoothly, I'll take a complete image of the setup and then restore from that point in the future...
Cheers,
Roy
Backup your XP laptop (use the file/settings transfer wizard to back everything up to one of your exeternal hard drives)
Insert your XP recovery disc
Reformat the drive and start from scratch.
Install XP
Install the necessary drivers ONLY
Apply the necessary service packs (1,2 & 3) - depending on what rev your recovery CD is
Once you are at SP3, apply the remianing windows updates
Install SmartDeFrag from IOBit.com and do a Deep Optimize
Create a Restore Point
Install LATEST drivers for your primary device/soundcard - not all of them
Install VDJ 3.4 & 6.0.2 (not 5 - let's skip that!)
Now do your tests. You have no other intefering software/hardware - this should be your base system build.
Assuming all goes will Create Another Restore Point
If not start tweaking the VDJ settings until you get the desired sound
Install any other remaining software/drivers you need
Check the VDJ set up between each install - you may just find the offending software/driver that's giving you all this grief
Only install what you need to
Try Game Booster from IOBit.com as well to shut down unnecessary processes.
If you get problems with that device, go back to your first restore point and repeat the steps above.
You should not continue to to play live if your setup is damaging your equipment - You need to make time for this, you can't use each gig as a live test, you can't spend the hour before each gig trying to resolve problems. You need to put the time and effort in to get this sorted.
If it means leaving the lappy at home for a few shows and working purely from CD, then that's what you are going to have to do.
As so many of the threads state here, it's rarely VDJ that's the problem (otherwise we'd all be screaming). If it is VDJ then a fresh install normally sorts that out.
Laptops/PC's are like cars, they need servicing regularly, failure to look after the engine can result in nasty problems down the line.
A fresh install of any O/S is like changing the oil & filter, cleaning the air filter and cleaning your spark plugs. It's necessary to keep things running smoothly.
I rebuild my laptop on average once every 6 months, sooner if something goes wrong.
I'm even considering getting some image software so that the next time I re-build and have it running smoothly, I'll take a complete image of the setup and then restore from that point in the future...
Cheers,
Roy
Posté Mon 02 Nov 09 @ 10:23 am
djcity
Great Idea Roy. The only issue with that is that it's ONLY the new version thats giving me hell.
3.4 sounds GREAT. Serato sounds GREAT. 5 and 6, not so much.
I may just have to re-do the 3.4 database and keep it moving like that but I know I "should" be able to run a newer version and have the same results as I have had with 3.4
I was hoping that by building the 5.2 database, I would be able to simply upgrade to 6.0.2 but when I upgraded, the database did not upgrade. I thought I lost 11 hours of database building work (Yes, I worked for 11 hours straight building the 5.2 database) but I re-downloaded 5.2 and my database was complete again.
My other alternative is to use Serato as my primary DJ software and I really don't want to do that.
3.4 sounds GREAT. Serato sounds GREAT. 5 and 6, not so much.
I may just have to re-do the 3.4 database and keep it moving like that but I know I "should" be able to run a newer version and have the same results as I have had with 3.4
I was hoping that by building the 5.2 database, I would be able to simply upgrade to 6.0.2 but when I upgraded, the database did not upgrade. I thought I lost 11 hours of database building work (Yes, I worked for 11 hours straight building the 5.2 database) but I re-downloaded 5.2 and my database was complete again.
My other alternative is to use Serato as my primary DJ software and I really don't want to do that.
Posté Mon 02 Nov 09 @ 11:20 am
GadgetMan
djcity wrote :
Great Idea Roy. The only issue with that is that it's ONLY the new version thats giving me hell.
3.4 sounds GREAT. Serato sounds GREAT. 5 and 6, not so much.
I may just have to re-do the 3.4 database and keep it moving like that but I know I "should" be able to run a newer version and have the same results as I have had with 3.4
I was hoping that by building the 5.2 database, I would be able to simply upgrade to 6.0.2 but when I upgraded, the database did not upgrade. I thought I lost 11 hours of database building work (Yes, I worked for 11 hours straight building the 5.2 database) but I re-downloaded 5.2 and my database was complete again.
My other alternative is to use Serato as my primary DJ software and I really don't want to do that.
3.4 sounds GREAT. Serato sounds GREAT. 5 and 6, not so much.
I may just have to re-do the 3.4 database and keep it moving like that but I know I "should" be able to run a newer version and have the same results as I have had with 3.4
I was hoping that by building the 5.2 database, I would be able to simply upgrade to 6.0.2 but when I upgraded, the database did not upgrade. I thought I lost 11 hours of database building work (Yes, I worked for 11 hours straight building the 5.2 database) but I re-downloaded 5.2 and my database was complete again.
My other alternative is to use Serato as my primary DJ software and I really don't want to do that.
You seem to have a lot of stuff on this one machine. I'm meticulous about what I load on to my laptop. I have an RMX that's it. I use VDJ. I don't have any other software. My concern is that you are masking the real problem which is preventing you from upgrading.
The reasons for the re-install were three fold:
1. You should do it regularly - like servicing your car
2. You are minimising the contamination of drivers/software/resources that could be impacting your performance
3. By starting over you can add/check, add/check to determine what is causing the actual issue.
It's standard technical support strategy:- Remove everything that could be affecting it and add things back in one at a time, checking and re-checking as you go.
As an example, I have just had a major problem with my central heating. The main pump between the boiler and the thermal store failed. It ceased because the thermostat on the thermal store wasn't cutting in/out. This was happening because the cowboy who originally fitted the stat (prior to me moving in here) used expanding foam to hold the stat in place. The foam had got behind between the stat and the tank and rendered it useless. I only found this out because I was upgrading other parts of my system and ended up having to strip the whole lot back and re-attaching everything to identify the weak spot.
Are you 100% sure you know what is corrupting the database, or do you think you know? There is no real way to tell until you strip back and re-build. For the sake of a day at the most, you could really find out. The worst case? You could be back to here but with a re-optimised machine - but then you will know for sure...
Cheers,
Roy
Posté Mon 02 Nov 09 @ 4:13 pm