EsotericLabs

Hello Midibox friends, Below is the MB50XG project in beta version. It is MIDIO128v3.13 with a driver for the Yamaha DB50XG, DB60XG and NEC XR385 wavetable daughterboards. With thanks to fellow midiboxers Roman01 & Sparx, hardware geeks Chiel & Serge and of course TK and all of you for the MB platform! Beta0.4.3 Xcode project here: . Ready to upload .hex here: . Hardware requirements: LPC17 core, SCS, SD card, any daughterboard adapter (see references below) plus a working soundcard of the said types. Functionalities: voicing system and effect operation in db50xg_base.h / .c / db50xg_list.h. Beta 0.4.3 with global parameters master volume, transpose and master tune implemented currently being tested for Beta0.4.4: line in functionality for DB60XG/NEC XR385 cards (not DB50XG). Pre-release here: rudimentary support in db50xg_extra.c for drum setups, multiparts and QS users voices. Menu support for SCS based apps in db50xg_scs_ui.c/.h, db50xg_scs.ui.inc goes into your scs_config.c file (see example 1). Basic midi implementation with cc's managing main effect settings: cc12 = effect type; cc13 = effect return; cc14=effect pan; cc15 = dry/wet; cc16-31 = effect parameters 1-16 with proper value range checking. chn1 = reverb; chn2 = chorus ; chn3 = variation (see example 2). To-do list: patch filing system, imidi implementation for master volume, transpose, master tune separated transpose for midi file, midi in ports etc (see known issues). sysex handler, midi implementation for advanced parameters of variation effect (connection, insert, control depths), SEQV4 menu support (based on seq_ui_todo.c) memory allowing, Full support for QS, drum setup, multipart and TB300 mode. Known issues: transpose function transposes all midi going to soundcard. Example 1. Include the MB50XG include file into your scs_config.c like this: ///////////////////////////////////////////// // menu items added for MB50XG ///////////////////////////////////////////// #include "db50xg_scs_ui.inc" Then add the MB50XG menu pages to your main menu like this: const scs_menu_page_t rootMode0[] = { SCS_SUBPAGE("DB50 ", subpageDB50XG), // this is the new one SCS_SUBPAGE("Midi ", subpageMIDI), // these three were already there SCS_SUBPAGE("I/O ", subpageIO), SCS_SUBPAGE("Sys ", subpageSYS),}; Example 2: MIOS32_MIDI_SendCC(soundcard.midi_port, Chn1, 12, 4); // sets reverb effect to reverb type = Room 2 MIOS32_MIDI_SendCC(soundcard.midi_port, Chn2, 15, 0x64); // sets dry/wet of chorus effect to 0x64 MIOS32_MIDI_SendCC(soundcard.midi_port, Chn3, 18, 27); // sets effect parameter 3 of variation effect to value 27, look it up in your db50xg manual Have fun! References for daughterboard adapters: copyright of respective owners.

Seqv4?

Sid pcbs and PIC still available?

Hello, If you're looking into casings for a midibox SEQV4L: I have C64 breadbin cases plus suitable formulor acrylic frontplates for sale: One set for € 25, (plus shipping from NL), free c64 breadbin keyboard to go with it if you want.

Hello Jumpatron, Yes you'll need a CORE LPC17 and a LPCXPRESSO (plus parts of course). I would say a Quad IIC is optional, only if you really need the extra midi out ports. The Core LPC17 has two midi out connectors plus USB midi out. Any hd44780 compatible 40x2 LCD will work. Some eat more current than others though. The control surface has three options: a) wait for Smash TV SEQ CS PCB. This will surely work, but hardware customization will be more difficult - i guess b) build a control surface yourself with cheaper standard buttons with straight wiring (see www.ucapps.de / seq v4 / manual / hardware options / how many buttons - leds do I need / check link to pinning diagrams). For this you need 3x DINX4 and 1x DOUTX4. You can add buttons and leds easily (hardware wise) but you'll need to go deep down in the code to add the functionality you want. c) build a control surface with matrix wiring: you will need 1x DIO_MATRIX and 1x DINX4 plus DIN/DOUT/DIO_MATRIX for the additional buttons and leds. The wiring is more difficult but you'll save on parts in the case. Here's the schematic for the matrix wiring of the control surface In any case, the butttons won't work without code customization. I'm looking into code changes for extra buttons myself, but this will not be ready soon. Your sketch looks cool, for sure, but isn't is easier to buy a small keyboard and hook it up? You will have velocity sensitivity, maybe extra buttons and sliders for control. I guess this is difficult if not impossible with the CS buttons. There is a midibox KB project and some people even found commercial keyboards with plenty of space for inbuilt midiboxes as well.

