Jump to content

Recommended Posts

Posted

out of the box: no

but I think you just have to enclose

[tt]MIOS_MIDI_Start();[/tt]

and

[tt]MIOS_MIDI_Stop();[/tt]

around all places where [tt]MIDI_Tx_BufferPut()[/tt] is called (Clock).

And set the Linker option for the Merger (see C-Function Listing).

This should make it compatible for linked Cores.

Best regards,

Michael

Posted

Ah excellent.

So the first midibox is declared as:

MIOS_MIDI_MergerSet(MIOS_MIDI_MERGER_MBLINK_FP)

...and the other is:

MIOS_MIDI_MergerSet(MIOS_MIDI_MERGER_MBLINK_EP)

cheers,

michel

ps. this will come in handy for a very simple replacement for my RM1x that I've been planning over a year:

sneakyseq2a.jpg

(31cm x 17cm x 10cm - It will have two independent cores. Each one will hold ~60 songs, up to 256 measures for each of the 6 tracks. They'll be triggering my 6gb handmade collection of audio loops on Kontakt 2 as well as my crazy KSP scripts)

Posted

Yes, the function parameters are correct.

Great to see a new sequencer concept comming!

Maybe the distance between the pots is a little bit too short for adjustments during a live session, I would reduce it to 2x2x4 pots

Best Regards, Thorsten.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...