Re: [Galan-list] ideas

[torben h. <to...@gm...>]

On 26 Sep 2002 11:02:58 -0700, Vonsur Kcin wrote:
> 
> I had an interesting idea that would lead to some flexibility in the
> network layout, mostly cosmetic. Have a 'bus' object, thats like a
> long bar that distributes data to any point along it. It doesn't fit
> into the current block and pin style thing, but It'd be useful for
> laying out things. Basically there'd be a vertical and a horizontal
> version, for events and signals. An alternative to this would be a
> 'null' object, wich would jsut be the pad from a pin that you could
> place anywhere you want, and connect wires to, so you could make right
> angles at least, and event a bus-like thing. This would probably work
> better within the 'galan wiring paradigm'.

yeah... the null object is simple.
like a box with a connector in it (there needs to be something with
which you can drag
the object around dragging with a connector does not work for obvious
reasons)

the bus is cool too but i dont know how to implement that (out of my
head)
need to look at the code some more for a good idea.


> 
> Hrm, another idea I had was when the sheet system works better to be
> able to impliment existing physical devices within gAlan, like classic
> synths and sequencers and such, like Reason from Propellerhead does.
> Actually in my mind gAlan is very close in possible application to
> Reason, so it'd be cool to bring it to a point where it could replace
> such software. Having classic synths and components in the 'sheet
> library', once sheet management is a bit better, would be sweet, and
> not that hard.


not hard at all..
How should sheet handling made better ?
No more registering (all sheets are available in sheet menu) ?
All sheets in <directory> are in the new menu ?

My sheet library is growing i can make that available on the web-page.


> 
> A nice component would be a signal timer or some such. Maybe
> associated with the sequence controller thing, so you know how long
> your opus is stretching to. This could be a whole new component
> actually, with a 'reset' pin antd button, and a display control, so
> you slave it to the reset on the sequence controler.

There is already Events/Timer
I dont exactly know what you mean.
timer emits the time between the last event and the current event.
with some eventgates it should be possible to build almost any timing
structure.

try that or describe again...



> 
> Another useful thing would be a BPM counter, or a 'BPM' format display
> associated with the clock (what does the clock value mean, anyway?
> steps per second? Hz? I can't correlate it with anything).

The clock_rate is in Hertz which is steps per second.
So if beat is every 4 steps
BPM = clock_rate * 60 / 4;




> 
> A bug I noticed was with LADSPA plugins. The controls on them don't
> reflect programmatic changes occuring in them; for example if I hook
> the feedback of a flanger up to a numeric sequence, the control for
> that doesn't show the changes as they occur (or indeed at all), it
> only shows what I previously set it to. Sort of annoying. 

ok... i fixed that in the current code base.
this is normally a missing call to gen_update_controls( g,
control_number )
in the evt handler....
it is missing in many plugins....
I should probably look at all plugins if the function is called.




> 
> -- 
> -><- Nick Rusnov
> -><- http://nick.industrialmeats.com
> -><- ni...@fa.../nic...@de... 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Galan-list mailing list
> Gal...@li...
> https://lists.sourceforge.net/lists/listinfo/galan-list
>