TK.
-
Posts
15,198 -
Joined
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by TK.
-
-
That's the reason why I haven't listed J10A/B in my requirements list - it's just important to have a standard control surface (SCS), otherwise applications won't be re-usable.
The 6 buttons + encoder could also be connected to an on-board DIN SR, connected to J9 as the first SR in the chain.
Would be happy to evaluate it.
Best Regards, Thorsten.
-
Yes, I think it's only a display problem in MIOS Studio, I should change this to a decimal value.
Best Regards, Thorsten.
-
Must-have requirements:
- STM32F407VG (1MB flash)
- SCS with 6 buttons, 1 encoder and 1 GLCD (so that we can also use the display as a scope)
- 1 MIDI IN, 1 MIDI OUT
- USB Device
- SD Card
- SRIO (J8/9)
- J19 for AOUT
- 50mm depth
- HP doesn't matter as long as it still fits into the Pod40X case together with the Expander modules
Optional:
- up to 3 additional MIDI IN/OUT (could also be provided as an optional module)
- USB Host
- 4 on-board LEDs
- Audio-DAC
Potential extension modules:
- SRIO based encoder/ledring modules
- AINSER64 module (with at least 8, but maybe 3x8 INs?) - inputs should be buffered, protected and maybe also amplified and level-shifted for +/- 5V
Such a module could also cover MBNG for script based processing.
Best Regards, Thorsten.
-
@Antichambre very nice! Does it provide J8/9, J10A/B and J15A? (For J15A the pins for GLCDs with serial interface might be sufficient)
@latigid ondepth >50mm isn't suitable, it won't fit into my case; I guess that this limit is considered by most Eurorack modules.
Best Regards, Thorsten.
-
A downstripped MBHP_CORE_STM32F4 module in Eurorack format would be nice-to-have as an alternative solution to the Euroreceiver - maybe with a SCS (6 buttons, encoder, display) - this would allow to run MBCV which gives us a lot of LFOs, Envelopes, sequencers, modulation matrices, etc.
Best Regards, Thorsten.
-
Modules in 4ms Pod40X case - fortunately fitting w/o modifications :)
Best Regards, Thorsten.
-
Fortunately no problem to support negative values :)
Please try this version: http://www.ucapps.de/mios32/midibox_ng_v1_037_pre5.zip
Best Regards, Thorsten.
-
In this particular case you could also "set ^section 2", it should do the same (because ^section 2 follows ^section 1, no jump required)
Best Regards, Thorsten.
-
Hi,
there is currently no way to declare custom variables, but you can use the storage of any unused event instead.
E.g. let's say you don't use LED:1000, then just use it to store your value.
Best Regards, Thorsten.
-
As mentioned by Christian, there was no special reason why assigned DIN and DOUT SR #9 to the DIO function.
I thought this might be better in case you would like to add more physical SRs in future, no need to change the IDs again until you reach #9. If you don't like this, you could also use SR #3, but not SR #1 or SR #2, because these positions are already allocated by the scan matrix.
Btw.: the most simple way to find out the hw_ids is to enter "set debug on" in the MIOS terminal, then trigger the buttons and observe the debug messages in the terminal (doesn't work with LEDs of course, but if you know the button position, you can easily conclude on the LED position)
Best Regards, Thorsten.
-
Hi,
I'm surprised, all events should listen to incoming MIDI messages, regardless of the bank.
Best Regards, Thorsten.
-
Yes, there is a conflict with the shift register assignments.
Try this one:
# now enable DIOs (0 = input / 1 = output) DIO port=J5AB emu_din_sr=9 emu_dout_sr=9 output_mask=01010000 # button events (DIN SR1 pins are assigned to hw_id=65/67) EVENT_BUTTON id=65 hw_id=65 type=CC chn=1 cc=16 range=0:127 fwd_id=LED:66 EVENT_BUTTON id=67 hw_id=67 type=CC chn=1 cc=17 range=0:127 fwd_id=LED:68 #EVENT_BUTTON id=65 hw_id=65 type=Meta meta=RunSection:1 button_mode=OnOnly #EVENT_BUTTON id=67 hw_id=67 type=Meta meta=RunSection:2 button_mode=OnOnly # LED events (DOUT SR1 pins are assigned to hw_id=66/68) EVENT_LED id=66 hw_id=66 type=CC chn=1 cc=16 range=0:127 EVENT_LED id=68 hw_id=68 type=CC chn=1 cc=17 range=0:127
Best Regards, Thorsten.
-
Could you please post your complete .NGC and .NGR file? I will check it tomorrow...
Best Regards, Thorsten.
-
No, don't worry, outputs are protected against shorts internally.
Just tried your configuration, it works after changing fwd_id=LED:3 to fwd_id=LED:2 (we always forward to a hw_id)
RESET_HW # J5A PORT SETUP # J5.A0 -> octave up switch # J5.A1 -> octave up LED # J5.A2 -> octave down switch # J5.A3 -> octave down LED # now enable DIOs (0 = input / 1 = output) DIO port=J5AB emu_din_sr=1 emu_dout_sr=1 output_mask=01010000 # button events (DIN SR1 pins are assigned to hw_id=1/3) EVENT_BUTTON id=1 hw_id=1 type=CC chn=1 cc=16 range=0:127 fwd_id=LED:2 EVENT_BUTTON id=2 hw_id=3 type=CC chn=1 cc=17 range=0:127 fwd_id=LED:4 # LED events (DOUT SR1 pins are assigned to hw_id=2/4) EVENT_LED id=3 hw_id=2 type=CC chn=1 cc=16 range=0:127 EVENT_LED id=4 hw_id=4 type=CC chn=1 cc=17 range=0:127
As you can see, I also added "RESET_HW" to ensure that previous settings are undone.
The LEDs shouldn't be dimmed.
Best Regards, Thorsten.
-
Pulse widths up to 10 mS are now supported, could be nice if you could try it out:
Best Regards, Thorsten.
-
Based on my experiences with MB808 the trigger width is crucial, therefore I can fully understand Andrews request that a digital option is desired.
The "pipeline based approach" is working fine, we can now adjust the width from 0 (=off -> gate function) to 10 mS
o DOUT_1MS_TRIGGER in the MBSEQ_HW.V4 file has been replaced by a configurable trigger width which can be adjusted in the CV Configuration Page with GP13 now-> http://www.ucapps.de/mios32/midibox_seq_v4_096_pre7.zip
It would be great if everybody could help to test this new firmware version, regardless if the new CV features are used or not (I hope that nothing else is broken!)
I would like to create a final v4_096 release, because v4_095 is from last december, and it started to smell! ;-)
Best Regards, Thorsten.
-
Update to the 1ms delay: I could "pipeline" the triggers, this way we could get a cheap pulse stretcher.
Is there the need for more than 4 mS (= 3 pipeline stages)?
Best Regards, Thorsten.
-
New version can now be found here: http://www.ucapps.de/mios32/midibox_ng_v1_037_pre4.zip
It's now possible to mix input and outputs on a single port as shown in this example: https://github.com/midibox/mios32/blob/master/apps/controllers/midibox_ng_v1/cfg/tests/diocfg_3.ngc
And J5 is supported as well (called J5AB) - it's even possible to mix digital with analog functions -> https://github.com/midibox/mios32/blob/master/apps/controllers/midibox_ng_v1/cfg/tests/diocfg_4.ngc
In your case, please keep the analog pins disabled
Best Regards, Thorsten.
-
4 minutes ago, latigid on said:
Wow, amazing! Are the CVs distributed out on J19, so the same RC1 channel or is RC2 used as well to double the transfer rate? What is the maximum data rate?
The data update rate is only 35 uS for all 4 modules, so no need to make it more complicated :)
That's also the reason why I enabled all 32 channels by default, it doesn't make a big difference.
Using a second CS line wouldn't help, because SPI transfer time would have to be consumed anyhow.
QuoteIs there a functional way to use all 32 CVs with only 16 tracks? Polyphonic tracks?
With channel 9-13 you can route note and velocity value to two CV outs - in this case you need all 32 outputs.
But you can also route CCs of a track to the CV outs (starting at CC#16 as far as I remember...)QuoteIs it possible to set (or preset) the drum trigger length to something longer? This is already available for the clocks but I couldn't see an easy way to do it for triggers.
Actually I looked into this, but there is a technical problem.
The 64 drum triggers are currently cleared with each SRIO update cycle, this was very pragmatic and effective and especially doesn't consume resources (counters) and CPU time (processing the counters)For individual delays I would have to implement counters for each trigger, and this is very costly.
And for a single delay we would potentially run into the problem, that each mS a new trigger could reset the counter, leading to "stretched signals" for all triggers for which the configured time already passed...
Best Regards, Thorsten.
-
New major enhancement available for MBSEQ V4+ users - up to 32 CV channels and gates! :-)
-> http://www.ucapps.de/mios32/midibox_seq_v4_096_pre6.zip
o Only for MBSEQV4+: support for up to 32 CV outputs (and corresponding gates). Means: up to 4 AOUT modules can be chained. Tested with MAX525 (and midiphy Eurorack Expander), but should also work with TLV5630 based AOUT_NG The additional CV outputs can be accessed with MIDI port CV2..4. o AOUT port has been renamed to CV1..CV4 o Utility Page, GP Button #11 now changes to the CV Configuration PageBest Regards, Thorsten.
-
On 16.8.2019 at 10:50 PM, k2z3k0 said:
my idea was to indicate with lower (if OFF),and upper(if ON) cases of first letters of each effect ,ECHO=E,e ,Humanizer=H,h and so on
i feel this can save a lot of time running around
here little example
letters are not exactly in place,but just to visualise
still relevant or just a quick idea?
Will lead to some effort at my side... therefore I would only add this if other people find it useful as wellBest Regards, Thorsten.
-
On 3.8.2019 at 5:56 PM, k2z3k0 said:
hi everyone
a quick proposal here
ON\OFF for MIDI MMC messages per port?
maybe in BPM menu?
for example some synths have sequencer without MMC filter
and in result when you hit play on Midibox, synth sequencer also starts
this might be undesired situation.
thank you for great work TK.
bests.k
I guess that you mean MIDI clock/start/stop (MMC isn't supported)
They can already be enabled/disabled for each MIDI port in the BPM menuBest Regards, Thorsten.
-
On 7.4.2019 at 10:43 PM, kasiofz said:
I used the latest release (midibox_seq_v4_096_pre5) on an LPC17 core. The beat led doesn't flash on the first step of the sequence. So I get 3 flashes in a 16 step loop.
If I set the track synchronisation to 32 steps, the beat led flashes normally on measure step 17, but doen't flash on step 1. So I get 7 flashes.
Release midibox_seq_v4_095 works without the above problems.
Fixed in v4_096_pre6
-
Yes, this will be possible - it's exactly the intention behind NGR to allow users such customizations without touching the application code.
Best Regards, Thorsten.
midiphy SEQ v4+
in MIDIbox SEQ
Posted
This isn't correct, see also the SN74HC595DR datasheet: http://www.ti.com/lit/ds/symlink/sn74hc595.pdf
Output drive current is 6 mA, which means in other words: you've to add an internal resistance of ca. 800 Ohm to the calculation.
This could be doublechecked by clamping an output to ground, and measuring the current draw while the pin is set to logic-1.
Best Regards, Thorsten.