[MIOS32 Bootloader V1 Updates]

V1.015 is available under http://www.ucapps.de/mios32_download.html

• workaround for USB MIDI under Windows when more than 1 USB MIDI port is enabled
• various LCD/GLCD driver updates for STM32F4

Best Regards, Thorsten.

[MIDIbox FM V1.4]

V1.4h is available:

 

MIDIboxFM V1.4h
~~~~~~~~~~~~~~~

   o Wavetables can now be changed via SysEx when they are stored in RAM

 

Best Regards, Thorsten.

[WaveTable Utility]

-After uploading firmware MBFM V1.4h, the MBFM display still shows MBFM V1.4g at startup. 

 

this is now changed in the official V1.4h release

 

 

From my quick tests it looks like just the first 16 steps are stored in RAM.

 

strange! All 32 steps should be stored iN RAM

 

Best Regards, Thorsten.

[SYSEX Record/Playback using MIDIO128]

Cool - finally somebody who confirms that the "new attempt" for a workaround solves the USB MIDI issues under MIDI! :-)

 

See also 

 

Best Regards, Thorsten.

[MIDIbox NG Release + Feedback]

Yes, you are right - it's much more work than expected, it's not a simple change! :-/

 

I started to adapt mbng_matrix.c, so that it should also allow MIOS32_SRIO_NUM_DOUT_PAGES == 64, but then I found much more places which actually need changes.

 

Also mbng_dout.c as you already noticed. The table has to be enhanced by more granular patterns, and also the variable width (e.g. u64 for 64 dim levels), and finally MBNG_DOUT_NotifyReceivedValue which transfers the pattern into the pages.

 

So, most of the code is constrained for 32 pages and 16 dim levels.

Adding more flexibility would result into too much work at my side - I don't want to do this.

 

Best Regards, Thorsten.

[MBFM 5V option?]

Well done!!! Great case, great buttons! :)

 

Could you please create a new Wiki page which explains the MCP6004 approach?

I would like to link it to the MBHP_OPL3 page to inform other builders about this option.

 

Best Regards, Thorsten.

[MIDIbox KB]

Ok, then this preliminary version should be sufficient for the first tests: http://www.ucapps.de/mios32/midibox_kb_v1_013_pre1.zip

 

 

By the way, may I also ask what's the scan rate Midibox KB achieves?

 

It depends on the number of scanned rows; with the "optimized" flag enabled, ca. 130 uS for a typical keyboard

 

Best Regards, Thorsten.

[LF33 Substitutes]

Any voltage regulator which converts from 5V to 3.3V should do this job, as long as it supports at least 500 mA (fine if it also supports 1A)

 

Maybe you can find a LM7833? -> http://www.taitroncomponents.com/catalog/Datasheet/LM7833.pdf

 

Best Regards, Thorsten.

[SYSEX Record/Playback using MIDIO128]

After I noticed how easy this is to implement, I couldn't resist to try it out immediately ;-)

 

Thanks for the file! Your utility added an "End of Track" marker, and according to the spec this is mandatory (a well hidden requirement...)

 

Please try this version: http://www.ucapps.de/mios32/midio128_v3_019_pre2.zip

 

The marker also allows proper looping synchronized to a 4/4 bar (for those who are interested)

 

Best Regards, Thorsten.

[SYSEX Record/Playback using MIDIO128]

After reading the MIDI file spec, I found a much easier solution: it's allowed to split SysEx streams into small chunks, so that no big RAM buffer for the complete SysEx message is required.

 

Could you please try this version: http://www.ucapps.de/mios32/midio128_v3_019_pre1.zip

 

I tested this with MIDIbox SID and FM patches.

They can be recorded and played back, and the SysEx messages are displayed correctly in Logic Studio after .mid file import.

So, it seems to work at my side. :smile:

 

Best Regards, Thorsten.

[John's Organ MIDIfication project]

I separated the topic. If you don't like the subject, just let me know how we should call it ;)

 

Best Regards, Thorsten.

[LED Digits Problem]

War meine Annahme denn richtig, dass Du LED Digits mit einer gemeinsamen Anode verwendest?

Dass Du die Shift-Register Positionen ebenfalls anpassen musst ist klar, oder?

 

Falls Du nicht weiterkommst, wuerde ich Dir empfehlen, die DOUTs mit den LED Digits erstmal direkt an das Core Modul anzuschliessen, und die Digits bspw. mit diesem .NGC File zu ueberpruefen: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fleddig1.ngc

 

So kannst Du mit verringerter Komplexitaet die passende DOUT_MATRIX Konfiguration herausfinden.

 

Gruss, Thorsten.

[MIDIbox KB]

The only missing piece is an EEPROM emulation for STM32F4.

I will implement this sooner or later, but it won't be available in the next 2..3 weeks.

 

If it's ok for you to start with a MBKB which can't store the parameters, I could give you a preliminary version.

 

Best Regards, Thorsten.

[STM32F4 Discovery]

Sounds like a lot of work to adapt this - any volunteer?

 

However, you could connect an ENC28J60: http://www.ucapps.de/mbhp_eth.html

Cheap breakout boards for only US $4 are available at EBay: http://www.ebay.de/itm/New-ENC28J60-Ethernet-LAN-Network-Module-For-Arduino-SPI-AVR-PIC-LPC-STM32-/310670027142?pt=LH_DefaultDomain_0&hash=item4855606986

 

Then connect this module to a Wifi adaptor of your choice -> done

 

Best Regards, Thorsten.

[Bug in MIOS Studio 2.4.6 for Linux? Feature request?]

This is strange, because the filebrowser works at my side.

Seems that it makes sense to update to a newer Juce version in the hope, that somebody already fixed this in the base library.

I will try this sooner or later.

 

Meanwhile, just enter the filepath directly into the entry mask left of the browse button.

 

 

I'd like to have a possibility, to send a midi file from MIOS studio. I my case I was looking for a way to enable the sampling option in my Waldorf Blofeld.

 

would be a very low prio topic for me.

I'm sure that there a suitable MIDI players for Linux which allow you to do this already.

 

Best Regards, Thorsten.

[LED Digits Problem]

# for "Common Anode" set inverted_row=1 and inverted_sel=1

 

Gruss, Thorsten.

[LPC1769 Rev C - Different layout than Rev A/B?]

If EA did this to sabotage the high volume sales caused by MIDIbox folks, they achieved a worst case marketing effect -> customers just switch to the competitor! ;-)

 

