Jump to content

TK.

Administrators
  • Posts

    15,246
  • Joined

Posts posted by TK.

  1. but I do have a preference for faders for envelopes

     

    No problem, sometimes I prefer faders & pots as well, especially when parameters should be tweaked during a live session and each fader/pot has a dedicated assignment anyhow.

     

    Such a PG-300 clone is a really easy entry point into the MIDIbox universe ;-)

    No programming skills are required if MIDIbox NG is used, since it provides an (hopefully easy to learn) configuration format.

     

    I found a SysEx specification under http://www.vintagesynth.com/roland/sysex.php

    And based on that I created a .NGC file to demo the configuration for a few control elements: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Fpg300.ngc

    You've to upload this file to the SD Card via the Filebrowser in MIOS Studio after the MIDIbox NG firmware has been installed.

    You can also edit this file in MIOS Studio later.

     

    It's incomplete (because it's only a demo), but as you can see, adding remaining parameters will be straightforward. Just copy&paste the event definitions and adapt them...

    If you need more guidance (and if the Manual doesn't give you the infos), just let me know and I will explain in more detail.

     

    For the MIDIbox NG you would need following modules:

    - MBHP_CORE_LPC17: http://www.ucapps.de/mbhp_core_lpc17.html

    - SD Card: http://www.ucapps.de/mbhp_sdcard.html

    - MBHP_AINSER64 for up to 64 pots & faders: http://www.ucapps.de/mbhp_ainser64.html

    - MBHP_DINX4 for up to 32 buttons: http://www.ucapps.de/mbhp_din.html

    - MBHP_DOUTX4 for up to 32 LEDs: http://www.ucapps.de/mbhp_dout.html

     

    Kits for these modules are available in SmashTV's shop: http://www.midibox-shop.com

     

    The MIDIbox NG firmware is located under http://www.ucapps.de/mios32_download.html and gets frequent updates - just follow the progress in this dedicated forum section: http://midibox.org/forums/forum/46-midibox-ng/

     

    Best Regards, Thorsten.

  2. I agree that I've seen the same issue.
    I just tried to edit some youtube links.
    Sometimes it was possible to get it right by removing special arguments (such as #t=x.ym), and by wrapping the url with ...
    But it also seems that the forum software only accepts the first two youtube videos, all others are displayed as plain URLs.

    I haven't found an option in the admin section which controls this.

     

    Found following option:

    Maximum number of media files per post: Too many media files embedded on one page can potentially crash the browser.

     

    However, I increased the number to 10

     

    but instead of creating a new post, it is putting the text into my previous post, as an edit! (I am currently the last poster in the thread.)

     

    ok, I disabled following option:

    When a member posts twice within n minutes, once after the other in a topic they will be merged into one post. Enter the number of minutes to capture concurrent posts. Enter 0 to not use.

     

    Let's try if it works.

     

    Best Regards, Thorsten.

  3. We should handle it like the swapped encoder pin issue - if more than 2..3 people encounter the problem, it makes sense to add this into the official firmware.

    Otherwise it's better to use a local workaround, and to wait what happens in the next months.

     

    Why? Because it could turn out, that the new parameter wasn't flexible enough, and that somebody else would need even more flexibility.

    Instead of adding "just another flag", it could be that a combined flag is the better choice, e.g. to enforce that conflicting configurations can't be selected.

    But if the "simple" flag was already published, it would be too late to change this, because it would affect the compatibility.

     

    Another reason could be, that I find a more clever idea for the implementation - again in this case it would be better to wait...

     

    In other words: I prefer to collect "use cases" before adding new features which I don't need myself to understand the potential issues which need to be solved, and to avoid unnecessary complexity.

     

    Back to your proposal: the code for LEDs is in MBNG_MATRIX_DOUT_PinSet and for patterns (ledrings, BPM digits, etc) in Hlp_DOUT_PatternTransfer

    You will notice that it's already quite complex.

    Even I would need several minutes to understand what I did several months ago, and where to change something to swap columns and rows.

     

    Especially since you will notice that I support MAX72xx as well.

    Which means, that I would have to ensure that the flag even works for this variant.

     

    And of course it would have to support all possible matrix variants, such as 4x8, 8x4, 8x8, 16x4, 16x8, 4x16, 8x16, etc...

    You see the problem at my side?

     

    Therefore please start with some experiments at your side.

     

    Alternatively, fix the PCB (cut tracks, solder wires) - could be faster ;)

     

    Best Regards, Thorsten.

  4. It should work if the EVENT_RECEIVER listens to the CC, and forwards it to a EVENT_SENDER which executes the meta event.

     

     

    unfortunately both dont work.

     

    the second one has syntax errors, such as "botton_mode" (wrong word, and wrong place, because a receiver isn't a button)

     

    Do you check for error messages in MIOS terminal whenever you update the .NGC file?

     

    Best Regards, Thorsten.

  5. The J1/J2 sockets are not "polarized" (no notch) - probably you decided this due to the missing space.

    But I would prefer this against J2 - so, just remove J2 again to make place for a polarized J1 connector.

    If somebody would like to chain multiple modules, he has to build an external adapter and solder it directly on the required pins.

     

     

    I isolated AGND and GND, and both top and bottom planes are connected. Is this a good idea? On the AOUT_NG PCB only the top layer is connected.

     

    to which ground are they connected?

    I would use the digital GND for both planes.

     

    Best Regards, Thorsten.

  6. Good progress! :)

     

     

    Everything is working except that after release the shift button and press it again, then all encoders are "activated" again, regardless their previous state.

     

    This shouldn't happen if you remove "Bank=2" from the EVENT_ENC statements which should be controlled from the .NGR script.

    Because with "Bank=2" the encoders will be part of the bank, and therefore automatically activated on each bank switching.

     

    Best Regards, Thorsten.

  7. I wonder if someone who is more familiar with the midibox than I am can comment on the advisability of simply lifting the back of R22 from the midibox board and connecting it to 5V (maybe from J2). Would that have any adverse consequences?

     

    Unfortunately this isn't possible with the LPC1769 due to a hardware bug in the chip.

     

    As you can read at the MBHP_CORE_LPC17 page: -> http://www.ucapps.de/mbhp_core_lpc17.html

    • output pins can't be used in open drain mode if a peripheral function like SPI or UART is assigned to it. This seems to be a design bug, because it isn't mentioned in the user manual (in distance: the description of the IO configuration implies that it should work, but it doesn't) - NXP support contacted, no reply yet!

     

    The consequence is, that the MIDI OUT pin can only switch between 0V and 3.3V, because works in push-pull mode.

     

    A workaround would be to level-shift the output to 5V, e.g. with a 74HCT541.

    This chip is already used for level-shifting, see also http://www.ucapps.de/mbhp/mbhp_core_lpc17.pdf

    You would need another one for the MIDI OUT port.

     

    Best Regards, Thorsten.

  8. Looks like a bug in the RAM based Wavetable option - I will check this soon!

    (I wasn't able to try SysEx access with this option due to the MacOS Java issues... :-/)

     

    As a temporary workaround, you could disable this option in your setup_*.asm file:

    #define WAVETABLES_IN_RAM   0
    

     

    Best Regards, Thorsten.

×
×
  • Create New...