Thread: [Bluemusic-users] tracker update
Brought to you by:
kunstmusik
From: Steven Y. <ste...@gm...> - 2006-07-24 14:54:31
|
HI All, Just thought I'd send an image link to show what's going on with the tracker: http://kunstmusik.com/tracker.png I managed to get it to start looking right and have added add capability to add tracks. It's taken a few days to get my head back into it but it's starting to move now. I'm trying to figure out the best way to configure these tracks, whether I should add a collapsible panel on the right side that as you select a track column, the properties for the track show up there, or if it is better to right-click on a column head and access everything through a popup menu, where options on the popup menu show further show a dialog to edit those properties. So far I am thinking pitch and amplitude will be set standard for all tracks, as well as a template note string (though that won't be shown except maybe as a tooltip rollover bubble thing). Extra columns could be added with different types to choose from, i.e. int with range limits, float with range limits, etc. For pitch, I am thinking: text - value output exactly as given pch - csound pch format (8.1 equals octave 8, pch 10) bpch - blue pch format (8.1 equals octave 8, pch 1) (perhaps should add Scala scale option here too so you could choose scale format) oct - csound oct format freq - frequency in hertz [for the below, not sure what to call xx, but the format that shows in most trackers where xx equals something like b00, c01, d-02, which is basically pitch and relative octave) xx_midi - hex format, converts to midi xx_pch - hex format, converts to pch xx_oct - hex format, converts to oct xx_freq - hex format, converts to frequncy in hz For amp types: text - values output exactly as given db - values given as db (limit can be configured, i.e. 0-100) amp - values as straight number (limit can be configured) midi - 0-127 I'm not sure if all of the above types are necessary but it would give the possibility to do validation on what the user enters and prevent them from putting in values that aren't really desirable. For notes, as requested, I was going to make it where notes are on until another note on is added or until an explicit note off is put in. I am also planning to add a tied-note field. Anything I'm missing? I figure this is a good set of initial requirements and afterwords when it gets into a usable state and I can get some feedback it'll be easier to see what's necessary in terms of editing features, etc. Thanks! steven |
From: Will L. <fil...@gm...> - 2006-07-28 20:50:50
|
On 7/24/06, Steven Yi <ste...@gm...> wrote: > HI All, > > Just thought I'd send an image link to show what's going on with the tracker: > > http://kunstmusik.com/tracker.png > > I managed to get it to start looking right and have added add > capability to add tracks. It's taken a few days to get my head back > into it but it's starting to move now. I'm trying to figure out the > best way to configure these tracks, whether I should add a collapsible > panel on the right side that as you select a track column, the > properties for the track show up there, or if it is better to > right-click on a column head and access everything through a popup > menu, where options on the popup menu show further show a dialog to > edit those properties. > > So far I am thinking pitch and amplitude will be set standard for all > tracks, as well as a template note string (though that won't be shown > except maybe as a tooltip rollover bubble thing). Extra columns could > be added with different types to choose from, i.e. int with range > limits, float with range limits, etc. For pitch, I am thinking: > > text - value output exactly as given > pch - csound pch format (8.1 equals octave 8, pch 10) > bpch - blue pch format (8.1 equals octave 8, pch 1) (perhaps should > add Scala scale option here too so you could choose scale format) > oct - csound oct format > freq - frequency in hertz > > [for the below, not sure what to call xx, but the format that shows in > most trackers where xx equals something like b00, c01, d-02, which is > basically pitch and relative octave) > xx_midi - hex format, converts to midi > xx_pch - hex format, converts to pch > xx_oct - hex format, converts to oct > xx_freq - hex format, converts to frequncy in hz > > For amp types: > > text - values output exactly as given > db - values given as db (limit can be configured, i.e. 0-100) > amp - values as straight number (limit can be configured) > midi - 0-127 > > I'm not sure if all of the above types are necessary but it would give > the possibility to do validation on what the user enters and prevent > them from putting in values that aren't really desirable. > > For notes, as requested, I was going to make it where notes are on > until another note on is added or until an explicit note off is put > in. > > I am also planning to add a tied-note field. > > Anything I'm missing? I figure this is a good set of initial > requirements and afterwords when it gets into a usable state and I can > get some feedback it'll be easier to see what's necessary in terms of > editing features, etc. > > Thanks! > steven > Steven, That sounds good so far. I think that the best option for the options panel is to stay consistant with the other options panels in blue and make is pop out from the side, like with the piano roll and the polyobject and the synth builder...you get my point. Thanks again, Steven. -will |
From: Steven Y. <ste...@gm...> - 2006-08-08 14:49:42
|
Hi Will, Sorry for the very long delay in replying. I have been spending most of my programming time on Csound lately so blue development has been put on the way side, but am beginning to start organizing myself a bit better. I am going with your suggestion for the options panel on the side and am sketching now on paper how that should look. something like [Track Editor] Name: [ ] Columns [list of columns] Column Properties * [dropdown to select type] * Custom [number range] That's a bad approximation but I think the design will work, at least as something to aim for for a first draft. I'm starting to get myself more organized and will start putting in time into blue from tomorrow. Thanks again for the feedback! steven On 7/28/06, Will Light <fil...@gm...> wrote: > On 7/24/06, Steven Yi <ste...@gm...> wrote: > > HI All, > > > > Just thought I'd send an image link to show what's going on with the tracker: > > > > http://kunstmusik.com/tracker.png > > > > I managed to get it to start looking right and have added add > > capability to add tracks. It's taken a few days to get my head back > > into it but it's starting to move now. I'm trying to figure out the > > best way to configure these tracks, whether I should add a collapsible > > panel on the right side that as you select a track column, the > > properties for the track show up there, or if it is better to > > right-click on a column head and access everything through a popup > > menu, where options on the popup menu show further show a dialog to > > edit those properties. > > > > So far I am thinking pitch and amplitude will be set standard for all > > tracks, as well as a template note string (though that won't be shown > > except maybe as a tooltip rollover bubble thing). Extra columns could > > be added with different types to choose from, i.e. int with range > > limits, float with range limits, etc. For pitch, I am thinking: > > > > text - value output exactly as given > > pch - csound pch format (8.1 equals octave 8, pch 10) > > bpch - blue pch format (8.1 equals octave 8, pch 1) (perhaps should > > add Scala scale option here too so you could choose scale format) > > oct - csound oct format > > freq - frequency in hertz > > > > [for the below, not sure what to call xx, but the format that shows in > > most trackers where xx equals something like b00, c01, d-02, which is > > basically pitch and relative octave) > > xx_midi - hex format, converts to midi > > xx_pch - hex format, converts to pch > > xx_oct - hex format, converts to oct > > xx_freq - hex format, converts to frequncy in hz > > > > For amp types: > > > > text - values output exactly as given > > db - values given as db (limit can be configured, i.e. 0-100) > > amp - values as straight number (limit can be configured) > > midi - 0-127 > > > > I'm not sure if all of the above types are necessary but it would give > > the possibility to do validation on what the user enters and prevent > > them from putting in values that aren't really desirable. > > > > For notes, as requested, I was going to make it where notes are on > > until another note on is added or until an explicit note off is put > > in. > > > > I am also planning to add a tied-note field. > > > > Anything I'm missing? I figure this is a good set of initial > > requirements and afterwords when it gets into a usable state and I can > > get some feedback it'll be easier to see what's necessary in terms of > > editing features, etc. > > > > Thanks! > > steven > > > > Steven, > That sounds good so far. I think that the best option for the options > panel is to stay consistant with the other options panels in blue and > make is pop out from the side, like with the piano roll and the > polyobject and the synth builder...you get my point. > > Thanks again, Steven. > -will > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |