Xpantastic! group photo

Yahoo Groups archive

Xpantastic!

Index last updated: 2026-04-28 23:44 UTC

Thread

Reprogramming a Matrix 1000 ROM for detune

Reprogramming a Matrix 1000 ROM for detune

2012-04-23 by Jeremy Smith

Hi,

I thought if you could modify the M1000 ROM chip (with the OS on it), 
you could make it detune across all 6 voices, play in unison!

This would be an amazing way to get a phatter sound from this synth, and 
approach Xpander levels of sound.

Any thoughts?

Jeremy.

Re: [xpantastic] Reprogramming a Matrix 1000 ROM for detune

2012-04-23 by PeWe

You cannot detune the 6 voices of a Xpander separately, even not in "unison mode".
You don\ufffdt even can detune a patch, you loaded in each slot of a multipatch in a Xpander and like you can w/ a Matrix-12.
There\ufffds no detune page in the Xpander.
As a workaround, you can store the same patch to 6 single patch memory locations, each version of this patch slightly detuned already,- then load in a multipatch and adjust volume and pan there and play all unison.
But this wastes 6 memory locations for each unison-detune sound.

That\ufffds the benefit of a Matrix-12,- 6 more voices, the detune page and the modulation page for better visability of used modulation sources and destinations,- that\ufffds all.

Matrix-1000 has a unison mode already and is cheap,- stack 4 and detune \ufffdem globally against each other while each being in unison mode.

I don\ufffdt know if the Matrix-1000 has enough processing power for your planned hack.
It has the same processor than Matrix-12 and Xpander,- but the Xpander has 2 already.

In the Matrix-12,\ufffd there are simply 2 voiceboards you stack.

You can put Matrix-1000 and Xpander in "guitar" mode,- so each voice receives pitch bend data separately on different MIDI channels.
With a sequencer, you can detune the voices that way, or if you own a MIDI processor w/ the ability storing and transmitting MIDI CC offset data to different MIDI channels, you can do it that way in realtime.
If the sequencer or MIDI processor is able to store sysex commands in addition and transmitting these, in strictly sequencial order and together w/ MIDI program change commands as well as MIDI CC offsets, to the Matrix-1000, you\ufffdd be able to remotely switch between operation modes like normal operation, unison mode and "guitar" mode.

Look at the MIDI specs in the manual.



Am 23.04.2012 21:34, schrieb Jeremy Smith:
Show quoted textHide quoted text
\ufffd

Hi,

I thought if you could modify the M1000 ROM chip (with the OS on it),
you could make it detune across all 6 voices, play in unison!

This would be an amazing way to get a phatter sound from this synth, and
approach Xpander levels of sound.

Any thoughts?

Jeremy.


Re: [xpantastic] Reprogramming a Matrix 1000 ROM for detune

2012-04-23 by Omar

regardless, you're not gonna get a 6/6R/1000 to sound like an Xpander....VCO versus DCO, and the characteristic multi-mode filter section are what makes the Xpander's trademark sound...The 6/1000 engine doesn't come close to it.
Show quoted textHide quoted text
On Mon, Apr 23, 2012 at 4:38 PM, PeWe <ha-pewe@...> wrote:

You cannot detune the 6 voices of a Xpander separately, even not in "unison mode".
You don´t even can detune a patch, you loaded in each slot of a multipatch in a Xpander and like you can w/ a Matrix-12.
There´s no detune page in the Xpander.
As a workaround, you can store the same patch to 6 single patch memory locations, each version of this patch slightly detuned already,- then load in a multipatch and adjust volume and pan there and play all unison.
But this wastes 6 memory locations for each unison-detune sound.

That´s the benefit of a Matrix-12,- 6 more voices, the detune page and the modulation page for better visability of used modulation sources and destinations,- that´s all.

Matrix-1000 has a unison mode already and is cheap,- stack 4 and detune ´em globally against each other while each being in unison mode.

I don´t know if the Matrix-1000 has enough processing power for your planned hack.
It has the same processor than Matrix-12 and Xpander,- but the Xpander has 2 already.

In the Matrix-12, there are simply 2 voiceboards you stack.

You can put Matrix-1000 and Xpander in "guitar" mode,- so each voice receives pitch bend data separately on different MIDI channels.
With a sequencer, you can detune the voices that way, or if you own a MIDI processor w/ the ability storing and transmitting MIDI CC offset data to different MIDI channels, you can do it that way in realtime.
If the sequencer or MIDI processor is able to store sysex commands in addition and transmitting these, in strictly sequencial order and together w/ MIDI program change commands as well as MIDI CC offsets, to the Matrix-1000, you´d be able to remotely switch between operation modes like normal operation, unison mode and "guitar" mode.

Look at the MIDI specs in the manual.



Am 23.04.2012 21:34, schrieb Jeremy Smith:

Hi,

I thought if you could modify the M1000 ROM chip (with the OS on it),
you could make it detune across all 6 voices, play in unison!

