Re: [Bluemusic-users] New ideas
Brought to you by:
kunstmusik
From: Steven Yi <ste...@gm...> - 2005-07-10 18:40:47
|
Hi Kevin, On 7/10/05, t grey <tg...@gm...> wrote: > > I have been using a method for doing global reverb instruments where > > in the instrument I have a global score like this: > > > > i<INSTR_ID> <PROCESSING_START> [<TOTAL_DUR> + 3 - <PROCESSING_START>] >=20 > That's what I was missing. I knew I used to do something to process > arithmatic in the score. I'm using the global notes as well, but only > had <TOTAL_DUR>. This is an ok solution, I still think a variable > (maybe set near render start and end times) would make it easier / > more user friendly... especially for changing on the fly. Well, I'm still inclined to simply go with the setup, probalby because I'm very used to it. The values of processing are associated with the instrument and that makes it portable between projects. I have also setup the template note in my code library so it's easy to add to any new effects instruments. I can put the post roll in, but it might have to wait until after the next round of changes. (Unless someone else has time to put it in.) > > Ctrl-Plus - zoom in horizontally > > Ctrl-Minus - zoom out horizontally > > Ctrl-Shift-Plus - zoom in vertically > > Ctrl-Shift-Minus - zoom out vertically >=20 > Sounds great to me. I tried using plus but it didn't work as the only plus sign I have on my laptop keyboard is the one that is accessible from the equals key, which requires a shift. So I changed the short cut to use ctrl-equals and ctrl-shift-equals. It works great and I think the shortcut is fine considering that the plus key is on top of the equals key. Any objections? =20 > > For the Object Properties, you can commit a change by either making > > the text field lose focus or by pressing enter while in the field. > > The object properties is not meant to be opened and closed for every > > object change, but rather to have up and around for changing values. >=20 > Yeah, I understand that committing the changes works. I usually don't > leave the window open. I guess the way you use it seems more fit to > be an attached "pane" instead of a floating window. Yeah, I can see your logic behind this. I think that I might be very influenced by the programs which I use very often for work which are Flash and Photoshop, where floating property panels are very common.=20 Flash has the option of docking the windows, which would be nice, but there's a bit of a real estate problem in blue I think and I am not using a docking library or written a class for that yet, so the floating window is what is avaialable. (I also tend to make a great number of the property panel/windows as windows in Flash, so this in blue is really a reflection of my usage patterns for Flash and Photoshop). I think then perhaps if the window is dockable it would make more sense. I don't think I'll have time for that for this time in Krakow, but I have it on my list of TODO's so will try to schedule it sometime. Thanks again for all the suggestions! steven |