Posts by mortl

    Hi,


    Your controller looks really nice!


    See my attached picture for the Pin-numbering:
    One tlc has 16 outs for the LEDs (if its the tlc5940) - so you only would need one for your 16 LEDs. First LED is OUT0 (PIN28)... last is OUT15 (PIN15).
    PIN 26 is "SIN" means Serial input.. PIN 17 is SOUT... so from 17 it goes to 26 of the next tlc5940.


    don't forget to tell the tlc-library how many tlcs you have..


    Basically the tlc has no outs, but inputs for the LED. You have to wire all "+" of all LEDs to "+" of your source... and every "-" from the LEDs has to go to one "OUT" of the TLCs..


    all the SCLK, XLAT, BLANK and GSCLK go to all the tlcs .. so from first to second and third and so on..


    The wiring for the arduino mega is:
    Mega pin 51 (MOSI) -> SIN (Tlc pin 26)
    Mega pin 52 (SCK) -> SCLK (Tlc pin 25)
    Mega pin 11 (OC1A) -> XLAT (Tlc pin 24)
    Mega pin 12 (OC1B) -> BLANK (Tlc pin 23)
    Mega pin 9 (OC2B) -> GSCLK (Tlc pin 18)


    optional (i didn´t use them)
    TLC pin 27 - set this to ground when not used.
    TLC pin 16 - you can leave this unconnected.


    hope i could help


    Martin

    translated word by word its "remember-variable"... thats even in german not a good word for that. what i ment is a variable to remember the state of the switch / expression-value... so they are called swst - for switch-state... or exprst for expression-state


    the 6 variables with "..temp" at the end (cnexptemp, expchanneltemp .. where "merkvariable" comes once more) . ) are not yet used in the code. I will use them to change the purpose of one expression pedal when using a specific effect. For example: one pedal is for delay-mix. when switching on a pitch effect the expression pedal will change to adjust the mix of the pitch-effect. when switching the pitch effect off, it should return to that purpose it was used before .. so i declared the "temp" variables to remember the state, channel, cc#, upper limit, low-limit etc. before changing the purpose.. does this make sense to you? :)


    martin

    Hi,


    thanks!


    the costs of just the material would be not much - but for most of you i don´t need to mention the time spent for this project. So if I want to sell my controller (or build some to sell them), the price definitively would reach that of the Kemper Remote.. I also wouldn´t be able to provide much support for troubles of any kind.
    and after all you can change it´s functions only by changing the code, there is no user-setup. -


    Here is the ino-file
    Be aware, that there are parts of the Code, which aren´t needed anymore (were there for testing things)... and some are not finished yet .. and so on.. :)


    In another post i wrote this:


    here is my ino-file
    but:
    1. i´m not a programmer, so i REALLY don´t know, if you even do programming that way, i did, or if there are WAY better ways :) - a friend of mine (programmer) just told me when reading my code: ".. hmmmmmm, so, if its working... "
    2. EVERYTHING is totally personalized for my needs ... but maby you can get some ideas out of it :-). Maby you don´t get any of my ideas, without me explaining it :)


    Its all in the ino file, no extra files except the included libraries..


    After all: Many of my comments are in german ... some in english..


    greetings
    Martin

    hi,


    here is my ino-file ...
    but:
    1. i´m not a programmer, so i REALLY don´t know, if you even do programming that way, i did, or if there are WAY better ways :) - a friend of mine (programmer) just told me when reading my code: ".. hmmmmmm, so, if its working... "
    2. EVERYTHING is totally personalized for my needs ... but maby you can get some ideas out of it :-). Maby you don´t get any of my ideas, without me explaining it :)


    Its all in the ino file, no extra files except the included libraries..


    After all: Many of my comments are in german ... some in english..


    greetings
    Martin

    Hey,


    maby this isn´t new, but i did´n find this information like this:


    i think i got the looper now in whole function, exactly like the manual describes it like it handles with the original remote:
    I tested ALL functions, including The Advanced features (holding buttons) - everything works here..
    But as said somewhere above you need a controller, that sends different Messages when pressing and releasing.


    Otherwise you can get the looper to work with the messages described in the original post.


    So:
    You do NOT need to program a state-machine for the buttons only for the LEDs to make them show the state of the looper.


    In Decimal-values (sorry, its simpler for me than hex) you just have to send following NRPN commands:
    Important: On Press of the button, always send Value 1, on release of the button always send Value 0
    CC#=controllernummer, V=Value


    Button 1: Rec/Play/Overdub:
    CC#99 V125, CC#98 V88, CC#06 V0, CC#38 V1 (on press), V0 (on release)
    Stop/Erase:
    CC#99 V125, CC#98 V89, CC#06 V0, CC#38 V1 (on press), V0 (on release)
    Undo:
    CC#99 V125, CC#98 V93, CC#06 V0, CC#38 V1 (on press), V0 (on release)
    Trigger
    CC#99 V125, CC#98 V90, CC#06 V0, CC#38 V1 (on press), V0 (on release)
    Reverse
    CC#99 V125, CC#98 V91, CC#06 V0, CC#38 V1 (on press), V0 (on release)
    1/2 Speed
    CC#99 V125, CC#98 V92, CC#06 V0, CC#38 V1 (on press), V0 (on release)


    Martin

    Hi,
    so: here´s a video of my DIY Controller with looper integration:
    see also: DIY Midi-Footcontroller .. With Tuner AND Looper


    It can do all the things with the looper: Button one is Rec, overdub, play (with the hold-function like the kemper remote). Button 2 is stop (hold it 2s: delete loop). Button 3 is undo/redo, button 4 is Retrigger, button 5 is 1/2 speed (with hold-function like described in the manual).


    The LED on button one is: dark-red, if stopped and empty, light-red, when recording, light-green, when playing, dark green, when stopped but there´s a loop. and dark red again, when loop is "deleted" (what i mean by delete: read below).


    what i don't get:
    - my button 4 (trigger) retriggers the loop when its playing: perfect: but, if it´s stopped, the button does nothing! I can not trigger the loop just for one "round" .. whats the nrpn-message for "trigger once when loop is stopped"?


    - Whats the thing with: delete loop:
    I did´n manage to delete a loop, as if i press play, it always is there and starts playing, no matter how often i send the delete-nrpn-message.
    How i "delete" it: Just send a Record-message when loop is stopped - no need to delete it in any way. the KPA just records a new loop...
    So my delete-function just tells the "record/overdup/play"-button not to send "play", but to send "record" - i hope it´s clear, what i mean.


    here is it in action:

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    what do you think?


    greetings
    Martin

    Hi everyone,


    what do you think about my DIY-Midi-Footcontroller? It´s based on an Arduino Mega.


    It has 18 Buttons, 19 RGB-LEDs (one for Tempo-info) and 2 7segment-Displays. (One for Bank and bmp, One for CC Value of the Expression pedals). Until now it has a (poor and quick built front-panel, but once i am satisfied with the Layout, it will get a 3mm Black aluminum-panel. The displays will move and i will increase the distance between LEDs and Switches a little).


    2 Expression Pedals conected
    1 Tap-Switch connected


    What it can do until now:
    - Send Programchanges in 2 Banks (a 4presets) for switching Rigs (I don't need more).
    - Switch Stompboxes on/off. (sending CCs)
    - Tap tempo (with Beat-Scanner, when holding button).
    - Switch 4 different Delay-Types with nrpn-commandos (different Delay-Clocks like dotted 8th, 4th, analog-Style, Stereo-Style) .. And switch delay off, if same Delay-Type-Button is pressed.
    (I use one Expression pedal for Delay-Volume.. The LED of the active Delay-Type fades with the state of the Expression Pedal :) ).
    - Switch Delay-Feedback to "much" or "less" (multiple nrpn)
    - Freeze-Function (thanks to Joptunes for the idea) (multiple nprn)
    - Complete Looper integration: Rec, Overdub, play, stop, undo/redo, retrigger, 1/2Speed with the holding-Function of the rec/overdub/play, the stop and the 1/2-Speed-button. (I don´t need the reverse function).
    - Display Tuner-Info from the KPA
    - second Midi-In to Get Infos (like midi-clock) from another device


    it will get another 3 LEDs to display Tuner-Info all the time via these LEDs.


    here it´s in action:

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.


    I will post/send the arduino code when it´s ready (until now many wrong/not-finised parts in the code) and any info you want to know.



    Martin

    Thanks, yes, makes sense...
    I had to turn the Reverb-Volume a little up... then the dry lead lines blend better with the (now louder) pad.


    thanks