The default skin is already limited to 30fps regardless of the fps of the skin on the computer
Posté Wed 25 Sep 24 @ 6:46 am
Great idea, thx Adion 🙏
Posté Wed 25 Sep 24 @ 7:12 am
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.
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.
Posté Thu 14 Nov 24 @ 2:35 pm
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
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
Posté Thu 14 Nov 24 @ 4:21 pm
hi
i dont see GAIN, you can add ?
i dont see GAIN, you can add ?
Posté Thu 14 Nov 24 @ 5:32 pm
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?

Posté Sat 23 Nov 24 @ 3:39 am
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
Posté Sat 23 Nov 24 @ 7:26 am
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
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
Posté Mon 07 Apr 25 @ 11:31 pm
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
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
Posté Tue 08 Apr 25 @ 6:28 am
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
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
Posté Tue 08 Apr 25 @ 2:16 pm
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.
But indeed there is no adjustable value for the action.
Posté Tue 08 Apr 25 @ 2:43 pm
What an AMAZING skin! I would send $$$ to whoever created this. Its covered most everything! It makes the prime 4+ 10000% better! Thank you!!!!
Posté Sat 13 Sep 25 @ 11:27 pm
Hey Lukeb,
thank you so much for your feedback. If you want to support my work, you'll find all informations here: https://www.electronic-green-room.de/support
Cheers Jochen
thank you so much for your feedback. If you want to support my work, you'll find all informations here: https://www.electronic-green-room.de/support
Cheers Jochen
Posté Sun 14 Sep 25 @ 7:10 am
Hallo Jochen,
A big thanks for sharing your nice work with the community. I'm just starting testing your skin for my Prime4+ and I have a few questions/remarks:
(sorry if these are newbie questions)
1. Is there a way to screenshot the prime screen while using a skin? (just to illustrate certain points here)
2. I wasn't able to customize the deck buttons (currently: Pitch 4% / Pitch 8 % / Broadcast / Record)
3. In "folder content" view, only one instant filter is visible: is it possible to have more?
4. Same view: if you select the button for filtering option (◉) then "unclick", everything displayed on the right disappears (including the quick filter button)
5. Is there a way to zoom in/zoom out the wave forms?
Thanks!
A big thanks for sharing your nice work with the community. I'm just starting testing your skin for my Prime4+ and I have a few questions/remarks:
(sorry if these are newbie questions)
1. Is there a way to screenshot the prime screen while using a skin? (just to illustrate certain points here)
2. I wasn't able to customize the deck buttons (currently: Pitch 4% / Pitch 8 % / Broadcast / Record)
3. In "folder content" view, only one instant filter is visible: is it possible to have more?
4. Same view: if you select the button for filtering option (◉) then "unclick", everything displayed on the right disappears (including the quick filter button)
5. Is there a way to zoom in/zoom out the wave forms?
Thanks!
Posté Sun 05 Oct 25 @ 4:50 pm
jeromeip wrote :
Hallo Jochen,
A big thanks for sharing your nice work with the community. I'm just starting testing your skin for my Prime4+ and I have a few questions/remarks:
(sorry if these are newbie questions)
1. Is there a way to screenshot the prime screen while using a skin? (just to illustrate certain points here)
2. I wasn't able to customize the deck buttons (currently: Pitch 4% / Pitch 8 % / Broadcast / Record)
3. In "folder content" view, only one instant filter is visible: is it possible to have more?
4. Same view: if you select the button for filtering option (◉) then "unclick", everything displayed on the right disappears (including the quick filter button)
5. Is there a way to zoom in/zoom out the wave forms?
Thanks!
A big thanks for sharing your nice work with the community. I'm just starting testing your skin for my Prime4+ and I have a few questions/remarks:
(sorry if these are newbie questions)
1. Is there a way to screenshot the prime screen while using a skin? (just to illustrate certain points here)
2. I wasn't able to customize the deck buttons (currently: Pitch 4% / Pitch 8 % / Broadcast / Record)
3. In "folder content" view, only one instant filter is visible: is it possible to have more?
4. Same view: if you select the button for filtering option (◉) then "unclick", everything displayed on the right disappears (including the quick filter button)
5. Is there a way to zoom in/zoom out the wave forms?
Thanks!
Hey Jeromeip,
here are the anwers:
1) That is a bit complicated, you could use the skin as the default main skin (instead of the default skin) and then make screenshots. But then you may have problems to go back to default skin. So it is not suggested. But this is the way I do screenshots.
2) You have to go to the settings of the skin, there is an option that toggels between custom buttons and the fixed buttons.
3) The filters available are those you configure in VDJ. So how many are there depends on you configuration.
4) That happens sometimes, espacially if you set the fps to more then 30fps for the skin. In that case the rendering is not accurate.
5) This works as with the default skin. Shift + Browse Knob should do the job.
Hope I could help.
Cheers Jochen
Posté 5 days ago @ 12:41 pm
Thanks Jorgen!
I'm going to test this asap and keep you posted!
Well... no! I have 2 instant filters in VDJ and only one was showing up (so I inverted my two filters to get the most useful visible in Prime screen). I didn't change anything in configuration, so fps is still set to 30!
I'm going to test this asap and keep you posted!
Electronic Green Room wrote :
3) The filters available are those you configure in VDJ. So how many are there depends on your configuration.
Well... no! I have 2 instant filters in VDJ and only one was showing up (so I inverted my two filters to get the most useful visible in Prime screen). I didn't change anything in configuration, so fps is still set to 30!
Posté 5 days ago @ 1:11 pm
Is there an optimal FPS to use and is the main skin FPS linked to the Prime units as well?
If I play two tracks together the waveforms get a bit jerky and difficult to follow. I tried both 30fps and 60fps but no difference at all.
If I play two tracks together the waveforms get a bit jerky and difficult to follow. I tried both 30fps and 60fps but no difference at all.
Posté 5 days ago @ 2:18 pm
The Prime skins are normally limited to 30fps, but the communication with the screens is unfortunately very slow, so it depends how much of the screen needs to be updated how fast it will actually refresh.
Custom skins for these units do need to take additional care that elements don't overlap, so that they don't require unnecessary additional updates to the screens.
debug drawing can be used on a custom button to verify if only the intended elements are being updated.
Custom skins for these units do need to take additional care that elements don't overlap, so that they don't require unnecessary additional updates to the screens.
debug drawing can be used on a custom button to verify if only the intended elements are being updated.
Posté 5 days ago @ 2:58 pm
I'll add to Adion's notes, experimentalSkinEngine needs to be on to see any results from debug drawing
Posté 5 days ago @ 3:35 pm
FWIW I was running an older version (from maybe 6 months ago) on both VDJ and the P4 skin, and recently updated to latest versions of both. I noticed on both my P4 and P4+ that the waveforms seem a bit "fatter" (the thinner ones were better I think), and fps seems a bit stuttery - used to be pretty flawless. I guess I had upgradeitis because I also updated to macos 26.
Not sure if any of this is related.
Not sure if any of this is related.
Posté 5 days ago @ 3:41 pm