Anmelden:     

Forum: General Discussion

Topic: Skin changes when loading second deck.. - Page: 1

Dieser Teil des Themas ist veraltet und kann veraltete oder falsche Informationen enthalten

I have been using this new laptop for over a month, in the club, 7 hours three days a week, no problems. Today is my first mobile gig with this machine. I am so confident, I leave my desktop in the van. I'm working in Lord & Taylor's department store, have worked there numerous times. Straight up video mixing new club, with some classics thrown in. About 20 minutes before it's time to quite, I load a deck with a track from the sidelist, and the grey color goes out of the skin. Unload the track, and it comes back. Now, it does not matter where I load the track from, or which deck. It does it on all skins. I'm home and it's doing the same thing. Take a look here, and you will see what I mean. Any help would be appreciated, as I'm in the club tomorrow. Well now, it's today. The machine specs are here.
 
geposted Sun 18 Jan 15 @ 1:42 am
If it is happening with that particular track, is it possible to send the track to me?
Also, which transition was selected?
 
It does not matter which track i load, or the transition. It is still doing it now that I am home.
 
maybe this is one of those delete settings.xml and try situations?
 
Example please?
 
Remove your settings.xml from the VDJ folder (keep it elsewhere) and try restarting the software to create a new one.

You will lose all your settings but the original file can be put back if doing that doesn't fix the problem.
 
What settings are we talking about losing?

 
Everything basically. All your configuration is stored in that file. You would have to go through and configure like you first installed V8.

Sometimes there are gremlins in V8 that sort themselves when that file is recreated fresh.

If you keep it and the refresh doesn't sort the problem you can just put it back and everything will be restored.
 
@kradcliffe, tried your fix, and it worked. I see which settings are gone, and it's not life changing. Thanks for the help guys. Any idea what could have caused this, so I don't do it again?
 
Nope. It's just one of those things that goes bump in the night Rick!

Just keep your old settings.xml file in case someone else comes up with a fix that doesn't include deleting the file.
 
Things that go bump in the night, usually get shot. Good thing I wasn't armed in the store. "Local DJ arrested for shooting his computer". Thanks again, now have to try to match the settings with the ones on my desktop, which I will bring with me. Showtime in 2 hrs 20 minutes.
 
You could always try the settings.xml file from your desktop, they should be pretty identical!
 
 
Did you happen to keep a copy of the original settings.xml that caused the problem or did you delete it already?
Would be useful to find out what caused it.
 
Adion, yes I can send that file, and the second one that I created, because it went bump in the night again while playing last night. You just need to give me step by step instructions, as I am not too swift with the latest technology. It happened with a different scenario last night. The slideshow failed to engage, during an audio track (it worked earlier in the night). I tried to manually activate with no success, and then went to milkdrop. Boom, screen went giggly, and skin left the building with Elvis. I was going to just keep going, because it would come back, once both tracks were playing, but after the mix and the first track stopped, it would happen again. Then I loaded a track, and got an audio glitch, like I could crash any minute. Thanks to what I learned from kradcliffe earlier, I put on a twenty minute mix from my phone, closed VDJ, copied and deleted the settings, opened VDJ, closed VDJ, deleted and pasted the previous settings, and was mixing in at 5:52 of the mix (wow that was a long sentence). Also, the first incident was with the Denon MC6000, which was the first time I had used with this machine. The second time was with the RMX2, that I have been using for over a month with this machine.
 
This was happening for me until i updated DirectX 9 from the Microsoft website.
 
It sounds like a shader problem in a plugin to me; try using only the built in plugins and see if you still get issues.
 
According to the german user, Milkdrop was causing this problem.
He was testing it on another laptop, same result.
After removing Milkdrop, everything was fine again.

Strange, because I'm (and hundreds of other users) are using milkdrop too without problems.
Another theory is an older installation of DX.
 
If it's Milkdrop then it's almost definitely a misbehaving shader!

Make sure DX9 and video card drivers are up to date.
 
 
74%