TK.

Administrators
  • Content count

    15,022
  • Joined

  • Last visited

Everything posted by TK.

  1. Hi Thomasch, I'm not working on it; motivation is low since AU/VST development is so cumbersome and I've the original device... If anybody else has the motivation & programming skills, he is welcome to take over. Best Regards, Thorsten.
  2. In the last weeks I re-implemented the MIDIbox SID sound engines in C, so that it is possible to run MBSID on a STM32 core, but also to emulate it accurately on a Mac or PC. The AU/VST gives you the possibility to try some MBSID patches before building the hardware. The sound isn't so fat like on the original, the filter sounds weak and there are a lot of aliasing effects when higher frequencies are played... but probably you will like it anyhow. The AU/VST is based on Juce, Dag Lem's reSID is used for SID emulation, and the part of my MBSID code is to control the SIDs with the possibilities described in the MIDIbox SID Manual. Download (current version 0.2 from 2014-09-28) AU (for MacOS): http://www.ucapps.de/midibox_sid/virtual/MIDIboxSID.component_v0_2.zip (64bit AU which works with Logic Studio 10) VST (for Windows and Linux): http://www.ucapps.de/midibox_sid/virtual/MIDIboxSID_v0_2.dll.zip Known issues: - only the first preset sound bank with 128 sounds is available. No possibility to access the sound parameters yet. - no access to CCs, NRPNs, SysEx yet This will be added very soon, so that it is possible to automate parameter changes, and to edit complete patches with Rutger's editor (Java), or Nils' editor under Windows - the VST doesn't work with Logic 5.5 under Windows - the AU requires MacOS 10.6 or higher - only 64bit supported anymore - only a single instance can be opened! To support multiple instances it will be required to implement the MBSID code in C++, but this will also increase the memory consumption which is bad for the STM32 build. I will evaluate the separation in classes later. Best Regards, Thorsten. P.S.: big thanks to Philetaylor for building the VST under Windows - it wasn't straightforward!
  3. MIDIbox SEQ V4 Release + Feedback

    Yes, drum labels are stored at the same place which is normally used for track names (a memory limitation...) However, feel free to try this out: http://www.ucapps.de/mios32/midibox_seq_v4_096_pre4.zip o It's now possible to customize the list of labels which are used during track/pattern name and category and drum selection. After booting the new firmware, following files will be created in the /PRESETS folder: TRKLABEL.V4P, TRKCATS.V4P and TRKDRUMS.V4P Edit these files with the MIOS File browser. Uploaded changes are immediately taken over. - TRKLABEL and TRKCATS: are used in MENU->EVNT, "Trk Inst.", "Edit Name" page (Use GP15 to select the Preset) - TRKDRUMS is used on the same page when a drum track is edited (instead of a track name we configure instrument names) Special treatment: TRKDRUMS.V4P also maps MIDI notes to the drum labels. Whenever a new preset drum is selected, the drum note will be changed accordingly. This allows you to fully customize drum maps. The first 16 drums are taken by default whenever a drum track is initialized, and the remaining drums in the list can be optionally selected to replace on of the 16 drum instruments. - TRKLABEL and TRKCATS are also used when a pattern is saved Best Regards, Thorsten.
  4. MIDIbox SEQ V4 Release + Feedback

    Yes, it's well hidden ;) I just remember that I wanted to make the "preset labels" configurable, so that they can be selected from a list stored in a file (so that users can define their own labels without changing the firmware). Will work in this later today... Best Regards, Thorsten.
  5. MIDIbox SEQ V4 Release + Feedback

    Yes, this is already possible: MENU->Event, press GP8 ("Track Instrument") At the right side you can edit the track name (and category) Once you gave the track a name, it will be displayed on the edit screen instead of MIDI channel and port Best Regards, Thorsten.
  6. The first demo with the final midiphy MBSEQ V4+ design - the melody is recycled and re-arranged from an older (10 years old) demo; somehow I was in that mood ;-) Best Regards, Thorsten.
  7. Config File - Assigning F1~F4 b uttons

    Hi Andrew, these button assignments don't exist, you should get an error message while the file is read (btw.: no need to reset the device, the file will be parsed automatically after upload). You could assign F1..F4 to BUTTON_DIRECT_BOOKMARK1 .. 4 instead. Please do this assignment at the prepared placeholders (which are assigned to 0 0 by default), otherwise they could overwrite your change. Once done, edit the MBSEQ_BM.V4 file: set for Slot1: +Page EVENTS Slot2: +Page DIRECTION Slot3: +Page DIVIDER Slot4: +Page LENGTH In these slots, also change the remaining "+" parameters to "-" (so that the values won't be taken over when you are pressing a bookmark button) Best Regards, Thorsten.
  8. Thanks for the hint and sorry for the trouble! :-/ I corrected the statement in the .pdf file Best Regards, Thorsten.
  9. MIDIbox SEQ V4 Release + Feedback

    You are right that this is a useful function, please try it out: http://www.ucapps.de/mios32/midibox_seq_v4_096_pre3.zip o New option 9/33 allows to unmute tracks on pattern changes Best Regards, Thorsten.
  10. MIDIbox SEQ V4 Release + Feedback

    Utility->GP15/GP16 Mutes/Unmutes all tracks at once (BLM works best in combination with the MBSEQ UI - better than inventing BLM shortcuts that we usually forget after 1 month...) The best way to get better control over mutes while changing patterns is the Phrase feature, especially if you use it from the beginning (e.g. store your pattern + mute + mixer map sets in Phrase slots via Song->Save&Take over patterns) Take care: this feature overwrites 1..4:A1..B7 depending on slot A..P) I should consider measure-synchronized Mute/Unmute for BLM as well (TODO) Best Regards, Thorsten.    
  11. MIDIbox SEQ V4 Release + Feedback

    I can add this to the wish list, it isn't so difficult to implement - but I know you guys, more people will request more assignable parameters, therefore I fear that sooner or later we reach the limits of assignable parameters and then a new concept will be required which is leading to much more implementation effort at my side. :-/ Best Regards, Thorsten.
  12. MIDIbox SEQ V4 Release + Feedback

    Happy new year!  Strange that I haven't noticed this during testing (maybe too much last minute code beautification ;) Here a new version: http://www.ucapps.de/mios32/midibox_seq_v4_096_pre2.zip Best Regards, Thorsten.
  13. MIDIbox SEQ V4 Release + Feedback

    I added a new option (13/32) which changes the ALL button behaviour. In addition I changed the behaviour of the selection buttons - this works much better for me :) o Improved selection handling for midiphy frontpanel: - if you press&hold the Bookm/Step/Track/Param/Trigger/Instr/Mute or Phrase button, and then make a selection with SEL or GP buttons, the selection button will jump back to the previous function - if you press&release these buttons without a selection, the function stays active. Example: let's say the track selection is active. Press&Hold Param button, change to a new parameter layer, then release the Param button -> the selection buttons will jump back to track selection. If it's desired to permanently control the parameter layer with the selection buttons, just press&release the Param button. o New option 13/32 allows to change the steps of the current selected view only -> http://www.ucapps.de/mios32/midibox_seq_v4_096_pre1.zip Best Regards, Thorsten.
  14. MIDIbox SEQ V4 Release + Feedback

    I remember that I never created new sequences on the RM1x and only used the preset patterns or sequenced the synth part with Cakewalk (a "DAW" running under Windows). And then I noticed that with a simple MB64 based sequencer I was able to work out interesting sequences much faster - this motivated me to add more and more features to the firmware, with the result that I created a dedicated sequencer with optimized UI - MBSEQ V2 was born: http://www.ucapps.de/midibox_seq_v2.html Best Regards, Thorsten.
  15. MIDIbox KB

    (need some time to think about the right connections) Best Regards, Thorsten.
  16. midiphy SEQ v4+

    Very good, you managed to finalize no. #3 :) Best Regards, Thorsten.
  17. sammichSID: troubleshooting [SOLVED]

    Hurray! :) Best Regards, Thorsten.
  18. MIDIbox SEQ V4 Release + Feedback

    MIDIbox SEQ started anno 2001 as an extension of MIDIbox64: http://ucapps.de/midibox64seq.html The interesting point: many basic concepts suchs as the layers and the unusual (but powerful) arpeggiator still exist today and make this device unique :) Best Regards, Thorsten.
  19. MIDIbox SEQ V4 Release + Feedback

    @monokinetic yes it should be possible without much effort to activate the same functions for MBCV (and MBNG) - will check this the next days @latigid on an optional enter button to confirm entries is not considered in the firmware and also not so easy to implement (too many changes at too many places) - I also wouldn’t use it by myself, therefore it won’t be supported. Best Regards, Thorsten.
  20. MIDIbox SEQ V4 Release + Feedback

    Finally v4.095 is available with a lot of christmas presents as found in the wishlist of many people :) MIDIboxSEQ V4.095 ~~~~~~~~~~~~~~~~~ o support for midiphy Frontpanel. The appr. HW configuration file can be found under hwcfg/midiphy_lh/MBSEQ_HW.V4 and hwcfg/midiphy_rh/MBSEQ_HW.V4 o introduced first "MBSEQV4+" function. MIDIbox SEQ V4+ is a special firmware variant for the STM32F4 core. It offers additional memory and/or CPU hungry functions which can't be implemented for STM32F1 or LPC17 due to resource limitations. These special functions are marked with "V4+" in future. o V4+: implemented CC layers for drum tracks. The CC numbers are statically assigned for all tracks of the session. They can be changed in the Options page (item 20/26) o trigger/layer edit views now also supported for drum tracks o reference step for pattern changes now works indpendent from reference step used for sync-to-measure o PATTERN page: pattern is switched immediately if SELECT button is pressed, regardless of the pattern change synchronisation option. o OPTIONS page: new option "Print and Modify Steps w/o changing Gate". If enabled: note values will always be print regardless if they are played or not. Changing a note value won't automatically enable the gate o OPTIONS page: new option "Print Notes with transposed value". Enabled by default (due to change in V4.093), can be optionally disabled now. o OPTIONS page: new option "Swap LED colours" (relevant for Wilba and midiphy Frontpanels) o OPTIONS page: new option "Invert Mute LEDs" o OPTIONS page: new TPD option "BPM" and "BPM with Beat": prints tempo value and optionally flashes to measure/beat o OPTIONS page: new TPD option "Logo" and "Logo with Beat": prints a 16x8 logo and optionally flashes to measure/beat There are individual logos for each session which can be edited in the MBSEQ_C.V4 file. If you don't find "TpdLogoLine" items there (because you are using an older session) just trigger the "Save" function o AOUT: MIDI Channel 9..12/13..15 now set the gate pins #1/3/5/7 as documented (previously it was #1/2/3/4 due to a code translation error) New: gate pins #2/4/6/8 are now set whenever the velocity is >100. This way the pins can be used as an accent trigger o V4+ AOUT: support for AOUT channel calibration. In the CV configuration menu, turn GP ENC #7 until 0V/1V/2V/.../Max will be visible. Calibrate the offset of the target value with ENC #8. Press GP #8 to cycle between min/0/max offset of the calibration point. Each V has a dedicated calibration value which can be configured this way, the output will be interpolated accordingly. Note that with exiting the CV configuration menu the calibration values are stored on SD Card in the MBSEQ_GC.V4 file (-> CV_Cali <cv-counting-from-0>). You could backup/set/restore the values from there if required. To reset all calibration values: delete all CV_Cali items in MBSEQ_GC.V4, store the file and enter "reset" in MIOS terminal. o Bugfix for permanently cleared notes if live recording is used after previous step recording o ProgramChange Layer: steps now disabled by default when the track is cleared o Whenever a track or parameter layer is unmuted, it will be automatically selected This option can now be disabled in the OPTIONS page (item 9/29) o new terminal command "lcd" allows to display a temporary message from on LCD from an external device via SysEx o encoder buttons can now be assigned in the MBSEQ_HW.V4 file (currently hardcoded to FAST function) o STM32F4 board: orange LED shows SD Card available, red LED any received MIDI IN, blue LED any transmitted MIDI OUT o experimental: terminal command "backup" creates a .tar file of the entire SD card. Whenever "backup" is entered, a new bak<incremented-number>.tar file will be created. This file can be downloaded from MIOS Studio (might take a lot of time!) or from a computer by plugging the SD Card into a SD Card reader. .tar files can be unpacked with "tar xfv <filename>" or with other decompression tools (might be already installed on your computer by default) o experimental (might be optional in future): show measure and pattern step position in main screen Best Regards, Thorsten.
  21. MIDIbox SEQ V4 Release + Feedback

    @midilab you will find the script which generates LCD screens under: http://www.ucapps.de/midibox_seq/gen_mbseqv4_screens It requires "perl" and "convert", and probably only works under Posix-like systems such as Linux and MacOS @monokinetic thanks for the feedback, it has been considered in the official release :) Best Regards, Thorsten.
  22. midiphy SEQ v4+

    Very very cool! :) Can't wait to get more time for MIDIbox again (in some days...) to continue with my build based on Peters superb tutorial :)  Will also release the firmware after some trial runs (and maybe some V4+ specific add-ons) Best Regards, Thorsten.
  23. BUTTON pins are DIN assignable?

    No this isn‘t supported – such mapping functions are very costly, without the NGC setup might be a bit more difficult, but I think this is an acceptable compromise. Best Reagrds, Thorsten.
  24. Thank you! :) Best Regards, Thorsten.
  25. This was a nice challenge for the weekend: I implemented a driver for USB MIDI Host mode into MIOS32 for STM32F4 :smile: (LPC17 and STM32F103 don't support USB Host mode...)   Tested with following devices: CME X-Key: Waldorf Blofeld: MIDIbox (here MIDIbox SEQ V4L): Ploytec GM5x5x5 USB MIDI Host mode just replaces USB MIDI Device mode via the USB OTG socket. The update will be available with all future MIOS32 applications, it's always available without special configuration. A special USB Micro-B -> USB 2.0-A adapter is required to connect the MIDI device.   Such an adapter is for example available at Reichelt (DELOCK 83183) for 5 EUR: http://www.reichelt.de/DELOCK-83183/3/index.html?&ACTION=3&LA=446&ARTICLE=126860&artnr=DELOCK+83183&SEARCH=DELOCK+83183   Pluck this adapter into the Micro-USB socket of the STM32F4-Discovery board, reset (or power-cycle) the core, and MIOS32 will automatically switch to USB Host mode.     Limitations: - USB hubs are not supported, the MIDI device has to be connected directly. - USB based Power-Supply is weak (limited to ca. 200..300 mA), which means that it might be required to power the MIDI Device with an external PSU - the MBHP_CORE_STM32F4 module has to be powered from the USB debug socket   Please let me know if you are interested to beta-test this enhancement, I could provide a preliminary version of a MIOS32 application.   Best Regards, Thorsten