Zam

Members
  • Content count

    472
  • Joined

  • Last visited

Community Reputation

24 Excellent

About Zam

  • Rank
    MIDIbox Tweaker

Recent Profile Visitors

670 profile views
  1. Midi forwarding with modification

    Ok... I'm not aware that you can define the midi note from an event... maybe try with a delay (1ms) just before looping the section with exec_meta command. What the debug say before the crash ?   Best Zam  
  2. Midi forwarding with modification

    Theses two line are not valid ! check manual for -send- command   best Zam
  3. Midi forwarding with modification

    Not sure it's the reason, but you don't define any note, so maybe default is C-2, try with note=all   Best Zam
  4. Midi forwarding with modification

    Only one fwd_id allowed, you should forward to a sender and duplicate this sender (same hw_id different id) each one sending/forwarding to a different led. Or you use meta runscript and then do your forwarding/conditional at NGR. Best Zam
  5. Midi forwarding with modification

    Hello Out of idea right now... just make sure if your led:3228 is used for other function that it's value is not different from 0 or 127. Best Zam
  6. Hello As I say, you can't modify the 32ch HUI limitation in PT You should be able to control way more channels in PT from your desk (remote) by using the fader bank Still I don't know how it react with 32 channels, dose the flip go per 8 meaning 1 to 32 then 9 to 40 etc... Or flip per 32, 1 to 32 then 33 to 64, you have to try. Anyway this will not be bidirectional. if you flip let say from 1-32 to 33-64, your first console channel no longer link to first PT channel which might be a problem in your use case as I understand it now. In fact the question is, do you need desk analog channel to be locked to the same PT channel all the time ?   Ok, so you already hook the VCAs ?   About protocol... In PT you have no options, HUI is 4, EuCon I don't know, but you won't get the protocol spec... In DP I'm able to use as many MCU modules as I want.   Best Zam    
  7. Hi Ok... I was thinking you where stuck with 8, so I give a solution for 32 (max allowed simultaneously) You should be able to bank channels (zone 0a) to swap per 8 BUT in your specific use case where analog hardware can't be "relative" channel as it physically link audio to the channel you have no solution, except using a DAW that allow more controller units. Maybe you already do but did you make a call at GS or GroupDIY for the schemo Automating VCA is possible with MIOS, but without schemo and initial system spec it's difficult (need time to reverse engineer the VCA section) Best Zam  
  8. Hello PT can handle 4 HUI devices At NGC you should define events to the different midi I/O. e.g for USB: All data to/from HUI n°1 with port=1000..... All data to/from HUI n°2 with port=0100..... etc then select the corresponding midi port at HUI setting in PT Best Zam        
  9. Midi forwarding with modification

    Hello   Can't confirm that, but if you observe this and are sure everything else is ok at your NGC then it's the case   Best Zam
  10. Midi forwarding with modification

    I guess you don't define led 2050 at NGC...  
  11. Midi forwarding with modification

    I don't get it... can you please show us the whole NGR section ? Best Zam
  12. Midi forwarding with modification

    I repeat myself, did you define your LED in NGC ? EVENT_LED id=1001 hw_id=1001 type=cc chn=1 cc=66 range=0:127 ports=1111110000000000 best Zam
  13. Midi forwarding with modification

    Hello There is no problem using dummy LED out of the hardware (hw_id=) count did you define your LED 1001 in the NGC ? fwd_id= send the value on the event. Best Zam
  14. Midi forwarding with modification

      Hello IIRC you don't "have to" with reset, all previous definitions will be erased without reset they will remain after loading new files   Best Zam
  15. Midi forwarding with modification

    For info, there is also the LOAD command that can flip and change whole configuration (.ngc .ngr)