Re: Meeting minutes 2017-01-20

[email protected]
Newsgroups gmane.comp.audio.supercollider.devel
Message-ID <[email protected]>
> On 23 Jan 2018, at 05:41, nathan-PB1wun9k+p9Wk0Htik3J/[email protected] wrote:
> 
> On 2018-01-22 16:00, [email protected] wrote:
>> Potentially a lot of IPC traffic.
>> Would this filter out OSC traffic for level meters, scope and
>> freqscope? If not, you open up any kind of meter, and the OSC-in light
>> goes on continuously, and becomes useless for troubleshooting user
>> traffic. (Or, different colors for system messages?)
> 
> definitely. i haven't really though it through myself. i got the idea from the original proposal here: https://github.com/supercollider/supercollider/issues/828

I agree with James that it’s problematic. If you’ve got something like a controller that streams in data, it would just be on all the time, trigger redraws, and not give you much info. Miguel’s proposal suggests a debugging intent. Given this, I’d suggest instead something like a menu item that adds some sort of feedback about OSC, so more convenient and discoverable than OSCFunc.trace. This could be enabling a light on the status bar, or maybe better a docklet that shows OSC traffic with sensible filters for serverstatus etc. (One problem with OSCFunc.trace is that it can flood the post window.
> 
> 
>> With the current horizontal layout, if the level meters are vertical,
>> you don't get much detail. If horizontal, you get more detail (and it
>> would parallel the presumably horizontal volume slider) but then large
>> numbers of channels would take a lot of vertical space.
> 
> first off -- i'm envisioning that the (pre-fader?) volume meter would be superimposed on the volume control, which saves a lot of horizontal space. reaktor does this and it's nice.
> 
> for multichannel, i think we should 1. vertically squeeze the channel meters so the bar always stays the same height, and 2. cap at 4 or 8 channels.
> 
> these features definitely should not be fancy, just some quick visual aid and some friendly interfaces that will be helpful for a majority of our users.

If you’re going to do channel meters and cap them, it needs to be crystal clear that it’s capped. I’d suggest just very simple input and output lights, just one for each, that are agnostic to the number of channels, 2 or 200. If you want channel grained info pop up the meter.

Will these be toggled? Otherwise will there be level synths running constantly?

S.

> 
> 
> nathan
> 
> _______________________________________________
> sc-dev mailing list
> 
> info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
> archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
> search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/


_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.