Hello midbox friends I have something strange (i think) with my midio128 based application..I added a code module, with its own Init() and several MIOS32_MIDI_SendDebugMessage() in the initialization code. Strangely, these are fired into MIOS Studio when the code starts after upload. They do not, however, appear when I power cycle the core (switch off and on). I then added debug messages to the App_Init() of midio128 itself with the same effect. Isn't that strange? I would expect App_Init to run whenever the program starts? Or is it a timing issue, that only after some running time, messages are sent to MIOS Studio? I'd be grateful for any clues, Thank you.

This is an update about connecting the DB50XG or clones to the Midibox core. Initially I had some difficulty in getting it running, but silly me forgot to wire the M+. I then followed the long route to conclude that a 74HC541 level shifter is needed to get the db50xg running. Not so: if you have a daughterboard on a GMvoice (or any compatible breakout board), just solder a 220R to the +5V of J4B and another 220R to the Sd (aka midi out) of J4B.This goes into a regular midi Din connector or header: +5V to M+ and Sd to M-. Works like a charm, no 74HC541 needed. The +5V output of J4B kinda does the level shifting, it is about pulling a current through the 6N138 on the daughterboard. This is cool as it frees up real estate inside a C64c case. I will have a SEQ V4 with built-in soundboard before soon!!

Hello Ilmenator, I did something comparable (I guess) in C for converting between u16s and u32s in mem and u8s or u7s for sysexes. Maybe the code snippet below is of some use to you. I'm not familiar with the NG, so maybe not... ////////////////////////////////////////////////////////////////////////////////////////// // conversion functions between MIOS32 types u32 u16 and Midi MSB LSB // Address Hi Mid Lo ////////////////////////////////////////////////////////////////////////////////////////// u8 MSB(u16 data){return ((data & 0x7f00) >> 8);} u8 LSB(u16 data){return (data & 0x007f);} u16 To16Bit(u8 MSB, u8 LSB){return (( (MSB&0x7f)<<8)|(LSB&0x7f));} u8 AddressHi(u32 address){return ((address & 0x7f0000)>>16);} u8 AddressMid(u32 address){return ((address &0x7f00)>>8);} u8 AddressLo(u32 address){return (address&0x7f);} u32 AddressFull(u8 Hi, u8 Mid, u8 Lo){return (((Hi&0x7f)<<16)|((Mid&0x7f)<<8)|(Lo&0x7f));}

That's the info I needed, thanks! Hmm, the xr385 needs quite some mem for settings storage and many lists, I'm afraid. I don't want to use the SCS UI, for seq v4 I must start from the seq_ui_todo? Thank you for the subtle hints I'm on the right track, yes, I take the challenge :-)

Hello everybody, May I ask about the seq4 firmware? I want to build a seq v4 with onboard db50xg clone sound card. The driver is ready, so is a scs based menu, I'm now working on filing. My questions are: The seq v4 manual says "3 physical ports are provided. The remaining one is reserved for the emulated mbseq". Does this mean midi out 4 at j4b is not available? Should I hook the card to midi out 3 or can I use midi out 4 somehow? I want to add extra buttons for access to the soundcard menu. These are not in the hardware config file. To add, I should: add buttons to seq_hwcfg.h and .c; modify seq_file_hw accordingly, make a button routine in seq_ui, add some lines to the button handler, make a seq_ui_db50xg UI handler from the seq_ui_todo template, add to the seq_ui_pages.inc . Did I oversee something? Thank you for your thoughts & ideas!

My pleasure to be of any help.

Hello DSL-man, if you have any 6581 or 6582 or 8580, i am interested! The same for one or two C64 or C64C cases and power supplies. wenn Sie 6581 oder 6582 oder 8580 haben, bin ich interessiert! Das gleiche gilt für ein oder zwei C64 oder C64C Gehäuse und Netzteile Martijn

Hello SEQV4L fans, I activated the remote keyboard function and modified it for SEQV4L. Here's the SEQV4L layout and the modified seq_ui.c.

No I'm sorry, nothing to learn... New repository, typedef present.

Must be something with the snapshot then (I.e my local copy of the svn?) . I found the same page on the web, was only confused by the 1311 version number. I did svn co svn://svnmios.midibox.org/mios32 from the terminal on macosx 10.7.5. Strange huh? I ll make a completely new snapshot then.

