Centralised Display

Tom7777 · 4 May 2006

It's quite simple, what you need to do is make mouse over green events for everything you want to appear on the display then you multiply by 1,2,3,4,5 ect use the select modules and hook this up to a selector with text values for each thing, as your 0 value you just leave it empty and if you want to display the control values you just use another selector with all the values input but have the original selectors green int data to choose which is which. Hope this helps 🙂

AngularMomentum · 4 May 2006

Thanks for the info, I will see how far I get with this, keep you posted! 😀

Tom7777 · 4 May 2006

😀

malc · 4 May 2006

Note that adding mouse over functionality will also require you to enable mouse move messages on the MGUIs of knobs etc. (these are disabled by default for effieciency).

For the display part ideally we'd have some components to help save you from having to link all the data back to a central point which is what you'll have to do at the moment (sorry).

Tom7777 · 4 May 2006

Well you could use wireless links for, they would make things a lot simpler its not that complex really though. 🙂

malc · 4 May 2006

Wireless links only go down the module hierarchy. I was imagining that you'd have some module at a fairly high-level (like the Preset Manager) that handles the display aspects. Data is then passed up to this module.

Have you thought of some cunning way round this?

Tom7777 · 4 May 2006

Wireless links only go down the module hierarchy

Well yeah would have the knobs then there outputs connected to wireless links, the selectors, select modules and the wireless inputs and text labels would all go into one main module to keep things organized. You would use wireless links for both the mouse over status and the values.

Edit - You will also need to redraw the area so just connect the int data to the redraw trigger.

angstrom · 4 May 2006

yes, but I think what malc is saying is ... how do you get up out of the standard heirachy?

synth/filtersection/FreqKnob/wirelessOutput the wireless will only get up as far as the 'Freqknob' level (using moduleWirelessOutput) and no further. It will then be forced to go down

with the display unit at synth/display... you have a lot of upward transmitting of values to accomplish in a standard synth

Tom7777 · 4 May 2006

Well what i do is create inputs for any float/int values if they use controls and put the knobs and sliders on the top layer and use a GUI module with a wireless link so it makes everything visible 🙂 I guess thats not the most organized way but it allows you to use wireless links that way 😀

AngularMomentum · 4 May 2006

The thing is I want to have this in the AddTable Synth. I want to have the parameter data appear in the preset manager display. I would sure love to go wireless on this as the latest synth I am working on in SE got 100's of wires just for that. I read other post that have troubles with the wireless hierarchy, that is why I asked in the first place. Come to think of it, I love wireless, in the Analog Warfare with major routing capabilities it might come close to a 10.000 wires , no horsecrap!

stefan · 4 May 2006

AngularMomentum wrote: The thing is I want to have this in the AddTable Synth. I want to have the parameter data appear in the preset manager display. I would sure love to go wireless on this as the latest synth I am working on in SE got 100's of wires just for that. I read other post that have troubles with the wireless hierarchy, that is why I asked in the first place. Come to think of it, I love wireless, in the Analog Warfare with major routing capabilities it might come close to a 10.000 wires , no horsecrap!

I often use busses when I want to reduce connections but don't want to or can't use wireless links.

oddson · 4 May 2006

AngularMomentum wrote: ...I want to have this in the AddTable Synth. I want to have the parameter data appear in the preset manager display...

You want all the parameter data to display for the end user? There are about a hundred parameters. How would you display it?

Assuming I'm not missing the point too badly... I would think the preset components allready have to have access to this data so it's already assembled. The Preset Text component, for example, clearly has all this available to it. So perhaps the devs could make it available without exporting to a text file.

I think a clearer description of what you want to do with it might help (or maybe I'm just a little dense this morning 😝 )

sambean · 4 May 2006

Here's a quick example of how it's possible to route it using busses/wireless and flow modules..

http://magalov.myweb.hinet.net/toolkit/ ... isplay.osm

You have to type it the preset names yourself, but it may be possible to hook this up to the preset names within the module in a similar fashion

Sam

malc · 4 May 2006

@oddson: I think AM is probaly just wanting to display the current control's data, either the knob/slider you are moving or the one that your mouse is over - like Vanguard and others. Is that right AM?

If wireless links could go up then it would make this very easy and neat. This is possible of course but at this stage in the game it's not something I'd contemplate attempting for fear of introducing a whole load of new bugs.

A less risky aproach would be to have a special system just for achieving this goal. So you could have a component that you put in your knobs/sliders that you send a formatted string to say and a trigger to say when you want to show it. Then a component that sits above that at PM level say that receives updates from the other components and has a String output and a trigger to say that an update is required. Haven't thought it through much yet but you get the idea. It acts like a special upwards wireless link I guess but not quite the same.

AngularMomentum · 4 May 2006

I made Analog Warfare in SE, I would like to recreate it in SM. I fiddled around a bit with the busses and routing and it's so much better then what I had to cope with in SE. Nothing bad said about SE, it proved itself to me in countless ways.

oddson · 4 May 2006

...I think AM is probaly just wanting to display the current control's data, either the knob/slider you are moving or the one that your mouse is over - like Vanguard and others. Is that right AM?

Why would you want to display the current control in the preset manager instead at or near the control itself? 😕

One solution is to extract all controls out of the signal processing and feed them downward from the top of the schematic via wireless.

If they are all together at or near the top of the hierarchy it would be easier to collect the data from the specific control you want to display and feed it up one or two levels instead of up from the depths.

Didn't some newbie suggest somthing along these lines as a general design principal here once? 😉

AngularMomentum · 4 May 2006

Would want it because it would save a lot of GUI space having the parameter display in one place and the best place for this would be in the preset manager window IMHO (I even saved space for it). Also because then there is no need for any parameter popup messages. Off course I won't do anything without your consent, so just tell me if you think it is a good idea to have it in the addtable.

oddson · 4 May 2006

I won't do anything without your consent

No... the look and feel are all yours... I just didn't get the 'why' behind it.

If it's for display space, you can insert a display label of a control that would hover over the control itself while being changed and disappear on release.

malc · 4 May 2006

oddson wrote: Why would you want to display the current control in the preset manager instead at or near the control itself?

I agree that it is much better in general to have the value nearby the control and your suggestion of a popup is a nice one (I think someone made one of these before). Everything would be localised then which makes the schematic neater.

At the end of the day it's up to you how you want your synth to work. I've seen the idea of displaying parameters on a single display used before and it works well enough.

As 'Our Graham' would say, "The decision, is yours!" 🙂

AngularMomentum · 4 May 2006

I sure understand that it is better to have things localised, for instance less eye movements... I just like to have the GUI as small as possible without having to switch panels or having popups on the AddTable GUI. There are other reasons to, one of them getting familiar quick with the GUI's parameters names...another that all of the hardware synths I own have everything centralized, like my JX-305, I like GUI's come close to having hardware.

Off course when one has build up a feel for a synth, who needs parameters anyway? 🙂