Is there an easier way to reach common settings for SurgeXT?

Hi,

Would it be possible to put the “A Common” section for SurgeXT at the top of the list?

If I want to adjust the volume or pitch bend, I have to scroll through 124 (!) items in the list before reaching the “Common” section.

It would be very useful if I could skip directly to the end of the list by pressing the UP button while on the first item. Then I only have to scroll through 67 items, almost half the number :wink:

A nested list would be ideal, of course, but I’m afraid that would be a major change.

Kind regards,

Hans.

We would need to edit the TTL files to get a better organization of parameters, but Surge’s TTL is huge and the amount of work is also huge. Perhaps it could be a work for the IA. Some time ago i did some tests with chat GPT and it can manage TTL files, so with some wise guidance, the work could be done, or at less we could get an improved wersion. Of course, if someone try it, please, keep a clean prompt that we can use later for updating the generated TTL when ot changes.

Regards,

1 Like

Don’t spend too much time on it. I can save the desired settings in a snapshot so I’ll be fine. I was just wondering if I overlooked something.

Kind regards,

Hans.

I’ve improved a little bit the group ordering. Please, update and test.

Regards,

1 Like

Better, but no cigar.

You have put the B Common settings on top, but the A Commons are still below the LFO settings. Could these go on top please? I don’t know what the B Commons do, but the A Commons set the volume etc.

Kind regards,

Hans.

What about this group ordering?




Update and try, please.

Regards,

2 Likes

Your order would be great. Mine is a little different, but workable:

The order seems to change every time I reboot. Strange…

Thanks so far!

Kind regards,

Hans.

What version are you running? Perhaps you are not running Oram staging or vangelis?
Please, send a screenshot of your webconf dashboard.

You can’t get updates if using a stable tag version. Please, move to Oram Staging or Vangelis.

Regards,

1 Like

I can confirm that the order of the parameter groups changed on every new instance (prior to this update of course).

I think, B Commons are the same as A Commons, but for the Scene B.

1 Like

Just moved to Vangelis, updated one moment ago.

This is even worse than Stable:

(Had to take the camera, Vangelis VNC does not accept opensynth or zynthian as password)

This is really strange. I will take a deeper look in a few days.

until them, could some other user check the issue?

Regards

1 Like

Take your time, it’s not urgent (more cosmetic than a real problem).

Kind regards,

Hans.

This thread is relevant to a thought I had, which is, “performance mode” for chain settings with “favorite” controls selected by the user.

As it stands, the LV2 controls are organized in a pre-determined way, which can be tweaked but will always be the same for everyone (as far as I understand). You can also do MIDI Learn to assign controllers of course.

But if one could assemble all of one’s favorite controls (perhaps from different chains / plugins) on a series of easily accessible, adjacent pages, then it doesn’t matter if the original organization of controls is a long scrollable list. You would just pick the ones that are relevant to that particular gig, or track.