TK.

Yes, each bank stores 64 patterns, and I'm normaly using a separate bank for each group (e.g. one bank with drum patterns, one with bassline patterns and synth lines, one for filling the song, another for loopback sequences to transpose/arpeggiate other patterns) It's half finished, but especially since a mkdir() is available now, there is no blocking point anymore already available, just create /SYSEX/<mysynthfolder> Do you really want such a deep hierarchie? Just create three folders for your synth Have you already tried to navigate through the SysEx menu? It's really fast - I don't really see a need for subcategories! Not implemented yet Not implemented yet, but prepared (you are just quoting the concept that I wrote some times ago in a different thread ;)) Thats the way how it will work. It's already possible to send dumps by pushing a button, have you already tried this? Is it working at your side? How would you exactly like to edit such a list? Would a .txt file with references to the dumps be sufficient? I'm not sure if I will find the time and motivation to integrate such an editor into the firmware (no usecase for myself) Again: how exactly would you like to edit this? I don't see a clear vision how the UI should be realized. It would be interesting how many people would really work this way, so that I know if it is really worth the effort to integrate additional editors so that absolutely no computer is required. To repeat Strophlex' statement: > There are so many concepts in the SEQ V4 so I get a bit confused... and this is what many people are saying. Best Regards, Thorsten.

Please don't reformat the SD Card, it would be interesting if it is working with beta17. Debug messages: thats a bug, I will fix this in beta17 as well. Best Regards, Thorsten.

I guess that the SD Card access is working, but: FAT12 is unusual, I never tested this format with DOSFS. However, since MBSEQ will use a new FAT driver (FatFs), there is a certain chance that the card can be successfully read with beta17 Best Regards, Thorsten.

The migration to FatFs was successful, directories can be created and especially copy operations are working much faster now! :) Questions to the users: do you really need 8 banks, or would it be sufficient to work with 4 banks in a session? This would speed up the creation of a new session, resp. the copy operation of an existing session would work faster as well. Note that it will be possible to switch between sessions in zero-time! :) But creating/cloning a session will consume some time (e.g. copy: ca. 30 seconds, with 4 banks instead of 8 maybe 20 seconds), and the sequencer will run unstable while files are copied. Best Regards, Thorsten.

No, this isn't normal. What are the results of the (overworked) MIDI troubleshooting guide? -> http://www.ucapps.de/howto_debug_midi.html It would be especially interesting if the loopback is working on TEST MIDI2, and *not* working if the Rx/Tx loopback is removed. The results of the other tests would be interesting as well to get a full picture. Another hint: use MIOS Studio 2 - it works more reliable than the Java based version. Best Regards, Thorsten.

Looks very interesting! It's worth a try - not at least to compare the performance (the integrated caching mechanism will make things easier) Best Regards, Thorsten.

Great results! :) the MBSEQ application uses the status LED for a different purpose, but since it's even possible to read the directory, the communication between core and SD Card seems to be ok. Could you please try usb_mass_storage_device_v1_1.zip? This version uses exactly the same SD Card driver like the MBSEQ release. The latest changes have been added by Phil to support MMC and HCSD - although your card seems to be a common type, it seems that the changes solve previous access problems. If the MSD application still crashes, it will be very difficult to debug this remotely :-/ (even with a TCP/IP connection to the core ;) Best Regards, Thorsten.

Hi David, it would be interesting if the MBSEQ V4 application is able to read the SD Card, or if the core will be rebooted as well. In the most recent release (beta16) I integrated a command interface to access debugging functions from the MIOS32 terminal, which is part of MIOS Studio 2: Could you please try it? Just enter "help" to test that the communication is working, and "sdcard" to retrieve informations from the SD Card Best Regards, Thorsten.

A new release is available: MIDIboxSEQ V4.0beta16 ~~~~~~~~~~~~~~~~~~~~~ o MIDI->Section Control: Octaves which are not taken for section selection can now be optionally forwarded to a configurable MIDI port. This saves you from adding a keyboard splitter to your MIDI keyboard, if you want to play a MIDI instrument from an unused keyboard zone. o fixed bug in live recording function (notelength sometimes not recorded correctly) o MIOS terminal functions have been added. Just enter "help" in the terminal which has been integrated into MIOS Studio 2 o copy function now works correctly together with the section concept o Follow function now available as dedicated button and with key combination MENU+EXIT o the Follow Song option under UTILITY->Options has been removed. The selected follow mode won't be stored on SD Card anymore. Follow is deactivated after power-on and has to be manually enabled (e.g. by pressing MENU+EXIT) [/code] Plans for the next version: it will allow to store/restore the complete setup (banks, songs, configuration, grooves, etc...) into "session" directories. This will lead to a new way how to organize patterns. E.g., it won't be required anymore to remember the banks where you stored your favourite sequences from last week, or the week before, or 3 years ago - just give the session a name, and store your work into a separate directory. Switch between the directories (load different sessions) to restore the complete setup. There is currently only one blocking point to realize this concept: the FAT32 driver I'm using to access the SD Card (DOSFS) doesn't support "mkdir" - I will have to implement this by myself. Best Regards, Thorsten.

