ssp

Programmer
  • Content count

    531
  • Joined

  • Last visited

Community Reputation

5 Neutral

About ssp

  • Rank
    MIDIbox Guru
  • Birthday January 01

Profile Information

  • Gender Not Telling
  1. understanding the .ngc code

    Got a few things working but not there yet 
  2. understanding the .ngc code

    I am sat here trying a few things out, i have two buttons in the breadboard and I am writing test lines of code as i go along, everything i have already learned i have applied and they are working , I am going to try to work out the code for these two buttons and try it, if i dont get it, then i will post up what i have done and if anyone can help me out then I will ask.   thanks
  3. understanding the .ngc code

    Is this what you are referring to (by example) and use this as a starting point? this is for a single button, i would need for this to be over two buttons. https://github.com/midibox/mios32/blob/master/apps/controllers/midibox_ng_v1/cfg/tests/mapbtn.ngc RESET_HW   LCD "%CMap Button Values"   # the used map: MAP1 0 1 2 4 8 16 32 64   # define a radio group with a single toggle button but multiple LEDs EVENT_BUTTON id= 1 fwd_to_lcd=1 type=CC chn=1 cc=16 button_mode=Toggle range=map1 radio_group=1 lcd_pos=1:1:1 label="^std_btn"   # Note: the map will only be considered if a button is configured for button_mode=Toggle !   # these LEDs are mapped to radio_group1, and therefore will get an "automatic feedback" whenever the toggle button changes the value (or receives a new value) EVENT_LED id= 1 range=0:0 radio_group=1 EVENT_LED id= 2 range=1:1 radio_group=1 EVENT_LED id= 3 range=2:2 radio_group=1 EVENT_LED id= 4 range=4:4 radio_group=1 EVENT_LED id= 5 range=8:8 radio_group=1 EVENT_LED id= 6 range=16:16 radio_group=1 EVENT_LED id= 7 range=32:32 radio_group=1 EVENT_LED id= 8 range=64:64 radio_group=1     # a button which doesn't toggle, but just turns on/off # in this case either the lowest or highest item of a map will be taken EVENT_BUTTON id= 2 fwd_to_lcd=1 type=CC chn=1 cc=17 button_mode=OnOff range=map1 radio_group=1 lcd_pos=1:1:1 label="^std_btn"
  4. understanding the .ngc code

    Thanks for the info I remember on the MB64e you could change the inc,dec buttons to an encoder with a slight code change. In effect this is the opposite, an encoder function to, two buttons, with a range of 0-100 instead of 0-127. and each button press has a stepped range of 20.  however after pulling  another late night the first press is 0-20 the second press actually starts at 20.5 as this is a marginal step over 20 it changes the plugin transpose position but you can round this to 21. hopefully i will give it a try today, im not holing out for much success as i cant see any reference to a function for buttons like this on the forum or in the manuals other than the enc_mode or the emu_enc_mode functions. I am writing test lines of coade as shown in the "First steps" section and trying things as i go. I have got a few other things working but this and the 3 digit values issue are griefing me.
  5. understanding the .ngc code

    In this case would I use either the:  enc_mode= Incxx_Decxx.  Or would i use emu_enc_mode=<mode> Incxx_Decxx function and use the +or- 20 values in hex.   This seems logical to me. once this is in place i then have to have each value linked to each led. so if the value is 41-60 (this is the range of the value for the 0 position led to be lit and active and can be any number between that range)   so for example for the steps i want: enc_mode= Inc14_Dec14 (this is the hex value for the decimal value of 20) im sure an event_reciever is needed also but I am not sure where to implement this.   I am looking through this page here: https://github.com/midibox/mios32/blob/master/apps/controllers/midibox_ng_v1/cfg/tests/emu_enc.ngc to see if this can help me.
  6. understanding the .ngc code

    this is a good comparison in the manual where a dimmed LED steps in values of 16   Dim me! While previously the LED was only switched between on and off state depending on the incoming MIDI value, now we want to control the brightness level with the received velocity value instead: EVENT_BUTTON id=1 fwd_id=LED:1 dimmed=1 type=NoteOn key=36 lcd_pos=1:1:1 label="Button #%3i: %3d" Only the dimmed=1 parameter has been added. The LED will change the brightness over the 0..127 value range in 16 levels. Just for fun you could also control the brightness from a CC event: EVENT_LED id=1 dimmed=1 type=CC cc=16
  7. understanding the .ngc code

    OK question. I want to have to buttons function as an down value and one as an up value rather than using a pot or encoder.  I have two buttons linked to the din module and in effect they are replacing an encoder for the up and down values but in essence are acting as an encoder. The buttons work like this, the maximum values needed for this are 0 to 100 not 0 to 127 but in steps of 20 these are for transposing the plugin i am using values: -2:= 0 - 20 -1:= 21 - 40 0=: 41 - 60 1=: 61 - 80 2=: 81 - 100 so if the button is in the middle ie:"0" then the button state is at a value between 41 - 60, if i then press the left button once the value changes to 21 - 40 and again to 0 - 20, if i then press the right button it brings the values back up.   OK so i have got a din with two buttons conencted to the mb_ng. on the first shift register to replicate an encoder such ENC n= 1 sr=1 pins=0:1 type=non_detented (an encoder uses two of the sr pins) each press of the button on sr=1 pin:0 is the left button with a decreasing value of to 0 in steps of 20 pressing button on sr=1 pin:1 increases the value by 20. would i need to make a value table or meta event for this? to make each button press of either decrease or increase the value of the set range 0-100? I am looking at the manual as I am typing this but I cant see anything that resembles this. In other good news more of my bits turned up, also my ainser64 have arrived so I building those as well.   Thanks EDIT:  so the buttons will work as an encoder thats fine, i just need to set the min-max value range of 0-100 instead of 0-127 but it needs to travel in values of 20 at each press. Can i set this value range and steps?
  8. multiple Clcd's

    nope none of the above, i didnt go with the -63/-/64 as i am trying to make a replica controller of the plugin. I can get the usual bit working encoders pots, linking the 7 segments to the dout and assigning it in the code etc. I have no idea about nrpns , how to work them out etc. I have however printed out some info sheets and I will see how i go. I have learned so much already, i just have to push a bit more, if i fail then at least I have tried. I am trying with just one pot and one 3 digit lcd. But if there is something in the manuals point me to it and I will read through it
  9. multiple Clcd's

    I spent the weekend trying to get the nrpn to work but I failed. this is the issue that I couldn't resolve a dual command. The potentiometer needs to send a cc# to the vst plugin, it still expects 0-127 to move the virtual knob, the on screen 3 segment shows -99 to 99 values with a line for 0 as i have shown. The 3 digit 7 segment I am fitting into my controller needs its instruction from the core not the plugin as the plugin does not output its led values out via midi. so the pot needs to send two different commands. If i have to use nrpn this needs to only effect the hardware 3 digit display. In simple turms, turning the potentiometer outputs both a cc# to the vst plugin and also  changes the value on the 3 digit 7 segment display to reflect the on screen led value. Everything else I have been working on has been fine and I have understood it, but this is seriously pickling my brain, its there but i just dont see it for some reason. I could really do with some pointers on this. or.. basically can someone smarter than me help and point me in the right direction.   thanks    
  10. Save and recall sysex strings

    Puts hand up...  quite freely admits that I dont understand how to do this. Sorry really not smart enough.
  11. Save and recall sysex strings

    i use presonus studio one, the track names are spat out as asci converted to hex, its in my one thread. I have been meaning to test the code i have written but forgot about it as I was soucing parts and building. I will give it a try tonight see if i can get it to work on mine. S1 output per channel F0 00 01 06 16 12 00 00 00 73 74 72 69 6E 67 73 F7 this hex is an example ascii for the track name "strings": 73 74 72 69 6E 67 73 this changes as you either tab over channels or bank swap as you would expect for more than 8 channels.   thread start from here: http://midibox.org/forums/topic/21235-understanding-the-ngc-code/?page=2   there was also this comment that had been previously made that i needed to find to link into the thread for throsten to look at http://midibox.org/forums/topic/17498-midibox-ng-release-feedback/?do=findComment&comment=185392  
  12. understanding the .ngc code

    Thank you Thorsten, as soon as the pcbs arrive i will edit the code for this and try it out along with the new revision for NRPN numbers.
  13. understanding the .ngc code

    When I use a core 8 for a build and i want to do some testing, I usually just connect one fader or pot to J5 on the core and then I edit the code as shown by default using the MB_64e V2 it is: #define DEFAULT_NUMBER_AIN 64 #define DEFAULT_ENABLE_AIN_MUX 1 if you only have one fader you need to link any unused pins to ground however,  I always just change the code to this and everything is fine as it is not expecting any other inputs. #define DEFAULT_NUMBER_AIN 1 #define DEFAULT_ENABLE_AIN_MUX 0 This makes the core happy and only sees the one input. My question is can I also edit the MB_NG in a similar manner for the Ainser 64 rather than having to ground all the other pins? This is such a time saving way for me to check and test a single pot or fader. I dont have my ainser 64 pcbs from the states yet so I have no way of trying it for myself rather than asking a question. thanks  
  14. understanding the .ngc code

    I didnt think of that, I want to try and figure out the nrpn this weekend (this is dependent on my ability to keep a stable path for the required neuro transmitters to create a link from the correct areas of my brain to form a cognetive thought and also hold a stable enough charge to allow the required areas to form a coherant memory) or in simple terms... not have a brain fart and have a mild ability to understand stuffz....
  15. understanding the .ngc code

    Question,  is it possible to connect a single pot to the MB_NG without the ainser? i have got a single 3 digit 7 segment here and and single pot on breadboard, so i can try working out the code for the nrpn -99/-/99 values. and see if it will work.   thanks   edit,, just the pot info is needed