Jump to content

FantomXR

Members
  • Posts

    1,035
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by FantomXR

  1. Hey,

     

    thanks for the tutorial.

    But I'm stucked at the perl-point. The perl-script says:

    ERROR: Wrong Pixel Size - expecting x = 192!

     

    I double checked everything. I converted the file first to bmp, than to xpm like described in the tutorial. I also tried to export it directly to xpm. 

    Any tipps you can give on that? The file has a size of 192x128, exactly like your example...

     

    //edit: Ok... solution: It has to be black and white... no grayscale... I overread this point... let's go on ;)

  2. I did an order at Yoybuy at 26th of april and received all parts (10 displays) today. That was really fast... I paid with credit card... so my experience is good.

    Incl. shipping I paid $100... so less than $10 per display. The shipping is quite expensive, if you want to get it fast. If you have time (like 30 days), than it's a lot cheaper.

  3. Lieber Stephan,

     

    die Verschaltung laut deinem Plan sieht soweit korrekt aus. Da kann man auch wenig falsch machen, außer, was mir recht oft passiert und eine unangenehme Fehlerquelle ist, ist die Orientierung der Stecker. Achte darauf, dass du immer die immer richtig steckst. 

     

    Das Benehmen des Octatracks ist wirklich seltsam. Am einfachsten wäre, wenn der Octatrack immer alle CCs raussendet, wenn du ein Programm wechselst. Sollte es das nicht können, wundert mich das aber auch nicht. Selbst ein Yamaha Motif ist dazu nicht wirklich in der Lage...

     

    Du kannst jedem Parameter einen Namen zuweisen. Dafür müsstest du dich mal mit dem NGL Format beschäftigen. Das hab ich bisher noch nicht gemacht, wird aber auch bald kommen. Hab mir gerade einen Satz Displays bestellt. 
    http://ucapps.de/midibox_ng_manual_ngl.html

    Hier findest du das Manual zum NGL. Damit sollte es möglich sein, was du vor hast. Auch kann ich dir diesen Guide noch ans Herz legen, der zeigt, wie man individuelle Symbole anlegt:

  4. Hey people,

     

    for those of you who are using motorfader with a 4pin connector I created a PCB. 

     

    6pin connector Fader_01, Fader_02, is going to the 4pin connector on the fader plus two cables for the motor.

    2pin connector Motor_01, Motor_02, etc. is going to the MF_NG pcb. 

    J1 is going to J2 (analog inputs).

    J2 is going to J14 (touch sensors). 

     

    Because this one is a single-layer layout, you need to connect the vias. I named the signals in eagle (use the info-tool).

     

    post-10331-0-41334000-1398700937_thumb.p

    MF_Adapter.brd.zip

  5. Hey,

     

    thanks for getting back to me.

     

    I found the dimled.ngc before, but not the other one. Thanks... I will try that today evening.

     

     

    //edit:
    A few days ago when I was in the local music shop I saw, that the company Kenton has a nice little module on the market. With this box you can convert USBMIDI to real MIDI. This is really useful, if you want to implement usb-midicontroller in your environment, that have no midi. The drawback is, that it's at 99€. TK, do you think to implement such kind of feature into the _NG too? 

  6. Hey people,

     

    just a short programming question:

     

    I have several LEDs connected in a DOUT_Matrix as well as several switches in a DIN_Matrix. I can easily assign one switch to LED to turn it on and off. But what I want to do is, not to turn off the LED completely. I want it to go down till, let's say, 25% of maximum brightness. How to do that? 

    With other word: Press button --> LED goes to 100%, press button again --> LED goes to 25%. 

     

    The reason why I want to do is, that I want to see the buttons even if it's dark outside. So I need kind of illumination of the buttons.

     

    Thanks,

    Chris

  7. Sorry, that wasn't clear.

     

    What I meant was, to chain two led-matrix-pattern. To simplify the case: Is it possible, to set up 2x16 LEDs (=32 LEDs in total) and to program the ngc-file in the way, that the first 16 leds listen to cc (x) and value 0-63, and the second set of leds to cc (x) and value 64-127? With that setup it should be possible, to get a higher resolution on led-feedback or am I wrong?

  8. Thanks for the link.

     

    Yes, I could chain two of these. That should work.

     

    Another idea is, to simply add two SR and add eight LEDs, which are assigned to a separate led-pattern. Than I scale the cc-value on the first led-stripe from 0-80 (value need to by correctly calculated) and the second stripe from 81-127. 

     

    How about this?

  9. Hey,

     

    I'm wondering, if there is a chance, to add more LEDs to a led-meter. I'm asking because I can't find any 16-segment-led-meter and would need to build them by myself, which is a lot of work. I found a 20-segment-led-meter. 

     

    Any informations about this?

     

    Thanks,

    Chris

  10. Seems like I need to bang my head against the wall to get the solution.

     

    I just try a simple thing. I have a set of LEDs but for testing I just use one. Because I want to be able to control a lot of LEDs individually, I use DOUT_MATRIX. Here is the code:

     

     

    RESET_HW
     
    DOUT_MATRIX n=1   rows=8 sr_dout_sel1=3  sr_dout_r1=4 inverted=0 led_emu_id_offset=1
     
    EVENT_LED  id=1  type=CC cc=16

     

    So, what I do expect is that the LED connected between D7 of SR3 and D7 of SR4 lights up as soon as it receives value 127 of CC16. But instead of this it lights up and it doesn't matter what I do with the slider in MIOS Studio. If I check all other pins, I have the same effect on every pin-combination. I expect them to be 0V but they aren't. If I swap anode and cathode the led is off with cc value 0. If I move the slider to 127 it begins to light... but it's very low. I have the same effect on every pin-combination.

     

    Time to go to bed?! This shouldn't be too hard to solve.... 

     

    I measured the voltages: It's 4,25V between every SR3 and SR4 pin. How come? I tried another DOUT module. Same here.

     

    I have another DOUT module here which is equipped with a ULN2803 on the first SR. With this one and this code:

    DOUT_MATRIX n= 1 rows=8 inverted_sel=1 sr_dout_sel1= 1 sr_dout_r1= 2

    the voltages between the pins are as expected. BUT the led is very low...

     

    Any tipps? Thanks! 

     

     

     

    //Edit:
    Okay... the next day... notice to myself: Read schematics carefully. I forgot to remove the resistor on the first SR in case #1. And I forgot to set the led_emu_id_offset=0 in case #2.

    But anyway: The led is really a lot brighter if I connect it directly to a DOUT without matrix or ULN. Even with ULN its pretty low... has it something to do that I use warmwhite LEDs?

     

    //edit:
    I'm using a ULN2803. So the short leg goes to D7 of SR1. Than I removed the resistor on SR2 and connected the long leg to D7 of SR2. It works, but even than it's not that bright. Is there a chance to get more brightness without connecting each LED individually?

  11. Hey,

     

    I set up my motorfaders and try to get the touchsensors running. For testing I use just one fader and limit the numbers of faders in to MF_NG tool inside MIOS Studio to 1 to not get any jitter values of the open fader-ports.

    I connected T0 of the PCB to the touchsensor of my motorfader (ALPS coreless 100mm 10k lin.), GND to GND of the motorfader. There is nothing happening... even if I disconnect the touchsensor-cable I would expect, that I get a lot of random values, because the touchsensor port is open and not connected to anything. But: The monitor says nothing. 

     

    It also doesn't care which fader-mode I use... same with touchsensor-mode and touchsensor sensibility.  

     

    Well, it's late now so I will give it a fresh look tomorrow. But any tipps are welcome :)

     

    Thanks,

    Chris

  12. Hey people,

     

    due to the limit of space in my upcoming project I need to design a PCB, which is as small as possible.

    It just needs to run MB_KB, so the only things, which are necessary, are the power supply (no USB needed here) and power-schematic (not included in the attached image), the LPC itself, the 74HCT541N, MIDI Out 1, J5A (for sustain / expression) and J8/9 (for DIO_Matrix).

     

    So here is my design I just created. I need someone to confirm, that it will work like this and I didn't forget any connections. For example: How about the unused pins of the 74HCT541N? Do I need to ground them?

     

    I hope, that someone will get back to me ;)

    Thanks again,

    Chris

    post-10331-0-12465300-1394069625_thumb.p

    post-10331-0-13277600-1394069626_thumb.p

  13. Thanks for the fast replys!

     

    Okay, than I stick to the old MIDI.

     

    And: What is the smallest (in budget and dimensions) MIDI Interface with at least 4 inputs and 2 outputs? Still the midibox core or is there anything else I overlooked?

  14. nIs there any sense in transmitting the midi signal in a OSC bundle via ethernet to my mac? I read through the OSC-page of ucapps and it says, that OSC is faster then MIDI... but to do this, first a MIDI signal has to be created to be packed into a OSC bundle. Is that correct?
    If yes, there is no advantage in speed, right?

×
×
  • Create New...