Jump to content

FantomXR

Members
 View Profile  See their activity

  • Posts

    1,035

  • Joined

  • Last visited

  • Days Won

    22

 Content Type 

Posts posted by FantomXR

  2. AINSER deadband configuration?

    in MIDIbox NG

    Posted

    31 minutes ago, Zam said:

    I'm not used to this color LEDs but they use PWM to acheave 20% power and color change right ?

    Yes! Correct!

    31 minutes ago, Zam said:

    PWM can introduce noise which can also be the reason you notice jitter, in conjunction with voltage drop if there is any ?

    I tried to measure this with my DMM. But I'm afraid my DMM is not the best. I'll use my oscilloscope to check that.

    32 minutes ago, Zam said:

    By the way, what for the 19V rail is?

    This is for a small computer which sits in the housing. It's a great idea to use a small regulator... but like you said: I'll start with separating the PCBs.

    Thanks for your help!

  3. After boot MIDIbox sends weird informations

    in MIDIbox NG

    Posted

    Hey people,

    when I connect my MIDIbox-Keyboard (KB-app, not NG) to my MacBook and boot the MacBook, the keyboard sends weird informations like note Off instead of note-on. If I switch off the MIDIbox and start it again after the OS has booted, it works perfectly. Do you have any ideas what is causing this issue? The fastboot-setting doesn't change anything....

    Thanks,
    Chris

  4. AINSER deadband configuration?

    in MIDIbox NG

    Posted · Edited by FantomXR

    @Zam: Thanks for your suggestions. If you take a look at my screenshot above you will notice 9 4pin-pinheaders right next to the faders. This where the WS2812-PCB sits on. Do you think it makes sense to remove those headers and connect the LEDs directly? Maybe it's a problem that both (faders & LEDs) share the same PCB?

    BTW: I use a MeanWell RS15-5 Powersupply and I have 6 LEDs next to each fader => 6*9 = 54 LEDs. And none of them running at full power. They are at about 20%...
    I need to measure the current of the whole circuit. Maybe I should upgrade the PSU to MeanWell EPS-35-5?

    //edit: While my current PSU RS15-5 has a load regulation of  +-1,5% which means 75mV the EPS-35-5 has a load regulation of 1% => 50mV.
    So you would suggest to add another power supply that is just connected to the LEDs? What is sense detection? I'd be happy to NOT add another power supply because I already have two supplys in the housing... 19V and 5V.

    Thanks for your help!

  5. AINSER deadband configuration?

    in MIDIbox NG

    Posted

    Dear @Zam

    You are totally right. That doesn't make any sense ;-)

    Today I checked what you suggested. In the end it were the WS2812 LEDs that caused the potentiometers to jitter.... if I don't connect them, everything works great.... so I need to find another way to implement them into my setup....

  6. AINSER deadband configuration?

    in MIDIbox NG

    Posted

    7 hours ago, Zam said:

    If that's the question you ask ?

    No. What I was asking is: If you configure your analog inputs via the AINSER command (AINSER n=1 enabled=1 cs=0, etc. pp.) the resolution of the EVENT_AINSERs that belong to this configuration of course use the resolution you entered in the AINSER configuration. 

    I basically use the AINSER64. And using the standard method for the configuration allows me to set ONE resolution for the whole AINSER64 module. But what if I need a resolution of 7bit for the first 8 inputs and 11bit on the second 8 inputs? Hmmmm :-)

  7. AINSER deadband configuration?

    in MIDIbox NG

    Posted

    @Zam: I had no time yet to follow up on your suggestions. But I'll do as soon as possible.

    Maybe you can answer another question: Is it possible (f.e. by modifying the source code) to set the resolution on a per-pin-base and not on a per-chip base? I ask because if I connect pedals as well as pitch to my board, than I don't need 11bit on the pedals, but I need them on the pitchwheel. I don't want to waste an IC just for one analog input ;)

    Thanks,
    Chris

  8. Midi Controller für "The Legend"

    in Deutsch

    Posted

    Grüße!

    Meiner Meinung nach kann ein Encoder nie das Gefühl eines Potentiometers nachbilden. Und da ein Potentiometer keine Rasterung hat, würde ein Encoder ohne Rasterung dem Poti wohl am nächsten kommen. 

    Bzgl. Knöpfe teile ich dein Leid. Ich hab zwar eine gute Quelle gefunden, allerdings sind die MOQ ziemlich heftig mit 1000stk. Schau mal rein bei chiashinknobs.com.tw

    Lg,
    Christian

  10. Send delayed midi message?

    in MIDIbox NG

    Posted

    Yes, sure. But the NGR doesn't track any other midi commands. So for example take a fader which sends CC80. If the fader is not moved for 3 seconds, CC81 value 127 should be send. But if the fader is moved after 2 seconds, the timer needs to reset. This is not possible with NGR afaik. 

  13. Send delayed midi message?

    in MIDIbox NG

    Posted

    Hey people,

    I use a vst live host that allows showing / hiding the GUI of a plugin by sending a midi message. If I f.e. move a fader on my controller, the plugin shows up. But what I need is another midi message that gets send after a delay of f.e. 3 seconds after the fader has been moved to hide the GUI again. 

    Any ideas how to do that? 

    Thanks,
    Chris

  14. AINSER deadband configuration?

    in MIDIbox NG

    Posted

    Thanks for your suggestions! I'll try that, but time is very limited at the moment! Will give you a feedback asap!

    Regarding your questions:

    - GND-Plane is on both sides.
    - I have the impression that the first faders are not jittering... but will need to do some more testing here
    - will do! Thanks!

  16. [SOLVED] Multiple MIDIbox cores in windows

    in MIDIbox NG

    Posted

    You are wrong! ;-)

    I added these lines to the mio32_config.h file of the desired application (no bootloader rebuild needed). 

    
