Sign In:     

Forum: Addons

Topic: Prime 4 Extended Screen Skin - Page: 3
The default skin is already limited to 30fps regardless of the fps of the skin on the computer
 
Great idea, thx Adion 🙏
 
Hello,
thanks for helping out the other day. I just noticed something and not too sure how to get it fixed. The color scheme on the denon prime 4 when the skin is loaded are deck 3 green, deck 1 blue, deck 2 red and deck 4 orange or yellow, not quite sure. However when loading tracks, the load buttons change according on decks 123 but not 4, the deck 4 load button remains red after selecting deck 4 on the controller. is there anyway to fix that. and is there anyways to change those colors of i dont want them that way.
 
Hi,
this is an interesting observation. Never noticed. But you are right.
But:
The colors on the controller are not part of the extended skin. Those are controlled by the controller mapping.
For instance the mapping for the led of the right load button LED_LOAD_RIGHT is defined as:

deck right loaded ? deck right get_deck_color "absolute" : deck right get_deck_color "absolute" 40%

As you can see, the get_deck_color script returns the color been used. Not sure if this can be changed somewhere else as the documentation of this verb says:
return blue or red if the deck is the left deck or right deck (and gray otherwise). Can be used with a darkness modifier: 'get_deck_color 50%' Use 'get_deck_color "absolute"' or 'get_deck_color "absolute" 50%' to get a color based on actual deck rather than left/right (red for deck 1, blue for deck 2, orange for deck 3, green for deck 4)

Seem so me as those colors are fixed. But you could change the color of all leds on the controller by creating a custom mapping. But this has to be done for any led that reflects the deck color.

If you want to change the color in the Extended Skin, this is easy. Just search for lines like this one in the XML:
<define color="deckcolorbright" value="#63A9F0" deck="1"/>
...

Change the value to the color you want for the deck you want and you should be done. In my skin I try to refer to this color definitions everywhere a deck color is displayed.

Hope that helps
Cheers
 
hi
i dont see GAIN, you can add ?
 
Electronic Green Room wrote :
Discussion about Prime 4 Extended Screen Skin

Hello, would it be possible to use this skin on a computer screen? To use on touch screens as in the image?
 
There is a prototype. But it has not been tested very well. Send me an email and I send it back to you so you can try it: electronic.greenroom@gmail.com
 
Hello,

First of all, I want to express my appreciation for the amazing work you've done with this skin. I'm truly impressed with how well it integrates with the Prime 4+ and Virtual DJ, creating such a seamless experience!

I have a small question or request regarding the browser's behavior. When the "Browser Auto Switch" option is enabled, the browser becomes inactive after 5 seconds of inactivity, but I personally find that 5 seconds is a bit too short. Would it be possible to increase this timeout to 10 seconds, or even better, provide an adjustable setting in the options so users can set the inactivity timeout duration to whatever they prefer?

Additionally, I've noticed that the browser is considered inactive when scrolling with the finger or when looking at track info through the “i” icon. Even when actively working in the browser, the timeout causes it to disappear. Perhaps this could be reviewed and fixed, or maybe a new setting could be introduced so that the auto switch only triggers when a track is loaded, not due to inactivity?

Thank you once again for the fantastic work on the skin, and I really appreciate your help and consideration!

Best regards,
Mpex
 
Hey Mpex,

thank you very much for your feedback. It is really appreciated.
Regarding the Browser-Auto Switch feature:
The functionality is derived from a native VDJ function. The verb used to do so is: browser_isactive
The documentations says:
return true when the browser was used by a controller in the past 6 seconds

So it is nothing that can be controlled by a skin developer. :-(
Since it is a core feature, which btw. is used by the default skin as-well, you can ask in the forum the VDJ developers on an option. Especially regarding the touch-is-not-recognized-as-a-browser-action problem.

Cheers
Jochen
 
Hi Jochen,

Thanks a lot for the info! I’ll check with support to see if there’s anything that can be configured or adjusted – maybe they’ll make it a user setting in the future.

Thanks again, and for now I’ll just leave the feature turned off. Everything else is working perfectly – really great skin!

Best regards,
Mpex
 
If some Browser areas or functions do not refresh the Timer, you could overlay some "ghost" buttons with action="browser_isactive on" (and perhaps with clickthrough="pass" ) which would keep the Browser visible for another 6 secs.
But indeed there is no adjustable value for the action.