Make a widget react to next song part, but I'm not software literate

I tried for 3 weeks to not write this post and figure it out. I’m just not good at this.

I’ve been trying, and failing, to write a script to do something that the SundayKeys app can do … if I wanted to pay $12+ a month forever. I don’t write code, don’t really understand what I’m looking at in a script/terminal, and despite trying, still don’t understand how to make scripts work unless I’m copying someone else’s work. Yes, I’ve posted about this feature before, which left me thinking about how to write a script for it until/unless it drops as a feature.

Here’s what I want to happen… I’m sure there’s a way:

When I tap the next song part, I want the widget value saved for that song part to move, over a set period of time, to the next widget value.

For example, I have a filter knob. In the intro, I save it to the intro song part at 10%. In the verse, I save it to the verse at 30%. In the Chorus, it opens at 80%… etc. That movement can take 200ms.

Right now, I can easily store the values (song mode is awesome). But… they jump instantly. It’s REALLY annoying, and depending on the synth and fx chain can create audible, distracting artifacts. I want the knob to smoothly transition between the widget values I’ve stored to the song part.

For starters… 1) In which editor do I put this code so that a rackspace widget can reference a song part? I’ve discovered that putting scripts into the rackspace editor will have different outcomes than the global rackspace.

  1. By trial and error, it looks like I need some combination of song part call backs, ramp functions, value updates, and the timertick to make this work? The various AI apps all failed me, even using them to check against each other. It never compiled fully. I can post what they told me if anyone’s curious, but inevitably they’re incorrect.

  2. If this has to go in the global rack to control rackspace widgets saved in the song, do I need 6 copies of the code for 6 widgets, or does declaring the widgets as variables and giving them handles mean I only need to do that once?

Please be kind. I’m totally lost to this stuff, and am normally a happy as a player and audio tech. My programming experience is zero.

The scriptlet contained in this gig file is a good place to start.
I would take some time using it for simple tasks and work through how it is doing what it is doing before proceeding onto your final goals.

Since you don’t have any programming experience, patience and small steps are going to be your best ally in achieving what you’re looking to do. Simplify small tasks down to the bare minimum of variables, and then once you have a grasp on that, you can apply them to your larger project.

Thank you for the encouragement. This auto move script was actually part of my impetus to try and figure this out.

I’m sure it’s possible. Dedicating brain power and time are the usual obstacles.

Here’s an example I made of the type of thing you’re looking for. :slight_smile:

1 Like