skins for discoDSP's OB-Xd synth

[zmix]

PS: How does one replace the skins in OSX?

[george]

Does not remember CC assignments in Audio Units format. I was able to assign each parameter to a CC external controller, which worked fine but the GUI did not update.
Removing and reinstanciating the instrument lost all controller assignments.

Thanks for the report. It's very likely to be because of the parameter refactor. I'm considering removing MIDI learn/unlearn from the plugin because now parameters are correctly recognised and should be assigned by the DAW instead.

PS: How does one replace the skins in OSX?

On the Skins folder at Documents > discoDSP > OB-Xd > there are several ones. A new one can de added by duplicating any existing folder and replacing the bitmaps. Coords.xml file is new in 2.0 and adds a lot of flexibility on the skinning. It's work in progress, however you can already modify window size, knobs (48x48) for now, will be changed soon to support scalable/retina GUI), etc.

Skins can be changed by right clicking the GUI btw.

[george]

Knobs are using 144x144 now. New default bitmap and Classic coords.xml. Might update the nightly builds later or you can get the updated files from the GIT repository.

[zmix]

Does not remember CC assignments in Audio Units format. I was able to assign each parameter to a CC external controller, which worked fine but the GUI did not update.
Removing and reinstanciating the instrument lost all controller assignments.

Thanks for the report. It's very likely to be because of the parameter refactor. I'm considering removing MIDI learn/unlearn from the plugin because now parameters are correctly recognised and should be assigned by the DAW instead.

No please do not remove it..!! It's very important for me to be able to assign the labeled controls on my MIDI controller to the same parameters on the OB-Xd so that the front panel has a 1:1 relationship to the plugin. If these are not assignable then it's going to be impossible to dial in sounds directly and intuitively. The Layout of the Korg Minilogue, for example is nearly identical to the original OB-Xd layout.

Screen Shot 2016-07-22 at 18.49.14.jpg

[george]

No please do not remove it..!! It's very important for me to be able to assign the labeled controls on my MIDI controller to the same parameters on the OB-Xd so that the front panel has a 1:1 relationship to the plugin. If these are not assignable then it's going to be impossible to dial in sounds directly and intuitively. The Layout of the Korg Minilogue, for example is nearly identical to the original OB-Xd layout.

Can you try latest nightly? I have modified some compilation parameters.

XML skinning is now ready. Here it is the Classic 2.0 skin preview. Artists please check the new coords.xml inside the skin folder and is required to make any custom GUI work.

[Faceless_79]

Here's a close-up shot:

[george]

Here's a close-up shot:

[gentleclockdivider]

Here's a close-up shot:

Fingerprints and some dust would make it perfect
Bravo , a trully gorgeous render

[george]

V 2.00 Does not remember CC assignments in Audio Units format. I was able to assign each parameter to a CC external controller, which worked fine but the GUI did not update.
Removing and reinstanciating the instrument lost all controller assignments.

Does it happens with the latest nightly? https://www.discodsp.net/obxd-nightly/

[zmix]

Question: When I installed only the AU Component of the previous nightly, none of the knobs appeared. Are the .VST and .VST3 files also required for the Audio units version to function properly?

[george]

Question: When I installed only the AU Component of the previous nightly, none of the knobs appeared. Are the .VST and .VST3 files also required for the Audio units version to function properly?

There is a new Skins folder that needs to be installed.

[zmix]

V 2.00 Does not remember CC assignments in Audio Units format. I was able to assign each parameter to a CC external controller, which worked fine but the GUI did not update.
Removing and reinstanciating the instrument lost all controller assignments.

Does it happens with the latest nightly? https://www.discodsp.net/obxd-nightly/

Yes, unfortunately it is the same.

When a parameter is assigned via the "Learn" button it is not remembered.
Also the CC data does not affect the GUI knob position.

CLUE: Right clicked presets (from those submenus) do not change the knob positions when they are selected either.

It would be nice if the "Learn" function would allow parameters to be assigned in one single operation:

Press "Learn", select parameter on GUI, wiggle knob sending CC, select another parameter on GUI, wiggle another knob sending a different CC.

Currently you need to press the Learn then select a parameter on the GUI then wiggle the CC the deselect "Learn" and repeat the same process for every single parameter.


Also when I left the skins from the previous nightly in the skins folder I got an error message when I loaded the plugin, I found I needed to overwrite the subfolders in the skins directory:

Screen Shot 2020-04-22 at 10.31.48 AM.jpg

[george]

When a parameter is assigned via the "Learn" button it is not remembered.
Also the CC data does not affect the GUI knob position.

Thanks for the report. I think it may be a good decision disabling midi learn/clear until a proper implementation is working as it should.

[zmix]

When a parameter is assigned via the "Learn" button it is not remembered.
Also the CC data does not affect the GUI knob position.

Thanks for the report. I think it may be a good decision disabling midi learn/clear until a proper implementation is working as it should.

It "works" now, but it doesn't properly save the assignments. Perhaps you could implement a recallable default state or a file that was read upon instanciation?

[george]

Replied at Obxd thread to keep this on topic with skins Anyone has tried adapting theirs to the news format?