From: teknopaul h. <tek...@gm...> - 2012-03-14 20:46:27
|
Hi lmms-dev, anyone out there? I fixed this problem and started on the next. I have now worked around midi crashes by implementing a Null Instrument which works well. I have LMMS talking to Windows by implementing midicast in LMMS as a plugin, again quite hacky as an Instrument since I cant find any other plugin handles. I have Jack Transport working kind of, it crashes if you restart the process but it starts and stops LMMS with Hydrogen which is what I needed. Next is Swing/Groove and this really does involve working inside LMMS no option to do a plugin there so I would appreciate a bit of advice, I dont want to write a bunch of code that will never be accepted and forever conflict with future versions. big up, getting some nice sounds going too! :P -- Sent from my Linux 2.6.38.6-27.fc15.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux |
From: Raine M. E. <ra...@ik...> - 2012-03-19 11:08:17
|
Quoting teknopaul hinds <tek...@gm...>: > Next is Swing/Groove and this really does involve working inside LMMS > no option to do a plugin there so I would appreciate a bit of advice, > I dont want to write a bunch of code that will never be accepted and > forever conflict with future versions. Could groove be part of the instrument parameters? There is already the chord/arpeggio logic, which must have some notion of timing. And think about how nice it would be to have groove adjustable separately for each instrument, like having musicians with different personalities. Just a thought on where I'd look for a place for it :) Thinking a bit further, should all time stuff (tempo, time signature and global groove, maybe markers of some kind?) be put into one place and all automation for these centralized into one "time track" or whatever you want to call it? (maybe this already is happening in the development branch?) I was poking around in the automation editor code looking for a way to find out where in time the cursor is when I realized that the translation from ticks to musical time is tricky when an automation segment somewhere could be changing the time signature from 4/4 to 3/4 and back at any time. No way of knowing without scanning trough the automation segments. Likewise for tempo: I did a song with a tempo ramp from 150 to 190 BPM, but if I jumped over that automation segment when editing I of course ended up listening to stuff at the wrong tempo. Much more annoying than some filter being left at the wrong frequency, IMO. -- ra...@ik... http://www.mikseri.net/radioproject |