ilmenator

After enabling single USB, did you store this setting in the core?

Looking at the PDF connection diagram I noticed that the legends for the 1k resistor and the 10uF capacitor are swapped - or is it that the components are swapped? Maybe this could be corrected for clarity's sake.

I'd be very interested in learning more about this, especially the #define / SysEx part!

Just FYI: on my STM32-based MIDIbox NG v1.022, issuing the 'help' command in the terminal gets me an error message, see below. Not necessarily an issue, but maybe I'm the only one around with that combination? [1242.871] help [1243.103] Welcome to MIDIbox NG V1.022! [1243.103] Following commands are available: [1243.103] system: print system info [1243.103] memory: print memory allocation info [1243.103] sdcard: print SD Card info [1243.105] sdcard_format: formats the SD Card (you will be asked for confirmation) [1243.105] network: print network info [1243.106] set dhcp <on|off>: enables/disables DHCP [1243.107] set ip <address>: changes IP address [1243.107] set netmask <mask>: changes netmask [1243.107] set gateway <address>: changes gateway address [1243.108] set osc_remote <con> <address>: changes OSC Remote Address [1243.109] set osc_remote_port <con> <port>: changes OSC Remote Port (1024..65535) [1243.109] set osc_local_port <con> <port>: changes OSC Local Port (1024..65535) [1243.110] set osc_mode <con> <mode>: changes OSC Transfer Mode (0..4) [1243.111] set udpmon <0..4>: enables UDP monitor (verbose level: 0) [1243.111] keyboard <1|2> (or kb <1|2>): print current configuration of given keyboard number [1243.113] set kb <1|2> debug <on|off>: enables/disables debug mode (not stored in EEPROM) [1243.113] set kb <1|2> note_offset <0-127>: selects the note offset (transpose) [1243.113] set kb <1|2> rows <0-16>: how many rows should be scanned? (0=off) [1243.115] set kb <1|2> velocity <on|off>: keyboard supports break and make contacts [1243.115] set kb <1|2> release_velocity <on|off>: keyboard supports NoteOff velocity [1243.115] set kb <1|2> optimized <on|off>: make contacts only scanned if break contacts activated [1243.117] set kb <1|2> dout_sr1 <0-32>: selects first DOUT shift register (0=off) [1243.117] set kb <1|2> dout_sr2 <0-32>: selects second DOUT shift register (0=off) [1243.119] set kb <1|2> din_sr1 <0-32>: selects first DIN shift register (0=off) [1243.119] set kb <1|2> din_sr2 <0-32>: selects second DIN shift register (0=off) [1243.119] set kb <1|2> din_key_offset <0-127>: selects the key offset between DIN1 and DIN2 [1243.121] set kb <1|2> din_inverted <on|off>: DINs inverted? [1243.121] set kb <1|2> break_inverted <on|off>: Only break contacts inverted? [1243.121] set kb <1|2> delay_fastest <0-65535>: fastest delay for velocity calculation [1243.123] set kb <1|2> delay_fastest_black_keys <0-65535>: optional fastest delay for black keys [1243.123] set kb <1|2> delay_fastest_release <0-65535>: opt. fastest release delay for velocity calculation [1243.124] set kb <1|2> delay_fastest_release_black_keys <0-65535>: opt.fastest release delay for black keys [1243.125] set kb <1|2> delay_slowest <0-65535>: slowest delay for velocity calculation [1243.125] set kb <1|2> delay_slowest_release <0-65535>: slowest release delay for velocity calculation [1243.127] set midimon <on|off>: enables/disables the MIDI monitor [1243.127] set midimon_filter <on|off>: enables/disables MIDI monitor filters [1243.127] set midimon_tempo <on|off>: enables/disables the tempo display [1243.127] router: print MIDI router info [1243.129] set router <node> <in-port> <off|channel|all> <out-port> <off|channel|all>: change router setting [1243.130] set mclk_in <in-port> <on|off>: change MIDI IN Clock setting [1243.130] set mclk_out <out-port> <on|off>: change MIDI OUT Clock setting [1243.131] testaoutpin: type this command to get further informations about this testmode. [1243.131] caliaout: type this command to get further informations about this testmode. [1243.133] testlcdpin: type this command to get further informations about this testmode. [1243.133] set dout <pin> <0|1>: directly sets DOUT (all or 0..255) to given level (1 or 0) [1243.134] set debug <on|off>: enables debug messages (current: on) [1243.135] set autoload <on|off>: enables autoload after filebrowser upload (current: on) [1243.135] save <name>: stores current config on SD Card [1243.136] load <name>: restores config from SD Card [1243.137] show file: shows the current configuration file [1243.137] show pool: shows the items of the event pool [1243.138] show poolbin: shows the event pool in binary format [1243.139] show id <element>:<id> shows informations about the given element id (e.g. BUTTON:1) [1243.139] show hw_id <element>:<hw_id> shows informations about the given element hw_id (e.g. BUTTON:1) [1243.141] lcd <string>: directly prints a string on LCD (can be formatted!) [1243.141] (ERROR: string passed to MIOS32_MIDI_SendDebugMessage() is longer than 100 chars! [1243.141] msd <on|off>: enables Mass Storage Device driver [1243.144] reset: resets the MIDIbox (!) [1243.144] help: this page [1243.144] exit: (telnet only) exits the terminal The cursor keys do a great job, thanks for that!

Yes, that is the limit for commercial goods. For private parcels, i.e. from one private person to another, and with no payment involved, the limit is 1000 norske kroner :smile: .

Congratulations on your new special effects machine!

Wow, nice find!

That sounds good! Actually, the C4 behaves like defined in enc_mode=Inc00Speed_Dec40Speed but that is probably the same on all Mackie Controls!?

