From the original SynthMaker forum (2004–2014), with its members’ names and dates.
SBMastering ·
Hi everyone! Had to take a short break from Synthmaker, now I'm back to my projects. Still a beginner, but I'm learning a ton.
Here is what I envision --
Parts:
- There is a slider control
- There is a set of 15 buttons, each in a default "off" position
- There is a "Clear" button at the end of the row of 15 buttons
Functionality:
- When you click a button, it goes into the "on" position, and stores the current value of the slider
- If you click a button that is already "on", the slider will go to the stored position
- The buttons store their values until the "Clear" button is pressed, which resets the set of buttons to their default position
These are basically memory buttons for a slider (or a knob or other similar control). I've seen something like this a few times. I am wondering if anyone has an idea for implementing this? I'm still a beginner and this one is a toughy.
I have a few problems like this, which I am going to post in separate threads to keep things organized and make them easily searchable.
Dell ·
I may be better explain what you are designing and, what feature you are trying to impliment with your buttons and sliders.
SBMastering ·
Ok, no worries.
In mastering, comparing things at the same volume level is essential. I am working on something to help me with that.
The idea is fairly simple -- there is a long gain control slider that I use on a track to match gains. I want to be able to store slider positions into buttons across the bottom. Click a button and the current gain level is stored. Click it again and the slider returns to that position. Hit the clear button and all the stored positions are cleared.
It's kind of like Samplitude Pro X's Object Snapshots: http://www.youtube.com/watch?v=hOHVvLBlIpI
This is part of a tool I made that has many features, this is just one of the features.
Dell ·
That video did not offer much information on what you are trying to do.
If you want to save and recall settings, that is what the preset manager is for.
attic ·
Take a look at the 1 through 50 buttons on the Cassette2.osm at the link below. I am pretty sure that you could use that as an example to get what you want. If that doesn't work let me know and I may have something buried somewhere that may also work. The buttons store loop position...... fool with it you will see. 😉
Cassette Loop Points
SBMastering ·
That cassette OSM is close -- it wasn't exactly what I was looking for though.
When the button is pressed, thus saving my slider's current position in it, I want the button to display a graphic that signifies the button is pressed "down". Otherwise, I want it to display the graphic that signifies a button is "up".
Basically -- click a button, it changes to a down-state graphic and stores the current position of the slider. Click it again and it sets the slider to the saved position. Press clear and all buttons go into the up-state and are ready to save slider positions again.
The cassette example doesnt go into a down state, or at least I couldn't get it to while playing with it.
attic ·
Maybe this Osm will help. 😉
trogluddite ·
Would something like...
Right Click (press CTRL+number key?) - store a 'Preset'
Left Click (press number key alone?) - send 'Preset' to slider
...not be more simple/useful?
Couple of reasons why I suggest that. 1) Project Build - this system would be much simpler logic to program, as the button behaviour is consistent regardless of the current state. 2) Usage - with your suggested setup, once you have assigned all of the buttons, you would have to clear them all and start over just to make a small tweak to one of them. You could maybe make do with less buttons if you use the simpler alternative.
Of course, this is just a polite suggestion, maybe you have good reason for wanting your proposed method - it certainly can be done, but it will require many more components, and you will need to be very careful with SM's trigger system to avoid unexpected behaviour. I can offer some help with this, as I've done a lot of sequential logic in SM - but I'd advise giving the simpler option serious consideration before getting stuck in.
In either case, Attic's slider will get you at least some of the way, as you are always going to need a slider that can accept incoming 'Preset' values - a glaring omission on the stock controls!!
SBMastering ·
Trogluddite, I think your idea is perfect, as long as it would be possible to have the graphic change when it is pressed down. I'm not sure how to program that though. Capturing mouse actions in a specific area is still fuzzy to me. Still quite the beginner here -- but I can tell you, I will be using Synthmaker for many years. Also, as soon as I can figure out a way to really contribute something big, I will.
trogluddite ·
SBMastering wrote: Capturing mouse actions in a specific area is still fuzzy to me
The simplest way at first is to keep each control isolated within it's own module - taking the area of the module view then gives you a simple mouse area that always covers the panel for that module, and follows any re-sizing of the control that you do...
...you can then position a bunch of these small modules on your panel any way you like. This is much simpler than trying to make a single module with lots of separate mouse areas - though that can be done too, once you get the hang of manipulating areas (using 'Area to Float' and 'Float to Area' primitives to define the boundaries).
Here's a rough draft of the button idea I set out previously.
The small button modules use R-Click to store, and L-Click to send - with the stored value shown on the button when it is in use. The modules are made so that you can chain as many of them together as you need. I also tried to make it as 'modular' as possible, so that it will be simple to modify with prettier graphics etc.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker