From: Robert J. <rob...@da...> - 2004-05-04 17:31:39
|
Hi all, MusE 0.7pre2 is now ready for download. Some changes in this release: * Custom guis for plugins work again * Splash screen * LADCCA/LASH support updated * Cleaned up shortcuts * Single key shortcuts for edit tools * Update marker list on tempo change * Allow adding markers from the ruler with shift-click * Metronom now sends proper note off events * Clip list editor deaktivated * After loading of template, treat current project as "untitled" * Song format changed due to bugfixes * Shortcuts to bug reporting tool and homepage from help menu * Updated AboutBox * Fixed QT version check in m4/qt.m4 * And a number of other bugs check the Changelog for a complete list of changes. Also check http://lmuse.sourceforge.net/wiki/index.php/TODO for currently known issues. The download is available at: http://sourceforge.net/projects/lmuse Regards, /MusE Development team (Note: Below is release notice for muse-0.7pre1.) -------------------------------------------------------------------- Hi everybody, This mail is to inform you that the first prerelease of MusE 0.7 is available for download. People are encouraged to test this as much as possible. MusE 0.7 has received a huge amount of new functionality (It has been in development for almost six months), but still stability is the primary goal to achieve. If you find any issues, enter them in the bug-system (http://sourceforge.net/tracker/?group_id=93414&atid=604222) or report them back to the mailinglist. [Some highlights] * Lots of performance improvements - Internal redesign leading to realtime performance greatly improved - Softsynth interface redesigned for better performance * MusE now is always a Jack application - Interface to jack extended greatly - support for jack transport (both master and slave) - freewheeling mode for mixdown etc... * Audio functionality extended in - Mixer merged with midi-mixer - Audio routing redesigned - New types of generic 'tracks' Input/Output/Aux/Group/etc * Automation - A new automation subsystem has been implemented (only volume works at the moment) * Configuration and customization - lots of new dialogs are added to improve the customization options in MusE - shortcut editor * Editor improvements - drum editor improved with many shortcuts - arranger keyboard navigation and shortcuts (work in progress) * Bugs bugs bugs - they are all fixed :) .. oh perhaps one or two is still lurking around, if you find them be sure to report them back here! * Score editor is no longer available For a full list of changes, check the Changelog [Known issues] Have a look at the TODO list at http://lmuse.sourceforge.net/wiki/index.php/TODO for a more or less complete list of known issues with this release. [Download] Go to the sourceforge project page at http://sourceforge.net/projects/lmuse. [Misc] In case you haven't noticed a lot is going on at the MusE homepage also, a wiki has been installed that is being very actively updated. Do check it out! Have fun and please report any findings. /The MusE development team |
From: Linium <in...@ne...> - 2004-05-05 22:44:41
|
On Mardi 4 Mai 2004 19:30, Robert Jonsson wrote: > Hi all, > > MusE 0.7pre2 is now ready for download. > > Some changes in this release: > > * Custom guis for plugins work again > * Splash screen > * LADCCA/LASH support updated > * Cleaned up shortcuts > * Single key shortcuts for edit tools > * Update marker list on tempo change > * Allow adding markers from the ruler with shift-click > * Metronom now sends proper note off events > * Clip list editor deaktivated > * After loading of template, treat current project as "untitled" > * Song format changed due to bugfixes > * Shortcuts to bug reporting tool and homepage from help menu > * Updated AboutBox > * Fixed QT version check in m4/qt.m4 > * And a number of other bugs > Great ! :) Well, i am tempted to make a try, but i don't know how usable it is, do you (or someone else) have a personal feeling on the question ? I don't need much the advanced audio features yet (automation, routings), well i would be happy to route the tracks with jack, but the jacktransport and the sync feature with ardour would suffice to make me convinced :) BTW, will it load the old muse file ? Maybe should I wait a little if this aspect matters ? Thks everybody for the continous work, it's very impressive ! Linium |
From: John C. <j4s...@bi...> - 2004-05-06 01:45:40
|
On Wednesday 05 May 2004 06:51 pm, Linium wrote: > On Mardi 4 Mai 2004 19:30, Robert Jonsson wrote: > > Hi all, > > > > MusE 0.7pre2 is now ready for download. > > > > Some changes in this release: > > > > * Custom guis for plugins work again > > * Splash screen > > * LADCCA/LASH support updated > > * Cleaned up shortcuts > > * Single key shortcuts for edit tools > > * Update marker list on tempo change > > * Allow adding markers from the ruler with shift-click > > * Metronom now sends proper note off events > > * Clip list editor deaktivated > > * After loading of template, treat current project as "untitled" > > * Song format changed due to bugfixes > > * Shortcuts to bug reporting tool and homepage from help menu > > * Updated AboutBox > > * Fixed QT version check in m4/qt.m4 > > * And a number of other bugs > > Great ! :) > Well, i am tempted to make a try, but i don't know how usable it is, do you > (or someone else) have a personal feeling on the question ? Much more usable than the 0.6 series. > I don't need much the advanced audio features yet (automation, routings), > well i would be happy to route the tracks with jack, but the jacktransport > and the sync feature with ardour would suffice to make me convinced :) > > BTW, will it load the old muse file ? Maybe should I wait a little if this > aspect matters ? > No, it won't. Song format has changed. I'd suggest exporting to standard midifile with an older version before moving to the new. I don't beleive addressing this is a priority. > Thks everybody for the continous work, it's very impressive ! > > Linium > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |
From: Emiliano G. <emi...@po...> - 2004-05-06 09:31:10
|
marted=EC, 04 maggio 2004 alle 19:30:54, Robert Jonsson ha scritto: > Hi all, Hi Robert,=20 I've tried the 0.7.0pre1 and I'm very impressed. You guys have done a ver= y good job! IIUC the development has been "splitted" into old muse and this new branch. IMHO one of the most exciting features of the new version is the jack_transport implementation: I've played a lot in perfect sync with hydrogen and I've got real fun :) Do you think that this feature can be "backported" to the old branch? Or = do you plan to leave completely 0.6.3 as the last version of that branch? Now some considerations/thoughts [1]: - List editor doesn't allow me to insert arbitrary controllers (I would like to create slurs like is described in http://www.borg.com/~jglatt/tutr/slur.htm - but list editor seems not t= o accept controllers 100 and 101) or there is another way of doing this? =20 - MIDI import/export of single tracks: I don't know how much this is diffficult to implement from the programmer point of view, but would definitely be an handy addition.=20 - MIDI constraint: it would be cool in the piano roll editor if one can select say a chord or a scale from a drop down box and the relative not= es are highlighed (like in jazz++ when you select a chord in the harmony browser) and the new inserted notes "snap" to that notes. - MIDI groove templates: I think we lack a facility to define quantizatio= n patterns, like you find in cubase for example. I guess this is not easy to do, but is worth the effort, IMHO. With such a tool an user can defi= ne a library of quantization patterns that can be exported and shared with other users, and/or included in the next versions of muse. As you might have noted, I use most the MIDI part of muse. As far as audi= o goes, I have used it only few times but muse react well for what I need (= eg dump a MIDI track into an audio one). Best regards, [1] I'm not a programmer, so I can speak only from the user perspective: = I don't know if my requests are difficult to implement or impossible at all= =2E --=20 Emiliano Grilli Linux user #209089=20 http://www.emillo.net |
From: John C. <j4s...@bi...> - 2004-05-06 23:56:01
|
On Thursday 06 May 2004 05:30 am, Emiliano Grilli wrote: > marted=EC, 04 maggio 2004 alle 19:30:54, Robert Jonsson ha scritto: > > Hi all, > > Hi Robert, > > I've tried the 0.7.0pre1 and I'm very impressed. You guys have done= a very > good job! IIUC the development has been "splitted" into old muse an= d this > new branch. IMHO one of the most exciting features of the new versi= on is > the jack_transport implementation: I've played a lot in perfect syn= c with > hydrogen and I've got real fun :) > Do you think that this feature can be "backported" to the old branc= h? Or do > you plan to leave completely 0.6.3 as the last version of that bran= ch? > > Now some considerations/thoughts [1]: > > - List editor doesn't allow me to insert arbitrary controllers (I w= ould > like to create slurs like is described in > http://www.borg.com/~jglatt/tutr/slur.htm - but list editor seems= not to > accept controllers 100 and 101) or there is another way of doing = this? > > - MIDI import/export of single tracks: I don't know how much this i= s > diffficult to implement from the programmer point of view, but wo= uld > definitely be an handy addition. Are you talking about taking any random standard MIDI file and arbitr= arily=20 importing specific tracks without auditioning the whole file? > > - MIDI constraint: it would be cool in the piano roll editor if one= can > select say a chord or a scale from a drop down box and the relati= ve notes > are highlighed (like in jazz++ when you select a chord in the har= mony > browser) and the new inserted notes "snap" to that notes. > > - MIDI groove templates: I think we lack a facility to define quant= ization > patterns, like you find in cubase for example. I guess this is no= t easy > to do, but is worth the effort, IMHO. With such a tool an user ca= n define > a library of quantization patterns that can be exported and share= d with > other users, and/or included in the next versions of muse. > Groove templates developed out of the swing algorithm. Swing: Tempo i= s=20 calculated on the downbeats, the upbeats are late or early relative t= o the=20 tempo. I've been meaning to bring that up. > As you might have noted, I use most the MIDI part of muse. As far a= s audio > goes, I have used it only few times but muse react well for what I = need (eg > dump a MIDI track into an audio one). > > Best regards, > > [1] I'm not a programmer, so I can speak only from the user perspec= tive: I > don't know if my requests are difficult to implement or impossible = at all. |
From: Emiliano G. <emi...@po...> - 2004-05-07 07:51:12
|
gioved=EC, 06 maggio 2004 alle 20:02:50, John Check ha scritto: > > - MIDI import/export of single tracks: I don't know how much this is > > diffficult to implement from the programmer point of view, but woul= d > > definitely be an handy addition. >=20 > Are you talking about taking any random standard MIDI file and > arbitrarily importing specific tracks without auditioning the whole fil= e? Yes, it would be useful: 1) being able to export a single track to midifile (eg you click with the right mouse button on trackname -> export this track as midifile) - of course you can delete all other tracks and export, but isn't very handy..= =2E 2) being able to merge into the current project a track imported from an arbitrary midifile (ie with a dialog that ask you what track number you want) - of course tempo will adapt to current song. The function can be called "merge track from midifile". IIUC now for doing this you have to close the project you are working on, import the midifile, select the track/part you want, copy it, reopen your project and paste the part you have in the clipboard: a lot of actions... =20 > > - MIDI groove templates: I think we lack a facility to define > > quantization patterns, like you find in cubase for example. I guess > > this is not easy to do, but is worth the effort, IMHO. With such a to= ol > > an user can define a library of quantization patterns that can be > > exported and shared with > > other users, and/or included in the next versions of muse. >=20 > Groove templates developed out of the swing algorithm. Swing: Tempo is=20 > calculated on the downbeats, the upbeats are late or early relative to > the tempo. I've been meaning to bring that up. Glad to hear that :) Swing can improve a lot the human feel. I use it a lot in hydrogen. Best regards, --=20 Emiliano Grilli Linux user #209089=20 http://www.emillo.net |
From: Robert J. <rob...@da...> - 2004-05-06 09:50:18
|
Hi Emiliano, On Thursday 06 May 2004 11.30, Emiliano Grilli wrote: > marted=EC, 04 maggio 2004 alle 19:30:54, Robert Jonsson ha scritto: > > Hi all, > > Hi Robert, > > I've tried the 0.7.0pre1 and I'm very impressed. You guys have done a very > good job!=20 I'm glad you like it :) 0.7 is the accumulated effort produced from a numbe= r=20 of people, mainly Werner ofcourse who works for two :). > IIUC the development has been "splitted" into old muse and this=20 > new branch. IMHO one of the most exciting features of the new version is > the jack_transport implementation: I've played a lot in perfect sync with > hydrogen and I've got real fun :) > Do you think that this feature can be "backported" to the old branch? Or = do > you plan to leave completely 0.6.3 as the last version of that branch? The quick answer is no, there is too little manpower to keep going in two=20 directions. But read on for other solutions. The development was split, but it was a temporary solution to be able to=20 produce one more release in the 0.6 series (that in the end became two=20 releases).=20 Almost everything that was implemented into the last releases of MusE 0.6.3= is=20 meant to be available in 0.7. Notable exceptions are: =2D no alsa mode =2D no midi only mode (both these where removed to simplify the architectur= e and=20 make MusE more stable) =2D no score (I think Werner was not fully satisfied with what could be=20 achieved) This leads me to the main question. What is it that you miss in the new Mus= E=20 that means you wish for a backport?=20 If there is something missing we would rather add it in the new instead. Ofcourse it could be a question of time, we don't have a release plan but m= y=20 own opinion is that we should be able to have it "ready" this summer. (I wa= s=20 going to say before summer but... that is now :) > > Now some considerations/thoughts [1]: > > - List editor doesn't allow me to insert arbitrary controllers (I would > like to create slurs like is described in > http://www.borg.com/~jglatt/tutr/slur.htm - but list editor seems not to > accept controllers 100 and 101) or there is another way of doing this? There was another another report about this too, Sadly I'm pretty=20 midi-illiterate when it comes to the advanced stuff, but I am keen to learn= =2E=20 I'll try it out myself.=20 I would be happy for responses from others :) > > - MIDI import/export of single tracks: I don't know how much this is > diffficult to implement from the programmer point of view, but would > definitely be an handy addition. When it comes to import I guess a work around is to simply remove the track= s=20 you don't want. You could do the same when exporting, but that is hardly=20 sufficient. I guess there is some work involved with adding this. I will add it to the= =20 wishlist. > - MIDI constraint: it would be cool in the piano roll editor if one can > select say a chord or a scale from a drop down box and the relative not= es > are highlighed (like in jazz++ when you select a chord in the harmony > browser) and the new inserted notes "snap" to that notes. Sounds like a great feature, too something for the wishlist. > > - MIDI groove templates: I think we lack a facility to define quantization > patterns, like you find in cubase for example. I guess this is not easy > to do, but is worth the effort, IMHO. With such a tool an user can defi= ne > a library of quantization patterns that can be exported and shared with > other users, and/or included in the next versions of muse. There are some external projects that deal with this, it might be possible = to=20 build on one of these. > > As you might have noted, I use most the MIDI part of muse. As far as audio > goes, I have used it only few times but muse react well for what I need (= eg > dump a MIDI track into an audio one). You should check out the other uses also, lots of fun stuff :) > > Best regards, > > [1] I'm not a programmer, so I can speak only from the user perspective: I > don't know if my requests are difficult to implement or impossible at all. We are quite happy to get requests from people that are actually trying to = use=20 it :) Ofcourse there is a technical side of things, but it's the features=20 that count. How to implement it is our headache ;) Thanks for the report! Robert |
From: Emiliano G. <emi...@po...> - 2004-05-06 10:28:30
|
gioved=EC, 06 maggio 2004 alle 11:45:34, Robert Jonsson ha scritto: > Hi Emiliano, >=20 > > IIUC the development has been "splitted" into old muse and this new > > branch. IMHO one of the most exciting features of the new version is > > the jack_transport implementation: I've played a lot in perfect sync > > with hydrogen and I've got real fun :) > > Do you think that this feature can be "backported" to the old branch? > > Or do you plan to leave completely 0.6.3 as the last version of that > > branch? >=20 > The quick answer is no, there is too little manpower to keep going in t= wo=20 > directions. But read on for other solutions. >=20 > The development was split, but it was a temporary solution to be able t= o > produce one more release in the 0.6 series (that in the end became two > releases).=20 > Almost everything that was implemented into the last releases of MusE > 0.6.3 is meant to be available in 0.7. Notable exceptions are: > - no alsa mode > - no midi only mode (both these where removed to simplify the > architecture and make MusE more stable) This is one of the missing features, imagine one that, for one reason or another can't eun jack: he can't use muse at all... this is the case of m= y ibook, where jack is not as smooth as it is on my athlon machine. > - no score (I think Werner was not fully satisfied with what could be=20 > achieved) > This leads me to the main question. What is it that you miss in the new > MusE that means you wish for a backport?=20 The main stopper that prevents me to use muse on my "stable" system is th= e requirement for qt 3.2 (my stable system is RH8+PlanetCCRMA), so I tried = it under debian sid, and all went fine... > If there is something missing we would rather add it in the new instead= =2E >=20 > Ofcourse it could be a question of time, we don't have a release plan b= ut > my own opinion is that we should be able to have it "ready" this summer= =2E > (I was going to say before summer but... that is now :) BTW, I think muse is the more advanced sequencer in the linux/audio scene... I can wait :) =20 > > Now some considerations/thoughts [1]: > > - List editor doesn't allow me to insert arbitrary controllers (I wou= ld > > like to create slurs like is described in > > http://www.borg.com/~jglatt/tutr/slur.htm - but list editor seems n= ot > > to accept controllers 100 and 101) or there is another way of doing > > this? =20 > There was another another report about this too, Sadly I'm pretty=20 > midi-illiterate when it comes to the advanced stuff, but I am keen to > learn. I'll try it out myself.=20 Me too, I'm not an in depth MIDI techie.... :) =20 > I would be happy for responses from others :) =20 > > - MIDI import/export of single tracks: I don't know how much this is > > diffficult to implement from the programmer point of view, but woul= d > > definitely be an handy addition. >=20 > When it comes to import I guess a work around is to simply remove the > tracks you don't want. You could do the same when exporting, but that i= s > hardly sufficient. I guess there is some work involved with adding thi= s. > I will add it to the=20 > wishlist. Thank you :) =20 > > - MIDI constraint: it would be cool in the piano roll editor if one c= an > > select say a chord or a scale from a drop down box and the relative > > notes are highlighed (like in jazz++ when you select a chord in the > > harmony browser) and the new inserted notes "snap" to that notes. >=20 > Sounds like a great feature, too something for the wishlist. > > - MIDI groove templates: I think we lack a facility to define > > quantization patterns, like you find in cubase for example. I guess > > this is not easy to do, but is worth the effort, IMHO. With such a to= ol > > an user can define a library of quantization patterns that can be > > exported and shared with other users, and/or included in the next > > versions of muse. >=20 > There are some external projects that deal with this, it might be > possible to build on one of these. Which ones? Can you point me to an URL? =20 > > > > As you might have noted, I use most the MIDI part of muse. As far as > > audio goes, I have used it only few times but muse react well for wha= t > > I need (eg dump a MIDI track into an audio one). >=20 > You should check out the other uses also, lots of fun stuff :) Sure, but I know that if I begin doing a lot of audio takes my hard drive can become full in few days :) (I'm not very tidy) However, listening to Mathias music, I saw great potential :) But I think also MIDI features are important, and list editor/quantizatio= n are the fields where I see more room for improvement. (BTW, excellent wor= k on the drum editor) > > [1] I'm not a programmer, so I can speak only from the user > > perspective: I don't know if my requests are difficult to implement o= r > > impossible at all. >=20 > We are quite happy to get requests from people that are actually trying > to use it :) Ofcourse there is a technical side of things, but it's the > features that count. How to implement it is our headache ;) Good to know, I'll go filling a 20 pages feature request, then :P =20 > Thanks for the report! > Robert Ciao --=20 Emiliano Grilli Linux user #209089=20 http://www.emillo.net |
From: Robert J. <rob...@da...> - 2004-05-06 10:42:02
|
> > > > > - MIDI groove templates: I think we lack a facility to define > > > quantization patterns, like you find in cubase for example. I guess > > > this is not easy to do, but is worth the effort, IMHO. With such a tool > > > an user can define a library of quantization patterns that can be > > > exported and shared with other users, and/or included in the next > > > versions of muse. > > > > There are some external projects that deal with this, it might be > > possible to build on one of these. > > Which ones? > Can you point me to an URL? > It seems I was mistaking. I thought about rhythm patterns. For this there are: http://gmorgan.sourceforge.net/ http://www.kootenay.com/~bvdpoel/mma/mma.html /Robert |
From: Emiliano G. <emi...@po...> - 2004-05-06 13:02:47
|
gioved=EC, 06 maggio 2004 alle 12:37:16, Robert Jonsson ha scritto: > > Which ones? > > Can you point me to an URL? > > > It seems I was mistaking. I thought about rhythm patterns. > For this there are: > http://gmorgan.sourceforge.net/ > http://www.kootenay.com/~bvdpoel/mma/mma.html Yes, I know these but they are arrangers... I mean something where you ca= n define the "groove" of your quantisation (eg slightly shift the 3rd beat ahead and so on) - I think cubase calls that "DNA grooves" or something l= ike this... Think of a "programmable humanization mask" :) Of course, it would be great also to save these templates, to build a library that should be shipped with the program. I would love to have various types of swing, shuffles, waltz, etc... to try on my sequences.=20 Most of the MIDI editing is concerning the positions of the notes, and so having more functions to vary the position (in a musical way) for me woul= d be a big plus. A more advanced improvement can be adding to these templat= es a "random factor" (eg define an horizontal range in which the note can fa= ll) The same method can be applied to other parameters, such as velocity or controllers, but for a start, just being able to control the position of the notes in a programmable/editable way is a must for a sequencer IMHO, because fixed quantisation is useful, but only for certain musical genres... and the only way to give an human feel to a MIDI track, for now is to edit in a note-by-note basis, which you have to admit, is not so comfortable ;) > /Robert Cheers, --=20 Emiliano Grilli Linux user #209089=20 http://www.emillo.net |
From: John C. <j4s...@bi...> - 2004-05-07 00:07:33
|
On Thursday 06 May 2004 05:45 am, Robert Jonsson wrote: > > - List editor doesn't allow me to insert arbitrary controllers (I would > > like to create slurs like is described in > > http://www.borg.com/~jglatt/tutr/slur.htm - but list editor seems not > > to accept controllers 100 and 101) or there is another way of doing this? > > There was another another report about this too, Sadly I'm pretty > midi-illiterate when it comes to the advanced stuff, but I am keen to > learn. I'll try it out myself. Slurs are like portamento without the transition time (AKA "glide"). IIRC as far as the midi stream goes all controllers have the same format so supporting the controller is no biggie. Implementing slurs inside MusE would be not unlike implementing monophonic rythm groups, except theres no way to get around the attack phase of the notes. |
From: John C. <j4s...@bi...> - 2004-05-07 00:38:57
|
On Thursday 06 May 2004 08:14 pm, John Check wrote: > On Thursday 06 May 2004 05:45 am, Robert Jonsson wrote: > > > - List editor doesn't allow me to insert arbitrary controllers (I would > > > like to create slurs like is described in > > > http://www.borg.com/~jglatt/tutr/slur.htm - but list editor seems not > > > to accept controllers 100 and 101) or there is another way of doing > > > this? > > > > There was another another report about this too, Sadly I'm pretty > > midi-illiterate when it comes to the advanced stuff, but I am keen to > > learn. I'll try it out myself. > > Slurs are like portamento without the transition time (AKA "glide"). IIRC > as far as the midi stream goes all controllers have the same format so > supporting the controller is no biggie. > Implementing slurs inside MusE would be not unlike implementing monophonic > rythm groups, except theres no way to get around the attack phase of the > notes. > Read the supplied link and it reminds me that a stacatto/legato algorithm is something else MusE is lacking. Basically, either refers to the percentage of space between the notes. |
From: Emiliano G. <emi...@po...> - 2004-05-07 08:04:31
|
gioved=EC, 06 maggio 2004 alle 20:45:46, John Check ha scritto: > On Thursday 06 May 2004 08:14 pm, John Check wrote: > > On Thursday 06 May 2004 05:45 am, Robert Jonsson wrote: > > > > - List editor doesn't allow me to insert arbitrary controllers (I > > > > would like to create slurs like is described in > > > > http://www.borg.com/~jglatt/tutr/slur.htm - but list editor seems > > > > not to accept controllers 100 and 101) or there is another way of > > > > doing > > > > this? > > > > > > There was another another report about this too, Sadly I'm pretty > > > midi-illiterate when it comes to the advanced stuff, but I am keen = to > > > learn. I'll try it out myself. > > > > Slurs are like portamento without the transition time (AKA "glide"). > > IIRC as far as the midi stream goes all controllers have the same > > format so supporting the controller is no biggie. Implementing slurs > > inside MusE would be not unlike implementing monophonic rythm groups, > > except theres no way to get around the attack phase of the notes. > > >=20 > Read the supplied link and it reminds me that a stacatto/legato algorit= hm > is something else MusE is lacking. Basically, either refers to the > percentage of space between the notes.=20 On the link that I reported the legato is done with the pitch, as it is t= he most secure method (all synths support it) for going from one note to another without space between notes, and skipping the attack part. This i= s useful especially for string passages. The problem in muse is that there is no way to insert controllers 100 and 101 (which define the pitch wheel range) - IIUC, this should be easy to f= ix in the list editor window... The algorithm you are talking is like the function called "note force legato" in logic? With this function the end of every note is taken ahead until the start of the next note. Rosegarden has something similar, IIRC. This can emulate the piano legato, but for instruments such as strings, violin, etc... you want the attack part being played only by the first of the legato notes. Best regards, --=20 Emiliano Grilli Linux user #209089=20 http://www.emillo.net |
From: Robert J. <rob...@da...> - 2004-05-06 09:55:53
|
Hi, > > BTW, will it load the old muse file ? Maybe should I wait a little if > > this aspect matters ? > > No, it won't. Song format has changed. I'd suggest exporting to standard > midifile with an older version before moving to the new. I don't beleive > addressing this is a priority. For pure midi projects this should work pretty good. Werner has talked about providing a utility to convert songs. I imagine a scripted solution would work very well for this... mmmm... I'm almost thinking about looking into this ;) But, as John points out, this is probably not a priority yet. > > > Thks everybody for the continous work, it's very impressive ! Thanks! This is hopefully only the beginning ;) /Robert |
From: Linium <in...@ne...> - 2004-05-07 20:09:10
|
On Jeudi 6 Mai 2004 11:51, Robert Jonsson wrote: > Werner has talked about providing a utility to convert songs. I imagine a > scripted solution would work very well for this... mmmm... I'm almost > thinking about looking into this ;) > > But, as John points out, this is probably not a priority yet. What scripting language would you use ? I know a little gawk, but not enough to do it myself. I don't know at all how hard such a converter would be to do. BTW, do you now if it is possible to have both muse versions on the same system ? May be the "prefix" option at compile time should be enough for them not to confuse the softsynthi and other shared files ? Cheers, Linium |
From: Robert J. <rob...@da...> - 2004-05-07 20:17:43
|
Friday 07 May 2004 20.47 skrev Linium: > On Jeudi 6 Mai 2004 11:51, Robert Jonsson wrote: > > Werner has talked about providing a utility to convert songs. I imagine a > > scripted solution would work very well for this... mmmm... I'm almost > > thinking about looking into this ;) > > > > But, as John points out, this is probably not a priority yet. > > What scripting language would you use ? I'm just a beginner at scripting, what I do know is that perl is something you either love or hate. I hate it. Python looks very nice and very easy. > I know a little gawk, but not enough to do it myself. I don't know at all > how hard such a converter would be to do. I had a quick look. Saved two files with similar configuration in both muse0.6.3 and muse0.7pre2 and alot of the stuff is still the same. The things that differ require some work but it does not look impossible.... with Werners help it would be quite doable. > > BTW, do you now if it is possible to have both muse versions on the same > system ? May be the "prefix" option at compile time should be enough for > them not to confuse the softsynthi and other shared files ? Yes, quite possible. Infact I have one installed in --prefix=/usr (old muse from thac rpms) and one in --prefix=/usr/local (the one I'm working on). MusE has a few dynamically loaded modules but MusE is smart (ofcourse it has nothing to do with intelligence, rather the opposite) enough to figure out which libraries belong to it. So there should be nothing to worry about. /Robert |
From: Robert J. <rob...@da...> - 2004-05-06 11:14:11
|
On Thursday 06 May 2004 12.28, Emiliano Grilli wrote: > gioved=EC, 06 maggio 2004 alle 11:45:34, Robert Jonsson ha scritto: > > Hi Emiliano, > > > > > IIUC the development has been "splitted" into old muse and this new > > > branch. IMHO one of the most exciting features of the new version is > > > the jack_transport implementation: I've played a lot in perfect sync > > > with hydrogen and I've got real fun :) > > > Do you think that this feature can be "backported" to the old branch? > > > Or do you plan to leave completely 0.6.3 as the last version of that > > > branch? > > > > The quick answer is no, there is too little manpower to keep going in t= wo > > directions. But read on for other solutions. > > > > The development was split, but it was a temporary solution to be able to > > produce one more release in the 0.6 series (that in the end became two > > releases). > > Almost everything that was implemented into the last releases of MusE > > 0.6.3 is meant to be available in 0.7. Notable exceptions are: > > > > - no alsa mode > > - no midi only mode (both these where removed to simplify the > > architecture and make MusE more stable) > > This is one of the missing features, imagine one that, for one reason or > another can't eun jack: he can't use muse at all... this is the case of my > ibook, where jack is not as smooth as it is on my athlon machine. Ok, could you describe the problems? If we can make jack run everywhere tha= t=20 would make the problem go away :) Though, since an ibook is big endian I imagine there still are bugs lurking= =2E=20 Big endian systems sadly don't get as much testing as little endian=20 systems. :-/ Though...there is actually a dummy audio-output in MusE, but I don't think = it=20 is stable and meant to be used for anything else but testing... > > > - no score (I think Werner was not fully satisfied with what could be > > achieved) > > This leads me to the main question. What is it that you miss in the new > > MusE that means you wish for a backport? > > The main stopper that prevents me to use muse on my "stable" system is the > requirement for qt 3.2 (my stable system is RH8+PlanetCCRMA), so I tried = it > under debian sid, and all went fine... True, but this just means that it's time for you to upgrade ;-) Regards, Robert |
From: Emiliano G. <emi...@po...> - 2004-05-06 13:13:22
|
gioved=EC, 06 maggio 2004 alle 13:09:21, Robert Jonsson ha scritto: > > > - no midi only mode (both these where removed to simplify the > > > architecture and make MusE more stable) > > This is one of the missing features, imagine one that, for one reason > > or another can't eun jack: he can't use muse at all... this is the ca= se > > of my ibook, where jack is not as smooth as it is on my athlon machin= e. =20 > Ok, could you describe the problems? If we can make jack run everywhere > that would make the problem go away :) I have experience that USB devices doesn't work well with jack, or at lea= st they doesn't work well without hard tweaking of the .asoundrc file. On th= e ibook there is no input, so you have to run jack in playback-only mode, a= nd the performance is not as good as it is on i386. =20 > Though, since an ibook is big endian I imagine there still are bugs > lurking. Big endian systems sadly don't get as much testing as little > endian systems. :-/ The only problem I had with muse (exporting bad midifiles) was solved som= e time ago thanks to you ;) =20 > Though...there is actually a dummy audio-output in MusE, but I don't > think it is stable and meant to be used for anything else but testing..= =2E This has remind me that also in jack there is a dummy device, and using that you end up with a MIDI-only muse ;) so... this problem is solved (I have to try but suppose that works this way) > > > - no score (I think Werner was not fully satisfied with what could = be > > > achieved) This leads me to the main question. What is it that you > > > miss in the new MusE that means you wish for a backport? > > > > The main stopper that prevents me to use muse on my "stable" system i= s > > the requirement for qt 3.2 (my stable system is RH8+PlanetCCRMA), so = I > > tried it under debian sid, and all went fine... >=20 > True, but this just means that it's time for you to upgrade ;-) It's true.. but PlanetCCRMA is a great meta distro, and now my RH8 works like a swiss clock, I'm sad to leave it ;) > Regards, > Robert Ciao --=20 Emiliano Grilli Linux user #209089=20 http://www.emillo.net |
From: Robert J. <rob...@da...> - 2004-05-06 13:56:12
|
Hi, > > > Though...there is actually a dummy audio-output in MusE, but I don't > > think it is stable and meant to be used for anything else but testing... > > This has remind me that also in jack there is a dummy device, and using > that you end up with a MIDI-only muse ;) so... this problem is solved (I > have to try but suppose that works this way) That would be good if you tried it, for several reasons. I talked to Joachim Schiele the other day and he was trying MusE in this configuration with external midi equipment. He was however experiencing frequent crashes, not good :-/. One possibility is that MusE has timing problems with jack running in dummy mode and failed to handle it gracefully. If it is we need to know. /Robert |
From: Linium <in...@ne...> - 2004-05-06 14:29:09
|
On Jeudi 6 Mai 2004 15:13, Emiliano Grilli wrote: > > > The main stopper that prevents me to use muse on my "stable" system is > > > the requirement for qt 3.2 (my stable system is RH8+PlanetCCRMA), so I > > > tried it under debian sid, and all went fine... > > > > True, but this just means that it's time for you to upgrade ;-) > > It's true.. but PlanetCCRMA is a great meta distro, and now my RH8 works > like a swiss clock, I'm sad to leave it ;) May be you can compile qt3.2 alongside with your other qt3 installation, and keep RH8 ? For sure at the compile time you should be able to give argument for the location of the newer qt. Then at launch time, it should be possible to give some commands (some LD PRELOAD things ?), if ever the executable were not able to use the right qt ? Cheers, Linium |
From: Robert J. <rob...@da...> - 2004-05-06 14:39:48
|
On Thursday 06 May 2004 16.36, Linium wrote: > On Jeudi 6 Mai 2004 15:13, Emiliano Grilli wrote: > > > > The main stopper that prevents me to use muse on my "stable" system > > > > is the requirement for qt 3.2 (my stable system is RH8+PlanetCCRMA), > > > > so I tried it under debian sid, and all went fine... > > > > > > True, but this just means that it's time for you to upgrade ;-) > > > > It's true.. but PlanetCCRMA is a great meta distro, and now my RH8 works > > like a swiss clock, I'm sad to leave it ;) > > May be you can compile qt3.2 alongside with your other qt3 installation, > and keep RH8 ? > For sure at the compile time you should be able to give argument for the > location of the newer qt. Then at launch time, it should be possible to > give some commands (some LD PRELOAD things ?), if ever the executable were > not able to use the right qt ? Indeed. You can do this like this (if I remember correctly): 1. get qt3.2 or newer in source form (might aswell go for qt3.3 ) 2. unpack it and run ./configure -thread -prefix=/the/path/you/want/it 3. do 'make' and 'make install' 3. set environment variable QTDIR to point to this location e.g. export QTDIR=/the/path/you/want/it 4. run ./configure with your favourite switches in the muse dir muse should now pick up the correct QT version and use it during compilation. Note: it might be a good idea to do ./configure --prefix=/a/separate/muse/path if you want the new muse to not affect your current install 5. do 'make' and 'make install' 6. try it: $> /a/separate/muse/path/bin/muse And report back :) /Robert > > Cheers, > > Linium > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |
From: John C. <j4s...@bi...> - 2004-05-07 00:17:47
|
On Thursday 06 May 2004 09:02 am, Emiliano Grilli wrote: > gioved=EC, 06 maggio 2004 alle 12:37:16, Robert Jonsson ha scritto: > > > Which ones? > > > Can you point me to an URL? > > > > It seems I was mistaking. I thought about rhythm patterns. > > For this there are: > > http://gmorgan.sourceforge.net/ > > http://www.kootenay.com/~bvdpoel/mma/mma.html > > Yes, I know these but they are arrangers... I mean something where = you can > define the "groove" of your quantisation (eg slightly shift the 3rd= beat > ahead and so on) - I think cubase calls that "DNA grooves" or somet= hing > like this... Think of a "programmable humanization mask" :) > Basically it's swing applied in beat increments with a "master track" to hold the specific overall pattern The path to implementation starts with simple swing > Of course, it would be great also to save these templates, to build= a > library that should be shipped with the program. I would love to ha= ve > various types of swing, shuffles, waltz, etc... to try on my sequen= ces. > Most of the MIDI editing is concerning the positions of the notes, = and so > having more functions to vary the position (in a musical way) for m= e would > be a big plus. A more advanced improvement can be adding to these t= emplates > a "random factor" (eg define an horizontal range in which the note = can > fall) > > The same method can be applied to other parameters, such as velocit= y or > controllers, but for a start, just being able to control the positi= on of > the notes in a programmable/editable way is a must for a sequencer = IMHO, > because fixed quantisation is useful, but only for certain musical > genres... and the only way to give an human feel to a MIDI track, f= or now > is to edit in a note-by-note basis, which you have to admit, is not= so > comfortable ;) Re quantization - Yes and no. The whole trick to making convincing se= quences=20 is not to go too far in the editing. If you quantize with a broad bru= sh it's=20 limited. Without swing/groove templates it's just a lot more work. Fi= ne=20 tuplets (BTW ones other than triplets would be awesome) and dotted no= tes can=20 get you where you need to go feel-wise > > > /Robert > > Cheers, |
From: John C. <j4s...@bi...> - 2004-05-07 00:19:50
|
On Thursday 06 May 2004 10:36 am, Linium wrote: > On Jeudi 6 Mai 2004 15:13, Emiliano Grilli wrote: > > > > The main stopper that prevents me to use muse on my "stable" system > > > > is the requirement for qt 3.2 (my stable system is RH8+PlanetCCRMA), > > > > so I tried it under debian sid, and all went fine... > > > > > > True, but this just means that it's time for you to upgrade ;-) > > > > It's true.. but PlanetCCRMA is a great meta distro, and now my RH8 works > > like a swiss clock, I'm sad to leave it ;) > > May be you can compile qt3.2 alongside with your other qt3 installation, > and keep RH8 ? > For sure at the compile time you should be able to give argument for the > location of the newer qt. Then at launch time, it should be possible to > give some commands (some LD PRELOAD things ?), if ever the executable were > not able to use the right qt ? > Bleaaugh.. Statically linked binaries would be more inviting, even if they are huge. > Cheers, > > Linium > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |
From: John C. <j4s...@bi...> - 2004-05-08 01:31:08
|
On Friday 07 May 2004 02:47 pm, Linium wrote: > On Jeudi 6 Mai 2004 11:51, Robert Jonsson wrote: > > Werner has talked about providing a utility to convert songs. I imagine a > > scripted solution would work very well for this... mmmm... I'm almost > > thinking about looking into this ;) > > > > But, as John points out, this is probably not a priority yet. > > What scripting language would you use ? > I know a little gawk, but not enough to do it myself. I don't know at all > how hard such a converter would be to do. > > BTW, do you now if it is possible to have both muse versions on the same > system ? May be the "prefix" option at compile time should be enough for > them not to confuse the softsynthi and other shared files ? > > Cheers, > > Linium > I haven't had both from scratch but I've had multiple versions installed. One from debian, one from CVS. > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |
From: John C. <j4s...@bi...> - 2004-05-08 02:25:31
|
On Friday 07 May 2004 04:17 pm, Robert Jonsson wrote: > Friday 07 May 2004 20.47 skrev Linium: > > On Jeudi 6 Mai 2004 11:51, Robert Jonsson wrote: > > > Werner has talked about providing a utility to convert songs. I imagine > > > a scripted solution would work very well for this... mmmm... I'm almost > > > thinking about looking into this ;) > > > > > > But, as John points out, this is probably not a priority yet. > > > > What scripting language would you use ? > > I'm just a beginner at scripting, what I do know is that perl is something > you either love or hate. I hate it. > > Python looks very nice and very easy. > > > I know a little gawk, but not enough to do it myself. I don't know at all > > how hard such a converter would be to do. > > I had a quick look. Saved two files with similar configuration in both > muse0.6.3 and muse0.7pre2 and alot of the stuff is still the same. The > things that differ require some work but it does not look impossible.... > with Werners help it would be quite doable. > Translating XML shouldn't be a big deal. That's the beauty of XML. > > BTW, do you now if it is possible to have both muse versions on the same > > system ? May be the "prefix" option at compile time should be enough for > > them not to confuse the softsynthi and other shared files ? > > Yes, quite possible. > Infact I have one installed in --prefix=/usr (old muse from thac rpms) and > one in --prefix=/usr/local (the one I'm working on). MusE has a few > dynamically loaded modules but MusE is smart (ofcourse it has nothing to do > with intelligence, rather the opposite) enough to figure out which > libraries belong to it. So there should be nothing to worry about. > > /Robert > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |