Free Sequential Style Vintage Skins for Repro-1 and Repro-5 (Updated 3-09-25)

[A_K_F]

That's magic

[Funkybot's Evil Twin]

Hey, I seem to be missing something, why does your Velvet effect have so many parameters that I don't have?

Another clever KVR user (drzhn) found some hidden parameters and posted in a different thread how to expose them so we were able to add them. Secret feature. Pretty neat!

[e-musician]

I have just discovered that the labels RATE (LFO), DEPTH and SOURCE / DESTINATION (2x MM) and VOICE DETUNE are misaligned.

You can correct their positions by using these lines in the script:


CONTROL type='Label' name='Label 1613' bounds='15.00 73.00 60.00 14.00' parent='Pane LFO-Layer' layerMask='1'
PROPERTY control='Label 1613' name='colours' id='0' value='none'
PROPERTY control='Label 1613' name='colours' id='1' value='Repro Label'
PROPERTY control='Label 1613' name='graphics' id='0' value='none'
PROPERTY control='Label 1613' name='labeltext' id='0' value='RATE'


CONTROL type='Label' name='Label 3364' bounds='525.00 298.00 50.00 14.00' parent='Pane MainTabs' layerMask='1'
PROPERTY control='Label 3364' name='colours' id='0' value='none'
PROPERTY control='Label 3364' name='colours' id='1' value='Repro Label'
PROPERTY control='Label 3364' name='graphics' id='0' value='none'
PROPERTY control='Label 3364' name='labeltext' id='0' value='DEPTH'


CONTROL type='Label' name='Label 3764' bounds='585.00 300.00 115.00 10.00' parent='Pane MainTabs' layerMask='1'
PROPERTY control='Label 3764' name='colours' id='0' value='none'
PROPERTY control='Label 3764' name='colours' id='1' value='Repro Label'
PROPERTY control='Label 3764' name='graphics' id='0' value='none'
PROPERTY control='Label 3764' name='labeltext' id='0' value='SOURCE / DESTINATION'


CONTROL type='Label' name='Label 3765' bounds='325.00 298.00 50.00 14.00' parent='Pane MainTabs' layerMask='1'
PROPERTY control='Label 3765' name='colours' id='0' value='none'
PROPERTY control='Label 3765' name='colours' id='1' value='Repro Label'
PROPERTY control='Label 3765' name='graphics' id='0' value='none'
PROPERTY control='Label 3765' name='labeltext' id='0' value='DEPTH'


CONTROL type='Label' name='Label 3766' bounds='385.00 300.00 115.00 10.00' parent='Pane MainTabs' layerMask='1'
PROPERTY control='Label 3766' name='colours' id='0' value='none'
PROPERTY control='Label 3766' name='colours' id='1' value='Repro Label'
PROPERTY control='Label 3766' name='graphics' id='0' value='none'
PROPERTY control='Label 3766' name='labeltext' id='0' value='SOURCE / DESTINATION'


CONTROL type='Label' name='Label 3770' bounds='762.00 298.00 70.00 14.00' parent='Pane MainTabs' layerMask='1'
PROPERTY control='Label 3770' name='colours' id='0' value='none'
PROPERTY control='Label 3770' name='colours' id='1' value='Repro Label'
PROPERTY control='Label 3770' name='graphics' id='0' value='none'
PROPERTY control='Label 3770' name='labeltext' id='0' value='VOICE DETUNE'

[Fannon]

Btw. if you feel comfortable with using a CLI tool like git, you can also create patch files / diffs with it that git can then also apply again on a file. It basically applies the patch for you automatically and is quite smart (if other changes have been made, it mostly can handle that, too).

Unfortunately there doesn't seem to be a convenient web-tool for this.

[abernathy]

I have just discovered that the labels RATE (LFO), DEPTH and SOURCE / DESTINATION (2x MM) and VOICE DETUNE are misaligned.

Fixed. New version posted. Thank you for noticing this and for providing the fixed code! It takes a village...of OCD musicians.

[EvilDragon]

There's a small bug on Tweaks page, when you do MM A MM B page switch, MM3/4 labels are overlaid on top of MM1/2 labels.

EDIT: Found it. Gotta remove the two labels on lines 3689-3699.

[Funkybot's Evil Twin]

Nice catch and solution ED!

[abernathy]

There's a small bug on Tweaks page, when you do MM A MM B page switch, MM3/4 labels are overlaid on top of MM1/2 labels.

EDIT: Found it. Gotta remove the two labels on lines 3689-3699.

Fixed! Thanks EvilDragon!

[mesamask]

...

...

...

...

Sorry for "pinging" you all at once, but I'm kind of interested what kind of tools you guys are using for comparing and implementing changes from script to script?
I've recently seen that question popping up elsewhere (think it was referring to Hive2), and am curious how one would actually do this in practice, too. I mean, looks like Hive2 scripts have more than 20000 lines, so I assume "manually" comparing and copy-pasting is quite a PITA.
Also I remember I've done something similar years ago (not music related, purpose was for a computer game) and it was a rather horrible job to do

@Fannon was mentioning "git" and I suspect using a version control system like git would be the only way to "automate" something for this task?
Though I guess using git would require to have at least basic programming skills. (I'm anything but familiar with git, I know what it basically is and have it even installed, but that's about it...)
Or is it like one could just create a new repo that contains "script A" --> create a new branch that contains "script B" --> use the version control for comparison --> use tools like diff/merge to implement changes ??
I'm most likely completely off with the idea above lol, but that's why I'm asking. To get a bit of a picture how this would work in general.

[Fannon]

@mesamask: I would not say that you need to be a programmer to use git, there's no programming involved. But git is a tool that was created by programmers for programmers, so its rather technical to use.

In theory there could be an online-tool, which let's you do this without installing / learning git. But I only found one online tool which can create patches (if you set output mode to "patch"): http://incaseofstairs.com/jsdiff/

Then you can share this patch (which is rather small) and you can apply it again to the current file you have. This can be fully automatic and handled by a tool, yes.

[mesamask]

Thanks @Fannon for the explanations and link for that tool.
Somehow I'm a bit in doubt if using something like git would be more effective than doing this for the most part "manually" (like using compare in Notepad++ and maybe a second editor for moving things around).
In particular, a custom skin already contains a lot of intentional differences, so I guess a version control system must be told to differentiate between the differences (lol) first (?)
Might just be my lack of knowledge, but sounds like it requires some effort to properly set it up in the first place.
Right now I believe best (when using git) would be to use the earlier versions as starting point, in order to keep track of the intentional differences and make them easier to handle later on.

[Funkybot's Evil Twin]

Do you have an existing skin you want to add the new features to? What's your specific goal and start/end points?

[mesamask]

Well this is more out of general interest.
I've seen "git" recommended not only here, and haven't really thought of using git for this before. So I was wondering what somebody like you is actually working with in practice.
Asking someone like plugmon or Ploki probably wouldn't make sense, because many of those skins are so different to the originals that I'm assuming they are writing their GUI scripts more or less entirely from scratch.

Only later on I thought about maybe updating this "Arterrador" skin and use it as a starting point for something else.
But in the end this is probably more for the purpose of having an example at hand.

(btw, sorry OP if this is drifting too far off topic )

[Funkybot's Evil Twin]

Well this is more out of general interest.
I've seen "git" recommended not only here, and haven't really thought of using git for this before. So I was wondering what somebody like you is actually working with in practice.
Asking someone like plugmon or Ploki probably wouldn't make sense, because many of those skins are so different to the originals that I'm assuming they are writing their GUI scripts more or less entirely from scratch.

Only later on I thought about maybe updating this "Arterrador" skin and use it as a starting point for something else.
But in the end this is probably more for the purpose of having an example at hand.

(btw, sorry OP if this is drifting too far off topic )

I posted some more detailed info here on how to add these controls to an existing skin:

viewtopic.php?p=8981857#p8981857

...it's not too hard to figure out if you just sit down and think logically about it. My approach was: take the original default skin theme pre-update and open in Notepad++, take the new default skin post-update and open in Notepad++, run the compare plugin. Look for big differences (things that were more than just a label X or Y position being moved). Try to figure out based on the name/pane what the change was and how it applied.

It's not hard. Just keep a backup of your original theme and experiment. I'm no programmer and could kind of figure it out.

[mesamask]

Thanks a lot @Funkybot for the useful infos
Maybe it's the case this looks more overwhelming at first glance than it is in reality.