Thanks for the report, it is reproducable here and works exactly as you described. I'm going to see if i can fix it, but i suppose that won't be before Friday this week :( Btw, i've opened a ticket (#84) for this bug. Thanks!! - Sebastian
On Tue, 24 Feb 2009 18:02:00 +0100, Salvatore Di Pietro <[email protected]> wrote: > [email protected] wrote: >> Am Mon, 23 Feb 2009 16:59:02 -0600 >> schrieb "Gabriel M. Beddingfield" <[email protected]>: >> >>> Salvatore Di Pietro wrote: >>>> I've been trying rev 802, 805 and now 841. >>>> They all behave well, except a little annoyance when using right-click >>>> on notes to alter their length. The recipe is the following, the >>>> numerical values are not strictly the ones given, but they work as > test >>>> case: >>> Wow! I didn't even know H2 did this. >>> >>> But... I though H2 didn't implement any note length or "note off" > events in the >>> sampler. We just play the sample until the sample ends. Right? >>> >>> Peace, >>> Gabriel >> >> nono :-) h2 have a well working note length feature. including the > instrument adsr to control the r = (note off release). so note off will > fade out controlled. the mute group feature also based on this. and also > the right click and move mouse to set note length feature use this. >> in the fx and sample fun branch i also include note_off notes based on > this feature. and in this branch it's possible to record note_off's > (notelength) from midi. all this will computed in sampler.cpp. > > Yes, it is great, and the samplefun branch must be veeeery cool! I > should try it one day :) > But (at least) trunk has this annoyance/bug: if you have two or more > notes on the same instrument (which happens almost always) and you want > to resize a note that isn't the *first one* in the pattern, you have to > place the mouse pointer on the *start* of the note you want to > resize(1), not on the *tail*, as intuition would suggest, like when you > resize a gimp selection, or, notably, in rosegarden, when you resize > note lengths, you resize them grabbing them by the "tail". > > If you don't do this, you just get an extremely stretched first note, > which is not what you wanted :) since you were not wanting to resize the > first note! > > > (1) Precisely, you have to place the mouse pointer in an inner point of > the (mathematical) neighborhood of the note-on point. The boundaries of > this neighborhood are: > - the midpoint between the dash before the actual note-on position (yes, > before!) > - the midpoint between the dash after the actual note-on position. > Just refer to the screenshots to see what I mean. > This is the same at any pattern resolution, and things get more strange > when you try to resize notes that don't start on a dash, for example > when you start composing with a resolution of say 8T and then switch > over 8. The note-ons don't align anymore with the dashes, and you have > to place the pointer on the "positive side" of the note-on neighborhood. > > So I think the note resizing code should be fixed to let you resize > notes operating on their "tails", like in rosegarden, or at least avoid > that the first note gets an unwanted resize, if I don't click within the > note-on neighborhood (and the "negative" side of it, which doesn't make > much sense)... I'm not resizing (and I'm not clicking on) the first > note, after all. > > Let me know if you need additional info/explanation... > > Ciao and thanks! > > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Hydrogen-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