Best Regards, Thorsten.

[John's Organ MIDIfication project]

Yes, a separate topic makes sense for all conversations which belong to John's project, so that it's easier for interested readers (who want to build something similar) to follow.

 

Any proposal for the subject?

 

Best Regards, Thorsten.

[SYSEX Record/Playback using MIDIO128]

Ok, sounds feasible! :)

 

I will implement this in one of the next weekends.

 

Best Regards, Thorsten.

[MIDIbox CV V2 Concept]

The warnings can be ignored, the app is ready for upload :)

 

Sidenote: I got the differential line drivers two days ago, and will test them with the AOUT_NG (for CV out) and DOUT (for gates/triggers/switches) modules next weekend.

 

Best Regards, Thorsten.

[SYSEX Record/Playback using MIDIO128]

Yes, it's on my TODO list.

 

Only problem is that the complete SysEx stream needs to be buffered in RAM before it's stored on SD Card.

Accordingly, the used core module (LPC17 or STM32F4) will limit the max size.

E.g. with STM32F4 it would be possible to handle 64k dumps easily, but for LPC17 I fear that only 4..8k can be buffered.

 

How long is the SysEx dump of your drum machine?

 

Best Regards, Thorsten.

[John's Organ MIDIfication project]

I can't help you on potential issues with jOrgan, Linux or your special hardware circuitry.

 

However, hopefully a hint which helps:

 

however,  when the gc is pressed to clear the stops, multiple things happen:

1. The pre set stops turn off.

2. other SAMS turn on and stay on,

3. other SAMS flutter on and off.

4. pressing the gc multiple times changes the state of some SAMS, on to off and  off to on  .

 

I don't know what you mean with "gc", but I guess that you want to say, that strange (uncontrollable) things happen when many outputs are changed at once, right?

 

Does this also happen if you remove parts of the hardware?

E.g. especially to 3) - do these SAMS also flutter if all other SAMS are disconnected?

 

And how long are the cables between the Core, DIN and DOUT modules?

They should be as short as possible!

 

Best Regards, Thorsten.

[Phase question]

As long as the oscillators are running at the same (or dividable) frequency, they will stay in phase.

Once you change the finetune value, they should get out of phase again.

 

 

Also, has anybody an insight about how the global Phase knob in the CTRLR panel actually affects the oscillator phases?

 

It's the same phase that you find in the OSC menu page of the CS.

There is only a single phase parameter for all 3 oscillators.

 

Best Regards, Thorsten.

[MIDIbox CV for controlling 2 x MS-20 clone filters]

Well, the best way would to use a MIDIbox CV V2, since it provides special stereo effects in the modulation matrix.

See also my 2xSSM2044 experiments :) -> 

 

I have an MB AOUT module, and plan to power the TL074's with +/- 15V

Could I tap this directly from the filter power circuit?

 

yes!

 

 

The LM317LZ only provides 100mA

 

no problem, the OP Amps of the AOUT module will require less than 10 mA

 

 

Another thing is the output voltage of the AOUT module

The schematics suggests R_x=10K, R_y=2,2K, R_p=500

Will this work for my purpose?

 

What is the CV control range?

Anyhow, just start with these values, they are fine for 0V..11V

Solder R_x and R_y in a way that you could easily remove them if you need different values.

 

 

I also would like to have MIDI control of the LP/BP/HP switch

 

with MBCV2 you will get up to 64 additional gate/trigger/switch outputs in the DOUT SR chain.

You could use some of the outputs for this purpose.

 

And then for last, CV V1 or V2?

Any big advantage in the new V2 for this use?

 

V2 is the better choice.

 

Best Regards, Thorsten.

[MIDI and interrupts]

Yes, it's always better to accept dropped events than running into the danger of an infinite loop.

Working with the reduced resources of an embedded system means to accept potential failures which are almost everywhere.

The challenge is to design the software in a way so that a common user will never notice this ;-)

 

Best Regards, Thorsten.