Search the Community

Showing results for tags 'sysex'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 7 results

  1. hi all,  i posted this question in the troubleshooting section first, but jaytee recommended to post it here to call more attention-   i have a strange problem with my sidbox; it seems it does not send any sysex messages. my setup: -macbook with 10.9.5 -neusonik im/one midi-interface (successor of the uMIDI/O22 on the whitelist, claimed to be technically identic) -sidbox (one core, two sids, latest firmware (v2_044)) Uploading the firmware works fine and i can also send patches from computer to sidbox (e.g. taken from the vintage bank). But if i click "receive patch" or "receive bank", the sidbox only sends short stuff like "F0 00 00 7E 4B 00 F7" or "F0 00 00 F7". Same thing when trying to dump with "shift+button5" from the sidbox CS. The different patch editors (tried jsynthlib, ctrlr and the MBSIDV2-Editor) also need bidirectional sysex, so don't work either. i tried with another synth (ML-303; i think TK took a hand in this one, too :-D) to check if it is caused by the midi interface (or something else inside OSX or the software), but with this one, i can store/dump patches in both directions.  i'm a bit perplexed; getting "Application is up & running!" and clock ticks indicates that the sidbox's midi-out port is working and there is no wiring error (there is only one TX-pin on the PIC..); the test with the 303 indicates that my midi-IF/computer/software setup should properly transmit sysex data in both directions. So why can't i get data from the sidbox? is there any option i could have missed? any ideas? regards  simon
  2. i have a strange problem with my sidbox; it seems it does not send any sysex messages. my setup: -macbook with 10.9.5 -neusonik im/one midi-interface (successor of the uMIDI/O22 on the whitelist, claimed to be technically identic) -sidbox (one core, two sids, latest firmware (v2_044)) Uploading the firmware works fine and i can also send patches from computer to sidbox (e.g. taken from the vintage bank). But if i click "receive patch" or "receive bank", the sidbox only sends short stuff like "F0 00 00 7E 4B 00 F7" or "F0 00 00 F7". Same thing when trying to dump with "shift+button5" from the sidbox CS. The different patch editors (tried jsynthlib, ctrlr and the MBSIDV2-Editor) also need bidirectional sysex, so don't work either. i tried with another synth (ML-303; i think TK took a hand in this one, too :-D) to check if it is caused by the midi interface (or something else inside OSX or the software), but with this one, i can store/dump patches in both directions.  i'm a bit perplexed; getting "Application is up & running!" and clock ticks indicates that the sidbox's midi-out port is working and there is no wiring error (there is only one TX-pin on the PIC..); the test with the 303 indicates that my midi-IF/computer/software setup should properly transmit sysex data in both directions. So why can't i get data from the sidbox? is there any option i could have missed? any ideas? regards   
  3. hi my idea is: put a *.syx on the SD-Card put the SD-Card in a STM34F4 core var a. Core recognizes a *.syx and send it out on Port 32 (Midi A) var b. I activate something in the program (with a Dip switch for example) and now it loads up   for what: in use with generic Midicontrollers (BCR2000) to transfair a CC-Layout that is fitting to the Midibox programm   for which project: http://wiki.midibox.org/doku.php?id=msq-cc-bcr   what i have up to now... char filepathL[8]; //Number of Pathsymbols tm/bcr.sys >>> 8 max! MUTEX_SDCARD_TAKE; statusDir = FILE_DirExists("syx"); MUTEX_SDCARD_GIVE; if(statusDir != 1) {MUTEX_LCD_TAKE; MIOS32_LCD_DeviceSet(0); MIOS32_LCD_Clear(); MIOS32_LCD_PrintFormattedString ("%s %d", "no bcr.syx", statusDir); MUTEX_LCD_GIVE;} if(statusDir == 1) { sprintf(filepathL, "tm/bcr.syx"); FILE_ReadOpen (&midifile_fi, filepathL); //normally i then start by reading the content and transfair it into variables..... but happens if i have Sysexfile instead? how to tunnel this to midiport? FILE_ReadBuffer((u8 *)file_typeBank, 4); //"MQ01" = 4 Positons FILE_ReadBuffer((u8 *)CC_SEQ, 32); //Container for static not touchable Variables FILE_ReadBuffer((u8 *)CC_Morph, 128); //Container for morphable Variables FILE_ReadBuffer((u8 *)Velo_Morph, 256); //Here we have 8x32=256, FILE_ReadBuffer((u8 *)CC_Store, 256); //Here we have 8x32=256, FILE_ReadBuffer((u8 *)MSQ_Store, 65536); //Motion-Sequence-Data 8x32*256=65536 FILE_ReadClose (&midifile_fi); MUTEX_SDCARD_GIVE      
  4. Wavetable Editor for Lead Engine in PD

    Hi! Since there is no Wavetable Editor in Ctrlr for the lead engine yet, i made one in PD. I attached a simple Patch that just writes into the patch-buffer. The second also reads from the buffer or from saved patches (*.syx). You will need Pd-extended to run the patches. Editing the wavetable is done by drawing around. I kept these patches as simple as possible, so you can use them as a starting point and add other sysex functions, ipad-support (via osc), reversing, scaling, harmonizing,... ( try py/pyext) by yourself, before porting it to Max for Live.   tested on Mac OSX and Linux ( Raspbian )   have fun Jens sid_wavetable_editor.zip
  5. I decided to go ahead and try to write my own sammichSID patch editor for the GURU Renoise tool. There's one slight problem - I have no *$%$% idea what I'm doing. I'll explain my dilemma...   After some research I see that someone already created a GURU script for sammichSID. Great! It uses CC messages, but because the Sammich does NOT save CC changes to the patch buffer this does me absolutely no good. Not so great. So I see there is a Ctrlr panel for MidiboxSID/sammichSID. Great! It is buggy at absolute best. Not so great. I'm using Vista, and to put things simply, the Ctrlr panel does things at random or whenever it feels like.    So here I am with a wonky knob on my Sammich due to overuse. A patch editor is absolutely necessary because I'm at a point where all I can really do is play notes and change patches.   I looked, studied, read, reread and tried to generally wrap my head around the MidiboxSID sysex documentation located here:   http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v2%2Fdoc%2Fmbsidv2_sysex_implementation.txt   After hours (possibly days) of trying things out, I managed to get it half working. Even that is pushing it.   tl;dr - Someone please help. ---------------------------------------------------------- Here is what I know (or don't) so far...   Someone please correct me if I am wrong. The manual states that the sysex format for patch editing is: F0 00 00 7E 4B <device-number> 06 <WOPT> <AH> <AL> <value_l> <value_h> F7 So let's say for example's sake I set the device number to "0" and ignore the <WOPT> for now. Let's also say that I would like to edit the volume on the lead engine. The manual says: 0x052 | [6:0] Volume (0-127, only most significant 4bits are used by SID) Now this is where I'm completely ^&*$^*# up. The manual doesn't really make clear what [6:0] means. Furthermore, the manual says:   (<AH> = 0..3, <AL> = 0..7F) Patch address: (<AH> << 7) | <AL>   ...in the description of the patch sysex layout. I have NO idea what this means and it's not really obvious (to a newb) where to find this information. As a workaround I loaded Ctrlr to see what it was sending in the MIDI monitor window for volume/lead engine control.   [f0 00 00 7e 4b 00 06 00 00 52 0f 07 f7]   ...is what it was displaying, with the two value bits (0f, 07) changing, of course. I'm still confused on how this string relates to what was posted above. So I open GURU and enter:   sysex_message_template = {0xF0, 0x00, 0x00, 0x7e, 0x4b, 0x00, 0x06, 0x00, 0x00, "nn", "vv", 0xF7},       number = 52,       max_value = 127,   ...where nn=number and vv=value. I've tried both hex/decimal values without success. Other times where I did get it to do something, GURU would jump 100 values or so, making it useless. So I please ask for some input on this. I'm determined to write out a new patch editor, but I cannot seem to get past the learning curve of sysex.
  6. combine two nibbles to a byte?

    I am trying to remote control a synth that can send its current synthesis parameters as SysEx blocks of data. This is handy because in theory it allows initialization of the NG event settings to the actual values in the synth. The synthesis parameters themselves can be controlled via NRPNs.   However, the SysEx data sent by the synth is organized in nibbles. E.g., a parameter value of 63 is sent as 03 15 (0x03 0x0F), and 64 is sent as 04 00 (0x04 0x00). Is there a way to convert that into regular 7bit or 14bit values that can then be output by the NG? Something like EVENT_ENC id=1109 hw_id=9 ports=0000100000000000 type=NRPN nrpn=16 syxdump_pos=2:35 fails because it can only take into account the upper or the lower nibble of the value I'm after, as syxdump_pos points to a single byte in the ^dump only.
  7. Hi folks,   I am building a sammichSID from the recent batch and have an issue.   I am at the stage where I am trying to use MIOS Studio to speak to the Sammich.  After turning on the Sammich while plugged in, I saw a single f0 00 00 7e 40 00 01 f7 message in the MIDI In window.  And now when the Sammich turns on I get "MIOS V1.9"  and then "Ready."   When querying I received a "No response from MIOS8 or MIOS32 core!" message and started following the Troubleshooting guide.   So when testing my interface via Loopback, I got a detected feedback loop.  Good!   But when I tried to send a SysEx command, I didn't get an echoed response.  In other words, I fail at this step becaue the grey messages aren't repeated back in black: http://www.ucapps.de/mios_studio/mios_studio_feedback_sysex.png   So I tried my 2 other interfaces on both my Mac and PC, no luck.  I even went out and bought a fourth device on the whitelist (the MOTU FastLane USB).  No luck (and $60 bucks down the drain).    I must be missing something...   Please help!!!!  I have been reading alot about Mandolane maybe helping here, but the mandolane website appears to be offline :(   EDIT Oh one more note, when sending these messages, the LEDs for both input and output light up on the MOTU device.  So I feel like some kind of filtering must be happening on the software end.  Or maybe I just need better Java MIDI drivers?   When I route through my Sammich and Query, I do NOT get input LEDs to light up.  So maybe there is another problem, but I figured I would start with the loopback.