TK.

Could this be related to the same issue like here? -> Best Regards, Thorsten.

Still waiting for the PCB (hopefully it isn't stucked at german Zoll...) For the STM32F4 version you can expect a pool size of 64k! :) Best Regards, Thorsten.

Ok, now it's clear to me what is going wrong here: else set_active (id)Enc:1371 1 The parser doesn't read commands after an ELSE statement. On the other hand, it didn't complain about the command - and this caused the confusion at your side. Here a new version which prints an error message whenever a command is detected after ELSE or ENDIF -> http://www.ucapps.de/mios32/midibox_ng_v1_029_pre3.zip Best Regards, Thorsten.

Hm... but how to switch between the different behaviours? I guess that most people don't want to add "dump=1" to all EVENTs, so that it can only be an optional parser feature. Best Regards, Thorsten.

The LCD cable should be as short as possible, I wouldn't use lengths > 30 cm Sending to an iPad/phone via OSC sounds like a good plan! It shouldn't be so difficult to integrate this into MIDIO128. But I'm unsure about a suitable application to display the text (at least OSC doesn't prevent you from sending strings) Best Regards, Thorsten.

Yes, the allowed voltage range is +/- 18V Best Regards, Thorsten.

It will take some time at my side until I will be ready to jump on the train, but I already found a very interesting usecase for this board: -> concurrent emulation of 8 SIDs for MIDIbox SID (V2 and also V3?) :tongue: Best Regards, Thorsten.

Hi, which application are you using? And did you consider that the LD signal has a very short pulsewidth (ca. 1 uS)? Best Regards, Thorsten.

Kann es sein, dass Dir Reichelt faelschlicherweise einen Fader mit logarithmischer Kennkurve geschickt hat? Das wuerde das Problem erklaeren. Ueberpruefe das mal mit einem Ohmmeter. Gruss, Thorsten.

Rumors told me, that Fairlightiii want's to setup a new bulk order! :) Best Regards, Thorsten.

No problem, sometimes I prefer faders & pots as well, especially when parameters should be tweaked during a live session and each fader/pot has a dedicated assignment anyhow. Such a PG-300 clone is a really easy entry point into the MIDIbox universe ;-) No programming skills are required if MIDIbox NG is used, since it provides an (hopefully easy to learn) configuration format. I found a SysEx specification under http://www.vintagesynth.com/roland/sysex.php And based on that I created a .NGC file to demo the configuration for a few control elements: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Fpg300.ngc You've to upload this file to the SD Card via the Filebrowser in MIOS Studio after the MIDIbox NG firmware has been installed. You can also edit this file in MIOS Studio later. It's incomplete (because it's only a demo), but as you can see, adding remaining parameters will be straightforward. Just copy&paste the event definitions and adapt them... If you need more guidance (and if the Manual doesn't give you the infos), just let me know and I will explain in more detail. For the MIDIbox NG you would need following modules: - MBHP_CORE_LPC17: http://www.ucapps.de/mbhp_core_lpc17.html - SD Card: http://www.ucapps.de/mbhp_sdcard.html - MBHP_AINSER64 for up to 64 pots & faders: http://www.ucapps.de/mbhp_ainser64.html - MBHP_DINX4 for up to 32 buttons: http://www.ucapps.de/mbhp_din.html - MBHP_DOUTX4 for up to 32 LEDs: http://www.ucapps.de/mbhp_dout.html Kits for these modules are available in SmashTV's shop: http://www.midibox-shop.com The MIDIbox NG firmware is located under http://www.ucapps.de/mios32_download.html and gets frequent updates - just follow the progress in this dedicated forum section: http://midibox.org/forums/forum/46-midibox-ng/ Best Regards, Thorsten.

Thanks Kristal for documenting your build! Than more reports from different people, than less troublesome for most others! :) Btw.: an alternative report from Orange_hand can be found here: Resp. here: http://www.sequencer.de/synthesizer/viewtopic.php?f=13&t=70858&start=75 Unfortunately in german - but it has many pictures! ;-) Best Regards, Thorsten.

I will try this out tomorrow. Best Regards, Thorsten.

works :)

3

2

1

I agree that I've seen the same issue. I just tried to edit some youtube links. Sometimes it was possible to get it right by removing special arguments (such as #t=x.ym), and by wrapping the url with ... But it also seems that the forum software only accepts the first two youtube videos, all others are displayed as plain URLs. I haven't found an option in the admin section which controls this. Found following option: Maximum number of media files per post: Too many media files embedded on one page can potentially crash the browser. However, I increased the number to 10 ok, I disabled following option: When a member posts twice within n minutes, once after the other in a topic they will be merged into one post. Enter the number of minutes to capture concurrent posts. Enter 0 to not use. Let's try if it works. Best Regards, Thorsten.

Ok, I see... Please enable it from the MIOS Terminal: Best Regards, Thorsten.

Cool! Could you please document all changes in this thread, so that I don't have to start from zero if somebody else requests the same feature? Most simple way to display all changes: cd $MIOS32_PATH svn diff . Best Regards, Thorsten.

Everything ok! I've to change the message - the LPC17 doesn't use the MBHP_ETH module. And "not connected" means for LPC17, that no ethernet cable is connected. Keep it unconnected for this check. Best Regards, Thorsten.

We should handle it like the swapped encoder pin issue - if more than 2..3 people encounter the problem, it makes sense to add this into the official firmware. Otherwise it's better to use a local workaround, and to wait what happens in the next months. Why? Because it could turn out, that the new parameter wasn't flexible enough, and that somebody else would need even more flexibility. Instead of adding "just another flag", it could be that a combined flag is the better choice, e.g. to enforce that conflicting configurations can't be selected. But if the "simple" flag was already published, it would be too late to change this, because it would affect the compatibility. Another reason could be, that I find a more clever idea for the implementation - again in this case it would be better to wait... In other words: I prefer to collect "use cases" before adding new features which I don't need myself to understand the potential issues which need to be solved, and to avoid unnecessary complexity. Back to your proposal: the code for LEDs is in MBNG_MATRIX_DOUT_PinSet and for patterns (ledrings, BPM digits, etc) in Hlp_DOUT_PatternTransfer You will notice that it's already quite complex. Even I would need several minutes to understand what I did several months ago, and where to change something to swap columns and rows. Especially since you will notice that I support MAX72xx as well. Which means, that I would have to ensure that the flag even works for this variant. And of course it would have to support all possible matrix variants, such as 4x8, 8x4, 8x8, 16x4, 16x8, 4x16, 8x16, etc... You see the problem at my side? Therefore please start with some experiments at your side. Alternatively, fix the PCB (cut tracks, solder wires) - could be faster ;) Best Regards, Thorsten.

Hi, MIDIO128 provides a MIDI file player, but it doesn't allow to edit parameters like "Midfile Optimizer" Best Regards, Thorsten.

It should work if the EVENT_RECEIVER listens to the CC, and forwards it to a EVENT_SENDER which executes the meta event. the second one has syntax errors, such as "botton_mode" (wrong word, and wrong place, because a receiver isn't a button) Do you check for error messages in MIOS terminal whenever you update the .NGC file? Best Regards, Thorsten.

ok, noticed. I will check this sooner or later... Best Regards, Thorsten.