This would be an amazing way to get a phatter sound from this synth, and
approach Xpander levels of sound.

Any thoughts?

Jeremy.



Re: [xpantastic] Reprogramming a Matrix 1000 ROM for detune

2012-04-23 by Tony Cappellini

>>You cannot detune the 6 voices of a Xpander separately, even not in "unison mode".
Show quoted textHide quoted text

>>You don´t even can detune a patch, you loaded in each slot of a multipatch in a Xpander and like you can w/ >>a Matrix-12.

PeWe

I don't understand exactly what you're referring to.
If each single patch in a Multi patch is manually detuned - by going into the Osc Page and changing the Freq (??) value to - (insert random value), why won't that "detune each voice independently" ?




Re: [xpantastic] Reprogramming a Matrix 1000 ROM for detune

2012-04-23 by Omar

he's referring to the fact that you can't set the detune parameters as a setting in the multi.

it would have been much easier if the multi allowed detune. that way you could just load the same patch into each slot and then set the detune amount within the multi versus having to create 6 different versions of the same patch.
Show quoted textHide quoted text
On Mon, Apr 23, 2012 at 4:57 PM, Tony Cappellini <cappy2112@...> wrote:

>>You cannot detune the 6 voices of a Xpander separately, even not in "unison mode".

>>You don´t even can detune a patch, you loaded in each slot of a multipatch in a Xpander and like you can w/ >>a Matrix-12.

PeWe

I don't understand exactly what you're referring to.
If each single patch in a Multi patch is manually detuned - by going into the Osc Page and changing the Freq (??) value to - (insert random value), why won't that "detune each voice independently" ?





Re: [xpantastic] Reprogramming a Matrix 1000 ROM for detune

2012-04-23 by PeWe

Exactly !!!

:-)


Am 23.04.2012 23:08, schrieb Omar:
Show quoted textHide quoted text
\ufffd
he's referring to the fact that you can't set the detune parameters as a setting in the multi.

it would have been much easier if the multi allowed detune. that way you could just load the same patch into each slot and then set the detune amount within the multi versus having to create 6 different versions of the same patch.

Re: [xpantastic] Reprogramming a Matrix 1000 ROM for detune

2012-04-24 by Jeremy Smith

PeWe wrote:

>
>
> You cannot detune the 6 voices of a Xpander separately, even not in 
> "unison mode".
> You don\ufffdt even can detune a patch, you loaded in each slot of a 
> multipatch in a Xpander and like you can w/ a Matrix-12.
> There\ufffds no detune page in the Xpander.
> As a workaround, you can store the same patch to 6 single patch memory 
> locations, each version of this patch slightly detuned already,- then 
> load in a multipatch and adjust volume and pan there and play all unison.
> But this wastes 6 memory locations for each unison-detune sound.
>
> That\ufffds the benefit of a Matrix-12,- 6 more voices, the detune page and 
> the modulation page for better visability of used modulation sources 
> and destinations,- that\ufffds all.

But only 2 outputs for M12?

> Matrix-1000 has a unison mode already and is cheap,- stack 4 and 
> detune \ufffdem globally against each other while each being in unison mode.
>
> I don\ufffdt know if the Matrix-1000 has enough processing power for your 
> planned hack.
> It has the same processor than Matrix-12 and Xpander,- but the Xpander 
> has 2 already.
>
> In the Matrix-12,  there are simply 2 voiceboards you stack.
>
> You can put Matrix-1000 and Xpander in "guitar" mode,- so each voice 
> receives pitch bend data separately on different MIDI channels.


> With a sequencer, you can detune the voices that way, or if you own a 
> MIDI processor w/ the ability storing and transmitting MIDI CC offset 
> data to different MIDI channels, you can do it that way in realtime.
> If the sequencer or MIDI processor is able to store sysex commands in 
> addition and transmitting these, in strictly sequencial order and 
> together w/ MIDI program change commands as well as MIDI CC offsets, 
> to the Matrix-1000, you\ufffdd be able to remotely switch between operation 
> modes like normal operation, unison mode and "guitar" mode.

This (using pitchbend to change detune) sounds like the best solution.

Jeremy.

>
> Look at the MIDI specs in the manual.

Re: [xpantastic] Reprogramming a Matrix 1000 ROM for detune

2012-04-24 by PeWe

>>>

Am 24.04.2012 22:01, schrieb Jeremy Smith:
> But only 2 outputs for M12?

I have a Xpander, but 2 friends of mine had the Matrix-12 and IIRC, 
there was a single-output option.

>
> This (using pitchbend to change detune) sounds like the best solution.
>
> Jeremy.

With a sequencer in the studio,- yes,- in realtime on stage possibly not.
I\ufffdve never seen any realtime MIDI processor guaranteeing eactly the same 
sequential order of a bunch of sysex-, MIDI Prg.-Change and MIDI CC data 
offsets all day.

But it might be worth a try.

:-)

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.