Obxd synthesizer

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
OB-Xd - Virtual Analog Synthesizer

Post

discoDSP wrote: Wed Jul 01, 2020 7:24 am New nightly builds.

https://www.discodsp.net/obxd-nightly/

Fixed XML assert issues. Test and feedback is appreciated!
Just installed the latest nightly build, dated July 1. And I know you said the VST3 version would show which preset is chosen in some "final" update, but I'm not sure which one. This latest one still doesn't show the current preset in use, thought the VST2 version does.

This version didn't seem particularly sluggish in Sonar/Cakewalk by Bandlab, though it came up with a different skin than I remember using for the previous version. But that was easily fixed. And I'm not sure how to assign CC to anything in the synth. Clicking on the "Learn" button lights it up, but clicking on anything I want to control after that does nothing. And there's no indication of what I could control anyway. Again, I'm not sure how you're supposed to assign MIDI CC with this synth; there are no manuals with the nightly versions, and I must have deleted the "stable" version some time ago.

Steve
Here's some of my stuff: https://soundcloud.com/shadowsoflife. If you hear something you like, I'm looking for collaborators.

Post

Hello Steve, thanks for the feedback.

The preset issue may be due to being compiled using a prior JUCE 5. I will investigate what's going on.

Regarding MIDI CC, it never worked properly in the plugin version and we are now implementing a MIDI CC table as well as proper MIDI CC Learn for the incoming builds.

Cheers,
George.

Post

Next 2.0 nightly build will get MIDI CC support. Proper MIDI learn/clear will be implemented next.

Post

2.0 MIDI CC table. Nightly build will be available as soon as MIDI learn / clear gets fully implemented.

Code: Select all

15-> VOICE_COUNT
16-> UNISON
17-> OCTAVE
19-> LFOFREQ
22-> LFO1AMT
25-> LFO2AMT
33-> TUNE
34-> BENDOSC2
35-> LEGATOMODE
36-> BENDLFORATE
36-> LDEC
37-> LSUS
37-> VFLTENV
38-> FATK
39-> FDEC
40-> FSUS
41-> FREL
42-> RESONANCE
43-> OSC2_DET
44-> LFOSINWAVE
45-> LFOSQUAREWAVE
46-> LFOSHWAVE
47-> LFOOSC1
48-> LFOOSC2
49-> LFOFILTER
50-> LFOPW1
51-> LFOPW2
52-> OSC2HS
53-> XMOD
54-> OSC1P
55-> OSC2P
56-> OSCQuantize
57-> OSC1Saw
58-> OSC1Pul
59-> OSC2Saw
60-> OSC2Pul
61-> PW
62-> BRIGHTNESS
63-> ENVPITCH
71-> VOLUME
72-> LREL
73-> LATK
74-> CUTOFF
81-> PAN1
82-> PAN2
83-> PAN3
84-> PAN4
85-> PAN5
86-> PAN6
87-> PAN7
88-> PAN8
100-> OSC1MIX
101-> OSC2MIX
102-> NOISEMIX
103-> FLT_KF
104-> MULTIMODE
105-> BANDPASS
106-> FOURPOLE
107-> ENVELOPE_AMT
108-> ENVDER
109-> FILTERDER
110-> PORTADER
113-> PW_ENV
114-> PW_ENV_BOTH
115-> ENV_PITCH_BOTH
117-> PW_OSC2_OFS
118-> BENDRANGE
118-> LEVEL_DIF
119-> SELF_OSC_PUSH
120-> VAMPENV
121-> ASPLAYEDALLOCATION
122-> PORTAMENTO
123-> UDET

Post

July 1st build freezes the playhead in Reaper while transport is running and OB-Xd GUI showing, while automating any single OB-Xd parameter.


CC 120 and CC 123 probably shouldn't be used for MIDI mapping of parameters, as these are all-sound-off and all-notes-off (should also probably just respond to them properly as expected).

Post

