MatrixDelay

wolf · Post by **wolf** » Sat May 15, 2004 2:45 am

<a name="planetz-file"></a><a href="http://www.worldless.mine.nu/cgi-bin/dl ... .zip"><img src="/forums/images/file_icon.gif" border="0" alt=" File"> File</a> <a name="planetz-tag"></a>Price ($USD): 0 <a name="planetz-tag"></a>Type: Effect _____________________________________ MatrixDelay<script language="JavaScript">function klein(bild) {newWin = window.open("http://www.worldless.com/sfp/bild.html?" + bild,"fenstername","scrollbars=0,toolbar=0,location=0,directories=0,status=0,resizable=0,width=675,height=405");}</script><a href="javascript:klein('md.jpg')"><img src="http://www.worldless.com/sfp/pics/md-small.jpg" width="500" height="303" border="0"></a> (click on the pic to view original size)<a href="http://www.worldless.mine.nu/cgi-bin/dl ... zip">download demo</a><a href="http://www.worldless.com/sfp/md.html">more info</a><a href="http://www.shareit.com/product.html?pro ... R,USD">buy it !</a> the price of MatrixDelay is 40,- €<hr width="80%" size="1" noshade>OverviewBasically this is a very flexible ducking delay with a freely routable effect section, serial and parallel. The fx matrix itself - containing all effects - can be set pre, post or inside the delay. Additionally it can be set solo (delay bypassed), so you have some kind of filter bank. The effects can be modulated by four LFOs. The ducker compressor can be set pre or post delay to either exchange current delayed sound with new one from the input or just duck the delayed one.the matrix effects have a unique design and are the following ones :<table width="84%" border="0" align="center"><tr><td height="125"><ul><li>flanger, chorus or phaser</li><li>lowpass,highpass or bandpass filter (with special "analog" switch, only slightly different depending on frequencies)</li><li>distortion & exciter/bass enhancement</li><li>formant filter</li><li>comb filter with experimental singlesideband modulation</li><li> three external effect slots, order is selectable</li></ul></td><tr></table>for additional information please read the info inside the demo archive.<a href="http://www.worldless.mine.nu/cgi-bin/dl ... zip">download demo</a><a href="http://www.worldless.com/sfp/md.html">more info</a><a href="http://www.shareit.com/product.html?pro ... R,USD">buy it !</a> have fun ! Wolfgang

_________________
<a href="http://www.worldless.com/sfp">wolf audio design</a>
<a href="http://www.worldless.com">worldless productions</a>

[ This Message was edited by: wolf on 2004-06-14 18:27 ]

wolf · Post by **wolf** » Sun May 23, 2004 2:46 am

additionally and exclusively delivered with the MatrixDelay the (bought) package will contain also its small brother, the MatrixInsert.
This is just the serial/parallel matrix with inserts instead of effects.<img src="http://www.worldless.com/sfp/pics/mi.jpg" width="332" height="243">
have fun !
wolfgang

MD69 · Post by **MD69** » Fri Jan 06, 2006 4:46 pm

Hi

Just discovered this package (bought it) and found the Matrixinsert being really useful for XTC owner: you can view this as a kind of TC GMajor on steroid!
The only thing it lack is an assignable CC modulation matrix (kind of 4CC lines and 12 column (2 per insert FX) ) to make this a complete multiFx.

The MatrixDelay can do nice Fx too.

Really good and worth the money!

Michel

wolf · Post by **wolf** » Sat Jan 07, 2006 1:16 am

Hey Michel,

thanks for purchasing

What exactly do you want to control via CC ?
The positions or something else ?
As long as it is inserted in a midified device, all inserted fx should be controlable by CC.

kind regards
Wolfgang

MD69 · Post by **MD69** » Sat Jan 07, 2006 2:42 am

Hi Wolf

