Jump to content

TK.

Administrators
  • Posts

    15,261
  • Joined

Everything posted by TK.

  1. You can download it from this page: http://www.midibox.org/logo_competition/ Best Regards, Thorsten.
  2. Wie hast Du denn die Pull-Up Widerstaende an den DIN Eingaengen, sowie die Dioden an den Buttons verschaltet? Gruss, Thorsten.
  3. You can contact SmashTV for the current .brd file (he improved it meanwhile) Best Regards, Thorsten.
  4. I got the PCB files from Nils, and will handle the order next week (I'm too busy this week) Best Regards, Thorsten.
  5. Btw.: I've worked on MIDIO128 V3 in the last days. It runs on a MBHP_CORE_LPC17 module and will provide such nice features like: - storing/restoring presets on SD Card - integrated MIDI file player (files played from SD Card) - support for USB MIDI - support for up to 3 MIDI IN/OUT ports - support for OSC over Ethernet - optional user interface which can be directly connected to the core (no additional shift registers required): http://www.ucapps.de/mbhp/mbhp_scs_proto2.jpg - device can also be configured from the MIOS Terminal in MIOS Studio - preset files can be edited as a spreadsheet in Excel (or OpenOffice) Adding a 32x32 matrix driver would be a simple task for me, so if you are interested I could add this option Best Regards, Thorsten.
  6. Great! :) Best Regards, Thorsten.
  7. You are right, the selected sections are copied into SEQ_SELECTED_ABCD and played immediately. A synchronization mechanism isn't implemented, but it should be so difficult to add this. It's now in the Wishlist: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_808%2FCHANGELOG.txt Any other (simple to implement) feature request? Best Regards, Thorsten.
  8. Finally an useful feature which was easy to implement. :) MIDIboxSEQ V4.0beta46 ~~~~~~~~~~~~~~~~~~~~~ o added multi copy function: press MENU+COPY to export all selected tracks into the /PRESETS folder on SD Card. The resulting files are named COPY[track].V4T (the [track] numbers are independent from the actual track position) o added multi paste function: press MENU+PASTE to import "COPY[track].V4T" files from the /PRESETS folder into all selected tracks, starting from COPY1.V4T to (up to) COPY16.V4T o use these new functions to quickly copy&paste tracks between patterns and sessions, to create temporary backups, to duplicate tracks, or whatever. Note that you can also import these COPY[track].V4T files from the MENU->Event->PRESETS menu, e.g. to exclude certain parts of the preset o buttons of Wilba's Frontpanel are now debounced [/code] Best Regards, Thorsten. /edit: re-released at 21:15 since only the visible track was exported into the COPY*.V4T files
  9. Wenn ich Deine Notizen richtig interpretiere, dann sendet die rechte Seite der Matrix auch dann nichts, wenn die Shift-Register Zuweisungen getauscht werden, richtig? Dann ist hier sehr wahrscheinlich die Hardware falsch verdrahtet - die richtige Verdrahtung kannst Du Dir auf der linken Seite abschauen. Gruss, Thorsten.
  10. Did you load the same patch into all 4 cores? Best Regards, Thorsten.
  11. With a bit of luck it will work on your WinXP PC with MIOS32 Bootloader V1.4: But I fear that it won't help, as the WinXP issue on HP computers also happened with other generic USB MIDI interfaces in the past. Best Regards, Thorsten.
  12. Beta 45 is available: MIDIboxSEQ V4.0beta45 ~~~~~~~~~~~~~~~~~~~~~ o USB update for MacOS 10.7 Lion o Chords displayed correctly when a velocity layer is edited [/code] The scrub enhancement will need some work, as you won't notice any effect on the display if the sequencer is not running. The loop improvements for different track modes needs even more work. And session copy/create progress still not displayed Best Regards, Thorsten.
  13. A new bootloader version for MIOS32 is now available under http://www.ucapps.de/mios32_download.html It got an important update for MacOS 10.7 Lion - without this update, the USB MIDI port won't be available anymore, since MacOS tries to handle it like a CDC device. Even if you don't use MacOS the update makes sense, as it contains some minor improvements which I added in the last months. If you've already installed Lion and don't have an alternative computer with Mac OS 10.4/5/6, Windows or Linux available, an update is only possible via the common MIDI interface (port 1) Best Regards, Thorsten.
  14. NEWSFLASH: I installed MacOS Lion today, and noticed exactly the same problem at my side with the STM32, but also with the new LPC17 module! Funny, no? ;) MacOS reports that it tried to enumerate a CDC device (virtual COM port) - I remember that I fixed the descriptors so that the module is able to support USB-MIDI and CDC... let me check if it works better with a USB MIDI only descriptor. Best Regards, Thorsten.
  15. Ah - now I got it, and corrected the schematic! I'm sorry that this mistake caused trouble at your side! :-/ Best Regards, Thorsten.
  16. This is very strange, because the LEDs and buttons should be connected to the same common lines (blue lines in the mbhp_blm_map.pdf file), accordingly there is no reason why the LEDs should be mirrored. Could I have a look into your PCB layout? Modification: // extra row LEDs led_mod_ix = 4; led_row_ix = 1 + ((note >> 1) & 6); led_column_ix = note & 3; if( note >= 0x68 ) led_column_ix ^= 3; // mirrror LEDs 9..12 and 13..16 modify_led = 1; [/code] Best Regards, Thorsten.
  17. TK.

    MIDIbox FM V1.4

    Each velocity assignment allocates 3 bytes for CC assignment, initial value and depth. But the patch memory has only 4 bytes free. :-/ Best Regards, Thorsten.
  18. I already see a lot of exceptions in the code to get this properly working %-) will be fixed will be changed (starting the sequencer was my intention, but your argument not to do this is stronger) Short note from my side: the progress is currently not displayed if a new session is created, or an existing session is copied. It looks like the sequencer hangs up - but in fact only the LCD won't be serviced until the operation is finished. This should be fixed in the next release. Best Regards, Thorsten.
  19. Unfortunately this seems to be a common issue with HP computers and WinXP. See also and The last article contains a solution (install an alternative MIDI driver) Best Regards, Thorsten.
  20. Um zu ueberpruefen, ob es sich hierbei um ein Hardware- oder Software-Problem handelt, wuerde ich vorschlagen, in mios32_config.h die L/R SRs zu vertauschen: #define DIN_16x16_L0 11 #define DIN_16x16_R0 12 // DINs of second 16x16 matrix (counted from 1) #define DIN_16x16_L1 13 #define DIN_16x16_R1 14 // DOUTs of both matrices #define DOUT_16x16_L 1 #define DOUT_16x16_R 2 [/code] aendern in: [code] #define DIN_16x16_L0 12 #define DIN_16x16_R0 11 // DINs of second 16x16 matrix (counted from 1) #define DIN_16x16_L1 14 #define DIN_16x16_R1 13 // DOUTs of both matrices #define DOUT_16x16_L 2 #define DOUT_16x16_R 1 Welche MIDI Events werden nun gesendet? Gruss, Thorsten.
  21. Hi, The Java MIDI API which comes with MacOS 10.6 doesn't support SysEx. Workaround: install mmj: http://www.humatic.de/htools/mmj.htm Best Regards, Thorsten.
  22. This won't work, because the PIC based merger emulates the second MIDI IN via software, which requires low interrupt latencies. No chance to add the MIOS based SRIO driver, the PIC architecture is too slow (or you would need some really good assembly skills to manage this). You could use a second PIC to scan DINs... but today the most elegant solution would be to use the module (or a downstripped version built on veroboard) This tutorial demonstrates, how to route MIDI events: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F001_forwarding_midi%2F&# With following code in app.c: void APP_MIDI_NotifyPackage(mios32_midi_port_t port, mios32_midi_package_t midi_package) { // toggle Status LED on each incoming MIDI package MIOS32_BOARD_LED_Set(1, ~MIOS32_BOARD_LED_Get()); switch( port ) { case UART0: MIOS32_MIDI_SendPackage(UART0, midi_package); break; case UART1: MIOS32_MIDI_SendPackage(UART0, midi_package); break; } } [/code] you would route incoming events from MIDI1 and MIDI2 to the MIDI1 output The SRIO driver is already running in background. Following example demonstrates, how to handle DIN events: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F010_din%2F [code] void APP_DIN_NotifyToggle(u32 pin, u32 pin_value) { // toggle Status LED on each DIN pin change MIOS32_BOARD_LED_Set(1, ~MIOS32_BOARD_LED_Get()); // send MIDI event MIOS32_MIDI_SendNoteOn(DEFAULT, Chn1, (pin + MIDI_STARTNOTE) & 0x7f, pin_value ? 0x00 : 0x7f); } As you can see: there is no need to spend time on the old PIC platform anymore, because the new platform simplifies a lot. Best Regards, Thorsten.
  23. TK.

    metronome page

    Press EXIT, thereafter scroll with the datawheel to the right. The page is between "Save Pattern" and "MIDI Configuration" Best Regards, Thorsten.
  24. TK.

    seq jog wheel

    Wow! This gives me the vision of some new "MPC1000 jog wheel bulk order" topics :) Best Regards, Thorsten.
  25. Typically your DAW (like Logic, Cubase, Ableton Live) will allocate the MIDI port for the LC protocol, so that you are not able to control any other parameter from the same port. Accordingly you have to send MIDI events to a separate MIDI port anyhow. Best Regards, Thorsten.
×
×
  • Create New...