Re: [Bluemusic-users] Randomization

[Steven Y. <ste...@gm...>]

Hi Mark,

Thanks for mentioning the bug.  I made a change on VSlider then went
to test with an HSlider and a VSlider and strangely enough both were
working.  I made the change to HSlider too though.

Could you try this new version?

http://www.kunstmusik.com/blue_0.117.0_beta_installer.jar

Thanks!
steven

On 8/13/07, Mark Van Peteghem <Mar...@te...> wrote:
> I tried it out, and it works very well with dropdownlists. Thanks for
> adding this geature.
>
> I just found a bug when randomizing vertical sliders (probably with
> horizontal sliders as well): when you randomize them, the value shown at
> the bottom doesn't correspond with its value. Instead it shows the value
> it had before randomizing.
>
> Steven Yi wrote:
> > Hi Mark,
> >
> > I've implemented randomization for checkboxes and dropdowns.  The
> > change is in CVS and I've placed another build at:
> >
> > http://www.kunstmusik.com/blue_0.117.0_beta_installer.jar
> >
> > Checkbox probabilities... er... probably not going to happen. =P
> >
> > As for testing, has anyone check randomization with automation?  It
> > should be working but I haven't had a chance to test.
> >
> > Not sure when I'll get to implement the other randomization stuff;
> > work is very busy at the moment so not much free time for me for
> > programming blue or composing (*sigh*...).
> >
> > Thanks,
> > steven
> >
> >
> > On 8/8/07, Mark Van Peteghem <Mar...@te...> wrote:
> >
> >> Steven Yi wrote:
> >>
> >>> Hi Mark,
> >>>
> >>> I had considered percentages but I fell into a problem using
> >>> percentages a half year or year ago when storing line point values and
> >>> later changed to always using absolute values.  The percentages are
> >>> also not as intuitive for a user to work with I think as seeing the
> >>> values in the range.  I would like make a change such that if min or
> >>> max in the normal range changes, then random range would scale
> >>> themselves (so convert to percent, then recalculate and rechange to
> >>> absolute value).
> >>>
> >>>
> >> What I had in mind was just using percentages internally, and show the
> >> random range visually on the knob in a different color, that the user
> >> can somehow change on the knob. But if your proposal is also good, so if
> >> it's easier to implement...
> >>
> >>
> >>> Well, maybe it won't be so difficult... I'll take a look at the knob
> >>> or one of the sliders tonight to see what's involved.  The random
> >>> range would be available for sliders, knobs, xy controller but not
> >>> dropdown and check list as they don't really make sense to have ranges
> >>> I think.
> >>>
> >>>
> >> Of course. For some instruments with a lot of checkboxes it may be
> >> desirable that only a few are on at a time, so assigning a probability
> >> that it is on would be helpful, but maybe I'm going too far now :-)
> >>
> >>
> >>> Oh, also, regarding randomization of text fields from your prior
> >>> email, I do not think it would be possible to make random at this
> >>> time; the only way would involve creating a UI for choosing method to
> >>> randomize or accepting a python expression or something like that and
> >>> that's just too much.
> >>>
> >>>
> >> I think I'll use a workaround: temporarily add some knobs for each of
> >> these textfields and use these knobs in the instrument code, find
> >> interesting presets by randomizing, and finally copy the values in the
> >> textfields and remove the knobs.
> >>
> >> I also thought of an extra feature: the right-click menu should have a
> >> 'Center random range around present values' under 'Randomize', that
> >> would allow to easily make variations on presets.
> >>
> >> --
> >>   Mark
> >>   _________________________________________
> >>   When you get lemons, you make lemonade.
> >>   When you get hardware, you make software.
> >>
> >>
> >> -------------------------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc.
> >> Still grepping through log files to find problems?  Stop.
> >> Now Search log events and configuration files using AJAX and a browser.
> >> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> >> _______________________________________________
> >> Bluemusic-users mailing list
> >> Blu...@li...
> >> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
> >>
> >>
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________
> > Bluemusic-users mailing list
> > Blu...@li...
> > https://lists.sourceforge.net/lists/listinfo/bluemusic-users
> >
> >
> >
>
> --
>   Mark
>   _________________________________________
>   When you get lemons, you make lemonade.
>   When you get hardware, you make software.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Bluemusic-users mailing list
> Blu...@li...
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>