T.U.S. synth plugins based on DSP emulators (56300 and others)

Software
145

Looks like they’re all in /root/.local/share/The Usual Suspects/

2 Likes
146

Fine then! :slight_smile:

147

Lazily oodling on my Zynthian during the Christmas break after not having much time before Christmas, and noticed one thing that I haven’t noticed before with Osirus in the Zynthian UI: There are a bunch of parameter groups with names like Osc1 Settings, Amp Env, etc, which correspond to parameter group A in the Virus, i.e. those parameters which can be reached using MIDI CC; I thought these were the only ones that could be accessed using the Zynthian UI, but there are also a whopping 48 parameter groups called CH1#1, CH1#2 etc which seemingly contain all the parameters. Maybe this is something that arrived during the latest update?

The thing though is that the parameters are in a seemingly haphazard order. They don’t look to be in numerical order considering the parameter number in the respective parameter group as described in the Virus manual appendix, nor the numerical order of the ‘plug’ id in the dsp.ttl file, nor the actual order of the parameters in that file.

So what actually governs the order of parameters in the “CH1#…” parameter pages, and following from that, is it possible to rearrange and name them in a more overviewable order? (I’m guessing the ‘CH1’ comes from the fact that it’s the first part slot that is populated in the emulator, as I have only one Osirus chain in my setup at the moment.)

1 Like
148

Hi @ricard

Perhaps the same issue as this?

@jofemodo suggest to edit the TTL file. Perhaps that also works for Osirus.

Kind regards,
Hans.

149

Yeah, that was my thought as well, but I can’t figure out what actually governs the order of how the parameters appears in the UI, as it doesn’t seem to be the order of the parameters in the .ttl file which is what I’d have expected, so I think there’s something deeper going on.

150

Hi @ricard! Since your question made pop a memory in my mind, about a topic I remember we were chatting about in this forum a while ago, I’ve been able to trace back the related discussion, about arranging TTL parameters of DSP56300 emulators:

Don’t know if references, there or in the whole thread, may turn out to be useful.

Concerning this:

I seem to remember that selective choices had to be made, regarding what most useful parameters (of the enormous total quantity available) were better to be exposed and labeled on the Zynthian UI.

Cheers, and a happy new year!

151

Thanks @Aethermind, that’s the kind of memory-jogging that I was hoping to trigger from my query!

The particular post you refer to concerns the CC parameters, and they seem to have been grouped quite sensibly as it is now, so likely the work mentioned in the post has been carried out by someone already; the list of parameters is not even in that file anymore so I’d have to dig around in the git repo to see how it works. The thread seems to contain some useful information further on though regarding the “plug:” sections in the .ttl file.

I think the question of which parameters to expose comes down to the fact that only some Virus parameters are exposed via CC. The Virus range slightly oddly uses Polyphonic Aftertouch to expose the rest (the instrument does not support poly aftertouch per se, so instead they use the note number for a ‘control’ number, and the pressure value as the parameter value), for which I suppose support could be added, but as there already seems to be a method to access them that would be a roundabout way.

EDIT: The thread mentions an incompatibility between the naming of the ‘plug’ parameters, as the names start with ‘_’, which confuses lilv (the underlying library for jalv). It also mentions that changing the names would be a major undertaking (because they’re tied in with the plugin and the JUCE framework). Apparently this has been resolved in some way, because the parameter names still start with ‘_’ but they now do show up the GUI. I’ll have to do some more digging…

152

Hi @all!

I’ve updated the TUS plugins in Vangelis, fresh compiled with LV2 parameter integration in all of them, including Osirus and OsTIrus.

We need to customize the TTLs, sorting and grouping the parameters. The TTLs are super-long because they include all parameters x 16 channels, so i will write a script to do ease the task. Give me some days.

We still have several issues / limitations with TUS plugins:

  • We don’t have parameter feedback after loading a preset. This is a serious limitation that we need to solve. I’ve checked and it seems that the plugins don’t use the normal LV2 mechanism for updating the GUI when loading a preset, so zynthian UI don’t get the new parameter values. In the other hand, if you move a knob in the GUI, this work OK and zynthian UI gets updated.
    Question: Should we pre-learn the LV2 parameters to the “official” CC numbers?

  • We don’t have presets for Vavra, Xenia and JE8086. This would take a little bit of work, but the way is paved, more or less.

  • Finally, when the 2 issues above are solved, we would consider the multi-timbral implementation, at less for Osirus and OsTIrus.

The best,

3 Likes
154