ssp

Programmer
  • Content count

    596
  • Joined

  • Last visited

Everything posted by ssp

  1. Dout r5 wanted

    If anyone has some Dout r5 pcbs spare I am looking to buy some.  Thanks
  2. Dout r5 wanted

    yes let me know a price with postage to the uk.  thanks
  3. Dout r5 wanted

    in the uk i dont mind postage costs looking for a couple 2 is great 3 better, 4 bonus!!
  4. motorfaders

    also need better photos please, all around the fader, showing it all in the shot not just close ups. top and bottom, also how the cable is mounted for the fader movement etc. Also what desk is it from etc. as asked.  
  5. motorfaders

    they are an older series. PGF3200 series. there should be a cable like this coming from it this is before P&G were bought by curtiss-wright   you could try emailing them to see if they have got the legacy techincal docs for the fader.   the 8100 series and other has a side connector
  6. understanding the .ngc code

    this is what i am working on today, one encoder mapped to a button function. press button one and it changes display 1 value, press button 2 and it changes 2 value. Each button has a status led above it to show which is selected.
  7. I am getting to grips with the code however, can someone enlighten me on the last section of this example string> EVENT_BUTTON id=1 type=NoteOn key=36 lcd_pos=1:1:1 label="Button #%3i: %3d"    what is this section referencing/meaning?   #%3i: %3d so when i look at this i see (EVENT_BUTTON id=1)   the button id is 1 this is the first button on D0 (type=NoteOn key=36)     the midi event it is producing is a note on key value 36 (lcd_pos=1:1:1)   it is shown on lcd 1, line 1, (what is the 3rd 1 for?) (label="Button #%3i: %3d" )   and you got me here... no clue!!   Thanks
  8. understanding the .ngc code

    Thanks Thomas, yes a slight variation of that. I have my test setup on the table ready to try a few things out tomorrow. hopefully it will work!!
  9. understanding the .ngc code

    question: if i have 16 buttons as selectors for each 3 digit 7 segment led, and one encoder for value.  is it possible so if i press button 1 the encoder is mapped to the button one cc~ and value range selection and the led, then if i press button 2 it then changes for that and if i press 3 it changes for that? so the encoder becomes active for the toggle button you press. This would save me from having an encoder for each 3 digit and function. Is it possible to have an encoder function defined in a map? Thanks
  10. understanding the .ngc code

    been busy with work and other things or a while so I havent been in to update things. Today i had a play around with some new controller code, took a while to think about it and get it running, had to pick through some of my info i wrote down. All sorted in the end and i got things running.. the builds are progressing slowly these days because of lockdown here in the uk. But its giving me time to carry on learning new sections of code.
  11. multiple Clcd's

    i got the ainser up and running fine, all the code i ran through it worked first time and it all did what i wanted. I am working on the pcb's this weekend in altium before i send the gerbers to the pcb house, I also found someone to make the front panels for my enclosures as well who makes synth panels in various formats. I will link them in here this weekend. Picked up some really nice illuminated micro tact switches and for another project some larger size 12v illuminated rectangular switches that i pulled the bulb out and replaced it with a 3mm ultra bright led and it works fine. Al in all its all looking godd at the moment, I will update with some pics and build designs soon.
  12. multiple Clcd's

    I read in the lcd hardware section about putting multiple clcds onto the Ng is possible in this link : http://www.ucapps.de/mbhp/mbhp_lcd_6x2x20_mios32.pdf Question: Is it possible to attach 16 X  1 line 3 digit clcd's to the NG and have each one,  via code  linked to either a rotary pot or encoder in its value state? (would rather go this route) i understand an easier option is to either use oled displays or a single 2x40 with padded values spaced equally however,  thi cldcd route is something i really want to try out I want to build a vintage plugin controller and it has 16 3 digit clcds in its on screen display. The other reason for the clcds is that i want the old red segments. the other option i thought of was using one 2x40 clcds and padding them out so there are 4 sets of values per line but each value is padded equally and shows the 0-127 value above each pot/encoder now I understand the use of the padding for a name and the id-value, I just need a poke in the right direction as to which is the better option.  
  13. Encoder doesn't work

    Some of mine were jittery as hell. I opened them up and cleaned them with isopropyl and the brass contacts. There was far too much grease in them. All good now with a tiny bit of Teflon grease at the shaft point. No more jitters   
  14. multiple Clcd's

    just got the ainser 64 running set it to a single pot for now to test. and here we go!!.. EOL
  15. Someone left the door open and the light was on... So I had a quick look at the artwork.....  This is like getting a lapdance from your favourite movie star but you can't touch.!!  You sir are a tease, but I like you :).....     Queing patiently 
  16. multiple Clcd's

    Working just got the 3 digit displays running after some advice and help from Thorsten. Just doing the dance, code to follow.   
  17. multiple Clcd's

    Just put the Ainser64 together only to realise I hadn't ordered the Ic's... gutting..  now ordered for delivery tomorrow. whats one night waiting for parts...
  18. multiple Clcd's

    With a nudge in the right direction from thorsten i managed to get this working today to a certain extent. Using senders and maps i have got it working however the 128bit for encoders is the problem. I did see that there is a resolution setting for pots, so perhaps i can edit this to my advantage, I am just going to build my ainser64 board and give it a try. using this section of the manual MAP<n>/HWORDI  Applies linear interpolation between data points. Up to 64 datapoints can be specified, the value range is -16384..16383 (16bit). Example: # pot is working at 12bit resolution (0..4095) # 0..2048 should send CC value 127..0 downwards, # and 2049..4095 (the second half) should send 0..127 upwards. MAP1/HWORDI 0:127 2048:0 4095:127
  19. First post

    Well it has been a learning curve alright but with help from latigid on, Antichambre , TK. , FantomXR  and Zam I have been working on replica controllers for a couple of plugins i use here all the time, Arturia Sem Filter, Mini Filter and the Matrix Filter. I am lso doing a couple of plugin synth controllers. I am also working on the Blue Cat audio summing mixer MB7 thaty i use in my master chain, its a great plugin. As much as I love these plugins I also love being able to reach out to a knob, button or slider and turn it and that controls what happens but, I know I can buy a generic controller that everyone uses but building and desiging your own version of what you see, thats where the fun is for me. Years ago I designed an built the MOTU BPM replica and its still going to this day and has never let me down however, I can now upgrade this to the newer disco board and the .ngc and also look at adding the sample player to it making it self contained and designing a lighter casework as well. I figured out how to use the MB_MF and get the faders set up and calibrated. the new syntax and structure of the .ngc ngl files and ho to edit and test in real time in mios studio with some help. Every evening trying new things out all the time and constantly learning. I look forward to sharing things on the blog as I go, if I can help out in return please feel free to ask. Photo to come in my Gallery this week ;) May the blue smoke be with you. EOL
  20. is it strange??

    New Edit! EOL
  21. is it strange??

    1: Is it strange that all i could do all week was think about finishing work and getting on with starting to learn the mios32 code now i have gone through the .ngc code. 2: Is it also strange that i was looking forward to various components arriving today and gleefully picking them up from the delivery box after work 3: Refer to 1 & 2   EVENT_UNDERSTOOD    id= 1  type=command  CMD=1 range= 0:127 lcd_pos=1:1:1 label="^DoThis " COND_LABEL   DoThis COND <64    "Read 1&2" COND <127    "Goto 4:  " COND_ELSE  "--------" 4: Great success you are officially a midiboxer geek and should be proud ;) now refer to 1 & 2 but in C#
  22. understanding the .ngc code

    it is actually 5 rows of 8 but i used 2 rows as an example before i start trying this. I am just curious if it is possible, I will have a play this evening and see where i get to. I know that in thorstens blofeld files that there is the meta , bank and cond label used. i could alter this slightly but its the #cc as well. will see what happens tonight  
  23. understanding the .ngc code

    panel test day, checking fitment on led's and tact switches, then the pcb.
  24. understanding the .ngc code

    I have been playing with banks and cond labels again today all went well.  I was pondering something though. If i have a series of values i want to control from 3 knobs, so there are two lines of values, and 8 on each line, what i want to do to reduce the amount of encoders is have one for moving in the y direction between line 1 and line 2, then one to move in the "x" direction to step between 1 to 8 in the line, then a final encoder to change the value of the selcted cc#. in a basic explanation (not real code!!) Y= enc_1  if<64 line=1 Y= enc_1  if<127 line=2 X= enc_2  if<10 cc16   X= enc_2  if<20 cc17 X= enc_2  if<30 cc18 X= enc_2  if<40 cc18 Value= enc_3 type=CC ......... this encoder would have to change its code on each movement over x&y so cc=16, cc=17,cc=18 etc. Is it possible to do this in the .ngc?