New beta of OSC/PAR2 Available

OSC/PAR General Discussion
1

A full rewrite of OSC/PAR is now available for testing as OSC/PAR2. Your existing keys for OSC/PAR will work as-is, no need for a new purchase. Quite a few new output modes (LFO, Envolope etc) and features available.

Try it out and let us know if you have any issues and feedback. Download links here:

Windows

macOS

2 Likes
2

Is there documentation for the new features?

3

ahaha coming shortly, for now youre just gunna have to fuck with it. :wink:

2 Likes
4

Fucked around with it and here’s some early notes:

  • reordering things doesn’t change which VST parameter is assigned to each output module
  • sometimes multiple VST parameters will adjust the same module
    • Not easily replicable
  • Par2 will forget all message strings each time you close the VST window

Everything else seems to behave as expected.

5

Also the VST parameter glitches will crash Live if messed around ‘in the wrong way’

7

After messing around with it for a little while, there are a lot of things about this that intrigued me about it. Although, some things are still confusing. Maybe to some, it would be intuitive, but I’ve only played around with OSC data so much.

Envelope - Very cool that we can do this now, but I wish there were some way to trigger this with MIDI notes.

Had this weird crash in FL Studio trying to use the Param Module, this is no big deal to be because I have both Ableton and FL Studio, although still concerning.

Many of the other features I really like. In the future I’d love for you guys to develop an audio follower! Been looking for something like this for ages, but most audio followers I know of kinda suck.

8

yeah, most audio followers do suck… but i think with a selection of modes it could not suck, like RMS vs Peak w/ smoothing option (some algo).. but i think also for “audio env foloow” the way to go is to use an envelope and trigger it with a threshold from the audio (the way compressors / gates use thresholds) then you can tune it a bit better for the decay / sus / release.

ill play around with it, and make those other fixes this week.

9

you “can” trigger an env with a midi note…. youll have to map the param. but…. the parameter problem is, VST3 params cant really be created “dynamically” like we do when adding / removing “modules” … so ill have to find a workaround… as in maybe push 100 params, and only publish them when a module is loaded to reserve the param / name it. when you load a VST, traditionally, all params are baked in, so to speak. our are not, so ill have to find a kinda workaround.

1 Like
10

Very promising features here! I especially like the sequencer.

Is it possible to get more precision from the sent parameters? When automating a parameter using a slow ramp the stepping is noticeable.

Screenshot 2026-02-02 at 14.50.18
Screenshot 2026-02-02 at 14.50.182666×1290 199 KB

12

Yeah! I noticed this too. I was using OSC/PAR to convert to OSC data, then convert back to Midi, to control parameters In vst “PhasePlant”. I ended up linking the volume of a pure sin wave, to this value through a sideband, then sending it to an Audio Follower to smooth this value for PhasePlant with the attack and release.

Maybe the efficient way to implement this for OSC/PAR is a smoothing fader near the sequencer? I’m thinking of Shaperbox 3 vst as a reference.

13

Taking notes as I come across stuff…

  • First few attempts opening on my M1 macbook, Ableton crashed
    • I realized after messing around more that the crashes happened while trying to make changes when the session was playing. Later on I was safely making changes while session was playing so idk what the deal is.
  • Unable to change the OSC Space, it just crashes the DAW.
  • Transport controls flood the port, even when not playing the session. Biggest problem so far for me in terms of practically using it, but I’m assuming that’s not intentional.
  • Sequence is awesome
  • The setup for Notes makes sense to me
  • Is the idea behind Msg that you can kinda piggyback off assigned params to send cues?
  • LFO has the same issue as Transport controls at rest, the port is flooded with 0 values
    • Works as intended, I imagine, when session is playing. very useful
  • The port “banks” is a good addition, though I was slow in realizing I kept trying to “enable” ports where the transport controls are managed. Then I looked left lol

I like the add/remove UX. Idk if notes makes sense as something to add / remove like the others as you’re limited to adding one, so I sorta think of it the same as transport, you can enable or disable it, and that warrants a slightly different treatment (notes and transport could both be permanent rows with a toggle???). I like the value sliders for Sequence and LFO. I didn’t see how to change locking values to INT or FLOAT, so I hope that is kept from the first plugin.

Naming conventions and whether or not they’re kept the same as before (to be drag n drop with receiving tech of V1) is something to consider… so, transport controls are now nested in /Transport/, I think?, and note names looked a little different as well while also being nested under their own space.

1 Like