Yes, because only 64 patterns per bank are available. I will change this in the documentation I'm still unsure if I will take over this function into V4, since the handling is inconsistent. It's easier to select (and change) a parameter with the encoder There wasn't so much progress on this project lately. I will probably create a prototype on veroboard first, but before I'm starting with this, I have to be 100% sure about the additional buttons/LEDs. fixed in beta16 Btw.: I noticed a bug in the live recording function - it's fixed in beta16 as well Best Regards, Thorsten.

Hi *, MIOS Studio 2 is now available for download :) Thanks to all beta testers and especially to Phil who helped with the Windows adaption! Best Regards, Thorsten.

Hi David, It shouldn't flash - do you mean the same dimming effect which will be performed by the bootloader after power-on? This indicates that something resets the core. E.g. a short circuit once the card has been connected. After reset, and after the application has been restarted, the IO pin drivers will be enabled, and if this causes a short (-> power drop), the core will boot again. Period. Since you already checked the adapter, the issue could be located at the core side. E.g., check that J24 is connected to 3.3V position (not 5V!), check that R30 resistor arrays *not* mounted, check with a multimeter that there is no short between SI/SO/SC/RC pins Best Regards, Thorsten.

you got a link to the most recent MIOS Studio version, which isn't based on Java anymore and solves all Mac issues. Best Regards, Thorsten.

An EEPROM application based on this application note is already available under modules/eeprom Best Regards, Thorsten. P.S.: I gave you access to the programmers section of this forum.

Wow! Not only the construction, also your demonstration is really really good! I hope to see more - and that you share your patches, which are great as well :) Blogged Best Regards, Thorsten.

It sounds like a power problem with your Hub, are you using an external PSU for it? If not it's time to try this now, because if the hub is only supplied by your PC the total current drain shouldn't exceed 500 mA With an external supply it mainly depends on the specs of your PSU I've connected three GM5 interfaces and two MIOS32 cores (one is a complete MBSEQ V4) to a single hub, the total consumption is more than 1 ampere. If I disconnect the PSU the MBSEQ LCD backlights are dimmed and the devices won't work reliable anymore, regardless if the Hub is connected to a Macbook Pro or to a Dell PC Therefore my assumption that you noticed the same effect. Best Regards, Thorsten.

P.S.: note that I updated the binary with improved pinning for your special case - I hope that you like it, because I won't create another configuration

Hi, I created a special .asm file for your configuration here: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox64e%2Fsetup_midibox16e_without_ledrings.asm It will be automatically part of the next release package. Attached you will find the prebuilt .hex file of the current release. Best Regards, Thorsten. setup_midibox16e_without_ledrings.hex

There are no conflicts at the hardware side, and not that many adaptions have to be done at the software side. The code will look better after the migration, e.g. instead of // send mapped midi-note with 127 or 0 velocity MIOS_MIDI_BeginStream(); // midilink encapsulation header MIOS_MIDI_TxBufferPut((unsigned char) button_event_map[pin][0]); // first byte from table = CHANNEL MIOS_MIDI_TxBufferPut((unsigned char) button_event_map[pin][1]); // second byte from table = NOTE MIOS_MIDI_TxBufferPut(pin_value ? 0x00 : 0x7f); MIOS_MIDI_EndStream(); // midilink encapsulation tail [/code] you can now write: [code] MIOS32_MIDI_SendEvent(DEFAULT, button_event_map[pin][0], button_event_map[pin][1], pin_value ? 0x00 : 0x7f); where DEFAULT is a MIDI port (usually assigned to USB0) of course... Some tutorials can be found here: http://www.ucapps.de/mios32_c.html Recommented reads: #001: Forwarding MIDI Events #002: Parsing MIDI Events #003: Debug Message #004: Sending MIDI #009: Controlling up to 128 LEDs with DOUTX4 Modules #010: Scanning up to 128 buttons connected to DINX4 Modules #012: Scanning up to 64 analog pots (or even more) Best Regards, Thorsten.

This effect is caused by the infamous ADSR bug of the SID. More informations and workaround: go to my website, enter "adsr bug" into the "search ucapps" form Best Regards, Thorsten.

Happy Birthday - have a great day! Best Regards, Thorsten.

MBSEQ V4 can control 16 drum instruments per track - accordingly you will get up to 256 "drum tracks" :) Best Regards, Thorsten.

You only need to change the base address in iic.asm header. With IIC_DEVICE_ADDRESS EQU 0x18 the new device addresses will be 0x18, 0x1a, 0x1c, 0x1e No, it isn't possible to update the firmware via MIDI or IIC Best Regards, Thorsten.

Great! :) Best Regards, Thorsten.

Hallo, ich habe Dir eine PM mit einem Link zur aktuellen MIOS Studio Version geschickt. Wenn das LCD nicht initialisiert wird, ueberpruefe mal, ob Du auch die richtige MIOS Release erwischt hast (sie befindet sich unter pic18f4685/midi/mios_v1_9g_pic18f4685.hex) Die hex2syx.pl Fehlermeldung ("ERROR keine .ini Datei") kommt mir uebrigens etwas seltsam vor - das Script selbst gibt keine deutsche Fehlermeldung aus, und benoetigt auch keine .ini Datei. Wie dem auch sei, mit der aktuellen MIOS Studio Version ist es obsolet Gruss, Thorsten.