Entra:     

Forum: Addons

Topic: Denon DJ SC5000 Screen - Page: 2
Hello dear team, what new features does the latest update actually bring? Or is it just a compatibility update for the latest VDJ version?

Greetings from Berlin
 
Certainly you should be able to display two decimal places on the pitch on the player display, allow us to choose the deck color, allow us to hide BPM and phase meters, and make the moving waveform smoother or gone. This is way behind the Serato implementation. You might have better sound than Engine OS, but there's not much other perks to using VDJ with Prime.
 
@Reticuli Apart from the fact you can skin the entire device interface to your pleasing....?
 
Where exactly? This is all like MIDI 2.0 HID stuff. The mapping doesn't appear to be saved in my mapping folder. I've already changed functionality of some of the buttons to correct some issues.
And I'm not talking about the computer screen, rather the display on the player.

Also, virtual dj seems to have this goofy pitch reset when you load a track where it resets to zero. I want it to reset the soft takeover to pick up the current pitch fader state upon track load, but I don't see the option. I want the soft takeover to be overridden by track load, though, not continue to do the soft takeover. I invented this method and got it implemented for the Denon prime decks, but I can't find a way to do it in VDJ.
 
Yeah the thread here is about the device skin so obviously this is for the device screen
If it has a device skin, it can be skinned, if you can't skin there are people who can for you if you respect their time.

As for pitch, type "PITCH" into settings search, look again, because it's not a buried setting.
 
Where is the device skin saved when it is automatically downloaded? That's the problem. It seems to be saved to a hidden location.
 
It's in the skins directory. It's just coded (in the XML) so it doesn't show, to prevent loading it as a standard skin.
 
Found it. Thank you.

Using my extensive human factors engineering and industrial design training and some help from LLM AI, I have done a custom minimalist 6-deck 1920x1080 computer screen skin with 2 decimal places on the pitch, improved the 6-deck player screen skin for the Prime players with 2 decimal places and no automation distractions, and changed the SC5000 & SC5000M mappings to be more dim and make the platters monochrome and disabling sync:

https://drive.google.com/file/d/1iHtbsW_sDgqNS_NLZiA2vvqYRsGlffUC/view?usp=sharing

https://drive.google.com/file/d/1UJJMR5QzArmnu5U9P5QU1mTMMlFQn3UU/view?usp=sharing

If I can figure out a way to resolve the issues with reading the M's motorized platter when a lossless Tidal track is loading and being analyzed, which has not been resolved with latency adjustments, direct gigabit ethernet, and every other setting I can find, then I might consider buying the Pro Infinity or whatever it is finally for 300 bucks when this 30 day lite trial ends that creating a log-in on the VDJ install was nice enough to give me while I work out these issues. Seems to have linked to my account on here, and I've had a tone of bundled versions of VDJ over the years. Certainly the 10-minute nonsense wasn't going to cut it, and a log-in gave me the opportunity. I will keep trying to figure out a solution in the next month. Oh, here are my current settings if anyone is interested:

https://drive.google.com/file/d/13x4DzrY3hgVxSzqNzIKXewO_kqePL2xS/view?usp=sharing

Surprisingly, Engine OS's use of Elastique Efficient is still king, and even pitch quality of 4 is no match. I almost wonder if the keylock off mode on the Denons in standalone mode is intentionally degraded to match the degradation of keylock and key change, or if it's the core audio processing degradation on the Prime players that is the primary cause of the issues on them. Comparing keylock off on current VDJ to Engine OS is kind of shocking through an MP2015 slaved at 44.1khz with 44.1khz tracks. 96khz be gone! Even if you ignore Engine OS' treble roll-off, the high hats on liquid D&B are too crunchy, and tech trance is too muddy.

On the motor tracking issue, perhaps VDJ needs motorWheelLockTime simply to trigger not just when you push start or stop, but when you disengage or engage the motor, for which about 5-7 seconds appears sufficient, but also to remain in effect whenever tracks are loading or analyzing on any deck. That expansion of that feature might be sufficient. Right now, if you want to load a lossless track over Tidal and a motorized platter is running on a deck that is playing out, you best use two fingers to both hit the motor button and simultaneously stop the record. That's tough to remember and tough to carry out flawlessly, though.

I might actually try my interface mock-up's attempt at this key change method on-screen, too:

https://i0gc7q.axshare.com/#id=amtcx7&p&p=page_1

And try to add this as a pic that comes up in the center jog display of the non-Ms:

https://drive.google.com/file/d/1z5IjGo_icntfGdzzdDUYadZ3dwyVygVX/view?usp=sharing

If anyone is interested, here is also a key conversion utility I did that is helpful when currently we only have - & + buttons on screen:

https://jn6rep.axshare.com/#id=e9lsws&p&p=key_change_day

Like I said, if the motor tracking issue on track loading and analysis can be resolved, this system could be my go-to at home for practicing, live streaming online, and building set lists, with the Prime players in standalone mode being the obvious choice in live venues where sound quality with keylock off is less important and Elastique and Engine OS' finite impulse response processing (albeit super efficient and degrading) can really shine in imperfect environments.

P.S. While I usually use v3.4 of Engine OS on my players in standalone mode because I think they fouled up the later interfaces' layout, I *did* try v5 with VDJ, and it did not help the motor tracking issue. If anyone has any ideas, let me know.
 
 
Done.

BTW, you had an issue with the soft takeover lights on the mappings for the SC5000 non-M and M, and I fixed those on my mappings... besides messing with the lights and other stuff.

While I'm at it, I will upload some of my other stuff for posterity.
 
FWIW, the Engine OS method for dealing with unwanted pitch bending after motor disengagement is to wait until the platter stops moving to begin utilizing the velocity for the bend. When motor is turned off, clearly VDJ knows it's off, because it immediately begins reading the bend instead of using the platter to control the speed of the music. So, when start and stop are set to instant in settings, those are being ignored by motorWheelLockTime, and engaging motor is also using that value, but disengaging is not utilizing this value. The value would have to be 7 to 10 seconds, though, instead of only a second or two, and, again, not applying bend until the platter stops makes more sense for turning the motor off. Obviously with real turntables there are motor-off tricks, but that's not what we're talking about here and we already have stop time for that... though, that could also take advantage of this addition to appropriately ignore bend until the motor stops, or if you start it again before the platter stops then it just goes back to watching velocity for track speed directly like a turntable, that last part which it already appears to do correctly.