Hello, I was recompiling SEQV4L.072 in order to make some changes to the remote midi functions in seq_ui.c . But it appeared to me that typedef msd_state_t is missing in tasks.c of seqv4.072 (needed for seqv4light). I took this from revision 1311 on ucapps. and pasted it in: problem gone. ///////////////////////////////////////////////////////////////////////////// // Local types ///////////////////////////////////////////////////////////////////////////// typedef enum { MSD_DISABLED, MSD_INIT, MSD_READY, MSD_SHUTDOWN } msd_state_t; Am I correct to assume these lines are missing from svn revision 1718? anybody else had compile errors?

Soooooo Coooooool! You made the full case in the end!!!! I left out the core PCB mounting holes coz I was not sure they would line out with the back panel holes. And we used all premade holes in the CS PCB from SmashTV, didn't we? If you have an update on the eps file, please post it. My project developed into re-using a C64 case, see pics. To do: mount the core, wire the box and add several touches of paint to cover up the traces of my limited DIY skills.. Gut shots: Back plate made of L profiled MDF from the DIY store.

(solved)

Hello midibox friends, Update on the SEQV4L case: Formulor delivered the front plates today and they came out beautifully! Some pics: The apparent scratch on the lower center is a bubble in the protective foil. I ordered three to fill up the formulor template, but I've got use for only one. PM me if you want one for production costs plus postage. See

Hello midiboxers, this is just a possibly silly idea posted for getting your feedback. I (will) have this modified MIDIO128 with a SCS and a XR385 daughterboard sound card on midi port 4. There is room in the box (C64C) for another core and I have a spare SEQV4L CS. I could hook the second core running SEQV4L to midi 3 of the first core. Being mainly a guitar player, the MIDIO should (in the end) connect only to a few DIN foot switches and AIN expression pedals and maybe maybe some extra LED's or relays. Will this work? Will it need much code modifications? Can two cores work with a single SD card? How to deal with master and slave settings of both cores? Should one core handle all midi communication with external devices or should the second also have MIDI 1& 2 in & out connectors? Or should I go for the Grand Sequencer and dedicate one of its ports to the XR385? The code driving sound card should be modular enough to be incorporated in other applications.. Any thoughts will be much appreciated.

Confirmed! You're quite an amazing guy.. You mentioned about arpeggiator features (in the post with the ) hidden in the seqv4l under the transpose button? I found out echo settings #9-16 shift do pitch shift like echoes. Any more hidden arp features to be discovered? And as the SEQV4L most probably inherited the MIDI remote functions from her big sister, could we customize it for SEQV4L? That would be cool for him too. I followed your tracks into seqv4l/seq_ui.c with all the SEQ_UI_Button_SomeFunctions(s32 depressed). I suppose I'll have to experiment whether I can modify SEQ_UI_REMOTE_MIDI_Keyboard() unpunished? And devise a comparable SEQ_UI_MIDI_REMOTE_KeyBoard_CC() if we wanted? I guess I already know your answer on my second question :shifty: but if you could please enlighten me on the arps? :drool: Thank you!

I tried with the V4L.069, but I did not find that particular file in the browser. There is MBSEQ_C.V4. This looked most promising, but it does not contain this magic line. There is this and MIDI_OUT_MClock_Ports MIDI_IN_MClock_Ports 0x010f0f01 Should the small SEQV4Light also have a _GC file?

Thank you! I suppose it relates to these lines in seq_midi_port.c in Init()? // multi port (0xc0): default enables: // USB1, OUT1, OSC1, AOUT seq_midi_port_multi_enable_flags = (1 << 0) | (1 << 4) | (1 << 12) | (1 << 16); and the actual sending is in SEQ_MIDI_PORT_NotifyMIDITx()? Which is in the Tx hook in app.c, right? And seq_file_gc reads/writes between the file you mentioned and the variable here? Just being curious, I like to understand whats going on in the software..

Not yet tested, change of plan: I will make a SEQV4L in a c64 case with a transparent plexi front plate from formulor. Transparent and translucent cases will look cool with LEDs underneath. I ordered the plates today, curious how they come out. eps file attached, pics later. I dont think holes for leds make sense: the transistors are too high! If you use 13mm shaft push buttons, the LEDs need not stand out. I made this mistake with another seqv4l cs: too low buttons. Can't case it anymore, or replace all 48 push buttons with longer ones. Someone knows about midi out 2?