I set the bcc1 to volume and velocity to non-0 value and everything works! Here is the command.
amidi -p hw:2,0,0 -S "F0 47 7F 6D 02 00 0B 00 00 40 66 07 00 00 7F 00 7C 7D F7" On Sun, Sep 17, 2017 at 3:36 PM, Freeman LIU <freemanliu2...@gmail.com> wrote: > Are follow up, by aseqdump, I can see that control change messages with > different value. But the volume out of the speak is not change. Does > fuildsynth not honor the change? > > > On Sun, Sep 17, 2017 at 3:29 PM, Freeman LIU <freemanliu2...@gmail.com> > wrote: > >> Hi, Ben, >> >> Thanks for pointing out the transpose problem. I followed >> http://www.ewiusb.com/sysex_page2 and changed it and now the device >> started to work! >> >> The issue of initial volume can be fixed by setting the velocity to some >> non-dynamic value. Here is the cmd. Hope it is useful to anyone runs into >> the same problem. >> >> amidi -p hw:2,0,0 -S "F0 47 7F 6D 02 00 0B 00 00 40 44 11 00 00 7F 00 7C >> 7D F7" >> >> sadly, the volume does not change when blowing harder or more gently. But >> even if setting to 00 (dynamic) it will not change. >> >> Cheers, >> F >> >> >> On Sun, Sep 17, 2017 at 8:02 AM, Freeman LIU <freemanliu2...@gmail.com> >> wrote: >> >>> Hi, Tom, >>> >>> Thanks for your analysis. Looking at the note on messages more closely, >>> I can see that the note number is very low. That might be the problem that >>> makes it barely audible. I might need to adjust the transpose. Is there any >>> other reason that you can think about why the note numbers are so low? >>> >>> Cheers, >>> F >>> >>> On Sun, Sep 17, 2017 at 12:35 AM, Tom M. <tom.m...@googlemail.com> >>> wrote: >>> >>>> Ok, your EWI controls the expression controller CC11. Additionally the >>>> value for noteon velocity is taken from that controller. For the first note >>>> you're playing the expression value is pretty low resulting in a very low >>>> noteon velocity. Low expression and low velocity gives a very quiet note: >>>> >>>> B0 0B 16 >>>> 90 03 16 >>>> >>>> For the next note CC11 is higher again: >>>> B0 0B 3E >>>> 90 01 3E >>>> >>>> Dont know how other EWIs handle noteon velocity. However, you could try: >>>> - assigning noteon velocity to a fixed value (e.g. 64), since you're >>>> controlling the volume via CC11 anyway, or >>>> - this might be an issue with the very dynamic volume processing >>>> introduced in fluidsynth 1.0.9. In this case it might help to test it with >>>> fluidsynth 1.0.8 or you start fluidsynth with the *-o >>>> synth.volenv=compliant* option (since this is a new feature you'll >>>> have to checkout this branch >>>> <https://github.com/FluidSynth/fluidsynth/tree/volenv> and build >>>> fluidsynth your own) >>>> >>>> >>>> Tom >>>> >>>> >>>> 2017-09-16 11:31 GMT+02:00 Freeman LIU <freemanliu2...@gmail.com>: >>>> >>>>> Attached is the log from >>>>> >>>>> amidi -p hw:1,0,0 -d > log >>>>> >>>>> >>>>> I blowed into ewi usb and changed fingers and octave rollers randomly. >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> On Sat, Sep 16, 2017 at 5:44 PM, Tom M. <tom.m...@googlemail.com> >>>>> wrote: >>>>> >>>>>> You could dump the MIDI events from your EWI to file, so we have a >>>>>> way to reproduce this issue. >>>>>> >>>>>> >>>>>> Tom >>>>>> >>>>>> >>>>>> 2017-09-15 15:19 GMT+02:00 Freeman LIU <freemanliu2...@gmail.com>: >>>>>> >>>>>>> Dear experts, >>>>>>> >>>>>>> I got a EWI USB and managed to make it work with qsynth and >>>>>>> qjackctl. Awesome. And the real time support is great. The latency is >>>>>>> better than on windows. But there is a one deal breaker. When I blow >>>>>>> into >>>>>>> it, the volume is very low, almost unheardable. But once I change the >>>>>>> note, >>>>>>> the volume increase dramatically. This way, I can hardly play a piece of >>>>>>> music. >>>>>>> >>>>>>> I saw a old thread in 2015. >>>>>>> http://lists.nongnu.org/archive/html/fluid-dev/2015-10/msg00014.html >>>>>>> >>>>>>> I wonder if there is a plan to fix it. >>>>>>> >>>>>>> Thanks, >>>>>>> Freeman >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Go is a good language. >>>>>>> Google photo is becoming more and more useful. >>>>>>> Chromecast is just useful. >>>>>>> Let alone Google home. >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> fluid-dev mailing list >>>>>>> fluid-dev@nongnu.org >>>>>>> https://lists.nongnu.org/mailman/listinfo/fluid-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> fluid-dev mailing list >>>>>> fluid-dev@nongnu.org >>>>>> https://lists.nongnu.org/mailman/listinfo/fluid-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Go is a good language. >>>>> Google photo is becoming more and more useful. >>>>> Chromecast is just useful. >>>>> Let alone Google home. >>>>> >>>>> >>>>> _______________________________________________ >>>>> fluid-dev mailing list >>>>> fluid-dev@nongnu.org >>>>> https://lists.nongnu.org/mailman/listinfo/fluid-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> fluid-dev mailing list >>>> fluid-dev@nongnu.org >>>> https://lists.nongnu.org/mailman/listinfo/fluid-dev >>>> >>>> >>> >>> >>> -- >>> Go is a good language. >>> Google photo is becoming more and more useful. >>> Chromecast is just useful. >>> Let alone Google home. >>> >>> >> >> >> -- >> Go is a good language. >> Google photo is becoming more and more useful. >> Chromecast is just useful. >> Let alone Google home. >> >> > > > -- > Go is a good language. > Google photo is becoming more and more useful. > Chromecast is just useful. > Let alone Google home. > > -- Go is a good language. Google photo is becoming more and more useful. Chromecast is just useful. Let alone Google home.
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