// Following settings allow to customize the USB device descriptor
#define MIOS32_USB_VENDOR_ID    0x16c1        // sponsored by voti.nl! see http://www.voti.nl/pids
#define MIOS32_USB_VENDOR_STR   "Test"       // you will see this in the USB device description
#define MIOS32_USB_PRODUCT_STR  "Test2"      // you will see this in the MIDI device list
#define MIOS32_USB_PRODUCT_ID   0x0405        // ==1023; 1020-1029 reserved for T.Klose, 1000 - 1009 free for lab use
#define MIOS32_USB_VERSION_ID   0x0200        // v1.00

    The original which I found in the bootloader is this: 

    // Following settings allow to customize the USB device descriptor
#define MIOS32_USB_VENDOR_ID    0x16c0        // sponsored by voti.nl! see http://www.voti.nl/pids
#define MIOS32_USB_VENDOR_STR   "midibox.org" // you will see this in the USB device description
#define MIOS32_USB_PRODUCT_STR  "MIOS32 Bootloader"  // you will see this in the MIDI device list
#define MIOS32_USB_PRODUCT_ID   0x03fe        // ==1022; 1020-1029 reserved for T.Klose, 1000 - 1009 free for lab use... 0x3fe is required if the GM5 driver should be used
#define MIOS32_USB_VERSION_ID   0x1010        // v1.010

    I assume that windows takes the VID and the PID to identify the device. If you change those values for your second application, this works perfectly. Windows recognizes both devices! Also MIOStudio is able to edit both applications! :-) 

  17. [SOLVED] Multiple MIDIbox cores in windows

    in MIDIbox NG

    Posted

    @Duggle: I did some more searching on this topic. And I found some useful informations in the bootloader-source code. There you can define unique USB data f.e. Vendor ID, etc.pp. Unfortunately I'm not able to compile the bootloader... I get some errors and the file in the end is only 15kb compared to the bootloader from ucapps.de which is at 150kb or so...

  18. AINSER deadband configuration?

    in MIDIbox NG

    Posted

    5 hours ago, Zam said:

    I don't now about mux with distant wire, maybe buffer is requested for strong data over long trace, is your "jitter" random regarding value or "around" the actual pot position ?

    it's around the actual position. If the fader is at 105, it sometimes jitters on 106 / 107 f.e.

    Of course VREF and standard V+ (5V) do not share the same trace. I attached a screenshot of the PCB:
    https://www.dropbox.com/s/ibrunxjkxhdqs5z/BournsPTA.png?dl=0

    VREF is the big trace on the very top of the PCB. J1 is the input, J2 forwards the unused analog inputs of IC2, which I need for nine faders on this PCB. 

    I'll do what you suggested! Thank you for your help! 

    I use Bourns PTA slide-pots with 10k.

     

  20. AINSER deadband configuration?

    in MIDIbox NG

    Posted

    Hello Zam,

    thanks for your reply.
    It's not jittering like a lot of values are send by the slide pot. It's just like every now and then (like every 2-3 seconds but sometimes it stays stable for ever) it sends a value. So maybe I want to have it too perfect ;-) What I'd like to have is a kind of "IDLE" function, which I found in the mios32_ain.h in /svn/mios32/trunk/include/mios32/

    It's description reads: 

    // define the deadband which is used when an AIN pin is in "idle" state
