OB-Xtreme Version 2 - FULL VERSION RELEASED!

[Echoes in the Attic]

I recon this could be an issue for some as this make little sense when you read the parameter value transmitted to the DAW or see it displayed on your external controller, It would rather be in semitones (like 12 = +1OCT)
So why is this like that?
Simply because some parameters are legacy from the original OB-Xtreme version 1 I made in 2014.
In order to not break presets and banks compatibility I could not change the internal parameter range for the oldest ones (OSC tuning are) made at a time when I didn't care much about such details.

Not breaking backward compatibility makes sense, though for a V2, not always unexpected. But yeah most synths would have it in semi-tones, not decimal divisions of octaves (since they are divided by 12 so it doesn't make sense). Keep in mind I've already bought it, it might matter more to others at some point. Just trying to be constructive.

However I can do one thing: displaying the tuning in semitones when you grab an OSC tuning knob, the value would appear above the knob and would also display just by clicking without moving just to see where it's at.
For OSC 2 it will display a decimal point only when set to not scaled.
Would you like something like this?
it wouldn't break anything and could be added in an update.

I think it would be a good idea. You might also want the visual notches of the knob turning to align with semi-tone changes. As mentioned somewhere else, you can currently change the value and sound by dragging the mouse, but without the knob having moved yet, and also the knob can move without changing the sound. It's generally good to have the visual feedback line up with sonic changes, for example a visual step for every semi-tone change.

If you are really drawing precise automation at the semitone level you shouldn't be bothered by doing one little division to know what to enter in the automation lane.. wants to add a little staircase shift in semitones like +3 +7 +9... enter 3/12, 7/12 and 9/12..

Yep absolutely doable, might not be the best workflow-wise if you want to draw but not a big deal.

Last but not least in v2.0.1 you can ALT+Click on the DETUNE knob to reset it to perfect 0

I think a reset is very important, so this is good. Especially because there isn't an accurate visual representation of 0, so if both detune's are off 0, you might not otherwise know when you're back to 0.

[BONES]

I'll do it for you:

I really don't like the tune units BEING FROM -1.0000 TO 3.00000 with all the decimals in between even though it appears to jump in semi-tones. The values exposed to the DAW should be what they actually are (ie. semi- tones) so you can automate properly and also see real values on controller displays.

It's not the number of decimals that matters, it is the fact that it's reported as a continuous range between octaves in terms of decimals, but it isn't continuous, it jumps in semi-tones. I didn't say the problem is they use too many decimals anywhere there, I said that it uses a decimal range between integers which isn't the unit of the parameter. I'm pretty sure you aren't this dumb, so stop with the straw man crap. It isn't a big deal, but why pretend like someone is making an argument they aren't? The developer offered an explanation and a UI addition that might help people. You aren't helping.

Wait on, I read that as -1 semitone to +3 semitones and see no problem (because I have no idea which parameter you're talking about). Were you trying to say that the range is actually something else? Because that's not at all clear from what you've written, it just looks like you're complaining about decimal places. OTOH, if you're complaining that it might report a value of 1.43385 but is actually just 1 semitone, then I don't see a problem with that, either, as its such a common thing in lots of applications.

[Echoes in the Attic]

I'll do it for you:

I really don't like the tune units BEING FROM -1.0000 TO 3.00000 with all the decimals in between even though it appears to jump in semi-tones. The values exposed to the DAW should be what they actually are (ie. semi- tones) so you can automate properly and also see real values on controller displays.

It's not the number of decimals that matters, it is the fact that it's reported as a continuous range between octaves in terms of decimals, but it isn't continuous, it jumps in semi-tones. I didn't say the problem is they use too many decimals anywhere there, I said that it uses a decimal range between integers which isn't the unit of the parameter. I'm pretty sure you aren't this dumb, so stop with the straw man crap. It isn't a big deal, but why pretend like someone is making an argument they aren't? The developer offered an explanation and a UI addition that might help people. You aren't helping.

Wait on, I read that as -1 semitone to +3 semitones and see no problem (because I have no idea which parameter you're talking about). Were you trying to say that the range is actually something else? Because that's not at all clear from what you've written, it just looks like you're complaining about decimal places. OTOH, if you're complaining that it might report a value of 1.43385 but is actually just 1 semitone, then I don't see a problem with that, either, as its such a common thing in lots of applications.

Yes it’s the values in between octaves. 12 semi-tones are split into base 10 decimals meaning you get values that aren’t apparent what semi-tone offset it actually is. As you say it could be something like 1.43385 being 17 semi tones offset (I didn’t do the math). Always better if the units reported are true to the parameter. Another example aside from automation is using a controller like Ableton push where you see the value on screen with an endless encoder. It’s nice to know where you are putting that value if you already know the value you want. But yes you can do by ear, but if these things are easy fixes they are a nice quality improvement, not quite as nit picky as simply too many decimals! Anyways let’s not derail this anymore.

I like the quick card offset controls. Although obsession is cool, allowing you to adjust the offset if every parameter per voice, I would lean towards just wanting to quickly randomize (to greater or lesser extent) the difference between voices, as is possible with OBXtreme.

[BONES]

I still don't see any problem but at least you're not being as pedantic as I thought you were. To me that sor tof thing is more an aesthetic thing than a real issue.

[briefcasemanx]

Does this count as the official release? If there's not gonna be a separate thread for the full release, maybe this thread should have it's title changed? There are probably people ignoring because of the huge "PRE-RELEASE" text.

Although I hate going into a thread about a plugin and having to deal with pages of pre-release stuff

[BONES]

Good idea, all taken care of. Thanks.

[Echoes in the Attic]

Can anyone tell me how the patch Duo Dudes is changing the octave every other voice? I've stripped the patch back to basics trying to find what is modulating that and I've run out of controls that I can see, but it's still doing it. Thanks!

[Vortifex]

Edited

[MTorn]

The octave shift is actually pretty straightforward:

On the CARDS screen, at the bottom of each card there is a "pitch tuning" control (a drop-down text box). Every other voice card is set to one octave up. You have to select cards 5-8 on the next screen - a button in the lower right side (really seems like he should have squeezed all eight cards onto one screen, doesn't it?). Since the voices cycle through the cards for each new note, you get the every-other note octave shift.

This was a new feature introduced in the final 2.0 version. I suspect that the main reason to implement a note shift on a per-card basis was to allow for chords and octaves in unison mode.

If you haven't tried it yet, try using portamento with unison, and set the PORT slider high in the Macro Voltage Offsets area. Lovely bee-swarm glide!

[Vortifex]

Edited

[Echoes in the Attic]

The octave shift is actually pretty straightforward:

On the CARDS screen, at the bottom of each card there is a "pitch tuning" control (a drop-down text box). Every other voice card is set to one octave up. You have to select cards 5-8 on the next screen - a button in the lower right side (really seems like he should have squeezed all eight cards onto one screen, doesn't it?). Since the voices cycle through the cards for each new note, you get the every-other note octave shift.

This was a new feature introduced in the final 2.0 version. I suspect that the main reason to implement a note shift on a per-card basis was to allow for chords and octaves in unison mode.

If you haven't tried it yet, try using portamento with unison, and set the PORT slider high in the Macro Voltage Offsets area. Lovely bee-swarm glide!

Not sure how I didn't see that, thanks! I've even adjusted those before...

[Echoes in the Attic]

Does anyone else notice the sound of the "Base for Synth" preset change after anywhere from a few seconds to maybe half a minute or so? After playing notes for a bit, the volume lowers and attack kind of disappears. wondering why. Changing the preset and going back plays the changed sound. But if you save that as a daw preset and reload it's a different sound, much more punchy and louder.

Edit: Actually sometimes changing to another preset and going back puts it back the louder version with more attack.

[Echoes in the Attic]

Does anyone else notice the sound of the "Base for Synth" preset change after anywhere from a few seconds to maybe half a minute or so? After playing notes for a bit, the volume lowers and attack kind of disappears. wondering why. Changing the preset and going back plays the changed sound. But if you save that as a daw preset and reload it's a different sound, much more punchy and louder.

Edit: Actually sometimes changing to another preset and going back puts it back the louder version with more attack.

Nobody else gets this? Has me a bit concerned about the sound engine or if there’s a bug. Will report it.

[waiting man]

Does anyone else notice the sound of the "Base for Synth" preset change after anywhere from a few seconds to maybe half a minute or so? After playing notes for a bit, the volume lowers and attack kind of disappears. wondering why. Changing the preset and going back plays the changed sound. But if you save that as a daw preset and reload it's a different sound, much more punchy and louder.

Edit: Actually sometimes changing to another preset and going back puts it back the louder version with more attack.

Nobody else gets this? Has me a bit concerned about the sound engine or if there’s a bug. Will report it.

You definitely should. I admit I'm not touching it much.
The release, though gorgeous sounding as usual for all AJ projects, feels a bit rushed.

[Vortifex]

Edited