Thanks for your reply!
The idea is as follow:
Midi define 4 general purpose controler (8 or 16bits resolutions). What I would like is that I'll have a matrix (on a 2d screen) with 4 lines (CC ins) and 12 column (assigning 2 CC per insertable FX). At each intersection (line/column) there is an sensitivity adjustment. Ideally, the 2 midi CC assigned to insertable FX should be shared across FX in order to generalize the presets across FX (each FX would expect 2 incoming CC sources: always the sames). The CC number assignation for the incoming CC and matrix settings should be stored in the MatrixInsert preset. The CC assignation to insetFx should be statically pre assigned.

Don't know if this is clear, but if you do this, I'll buy the upgrade!!
It will be the plugin of the year for me!

Cheers

Michel

wolf · Post by **wolf** » Sun Jan 08, 2006 12:59 am

The CC assignation to insetFx should be statically pre assigned.

Here it becomes impossible to implement/work, as I don't know, which device will be inserted (and there a lots) and it would have to be preconfigured in regard to CCs.

kind regards
Wolfgang

MD69 · Post by **MD69** » Sun Jan 08, 2006 3:22 am

Hi Wolf,

Quote:
--------------------------------------------------------------------------------

The CC assignation to insetFx should be statically pre assigned.

--------------------------------------------------------------------------------

Here it becomes impossible to implement/work, as I don't know, which device will be inserted (and there a lots) and it would have to be preconfigured in regard to CCs.

You should not bother about the inserted FX, Just to send a predefined CC to it.
The inserted FX preset will be updated to integrate the CC manually.

The idea is that the MAtrixInsert and Scope FX behave coherently by "standardizing" the CC interface (that way the controler preset of each FX should be the same).

Maybe also, An input/Output gain to leverage presets and two assignables LFO could be added afterward (could be an update of the update if you sell enought....)

Sound like you could do the matrix .... PLEASE, this a really needed device, believe me. By addind matrix routing to XTC routing capability and making this routing managing CC as well, increase the XTC capabilities

Cheers

Michel

wolf · Post by **wolf** » Sun Jan 08, 2006 3:59 am

You should not bother about the inserted FX, Just to send a predefined CC to it.

Exactly that is the problem: Scope creates the "signal path" for CCs automatically hence I cannot "jump" in later. And disabling the automatic assignment leaves me with the problem, that there is no "signal path" to the inserted fx created, where I could send the CC along.
Hope my explanation is comprehensible

MD69 · Post by **MD69** » Sun Jan 08, 2006 4:17 am

Well, If I do understand, even if I manually assign an FX parameter to this CC number by right clicking on it, the inserted FX will not receive the midi event!

Then, would it be possible to leave the CC number assignment manual? (I wonder if then it will be possible to assign the same CC number to each FX?)

Or maybe using Sync/Async then Async/Sync back ?

Cheers

[ This Message was edited by: MD69 on 2006-01-08 04:30 ]

wolf · Post by **wolf** » Mon Jan 09, 2006 6:08 am

Well, If I do understand, even if I manually assign an FX parameter to this CC number by right clicking on it, the inserted FX will not receive the midi event!

no, when disabling the internal automatic assignment, it becomes a bit more complicated

In fact the control would receive two different CCs at the same time and couldn't decide, which one to select.

Then, would it be possible to leave the CC number assignment manual? (I wonder if then it will be possible to assign the same CC number to each FX?)

nope, this is not possible anyway. But you can use the MidiControl from my MidiToolBox, to control several destinations with one knob (to which you can assign a CC)

Or maybe using Sync/Async then Async/Sync back ?

This would require a separate conversion built in each inserted device, which isn't the case.

kind regards
Wolfgang

[ This Message was edited by: wolf on 2006-01-09 06:10 ]

MD69 · Post by **MD69** » Mon Jan 09, 2006 6:47 am

Hi Wolf,

Damn too bad!!!

Anyway, this little MatrixInsert is doing well already, it populated in nearly all my templates

Thanks for your support

Cheers Michel

[ This Message was edited by: MD69 on 2006-01-09 06:49 ]