From: Tim E. R. <ter...@ro...> - 2012-06-10 21:21:53
|
On June 10, 2012 9:53:39 PM you wrote: > 2012/6/10 Robert Jonsson <spa...@gm...>: > > Hi guys, > > > > 2012/6/9 Tim E. Real <ter...@ro...>: > >> On June 1, 2012 8:26:15 AM Florian Jung wrote: > >>> Am 01.06.2012 03:58, schrieb Tim E. Real: > >>> > On May 31, 2012 3:50:21 AM Tim E. Real wrote: > >>> >> The midi-to-audio controller value translation routine sucks ATM - > >>> >> > >>> >> logarithmic, boolean, and 'pan' type controls may be skewed or > >>> >> incorrectly biased. > >>> >> > >>> >> It already does basic midi to audio controller range-mapping, albeit > >>> >> > >>> >> incorrectly with log and 'pan' type controls as mentioned above. > >>> > > >>> > Fixed. Tested OK with logarithmic, linear, integer, and boolean > >>> > controls. > >>> > > >>> > So now the advanced mapping has something to go on... > >>> > > >>> > Forgot to note, currently it does not record the midi to audio > >>> > automation > >>> > > >>> > (automation touch, write). That should be done shortly... > >>> > >>> please try to implement this recording the same way as mouse-generated > >>> data is recorded; would make things easier later > >>> > >>> greetings > >>> flo > >>> > >>> > Tim. > >> > >> Hookay... > >> > >> Merged the r2_0 extra branch into release. > >> > >> Go ahead and test please. > > > > I'm late to the party, as always.. > > > > Never the less: Woohoo, lots of new code =) > > > > The downside is that it seems a bit much to hand it out untested so > > I'll spend a few days running it before going ahead with the release. > > If nothing "bad" crops up I'll do it soon. > > Ohmigod. I can control the volume of a track with my midi keyboard =) > Lovely! > > One thing though, I wasn't paying enough attention before when alsa vs > jack midi was discussed. > Now when MusE boots up all I see in the midi configuration dialog is > 'Create Jack device', from there I am pretty much lost... when I > create a such device it only has a generic name and doesn't seem to be > connected anywhere. > How is this supposed to work, how do I get my physical midi device to show > up? > > To get it working I started muse with -A, which seems to enable the > old functionality. Then my midi device popped up. Yes I did that. If Jack is running, no ALSA ports are listed. You supply the -A switch to force it to happen. The idea is that if Jack is running and you want to use ALSA devices, you should run Jack with the ALSA seq (-Xseq), or maybe even the raw. Failing that you should run that a2jmidid thingy, right Florian? I mean, we really shouldn't be listing both ALSA and Jack at the same time. There's no way to tell if someone is actually USING -Xseq. See what I mean? So I can't determine yes or no for certain whether to display ALSA or not, so I just made it this way. If you use other types of devices like Firewire, they should just show up. Is this acceptable? Aren't all use cases addressed by this functionality? Thanks for the extra time. PS I'll be on chat during for the next while waiting for questions... > > Regards, > Robert |