Jump to content

TK.

Administrators
  • Posts

    15,189
  • Joined

Everything posted by TK.

  1. TK.

    MB8080 zu MB9090

    Hallo, die Namen koennen im setup_*.asm File konfiguriert werden: https://github.com/midibox/mios8/blob/master/apps/sequencers/midibox_808/setup_808_default.asm Ich koennte Dir ein neues .hex File mit den gewuenschten Namen bauen, muesste dann aber genau wissen, wie sie ausschauen sollen - maximal 5 Zeichen pro Name! Gruss, Thorsten.
  2. This isn't possible (and firmware changes in this direction are not recommended): the only permanent storage is an EEPROM, and it 1) has limited write cycles and 2) causes some delay during write operations. Are you using a 2x20 or 4x20 display? Parameter names are only displayed on a 4x20 LCD If this is the case, add: #if DEFAULT_LCD_LINES >= 3 ;; request printing label call CS_MENU_UpdateLabel #endif Best Regards, Thorsten.
  3. Hi @lukas412 should be possible, I added this to the wishlist Hi @k2z3k0 I added this to the wishlist as well. Could be available if Channel "Auto" is selected in Jam Mode MIDI Routing Config The mentioned wait time will be important (e.g. switch only if within the last second no event from another MIDI channel has been received). Best Regards, Thorsten.
  4. Hi, syxdump pos goes up to 12bit (=4096 bytes) But you've to be careful with CPU load - than more events are listening to SysEx streams, than higher the chance to get input buffer overflows, which would lead to some missing bytes (as you noticed). Best Regards, Thorsten.
  5. Hi, CCs have to be explicitly enabled in the setup_*.asm file - by doing so, you also define the MIDI channels: ; Optional channels for configuration via CC (1-16, select 0 to disable) #define DEFAULT_MIDI_CHANNEL_LAYER_A 0 #define DEFAULT_MIDI_CHANNEL_LAYER_B 0 #define DEFAULT_MIDI_CHANNEL_LAYER_C 0 #define DEFAULT_MIDI_CHANNEL_CFG 0 Best Regards, Thorsten.
  6. Hi, the issue could be related to following SID pins: pin #1-4: no caps connected pin #6: clock connection between SID and PIC. If no scope is available, you could check continuity by unplugging SID and PIC from their sockets. pin #28: Vdd - should be 12V for 6581, and 9V for other SID derivatives Best Regards, Thorsten.
  7. Hi, by default it's assumed that a 64k EEPROM (24LC512) is used - in this case patterns and songs are stored into the same BankStick If you are using 32k 24LC256 instead, it will be required to change the CS number in the setup_mbseq_v2.asm file, and to rebuild the .hex file Best Regards, Thorsten.
  8. We can keep this posting, it's still useful for people who have the same question :) Best Regards, Thorsten.
  9. Hi Pavel, to 1 and 2: add bsf CS_STAT, CS_STAT_DISPLAY_UPDATE_REQ under SID_KNOB_SetValue in sid_knob.inc To 3: MBSID has a pretty stable timing. I guess that you notice up to 30 mS lags due to the "well known" SID ADSR bug? See also http://www.ucapps.de/midibox_sid_manual_l.html and search for "ABW" There are two solutions: either set Attack/Decay/Release to 0, or enable the ADSR Bug Workaround (which will add a constant delay which has to be compensated in your DAW Best Regards, Thorsten.
  10. For scanning encoders just call MIOS32_ENC_UpdateStates before APP_SRIO_Prepare() See also MBNG application, search for MIOS32_ENC_UpdateStates: https://github.com/midibox/mios32/blob/master/apps/controllers/midibox_ng_v1/src/app.c Best Regards, Thorsten.
  11. Hi Pavel, the display could be immediately updated by adding following statement after "call CS_MENU_MS_SendKnob" in main.inc: bsf CS_STAT, CS_STAT_DISPLAY_UPDATE_REQ Best Regards, Thorsten.
  12. This should be fixed now, please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_097_pre1.zip Best Regards, Thorsten.
  13. I can't access the files, could you please attach them to this posting? I guess you mean CS_MENU_BUTTON_Knob Best Regards, Thorsten.
  14. Unfortunately further probability values can't be added, this would result into too many layer assignment options which can't be implemented. So, only "workaround" that I see: use a second drum track. Best Regards, Thorsten.
  15. It should work now -> http://www.ucapps.de/mios32/midibox_ng_v1_037_pre13.zip Reason was, that I "compacted" the storage for conditions so that it fits into a 32bit value. But meanwhile we've so many different event types, that I had to spend another bit for the hw_id of the condition. As a quick solution I sacrificed two bits from the condition value, and gave it to the id Which means: currently it's not possible to check for values >12bit anymore, but the ENC event type should be found as expected Best Regards, Thorsten.
  16. I added some enhancements into the firmware to support RGB LED Ring Patterns: http://www.ucapps.de/mios32/midibox_ng_v1_037_pre12.zip Usage example can be found here: https://github.com/midibox/mios32/blob/master/apps/controllers/midibox_ng_v1/cfg/tests/rgbled_3.ngc Best Regards, Thorsten.
  17. Problem was, that earlier versions didn't support labels with more than 40 characters, and the corresponding error message caused the crash. The error message is working now, and I've increased the max label size to 128 characters: http://www.ucapps.de/mios32/midibox_ng_v1_037_pre12.zip Best Regards, Thorsten.
  18. This issue should now be fixed in http://www.ucapps.de/mios32/midibox_ng_v1_037_pre12.zip Best Regards, Thorsten.
  19. Unfortunately I can't check this so easily, because I would have to unmount the frontpanel PCB - but I don't think that such a typo would indicate a bootleg. The PCB color looks identical to the original one. Best Regards, Thorsten.
  20. This should work... will check this tomorrow. Best Regards, Thorsten.
  21. It's related to the NRPN optimization which only sends out 99/98 when necessary - the SysEx stream based NRPNs bypasses it, therefore the problem. I will think about a solution which can handle this configuration properly... Best Regards, Thorsten.
  22. @lukas412 I remember that I got increased noise when the module is supplied from MBSEQ, therefore I jumpered it so that it's supplied from the 4ms pod PSU Best Regards, Thorsten.
  23. Hi Pavel, yes, this should be possible. In cs_menu_buttons.inc you've to define a new CS_MENU_BUTTON function, and program what you need. It has to be registered as a DIN_ENTRY in your setup_*.asm file Best Regards, Thorsten.
  24. I got some PCBs - hurray! :-) And while testing them, I found a bug in the WS2812 driver, which falsified the colours, and also influenced the colours of other LEDs - a very stupid one! Here an updated version: http://www.ucapps.de/mios32/midibox_ng_v1_037_pre11.zip Best Regards, Thorsten.
  25. Found the bug - fixed! :) Best Regards, Thorsten.
×
×
  • Create New...