From: nilitonilito n. <nil...@ho...> - 2008-01-18 15:58:42
|
Hi there, What is the current status of vst support in MusE 2? I saw a parameter to set at ON in the CMakeLists to enable vst and vst.h/cp= p source files. But I could not manage to make that work. Is it coded yet? if yes how to make it work? if not what is, roughly, the r= emain coding task to complete it support. Thanks Cheers Nil P.S : I'm usually not a fan of VST and prefer to use linux plugins but ther= e is this outstanding VST piano emulator, PianoTeq, that works perfectly we= ll under linux. _________________________________________________________________ Nouveau ! Cr=E9ez votre profil Messenger ! http://home.services.spaces.live.com/= |
From: Werner S. <ws...@se...> - 2008-01-18 20:16:29
|
Hi Nil, long time ago i demonstrated some VST plugins with MusE II. So i think the = code is there. It worked with some ancient wine version. I dont know the current= status because i had not compiled it for ages. There is also DSSI support which works for me (i just checked the "hexter" = dx7 synth). DSSI also has a a VST wrapper for VST. Compiling/Installing worked. MusE sh= ows all installed VST plugins but crashes when selecting on. So it looks that there= is some debugging needed. Regards, Werner On Freitag 18 Januar 2008, nilitonilito nilitonilito wrote: > > Hi there, > > What is the current status of vst support in MusE 2? > > I saw a parameter to set at ON in the CMakeLists to enable vst and vst.h/= cpp source files. But I could not manage to make that work. > > Is it coded yet? if yes how to make it work? if not what is, roughly, the= remain coding task to complete it support. > > Thanks > > Cheers > Nil > > P.S : I'm usually not a fan of VST and prefer to use linux plugins but th= ere is this outstanding VST piano emulator, PianoTeq, that works perfectly = well under linux. > > _________________________________________________________________ > Nouveau ! Cr=E9ez votre profil Messenger ! > http://home.services.spaces.live.com/ > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |
From: Mathias L. <mat...@da...> - 2008-01-19 10:25:34
|
MusE 2, I like that name. Sounds much better than 'unstable MusE', or 'development branch MusE'. I haven't followed the lists closely lately, perhaps this is what people call it but it's the first time I spot the name 'MusE 2'. Any way, MusE 2, I like it. Sounds good. /Mathias Werner Schweer skrev: > Hi Nil, > > long time ago i demonstrated some VST plugins with MusE II. So i think the code > is there. It worked with some ancient wine version. I dont know the current status > because i had not compiled it for ages. > > There is also DSSI support which works for me (i just checked the "hexter" dx7 synth). > DSSI also has a a VST wrapper for VST. Compiling/Installing worked. MusE shows all > installed VST plugins but crashes when selecting on. So it looks that there is some > debugging needed. > > Regards, > Werner > > > On Freitag 18 Januar 2008, nilitonilito nilitonilito wrote: > >> Hi there, >> >> What is the current status of vst support in MusE 2? >> >> I saw a parameter to set at ON in the CMakeLists to enable vst and vst.h/cpp source files. But I could not manage to make that work. >> >> Is it coded yet? if yes how to make it work? if not what is, roughly, the remain coding task to complete it support. >> >> Thanks >> >> Cheers >> Nil >> >> P.S : I'm usually not a fan of VST and prefer to use linux plugins but there is this outstanding VST piano emulator, PianoTeq, that works perfectly well under linux. >> >> _________________________________________________________________ >> Nouveau ! Créez votre profil Messenger ! >> http://home.services.spaces.live.com/ >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Lmuse-developer mailing list >> Lmu...@li... >> https://lists.sourceforge.net/lists/listinfo/lmuse-developer >> >> > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |
From: Frank N. <bea...@we...> - 2008-01-19 18:04:47
|
Hi list, Mathias Lundgren <mat...@da...> wrote: > MusE 2, I like that name. Sounds much better than 'unstable MusE', or > 'development branch MusE'. I haven't followed the lists closely lately, > perhaps this is what people call it but it's the first time I spot the > name 'MusE 2'. Any way, MusE 2, I like it. Sounds good. I like that sound, too - though there never was a real "MusE 1", was there? Then again, this is perhaps just history repeating - the same happened to Ardour (0.99.3 -> 2.0). Maybe that's a good sign? :-) Greetings, Frank |
From: Robert J. <rj...@sp...> - 2008-01-19 19:31:47
|
Frank Neumann wrote: > Hi list, > Mathias Lundgren <mat...@da...> wrote: > > >> MusE 2, I like that name. Sounds much better than 'unstable MusE', or >> 'development branch MusE'. I haven't followed the lists closely lately, >> perhaps this is what people call it but it's the first time I spot the >> name 'MusE 2'. Any way, MusE 2, I like it. Sounds good. >> > > I like that sound, too Indeed. MusE 2 ... smells good! > - though there never was a real "MusE 1", was there? > Then again, this is perhaps just history repeating - the same happened to > Ardour (0.99.3 -> 2.0). Maybe that's a good sign? :-) > Hehe... not sure that's a good indicator ;-) Anyhow, Werner has actively changed the new codebase to 2.0 so that's what it is! And there WILL be an 1.0 release in the old tree, there's still work being done in that branch... Life is a bit hectic so I'm not sure when it will actually happen but when Tim has checked in his latest set of changes we might be getting close! Regards, Robert > Greetings, > Frank > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |
From: Tim <ter...@us...> - 2008-01-23 05:20:20
|
> Indeed. MusE 2 ... smells good! > > - though there never was a real "MusE 1", was there? > > Then again, this is perhaps just history repeating - the same happened to > > Ardour (0.99.3 -> 2.0). Maybe that's a good sign? :-) > Life is a bit hectic so I'm not sure when it will actually happen but > when Tim has checked in his latest set of changes we might be getting > close! Howdy all. Yes, still alive. Ok I'm an idiot. I shouldn't have announced commits 2 weeks ago and still not committed them. That will teach me to wait until all is really fixed. Really though, next day or two, no kidding... Been working very hard at it every day (that's why I'm so quiet). Some of these fixes were VERY difficult to lay down. More highlights (see my last post): *Added/fixed proper auto scroll for lasso, parts, and events - both horizontal AND vertical scrolling, even past the end of parts. *Fixed 'end of part' drawing problems - now you are guaranteed to see at least 1+1/4 extra bar after the end of a pianoroll/drumedit (also compensating for drumedit drummap/canvas splitter!), thereby allowing you to add/move/clone more notes past the end and allowing muse to properly auto-extend the part. *Fixed drawing of wave parts in arranger. I've been hungry for this so long! Now you can rely on the 'picture' of the wave inside the part lining up correctly with the time scale, regardless of tempo/timesig changes in the song! *More fixes to wave editor. *Geoff pointed out the multiple-part viewing in the pianoroll, which prompted me to correct the drawing order of events from ALL parts in the editor. *Lots of other 'unseen' fixes, especially drawing. PS: I know it's only been a few weeks since I said we should keep Muse 0+1, but you know, I like the sound of Muse 1 and Muse 2 too! Talk to you soon... Tim |
From: Geoff B. <son...@bi...> - 2008-01-23 19:46:29
|
can't wait. i'll be here.. drooling as usual :D sounds like some more really good stuff Tim. MusE lives ! best, g. |
From: Mathias L. <mat...@da...> - 2008-01-23 09:32:57
|
Tim skrev: >> Indeed. MusE 2 ... smells good! >> >>> - though there never was a real "MusE 1", was there? >>> Then again, this is perhaps just history repeating - the same happened to >>> Ardour (0.99.3 -> 2.0). Maybe that's a good sign? :-) >>> >> Life is a bit hectic so I'm not sure when it will actually happen but >> when Tim has checked in his latest set of changes we might be getting >> close! >> > Howdy all. Yes, still alive. Ok I'm an idiot. I shouldn't have announced > commits 2 weeks ago and still not committed them. That will teach me to wait > until all is really fixed. Really though, next day or two, no kidding... > Been working very hard at it every day (that's why I'm so quiet). > Some of these fixes were VERY difficult to lay down. > > More highlights (see my last post): > *Added/fixed proper auto scroll for lasso, parts, and events - > both horizontal AND vertical scrolling, even past the end of parts. > *Fixed 'end of part' drawing problems - now you are guaranteed to see > at least 1+1/4 extra bar after the end of a pianoroll/drumedit (also > compensating for drumedit drummap/canvas splitter!), thereby > allowing you to add/move/clone more notes past the end and allowing > muse to properly auto-extend the part. > *Fixed drawing of wave parts in arranger. I've been hungry for this so long! > Now you can rely on the 'picture' of the wave inside the part lining up > correctly with the time scale, regardless of tempo/timesig changes in the > song! > w00t!! That's one I'll be happy over!!! > *More fixes to wave editor. > *Geoff pointed out the multiple-part viewing in the pianoroll, which prompted > me to correct the drawing order of events from ALL parts in the editor. > *Lots of other 'unseen' fixes, especially drawing. > > PS: I know it's only been a few weeks since I said we should keep Muse 0+1, > but you know, I like the sound of Muse 1 and Muse 2 too! > > Talk to you soon... Tim > > Apart from this, I've actually been using the CVS-sources for MusE lately. Trying to put together midi backgrounds in order to make backgrounds for a "live" gig. I've stumbled upon a few problems though when doing this type of work (which I usually don't do). These are the problems I'm having with CVS muse, which aren't there in 0.9.2-pre something: - There was a need for removing note overlaps, caused dead notes with fluidsynth. This function has now been added to the pianoroll and commited. - I haven't managed to import a midi file (segfaults, haven't had the time investigating) - Weird problems with the mixer values. Those midi files usually come with program changes, volume changes, reverb/chorus etc coded into the file. After removing these via list editor I can still see that MusE sometimes changes these values (usually when moving the locator) although I can never find any of these controller values/program changes in the list editors! The problem is still there if I reopen the song etc. And no, I don't use mixer automation. - The values of the mixer are not updated upon opening of the project (moving one of the sliders causes a refresh of them, but the values are not the same as when I saved the project). - I can even add volume and other controller values to parts and neither the mixer nor the actual audio seems to come through to the synth. BTW, I've been using fluidsynth for all this stuff. It complains a lot about not being able to handle a lot of controller values on startup. Perhaps this is what is the problem - that the controller values have changed (might have to do with automation I guess). Hopefully I'll be able to fix some of these issues down myself but I'd be interested in hearing if other ppl have problems like these themselves. Perhaps someone else knows what might actually be the source of the problem. Right now my previous version is more usable - it's just that it lacks the 'delete overlaps'-function. :) Oh, and only one more. I really miss the previous functionality of the space-button (first stop, then rewind to nearest locator backwards if any, then rewind to beginning of song). Now I need to use two buttons to stop and rewind to locator instead of quickly double-pressing space. But any way - there has been quite a lot of good things that has been added since I was last around. I'm still soo happy about the soloing fixes. It really saves time and gives me a better mood! One thing that I also would love is to have the possibility to call some shell script/external command that would perform operations on selected notes and return. It would give MusE a very flexible way to implement f.ex. groove stuff. The realtime midi filters in MusE 2 is one thing that could do this, but sometimes you want to do more batchlike work. It would also be possible to wrap the functionality of the MusE2 midi filters in an external command to use them in batch mode. Is anyone else interested in this functionality as well? /Mathias |
From: Geoff B. <son...@bi...> - 2008-01-23 19:51:28
|
On Wednesday 23 January 2008 20:32:30 Mathias Lundgren wrote: > Oh, and only one more. I really miss the previous functionality of the > space-button (first stop, then rewind to nearest locator backwards if > any, then rewind to beginning of song). Now I need to use two buttons to > stop and rewind to locator instead of quickly double-pressing space. that was my fault mathias; Robert did the spacebar start/stop thing to stop me complaining and I'm very glad he did ! BUT, there is a checkbox for the old behaviour @ settings>GUI>'Use old style stop shortcut'. hth, g. |
From: Geoff B. <son...@bi...> - 2008-01-23 20:27:35
|
I'd love to know what the midi transformator is capable of and how it's supposed to work. can someone tell me ? if not, can someone explain it on the wiki or something. I need to remove duplicates etc and i imagine that this tool can do it ( and much else besides ) but i just can't begin to see how it works. also the program change pane in the piano roll doesn't list any numbers. how is that supposed to work ? am i missing something there too ? a power user needs these features and i'm sure you can do it so any help most appreciated. best, g |
From: Mathias L. <mat...@da...> - 2008-01-24 10:11:46
|
I remember doing something with the transformer a long while ago. At that time I think I found out that it works for most things but some things just doesn't work. Perhaps it was just that I didn't understand it, but I remember trying to figure it out from the source. It was a long time ago anyway. Nowadays I would like to be able to do those kind of things via external scripts/commands. Geoff Beasley skrev: > I'd love to know what the midi transformator is capable of and how it's > supposed to work. can someone tell me ? if not, can someone explain it on the > wiki or something. I need to remove duplicates etc and i imagine that this > tool can do it ( and much else besides ) but i just can't begin to see how it > works. > > also the program change pane in the piano roll doesn't list any numbers. how > is that supposed to work ? am i missing something there too ? > > a power user needs these features and i'm sure you can do it so any help most > appreciated. > > best, > > g > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |
From: Mathias L. <mat...@da...> - 2008-01-24 10:08:02
|
Geoff Beasley skrev: > > On Wednesday 23 January 2008 20:32:30 Mathias Lundgren wrote: > > > Oh, and only one more. I really miss the previous functionality of the > > > space-button (first stop, then rewind to nearest locator backwards if > > > any, then rewind to beginning of song). Now I need to use two buttons to > > > stop and rewind to locator instead of quickly double-pressing space. > > that was my fault mathias; Robert did the spacebar start/stop thing to > stop me complaining and I'm very glad he did ! BUT, there is a > checkbox for the old behaviour @ settings>GUI>'Use old style stop > shortcut'. > Ah, yes, it's those things where everyone has their own taste. I would have known if I had followed the discussions around here, but he told me yesterday. Great to have that checkbox! /Mathias |
From: Tim <ter...@us...> - 2008-01-27 05:34:23
|
On Wednesday 23 January 2008 04:32:30 am you wrote: > Apart from this, I've actually been using the CVS-sources for MusE > lately. Trying to put together midi backgrounds in order to make > backgrounds for a "live" gig. I've stumbled upon a few problems though > when doing this type of work (which I usually don't do). > > These are the problems I'm having with CVS muse, which aren't there in > 0.9.2-pre something: >... > /Mathias I am happy to report that I started CVS muse, and imported a MIDI file: "Right Now by Van Halen sequenced by Chiqui Abello " It consists of 17 tracks, and it's a complete version, not bad. I slapped on a fluidsynth of the Creative 4MB SF, turned on reverb and chorus in the fluidsynth loader gui, adjusted the reverb level to my liking, away we went. Played beautifully. Also, controller events worked fine, as heard in the solo etc. And I could see MIDI mixer strip sliders moving. Also tested reverb and chorus mixer knobs, which were enabled and automatically set at the right levels, in this song. Pleasantly surprised to see all working OK. Opened controller graphs in the editors, all looked OK. Even the MIDI device was already set on GM for me! It couldn't have gone more smoothly, I think. (I played that song way back in muse 0.8.1, too). Granted, there were a lot of messages like this: FluidSynth::setController() - error processing controller event: Ctrl out of range when loading the song, and this appeared once when starting the song: fluidsynth: error: There is no preset with bank number 255 and preset number 0 in SoundFont 1 FluidSynth::setController() - Error changing program on soundfont There is no preset with bank number 255 and preset number 0 in SoundFont 1, channel: 7 But I don't see a big problem. Mat, there may indeed be a problem with the event list editor, I don't use it a lot, but it seems to work OK for me, adding all kinds of controllers and even other types of events. Maybe with deleting events? And the 'Edit Controller Event' window (click 'Insert Event') has a few bugs. Interesting window. Who designed it? They seemed to put a lot of work into it. ** You know guys, I would really like to make all those MIDI mixer strip VU level meters come alive. They're just dead. I looked at the code way back last year, and it basically doesn't do much to try to make them light up. It was like a short 'gutted' version of the audio mixer strip VU code. Mat? Robert? Werner? What you think. You remember the code? He, he... |