From: webhead <we...@pa...> - 2005-01-24 15:13:32
|
Mathias Lundgren wrote: >l=F6r 2005-01-22 klockan 03.05 skrev webhead: > =20 > >>Hi all, >> >>Concerning that MC505 idf: >>Apparently, the only problem I have is getting the drums channel to=20 >>work. It would seem that the drums are on channel 0 (?). Whenever I=20 >>record some events it plays back correctly but editting them only give= s=20 >>none-drum sounds. I'll probably look some more at the midi data to=20 >>figure this out. >> >> >>Other problems are: >>1) recording/playing midi data gives double sound, obviously I need to=20 >>switch off the midi thru on muse, so far I'm avoiding this by pulling=20 >>cables :( >> =20 >> > >Hi! > >Have you tried using the midi input filter? There's a thru filter there >to the right. Now I'm not completely sure that it's working 100% as of >today, because of MusE's new internal controller handling, and I'm not a >midi expert so I'm actually not sure exactly how it is supposed to work. >Would be happy if someone could give me some hints. I know that people >have successfully turned off midi thru sometime in the past, but things >might have changed since then... > =20 > I'm not quite sure how that thing works... Maybe I need to twiddle it a=20 bit to figure it out... > =20 > >>2) recording midi data of an instrument on a track gives all channels i= n=20 >>1 track, I'd like to get all instrument channels on their own track, ca= n=20 >>this be done at recording time or post-recording, without actually=20 >>having to cut the several tunes out of the one track ? >> =20 >> > >You want midi data from different midi input channels to different midi >tracks? I think the answer is that this is not possible to do currently, >in the 0.7-series. Werner is working on a new list editor in the >0.8-branch where it's possible to do a lot of things, perhaps this would >be possible there. If it works there, it would be post-recording of >course.. If not, I guess it wouldn't be that difficult to implement a >specific post-rec function that would do what you're asking for.=20 > > =20 > >>3) pressing play on my MC505 with muse synced does not initiate play,=20 >>neither does muse start recording when I press the MC505's play button,= =20 >>I really need to record midi with the clocks in sync... >> >> =20 >> > >Midi clock sync is an issue that there's been some work on lately. >Actually, in the cvs for the 0.7-branch it works somewhat to use MusE as >slave, but it's not stable (the sync might run fine for several minutes, >but in some situations the algorithm unbalances itself. changing >position while running is not the best thing to do either ...). The new >clock-sync stuff has as of today worked, in it's current state, for at >least 3 persons, all of them with different setups. When I get the time >(as soon as possible) I'll try to improve the algorithm for the sync, >which is quite crude right now, and is probably the main source for the >problems. > > =20 > For some reason, pressing the jump buttons (to switch to a different=20 measure) on my MC505 does indeed move the cursor (well, the red=20 line/arrow thingy) around. It's not quite as it should be though,=20 instead of moving forward it moves three parts forward and then jumps bac= k. Anyhow, the main problem here is, and I think this IS the main reason=20 you want muse to be a slave, is to start recording as soon as I press=20 play on an instrument. That way, the midi data appears at the start of a=20 track and should be nicely laid out... >If you don't want to build cvs yourself (autoconf/automake/libtool et al >can be hopeless sometimes), I've made a package which includes the >latest midi clock sync updates. You'll find it here: >http://mattematik.is-a-geek.com/linuxmusic/files/muse-0.7.1-synctest.tar= .gz > > > =20 > I'll try that, thank you. >>Sorry about these maybe trivial problems but I couldn't figure it out=20 >>with the documentation at hand. >> >> =20 >> > >I don't think they're trivial at all, you're right on the weak spots. If >you try any of the above, I'd be very happy if you could give us some >more reports on your proceedings. > > =20 > Well, I've never liked computers for actually composing the music, the=20 tunes and paterns all get sequenced on the instruments themselves, after=20 all, they're short repetitive parts, no hassle and I prefer a 'hands on'=20 method here. Computers come in real handy when working on the song structure which is=20 much less visual on the instruments themselves. Also, as a song consists=20 of large structures, keeping an overview and the ability to move big=20 pieces around is just impossible on some of the instruments. A great=20 feature would be to be able to tune in volumes and panning, visually=20 over the track (think Cool Edit). Often when I record some intruments=20 (guitar for instance) it's natural to mess up a part here and there, for=20 now I can splice and remove certain parts which works but isn't exactly=20 user friendly. I do believe that was being worked on, right? I've never found a neat sequencer for paterns btw, or something to=20 compose and use an arpegiator... Don't get me wrong here, I'm happy something such as muse even exists,=20 at least I'm not being forced into a windows enviroment this way :) Thanks! >/Mathias > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting >Tool for open source databases. Create drag-&-drop reports. Save time >by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. >Download a FREE copy at http://www.intelliview.com/go/osdn_nl >_______________________________________________ >Lmuse-user mailing list >Lmu...@li... >https://lists.sourceforge.net/lists/listinfo/lmuse-user > > =20 > --=20 This email has been sent as a form of communication.=20 The fact that communication is generally perceived as more pleasant when = it takes place in both directions is widely accepted.=20 Thus, a reply would be appreciated and highly recommended for future rela= tions. --- http://www.webheadology.info/ --> for seekers of enlightment around the g= lobe ... |