Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#28 Graphical Response & Midi Controls

closed
Nick Copeland
5
2010-01-30
2009-11-16
iysil
No

It would be nice if the images of the keyboards (optionally) responded to midi controller events (not just mouse events). For example, if I move my pitch bend on my midi keyboard, it would move the pitch bend on the image of the organ as well.

That feature would go nice with the ability to use the knobs, linear sliders, and buttons on my midi controller keyboard with bristol =)

Discussion

  • Nick Copeland
    Nick Copeland
    2009-11-17

    • assigned_to: nobody --> ncopeland
     
  • Nick Copeland
    Nick Copeland
    2009-11-17

    You can get some of this to work now. When you start the application with ALSA interfaces (the default) you will see two ALSA midi ports open in 'aconnect -io': aconnect your keyboard to both the GUI and the engine which are called 'bristol' and 'brighton' and the keyboard will track you master keyboard. These are normally ID 128 (bristol) and 129 (brighton) but that depends on your system. Also, you can play the synth from QWERTY: put the mouse in the synth window and press keys, you should be able to play the synth and then I do track the QWERTY keys you press as well.

    In release 0.50 you will only get one ALSA port by default, the engine, it will internally redistribute events to the GUI to get tracking. There are ways to override that behaviour and connect to both processes as well.

    When you do this (aconnect to bristol and brighton) you can get controller automation or rather, tracking: put the mouse over a control, press the middle mouse button: then move the MIDI controller and it will be registered to track that device on your MIDI surface. Settings are saved when you save a memory so that are active next time you start the app.

    I do not track pitchbend or the mod wheel - I could do that and if you want I can track it under this feature request, it is a reasonable request it's just that I have not implemented it, just thought about implementing it.

    It is possible that to get this to work with Jack MIDI then I need to make some changes in the 0.50 version that will be released soon.

    regards, nick.

     
  • iysil
    iysil
    2009-11-17

    Wow, that's pretty cool that you've already implemented that much. As you know, the documentation is fairly old & contradicting (to itself). The main feature that I was interested in was using my midi controls (ie. sliders, knobs, buttons) in Bristol; the rest (ie. gui response) is just icing on the cake. I do use JACK heavily (as much as possible), so implementation through it would be great (but I believe that I'm still using ALSA for midi connection through JACK).

    Making the GUI response optional (when the midi connection is reduced to just Bristol in 0.50+) would be very nice, as most GUI related widgets (at least typical scroll bars, and such, in average programs) can cause clicks in the sound, which would be bad in a pro-audio setting.

    Thank you very much for hearing my suggestions. Bristol/Brighton is IMHO the best of its kind!

     
  • Nick Copeland
    Nick Copeland
    2010-01-27

    • status: open --> pending
     
  • Nick Copeland
    Nick Copeland
    2010-01-27

    Going to close this. The documentation of the current control features would make sense, will work on that later.

     
  • Nick Copeland
    Nick Copeland
    2010-01-30

    Closed

     
  • Nick Copeland
    Nick Copeland
    2010-01-30

    • status: pending --> closed