// this helps to avoid sporadical jittering values
// Set this value to 0 to disable the feature (it's enabled by default)
#ifndef MIOS32_AIN_DEADBAND_IDLE
#define MIOS32_AIN_DEADBAND_IDLE 230
#endif

// define after how many conversions the AIN pin should go into "idle" state
// - "idle" state is left once MIOS32_AIN_DEADBAND_IDLE is exceeded.
// - "idle" state is entered once MIOS32_AIN_DEADBAND hasn't been exceeded for 
//   MIOS32_AIN_IDLE_CTR conversions
// 3000 conversions are done in ca. 3 seconds (depends on number of pins!)
// allowed range: 1..65535
#ifndef MIOS32_AIN_IDLE_CTR
#define MIOS32_AIN_IDLE_CTR 3000
#endif

    I thought it may be possible to move the slider into the desired position f.e. to value 64 and "lock" it so it only sends any further CCs if the slide pot changes significantly. 

    Regarding my wiring: The slide pots are mounted on a PCB which I designed. 5V track is at 0,8mm and GND is designed as plane. The faders are scanned through an AINSER64 module. But this I also designed by myself. The 74HC595 and the MCP3208 are sitting on the mainboard, while the 4051 are directly mounted on the fader-PCB. The cable to the fader PCB is about 30cm. The faders are running at 7bit. 11bit leads to a lot of jitter. Power through USB at the moment, but I'll change that too a MeanWell 5V powersupply.

  21. AINSER deadband configuration?

    in MIDIbox NG

    Posted

    Hey people,

    I searched the NG-firmware for the parameter, which set's the deadband of the AINSER-inputs. I found this:

    #define MIOS32_AIN_DEADBAND 31

    But if I change that to f.e. 100 or more it doesn't change anything. My problem is, that my slide potentiometer have some jittering (even when the pinrange is set) when they are not at 0 or 127. 
    I also found the parameter

    #define MIOS32_AIN_IDLE_CTR 3000

    But changing this value also doesn't make any difference.

    Does anybody know where to set this value?

    Thanks,
    Chris

  22. [SOLVED] Multiple MIDIbox cores in windows

    in MIDIbox NG

    Posted · Edited by FantomXR

    Hey people,

    I have two MIDIboxes here and I have some trouble with connecting them to Windows. 

    I configured both cores to single-usb and I gave them individual names (f.e. Key and Controller). I also set the device ID of Key to 0 and of Controller to 1.

    If I now connect both MIDIboxes to my computer (running Win10) the thing is, that MIOStudio is not able to differentiate between both cores although I did set different device IDs. Also both cores will have the same name! It depends on which core I connect at first. If I connect Key at first, both MIDIboxes will be namened "Key". 

    Also my DAW names them the same but adds a number behind the name. So the first MIDIboxes is "Key" and the second "Key #2". 

    Is there any workaround for this issue?

    thanks,

    Chris

  23. RGB hue sweep

    in MIDIbox NG

    Posted

    Hey people,

    I have an idea in mind but I don't know if it's possible to program it. It seems like a challenge.

    Let's assume we have a midi-keyboard and a strip of WS2812 on top of the keys. What I want to do is, visualizing the split-zones of the keyboard. My DAW is able to send tons of different values f.e. CC, NoteOn, SysEx, NRPN, and so on.
    My first idea was to assign a CC to the LEDs f.e. CC16. If I now send CC64 to the MIDIbox, all LEDs would light up which are <= 64. But what if I only want LED10-LED16 to light up and not the LEDs which are lower than that? 
    Another idea: Assign a CC-value to every LED f.e. value 0 = LED1, value 1 = LED2, etc. But that would mean, that A LOT of MIDI data has to be sent to the MIDIbox on patch-change.

    So is there anything I overlook? Do you have any other ideas how to address a range of WS2812 LEDs?

    Thanks,
    Chris 

×
×
  • Create New...