From: Colburn H. <col...@gm...> - 2009-04-14 21:45:59
|
I have been using LMMS extensively over the months to create music, and it has, for the most part, been excellent. I had been writing most of my music under a 4/4 time sig because I was mostly composing on the computer. On the other hand, when I compose on my piano I will often compose in other time signature's, in my most recent case 6/8. Well, when I tried to then "make" the song in lmms I realized that, although lmms was in 6/8, the 8th I tried to add notes did NOT correspond correctly. They should have filled up ONE "grid block" in the 6/8 pattern but they don't, which means that LMMS is not interpreting and 8th note (or any othe for that matter) correctly. I have similar results in many other time sigs including 5/4 and so on. This is DEFINITELY something that needs to be fixed with the next update. All in all this app is great and i'll definately be around with new suggestions (I've already got some popin up in my head.) |
From: Andy K. <sup...@gm...> - 2009-04-14 22:25:51
|
Thanks for the bug report. I put it in the bug tracker: https://sourceforge.net/tracker/?func=detail&aid=2763341&group_id=105168&atid=640434 On Tue, Apr 14, 2009 at 2:45 PM, Colburn Hayden <col...@gm...>wrote: > I have been using LMMS extensively over the months to create music, and it > has, for the most part, been excellent. I had been writing most of my music > under a 4/4 time sig because I was mostly composing on the computer. On the > other hand, when I compose on my piano I will often compose in other time > signature's, in my most recent case 6/8. Well, when I tried to then "make" > the song in lmms I realized that, although lmms was in 6/8, the 8th I tried > to add notes did NOT correspond correctly. They should have filled up ONE > "grid block" in the 6/8 pattern but they don't, which means that LMMS is not > interpreting and 8th note (or any othe for that matter) correctly. I have > similar results in many other time sigs including 5/4 and so on. This is > DEFINITELY something that needs to be fixed with the next update. > > All in all this app is great and i'll definately be around with new > suggestions (I've already got some popin up in my head.) > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > LMMS-devel mailing list > LMM...@li... > https://lists.sourceforge.net/lists/listinfo/lmms-devel > > |
From: Paul G. <dr...@gm...> - 2009-04-15 05:41:12
|
For the record: the reason for the time.sig-switching madness is because LMMS only considers the song's time-signature for the current moment. That means: As the time signature changes, the WHOLE song is re-evaluated. I don't know if it is going to be fixed in 0.9.0 (not likely). But I believe this bug blocks version 1.0.0. I believe this feature could be fixed (and swing could also be implemented) if we use a beat-mapping strategy. LMMS can contain a beatmap. Basially: Every single beat will be in a list. Each beat has a function to obtain the absolute time that the beat occurs. This list will be sorted by time. Other information may be stored in the beat objects (beat#-of-bar?, duration?, title? metadata?). LMMS's mixer (or is it engine? I forget) will advance in seconds. The mixer will know when to advance the beat by looking at the beatmap. This also allows us to easily add Minutes:Seconds display along side the Bar:Beat display. Other features like jump-to-time could be implemented. Also, there is no reason all the beats in a single bar need to have the same duration (equal increments of time). This allows us the ability to add swing (groove/shuffle). Now, I know you are saying: "Paul, the user doesn't want to have to insert individual bars/beats/etc..". The above design is what will be available to the engine. I believe it (or a variation of it) will be very performant, flexible, and should be simple to implement. The user interface on the other hand will most likely be an extension of the Time-Line. The user could possibly add demarcations to the timeline to specify where time-sig changes occur. The automation editor will most likely be used for swing, and tempo changes. Also, because of the beatmap, the song-editor could properly display measures of differing time-signature. As far as storage goes, the big implementation detail is the interface to the engine and song that I described above. For all I care, the user's time-signature changes are actually stored, and the bar and beat times are calculated based on the user's view, tempo-model, and swing-model. Or perhaps the beats are stored and the higher-level concepts are stored in the beat's metadata. Changes to the view causes portions of the beat-list to be recalculated. Or maybe it is a hybrid caching approach and we invalidate entries when the model changes. I guess my overall view is that: our current time-signature implemention is a big step, but not sufficient for actual use. Swing/shuffle would be a nice feature to have. This requires some fundamental changes, but the end result should be clean. The gui task will be rather involved. I am up to the task of the GUI. In fact, this beatmap stuff is one reason I haven't commited much code to the nextgen editor. I see this feature as essential to the 1.0 version of LMMS, and I've pondered this feature for a few weeks. -Paul On Tue, Apr 14, 2009 at 5:25 PM, Andy Kelley <sup...@gm...> wrote: > Thanks for the bug report. I put it in the bug tracker: > https://sourceforge.net/tracker/?func=detail&aid=2763341&group_id=105168&atid=640434 > > On Tue, Apr 14, 2009 at 2:45 PM, Colburn Hayden <col...@gm...> > wrote: >> >> I have been using LMMS extensively over the months to create music, and it >> has, for the most part, been excellent. I had been writing most of my music >> under a 4/4 time sig because I was mostly composing on the computer. On the >> other hand, when I compose on my piano I will often compose in other time >> signature's, in my most recent case 6/8. Well, when I tried to then "make" >> the song in lmms I realized that, although lmms was in 6/8, the 8th I tried >> to add notes did NOT correspond correctly. They should have filled up ONE >> "grid block" in the 6/8 pattern but they don't, which means that LMMS is not >> interpreting and 8th note (or any othe for that matter) correctly. I have >> similar results in many other time sigs including 5/4 and so on. This is >> DEFINITELY something that needs to be fixed with the next update. >> >> All in all this app is great and i'll definately be around with new >> suggestions (I've already got some popin up in my head.) >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> High Quality Requirements in a Collaborative Environment. >> Download a free trial of Rational Requirements Composer Now! >> http://p.sf.net/sfu/www-ibm-com >> _______________________________________________ >> LMMS-devel mailing list >> LMM...@li... >> https://lists.sourceforge.net/lists/listinfo/lmms-devel >> > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > LMMS-devel mailing list > LMM...@li... > https://lists.sourceforge.net/lists/listinfo/lmms-devel > > |