>You could try the last git commit, there's a new "tvcurve" function that applies the velocity change to tracks. Let me know if it works. I could not get this working, but I'm guessing its me not understanding how to apply this to the "current" selection. Can you give an example of how to apply to a loaded midi file? Btw, thanks so much for making those changes, very awesome of you. >On Linux, you can chain two midish instances using the ALSA's "midi thru" devices. That suggestion was great, thanks! I Achieved this with two process, on my "player" process I ran dnew 0 "14:0" wo #alsa midi through import "/tmp/somefile.mid" p on my "filter" process I ran dnew 0 "20:0" wo #USB out dnew 1 "14:0" ro #alsa midi through new piano {0 0} inew pipe {1 0} fnew volume fvcurve {} (0) map { any pipe } { any piano } i I can then apply new fvcurve values to change the volume. On Sat, Dec 29, 2018 at 2:54 AM Alexandre Ratchov <alex@caoua.org> wrote: > On Fri, Dec 28, 2018 at 10:50:51AM +0100, Alexandre Ratchov wrote: > > On Thu, Dec 27, 2018 at 01:44:15PM -0800, dan cunningham wrote: > > > Thanks Raphaƫl I'll take a look at mido. I'm also wondering if anyone > has had > > > luck chaining midish instances together? I have a built a midi > jukebox of > > > sorts and I would love to be able to change the volume as the playback > is > > > happening. The FVCurve function seems perfect for this, now I just > need to > > > figure out how to apply it to a file instead of an input stream. > > > > > > > Hi, > > > > On Linux, you can chain two midish instances using the ALSA's "midi > > thru" devices. AFAICS, it's not hard to patch midish to apply the > > velocity curve rule to a tracks, i'll look at this. > > You could try the last git commit, there's a new "tvcurve" function > that applies the velocity change to tracks. Let me know if it works. > -- Sent from my mobile.Received on Sun, 30 Dec 2018 11:08:20 -0800
This archive was generated by hypermail 2.1.8 : Mon Dec 31 2018 - 01:32:46 CET