EvilDragon wrote: Tue Jul 14, 2020 9:03 pm July 1st build freezes the playhead in Reaper while transport is running and OB-Xd GUI showing, while automating any single OB-Xd parameter.
Can't reproduce that. Do you have more details about it and how to exactly reproduce it? (DAW, OS, plugin type, steps).
CC 120 and CC 123 probably shouldn't be used for MIDI mapping of parameters, as these are all-sound-off and all-notes-off (should also probably just respond to them properly as expected).
Yeah, will change those to another values.

Post

Remapped values:

Code: Select all

15->  VOICE_COUNT
16->  UNISON
17->  OCTAVE
18->  FILTER_WARM
19->  LFOFREQ
20->  VAMPENV
21->  ASPLAYEDALLOCATION
22->  LFO1AMT
23->  PORTAMENTO
24->  UDET
25->  LFO2AMT
33->  TUNE
34->  BENDOSC2
35->  LEGATOMODE
36->  BENDLFORATE
36->  LDEC
37->  LSUS
37->  VFLTENV
38->  FATK
39->  FDEC
40->  FSUS
41->  FREL
42->  RESONANCE
43->  OSC2_DET
44->  LFOSINWAVE
45->  LFOSQUAREWAVE
46->  LFOSHWAVE
47->  LFOOSC1
48->  LFOOSC2
49->  LFOFILTER
50->  LFOPW1
51->  LFOPW2
52->  OSC2HS
53->  XMOD
54->  OSC1P
55->  OSC2P
56->  OSCQuantize
57->  OSC1Saw
58->  OSC1Pul
59->  OSC2Saw
60->  OSC2Pul
61->  PW
62->  BRIGHTNESS
63->  ENVPITCH
71->  VOLUME
72->  LREL
73->  LATK
74->  CUTOFF
81->  PAN1
82->  PAN2
83->  PAN3
84->  PAN4
85->  PAN5
86->  PAN6
87->  PAN7
88->  PAN8
100->  OSC1MIX
101->  OSC2MIX
102->  NOISEMIX
103->  FLT_KF
104->  MULTIMODE
105->  BANDPASS
106->  FOURPOLE
107->  ENVELOPE_AMT
108->  ENVDER
109->  FILTERDER
110->  PORTADER
113->  PW_ENV
114->  PW_ENV_BOTH
115->  ENV_PITCH_BOTH
117->  PW_OSC2_OFS
118->  BENDRANGE
118->  LEVEL_DIF
119->  SELF_OSC_PUSH

Post

discoDSP wrote: Wed Jul 15, 2020 7:17 am
EvilDragon wrote: Tue Jul 14, 2020 9:03 pm July 1st build freezes the playhead in Reaper while transport is running and OB-Xd GUI showing, while automating any single OB-Xd parameter.
Can't reproduce that. Do you have more details about it and how to exactly reproduce it? (DAW, OS, plugin type, steps).
I mentioned Reaper. Latest version, W10. Open OB-Xd on a track, twiddle the filter cutoff and press Param button in Reaper's plugin header, show track envelope for last touched parameter. Draw some automation then hit play to start from beginning, then play some notes while transport is running. Play cursor doesn't move until the transport passes the last automation point entered. Plugin GUI needs to be displayed, it doesn't happen if its closed.

This doesn't happen with any other plugin.

Post

Can't reproduce the described behaviour using build from dev branch commit. Does it happen with VST2, VST3 or both?

Post

I was trying VST2. I tested what was on the nightly page. Please see this GIF for yourself:

Image

VST3 is slightly better but the playhead stutters like crazy, rather than not showing at all. GIF:

Image



It looks as if the plugin GUI is stealing UI refreshes from the host somehow.

Post

VST3:

Image

:shrug:

Post

Ha, dunno. I'm just reporting it.

I can confirm the same issue in Studio One.

Post

Very strange... will investigate. Thanks for the reports.

Post

Maybe graphics hardware related?

Just guessing here.

Post

It would be great if anyone else could confirm the same issue.

Post Reply

Return to “Instruments”