Fantastic, thanks! Edit: I just realized that the label apparently needs to be defined locally? In other words, it seems I cannot define a label globally in the .NGL file and have that transmitted as part of the SysEx stream? Also, would it be possible to define more SysEx variables in the SYSEX_VAR line? It seems the system ignores it when I try to add e.g. manuf1=0x00 manuf2=0x21 manuf3=0x02 and try to use these in the SysEx stream?

Hi, this might sound like a strange usecase, but I'll try to explain: Would it be possible to apply some of the EVENT_* parameters also to incoming MIDI events, but in a "reversed" way? E.g. I have a device that sends CC data depending on rotation speed and I want to transform that data into something else, say NRPNs: it is basically behaving like the enc_mode=00Speed, which makes transforming these events quite difficult interpretation-wise. Or am I just missing something here and it is easily achieved? Thanks, ilmenator

Perfect, thanks - looking forward to this!

Well, turns out it is working exactly like defined above - only, one should make sure the SysEx message is correctly defined :whistle: .

Hi TK, I have a situation here in which I need to display messages on an external device. This device (a Mackie C4) receives the strings via SysEx commands, indicating on which display (1 of 4) to print, and at which position, with the characters ASCII encoded. It would be nice if a modified label functionality (not necessarily the control characters, with the exception of ^<label> maybe, which seems very handy) could be used for this purpose? So instead of having to convert the strings manually into hex format and insert that into the SysEx message, have this done automatically? The C4 expects something like this for the first display: F0 00 00 66 17 30 xx [yy] F7 with xx = position of first character to display: 00 = first position in first line 36 = last position in first line 38 = first position in second line 6E = last position in second line and [yy] = sequence of ASCII coded characters For the other displays it's the same, only that you select a display in the following way: Display 2 (second from top): F0 00 00 66 17 31 xx [yy] F7 Display 3 (third from top): F0 00 00 66 17 32 xx [yy] F7 Display 4 (lowest): F0 00 00 66 17 33 xx [yy] F7 The main thing I need is to avoid having to convert the strings manually. Everything else should be doable via the SYSEX_VAR I guess. Would this be possible? Thanks, ilmenator

Hi, I'd like to "listen" to a certain incoming SysEx message and react to that in a specific way. This is what I think should do the trick: # EVENTs EVENT_RECEIVER id=1 type=SysEx ports=0000010000000000 stream="0xF0 0x00 0x00 0x66 0x17 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x34 0x31 0x06 0x00 0xF7" fwd_id=SENDER:1 EVENT_SENDER id=1 type=SysEx ports=0000010000000000 stream="0xF0 0x00 0x00 0x66 0x17 0x31 0x0C 0x4d 0x49 0x44 0x49 0x62 0x6f 0x78 0x20 0x4e 0x47 0x20 0x4d 0x61 0x63 0x6b 0x69 0x65 0x20 0x43 0x34 0x20 0x69 0x73 0x20 0x72 0x65 0x61 0x64 0x79 0x21 0xF7" The message I want to listen to is "0xF0 0x00 0x00 0x66 0x17 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x34 0x31 0x06 0x00 0xF7" as in the stream of the EVENT_RECEIVER. However, it looks like I am missing something, because the EVENT_SENDER is never triggered by that. I can trigger the sending of SysEx however with a simple NoteOn event (not shown above). What am I missing here? Thanks, ilmenator

Which bootloader version are you using? Make sure it is the latest one (v1.012), otherwise the application may not run properly.

Nein. LED-Matrizen schalten keine hohen Ströme. Nein. Den TÜV interessiert das übrigens nicht im geringsten...

<broken record>offsite docu bad</broken record>

Kann sein dass Emu-User ihr Equipment haeufiger nutzen als andere - ich hatte jedenfalls schon mehr defekte Bourns- als Alps-Encoder in den Fingern.

Die sind nicht wirklich zuverlaessiger, eher im Gegenteil - genau dieses Modell ist in den EMU Samplern verbaut, die teilweise massive Probleme haben. Allerdings reden wir hier von mehreren Jahren in Benutzung, es kann also etwas dauern bevor du etwas merkst :-).

In the meantime I have updated the TPD Wiki page with the frontpanel file required for the TPD. Also, I have modified the code so that I have now 16 columns showing the track position in Matrix (the movie) style running from top to bottom like in a waterfall. The four buttons and corresponding duo-color LEDs are also functional and can be assigned in the config file (one minor code modification to increase the number of scanned shift registers is necessary for this to work). I have a second set of proto boards on the way - should these turn out to be perfect then I might order some more boards for those interested in this SEQv4 extension. Expect this to happen not before May.

That sounds good to me. And just to support the impression that something is wrong on the Windows side of things: I am having issues with my Win7 32bit system not recognizing different cores as well. I installed the GM5 drivers long ago, because I have one GM5x5, one LPC17-based and one STM32-based experimental system, and one LPC17-based SEQV4. I have never gotten around to look into when exactly communication starts to fail, I cannot see any pattern. This is mainly a problem with the experimental systems, when the cores will just not be recognized after the upload of a new software. I then have to reboot the core, quit MIOS Studio (sometimes just rescanning for MIDI devices works) and start over again. I am never having issues with the SD card, though.

Traco rules - the TSR-1 series from Traco Power is running fine on my build. NO noise at all.

I'd say 10 mins is probably more than it should take. How about formatting the card on your computer?

To me that sounds as if something was fishy with the card. Have you tried to re-format it properly and see if the behaviour remains the same?

You can simply order the PCB at SmashTV's MIDIbox shop - since quite some time, actually :smile: . Edit: I went through this thread again, it seems like Tim has silently decided to just make available the PCB in his shop.