Karg

Solved the first of my problems: Turns out it was the AStart setting in the Jam page. Have not used the Jam page often yet, so I was not aware of that setting. Unfortunately, the issue with changing the step, instead of page persists on the cursor buttons.

Hello, puh, I accidentally must have enabled some setting parameters. Yet, I do not know which ones, and do not find it in the manual. Maybe someone here knows how to turn everything back to (my) normal: When I enter step triggers, the sequencer starts to play the sequence. It is not in live mode. I would love to turn that off again. Similarly, the forward/backward keys only move to the next/prev step. Formerly it was flipping the whole page (e.g. from Steps 1..16 to 17..32). Any help appreciate... Thanks, Karg

While I am still struggling to understand how the OTG mode really works, the issue indeed was on the MPC side (it simply cannot transmit MIDI through the USB B port). Thanks for all replies :)

Thanks. what I got is that you just used a different cable? I'll give that a try tomorrow...

Hi, unfortunately, I am stuck right now. How do I address Midi devices connected to USB OTG (currently Midibox Seq4+, latest firmware). I manage to send MMC message (currently MPC Live), but have not managed to receive them. Similarly, I do not manage to receive notes, and whatever I try to send to the Seq does not show up on the Midi Monitor. In this context, I also do not really understand yet which port to set on the instrument pages to send notes over the OTG port. After several round of trying different things/devices, searching the manual, etc I thought I post my question here. Thanks a lot in advance! Cheers, Karg

Awesome!!!! Great work! Thanks and happy holidays :)

Hi Peter, great news!!! thanks a lot!

Hi, I understood there will be another update after the matrix launch (any ETA yet?). While I use the LoopA more and more, there is one feature missing that continuously holds me back. I am not sure if it has been requested yet, but I can well image a general interest: File/Project Names!! :) Would be so great if that can be included. A very simple version would do the job, imho. Like one encoder for letter position, one to change character up/down. Maybe even using all four encoders with position, uppercase, lowercase, special character. Just a thought. :)

Hi, a quick question to help troubleshooting my setup :) Does the LoopA forward/route Program Change messages as well? Thanks a lot in advance!

Hi, I had a similar problem with the "non-plus" version of the sequencer. If I recall correctly, the issue was in 3.3V vs 5V. Check if Jarvis here in the OLED display thread on page 2 describes your issue. If so, the solution was provided a couple of posts below.

Thanks! That was just the small push into the right direction I needed...

Good morning, by any chance, does someone know a good alternative to the ALPS STEC12E08 rotary encoder which is panel mountable (thread + screw), but with similar properties (durability, steps, switch, etc)? I tried checking directly on the Alps homepage, but was lost in all their versions sooo quickly... Thanks a lot in advance. Best, Karg

Thanks Peter, I got is working :)

Hello, I would like to give my application MIOS32 File Browser capabilities. Having not found much information about this, I just started playing around a bit: Reading other peoples source codes, my impression is that the corresponding code is in terminal.c (LoopA and Seq4 code - is my impression correct?). Thus, I have begun by adding TERMINAL_Init(0); into my APP_Init routine. Further, I added several programming models to my Makefile: ################################################################################ # Include source modules via additional makefiles ################################################################################ # sources of programming model include $(MIOS32_PATH)/programming_models/traditional/programming_model.mk # application specific LCD driver (selected via makefile variable) include $(MIOS32_PATH)/modules/app_lcd/$(LCD)/app_lcd.mk # MIDI Router (and port handling) include $(MIOS32_PATH)/modules/midi_router/midi_router.mk # MIDImon include $(MIOS32_PATH)/modules/midimon/midimon.mk # UIP driver include $(MIOS32_PATH)/modules/uip/uip.mk # UIP Standard Task (with DHCPC + OSC server and client) include $(MIOS32_PATH)/modules/uip_task_standard/uip_task_standard.mk # generic sequencer modules #include $(MIOS32_PATH)/modules/sequencer/sequencer.mk # MIDI file Player #include $(MIOS32_PATH)/modules/midifile/midifile.mk # FATFS Driver include $(MIOS32_PATH)/modules/fatfs/fatfs.mk # FILE Access Layer include $(MIOS32_PATH)/modules/file/file.mk # USB Mass Storage Device Driver include $(MIOS32_PATH)/modules/msd/msd.mk # common make rules # Please keep this include statement at the end of this Makefile. Add new modules above. include $(MIOS32_PATH)/include/makefile/common.mk and also put the MUTEX routines into mios32_config.h: // map MIDI mutex to UIP task // located in app.c to access MIDI IN/OUT mutex from external extern void APP_MUTEX_MIDIOUT_Take(void); extern void APP_MUTEX_MIDIOUT_Give(void); extern void APP_MUTEX_MIDIIN_Take(void); extern void APP_MUTEX_MIDIIN_Give(void); #define UIP_TASK_MUTEX_MIDIOUT_TAKE { APP_MUTEX_MIDIOUT_Take(); } #define UIP_TASK_MUTEX_MIDIOUT_GIVE { APP_MUTEX_MIDIOUT_Give(); } #define UIP_TASK_MUTEX_MIDIIN_TAKE { APP_MUTEX_MIDIIN_Take(); } #define UIP_TASK_MUTEX_MIDIIN_GIVE { APP_MUTEX_MIDIIN_Give(); } Similarly, I have the following in my app.c: ///////////////////////////////////////////////////////////////////////////// //! functions to access MIDI IN/Out Mutex //! see also mios32_config.h ///////////////////////////////////////////////////////////////////////////// void APP_MUTEX_MIDIOUT_Take(void) { MUTEX_MIDIOUT_TAKE; } void APP_MUTEX_MIDIOUT_Give(void) { MUTEX_MIDIOUT_GIVE; } void APP_MUTEX_MIDIIN_Take(void) { MUTEX_MIDIIN_TAKE; } void APP_MUTEX_MIDIIN_Give(void) { MUTEX_MIDIIN_GIVE; } Yet, I still get the following error messages, and have not found a solution yet. I hope I am not on the completely wrong path for the MIOS32 File Browser implementation :) Cheers, Karg

What I wanted to add: great work by everyone involved!!I was really enjoying building the sequencer, and using it is a pleasure!