MIDI CC# bug - issue updated, also P5 crashing bug

Author
Post
Essentials Only Full Version
Goseba
Max Output Level: -86 dBFS
  • Total Posts : 244
  • Joined: 2006/11/27 05:03:17
  • Location: Geelong
  • Status: offline
2007/05/12 18:03:12 (permalink)

MIDI CC# bug - issue updated, also P5 crashing bug

I have noticed that some CC# are not transmitting to VST's. (They record but do not transmit back).

I discovered this while setting up Komplexer with my controller keyboard.

CC#'s 6, 19 and 91 are just 3 I have found not working.

I have tested Komplexer in Phrazor, Cubase LE and Live 6 demo and all is OK.

Wrapping Komplexer in Phrazor made no difference.

Controller 6 is frustrating because it is one of Komplexer's macro controllers.
post edited by Goseba - 2007/05/16 16:59:10
#1

6 Replies Related Threads
    b rock
    Max Output Level: 0 dBFS
    • Total Posts : 8717
    • Joined: 2003/12/07 20:31:48
    • Location: Anytown (South of Miami), U.S.A.
    • Status: offline
    RE: MIDI CC# bug 2007/05/12 21:00:15 (permalink)
    I just tried those three CCs in another synth, controlling pitch (for obvious results). I recorded them into a pattern in P5 2.5, and they played back and controlled pitch as expected. It might be something else interfering there. CC6 is always tricky, because it's the data value for RPNs and NRPNs. Potentially, that could affect a lot of parameters in a given synth. Let me test a few synths known to respond to NRPN, put them in 2.5, and see what happens next.
    post edited by b rock - 2007/05/12 21:03:31
    #2
    Goseba
    Max Output Level: -86 dBFS
    • Total Posts : 244
    • Joined: 2006/11/27 05:03:17
    • Location: Geelong
    • Status: offline
    RE: MIDI CC# bug 2007/05/13 05:00:46 (permalink)

    ORIGINAL: b rock

    I just tried those three CCs in another synth, controlling pitch (for obvious results). I recorded them into a pattern in P5 2.5, and they played back and controlled pitch as expected. It might be something else interfering there. CC6 is always tricky, because it's the data value for RPNs and NRPNs. Potentially, that could affect a lot of parameters in a given synth. Let me test a few synths known to respond to NRPN, put them in 2.5, and see what happens next.



    OK, thanks for looking.

    As I mentioned, Komplexer works fine in the other hosts I checked so it seems to be a conflict between it and P5.
    #3
    Goseba
    Max Output Level: -86 dBFS
    • Total Posts : 244
    • Joined: 2006/11/27 05:03:17
    • Location: Geelong
    • Status: offline
    RE: MIDI CC# bug - updated issue 2007/05/16 15:48:37 (permalink)
    I had an idea and loaded Komplexer into Phrazor in P5.

    I then drew in controller data in Phrazor for controller 6 which wasn't working and 11 as a control which was.

    I looped the pattern and neither the dials moved nor the sound changed as expected.

    Then I clicked on one of the dials and as if by magic it was all working.

    I closed the Komplexer GUI down, but when opened again and started again I had to click on a dial to get them to work.

    Trying the same experiment with Komplexer directly in P5 in a clip in the arrange view and P5 doesn't respond. In fact each time I tried to open the GUI with controller data running, P5 crashed.
    #4
    b rock
    Max Output Level: 0 dBFS
    • Total Posts : 8717
    • Joined: 2003/12/07 20:31:48
    • Location: Anytown (South of Miami), U.S.A.
    • Status: offline
    RE: MIDI CC# bug - updated issue 2007/05/16 16:06:25 (permalink)
    I've got a hunch (and it's just a hunch). Komplexer is a VSTi instrument, correct?
    Open up the GUI in P5, click on the VST button, go to Plug-In Properties, and select Do Not Intercept NRPNs.
    #5
    Goseba
    Max Output Level: -86 dBFS
    • Total Posts : 244
    • Joined: 2006/11/27 05:03:17
    • Location: Geelong
    • Status: offline
    RE: MIDI CC# bug - updated issue 2007/05/16 16:29:15 (permalink)
    You are an absolute star b rock, it works a treat now.......

    Well it did the first time but now P5 keeps crashing with just Komplexer loaded. I can load the VST, not even opening the GUI, and as soon as I start to do anything P5 crashes. But this is a separate problem.

    At least you resolved the initial problem I had, many thanks.

    EDIT: Just tried experimenting with Komplexer in Phrazor in P5 and it doesn't crash at all. The downfall is I lose the controllers again unless I create them manually inside Phrazor.
    post edited by Goseba - 2007/05/16 16:57:42
    #6
    jardim do mar
    Max Output Level: -66 dBFS
    • Total Posts : 1247
    • Joined: 2003/12/02 06:23:57
    • Status: offline
    RE: MIDI CC# bug - updated issue 2007/05/16 23:33:18 (permalink)
    it works a treat now.......
    ,,,,try directixer,(it's a wrap),,,the macro's should,,,like ,, all work ,,,,,,,,cc6 character,,,,,8 warp,,,,, 9 effect,,,,11 expression,,,,,3 attack,,,,,,,119 release,,,,,,62 decay,,,, 67 sustain,,,,,, like blame it on,,,ya know,,, midi protocol,,,i get sticky notes ,,with it wrapped with,,,,,,,,, cakewalks native wrapper ,,,no crashes ,,, though,,,,,,,don't ya just love phrazor,,,,,,,it blends so well wit p5,,,,,, ya know ,,,,,,ya can record the ,,"built in arp "midi data ,,,,,,,,,,,,,directly into phrazor as midi,,,,,,,,,

    marcella
    And Remember,,,,One thing at a Time.....
    #7
    Jump to:
    © 2024 APG vNext Commercial Version 5.1