Jump to content

TK.

Administrators
  • Posts

    15,246
  • Joined

Everything posted by TK.

  1. This is really strange! Especially because the working buttons are scanned over different matrix lines there is no simple explanation. In order to get a better picture, it would be interesting which buttons (and encoders) are working exactly. For this purpose I added a new testmode into the firmware: -> http://www.ucapps.de/mios32/midibox_seq_v4_089_pre1.zip After the upload, enter "set din_testmode on" into MIOS terminal, and then push all buttons and turn all encoders. Let me know, which buttons are working exactly (I need the Mx and pin number), and if the encoders are working. Best Regards, Thorsten.
  2. I spent some time this evening to make a proper map index handling possible - hopefully with success! Please try this version at your side: http://www.ucapps.de/mios32/midibox_ng_v1_033_pre7.zip step by step please! First we've to try to get the firmware stable again after the changes, this requires careful testing at both sides. I remember that there is an open request for defining transponse and split point, but my current focus is on fixing bugs, not adding new bugs^H^H^Hfeatures ;-) Best Regards, Thorsten.
  3. Ok, I added the new type "NoteOnOff", because there are more use cases (e.g. this btw. obsoletes the ain_mode=NoteOnOff) Could you please check if this works at your side? -> http://www.ucapps.de/mios32/midibox_ng_v1_033_pre7.zip This is a critical change, because there are some implications in the firmware that the type index matches with the MIDI event index + 8 (I tried my best to avoid a conflict, but it could be that I forgot a certain case) Best Regards, Thorsten.
  4. The DOUT module will work independent from the AOUT module. If you never tested the module before, it makes sense that you test it with another application. E.g. upload MIDIO128 and play some notes The MIDIO128 application also allows you to set DOUT pins directly from the MIOS Studio Terminal: set dout <pin> <0|1>: directly sets DOUT (all or 0..255) to given level (1 or 0) Best Regards, Thorsten.
  5. TK.

    New old bee

    Huebsch :) Gruss, Thorsten.
  6. Hi, this is because how maps are handled. With the current implementation, maps with duplicated values won't work. I've to check if an alternative option is possible which allows to handle your use case, stay tuned... Best Regards, Thorsten.
  7. Hi Justin, I don't know when a weekend starts at your side... ;-) However, here the quick&dirty migration: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fgoom%2F I expect that somebody else takes over the maintenance of this code, especially whenever Marks is doing updates. The code is taken from his website, it seems that sound parameters can be updated via Chn1 - at least I get some sounds when setting some CCs and playing notes. Best Regards, Thorsten.
  8. You could change the value to 0 during forwarding, this should result into NoteOff. Something like: fwd_id=SENDER:1:0 Best Regards, Thorsten.
  9. More likely somebody will use the 64 gate/triggers and control them from one or more drum tracks (which can be nicely configured with the BLM) than sacrificing common tracks for this purpose. Please don't get me wrong: such an option could be easily implemented into the firmware, and the configuration could be well hidden into a configuration file (or in the UTIL->Options page) in the hope that somebody (aside from you) will ever use it. But somehow I haven't the feeling that this is a useful feature compared to existing possibilities. And actually I would prefer to spend some time to overwork the CV/gate channel assignment concept and come up with a more flexible solution instead of providing just another poorly conceived extension. The current CV related possibilities are already too confusing and especially not scalable, as it turned out in various forum postings. Best Regards, Thorsten.
  10. The discussion gets confused - what is the actual use case for the 16 gates? And how should the gates be handled for drum tracks, which has actually multiple gates (one for each drum instrument). Best Regards, Thorsten.
  11. Hi, the first problem sounds similar (but not exactly) like the observed behaviour if a core with multiple USB ports is used under Windows. It would be interesting: - which windows version you are using - how does it behave if the "single_usb" option is enabled in the bootloader? -> see http://www.ucapps.de/mios32_bootstrap_newbies.html (you need to upload the bootloader update app to change the flag) - if you are using an older Windows version, such as WinXP, it might help to install the GM5 driver Strange indeed! I need more input under which circumstances this could happen, resp. if it can be reproduced. Has anybody else observed a similar issue in the past? Btw.: which MBNG version are you using? Best Regards, Thorsten.
  12. Just had a look into the source code - it shouldn't be so difficult to port this to MIOS32, I will check this next weekend. :) Best Regards, Thorsten.
  13. No, this isn't possible because the MBSEQ V4 based scheduler works MIDI tick based, not time based. Best Regards, Thorsten.
  14. The usage of the core based IO pins is dangerous, and therefore not recommended. Either a buffer IC (like the 74HCT541) is required for level-shifting (and protection), or just use a DOUT shift register which is the recommended and documentation solution at this page: http://www.ucapps.de/midibox_seq_manual_hw.html Best Regards, Thorsten.
  15. Well, actually I wanted to provide the "big solution" which allows complete external control - but it's too much effort compared to the benefit, especially since I always used the existing CS by myself whenever I made music with the MBSID (no need for any external editor capabilities at my side...) However, here the cheap solution: http://www.ucapps.de/mios/midibox_sid_v2_045_pre1.zip 0C/f) F0 00 00 7E 4B <device-number> 0C 20 <channel|instrument> F7 Changes the selected SID channel or instrument: - lead engine: selects between --, L-, -R, LR (range 0..3) - bassline engine: selects between --, L-, -R, LR (range 0..3) - drum engine: 16 instruments -> range 0..15 - multi engine: 6 instruments -> range 0..5 Numbers outside the range will be silently ignored In the hope that it satisfies your request, and doesn't require additional extensions... Best Regards, Thorsten.
  16. The next question will be to add CV outputs for channel 9..16 (which will require a lot of firmware changes), right? :-/ you could use the Duplication Fx for this purpose Best Regards, Thorsten.
  17. With such a configuration there is a certain danger for signal propagation delay issues with the result that the data value of one register won't be taken over by the following one with the rising clock edge (-> risk for a setup or hold violation). It might work at your side, but it could also fail. This depends on the wire lengths, impedances, ambient conditions. It's hard to calculate this (specially if cables and connectors are involved), or to give you a rule of thumb what is allowed or not. But I remember that many years ago some MIDIbox SEQ users noticed problems, such as flickering LEDs or random button events, due to a wild mix of DIN and DOUT SRs similar to this circuit http://www.midibox.org/midibox_seq_photos/3.html but just a little bit different (maybe longer cables between the SRs, or whatever) For the BLM16x16+X project I connected the DIN and DOUT registers Y like, and it works very robust: So - from my experience - I've to say that this seems to be a good way for stable shift register transfers. You might find some literature about this topic via Google to get an independent opinion, and maybe more hints how to get your layout "first time right". Best Regards, Thorsten.
  18. The MBHP_CORE_STM32F4 has more robust analog inputs, 7bit resolution is possible without jittering values. Best Regards, Thorsten.
  19. Hi, with MBHP_CORE_LPC17 (and later MBHP_CORE_STM32F4) I started to separate the RC pins at the core side for more flexibility (e.g. so that the SPI interface could be used for other purposes). So: on the rev5 DIN/DOUT board the bridge between the RC pins exists due to historical reasons, but it wouldn't be required anymore. On the other hand, only a single RC line is required for both chains (to answer the actual question) No, because SI has a different direction (it is driven by the 74HC165 chip and not by the microcontroller) no, this isn't correct (see answer above). The main reason for the Y cable is, that this is the best way to get two independent serial register chains. Mixed and/or unbalanced chains can result into electrical problems when multiple chips are connected together. However, if you use line drivers between the "bus boards", potential electrical problems are "localized" and therefore less relevant. But for common users who use MBHP_DIN and MBHP_DOUT modules the Y cable is "best practice" Best Regards, Thorsten.
  20. Hi, at which resolution are you using the analog inputs? (just copy&paste the configuration part of your .NGC file into this thread) Best Regards, Thorsten.
  21. Great! :smile: So - the final V4.088 is now available for download. Changes: MIDIboxSEQ V4.088 ~~~~~~~~~~~~~~~~~ o improved glide function for polyphonic steps o BLM16x16+X support for Mute and Solo The new functions are available at Extra Row Button #3 and #4 (if a BLM16x8+X is connected, they replace Start/Stop at Extra Row Button #1 and #2) If Mute active: the extra column buttons mute/unmute tracks If Solo active: the extra column buttons solo/unsolo tracks LED Colour coding: - LED off: Track neither muted nor soloed - LED green: Track muted - LED yellow: Track soloed - LED red: Track muted and soloed - solo has higher priority, therefore track will be played Special Key combinations: - ALT+Mute clears all mutes - ALT+Solo clears all solos o added Robotizer Fx from Borfo o added LCD Screensaver. It will be active after 30 minutes by default. The time can be changed in the UTIL->OPT menu page. o added DETENTED4/DETENTED5 option for rotary encoders in MBSEQ_HW.V4 file o added new parameter layers "Nth1" and "Nth2" which trigger a special action on each nth bar (Nth1) starting at the 1st bar, or after nth bars (Nth2). Following trigger conditions are available: - Pl (Play each nth bar) - Mu (Mute each nth bar) - Ac (Accent each nth bar) - Ro (Roll each nth bar) - Fx (enable Fx each nth bar) - Nx (don't enable Fx each nth bar) o combined Record and Live page to a new single "Jam" page with sub pages to improve the overview and simplify the configuration. o added Live Pattern Recording to Jam page which can be used to play and record customizable arpeggiator sequences. Available in the Jam page (Utility->Jam->Ptn) See updated user manual for further information. The new features are described (in a bit more detail) in the user manual: http://www.ucapps.de/midibox_seq_manual_m.html Best Regards, Thorsten.
  22. Yes. The example shows: EVENT_BUTTON id=2000 type=Meta meta=SetBank button_mode=OnOnly range=1:1 With: EVENT_BUTTON id=2000 type=Meta meta=SetBank button_mode=OnOff range=0:1 the button would set the second bank when press, and the first bank when depressed Or with: EVENT_BUTTON id=2000 type=Meta meta=SetBank button_mode=Toggle range=0:1 the button would toggle between the first and second bank Best Regards, Thorsten.
  23. The question was related to MIDIbox NG. Here a configuration example for 4 banks: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fencbanks.ngc It shows how to send different CCs, but you could change the configuration to select different channels instead. E.g. instead of: # Bank 2 EVENT_ENC id= 17 hw_id = 1 bank=2 fwd_id=LED_MATRIX:1 fwd_to_lcd=1 type=CC chn= 1 cc= 32 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:1:2)%B" EVENT_ENC id= 18 hw_id = 2 bank=2 fwd_id=LED_MATRIX:2 fwd_to_lcd=1 type=CC chn= 1 cc= 33 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:2:2)%B" EVENT_ENC id= 19 hw_id = 3 bank=2 fwd_id=LED_MATRIX:3 fwd_to_lcd=1 type=CC chn= 1 cc= 34 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:3:2)%B" write: # Bank 2 EVENT_ENC id= 17 hw_id = 1 bank=2 fwd_id=LED_MATRIX:1 fwd_to_lcd=1 type=CC chn= 2 cc= 16 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:1:2)%B" EVENT_ENC id= 18 hw_id = 2 bank=2 fwd_id=LED_MATRIX:2 fwd_to_lcd=1 type=CC chn= 2 cc= 17 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:2:2)%B" EVENT_ENC id= 19 hw_id = 3 bank=2 fwd_id=LED_MATRIX:3 fwd_to_lcd=1 type=CC chn= 2 cc= 18 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:3:2)%B" ... Best Regards, Thorsten.
  24. Another special condition that I haven't considered... ;-) Please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_088_pre23.zip Best Regards, Thorsten.
  25. Ok :phone: Best Regards, Thorsten.
×
×
  • Create New...