lewis lepton

Just a quick question regarding a FM sequencer i am building.

I am just having a little bit of trouble with it, mainly for the fact it does not sound like it is hitting the bet when needed, but rather like a jack hammer.

Anyhow, i have a [matrixctrl], [route] and especially the [unpack] object to try a break up the signal of the [matrixctrl]. the unpack has many outputs, i think 8 in total, all which would then go an fm signal, each time changed to a different tone and note a together, whether you want a kick drum sound or anything else. But when played along with the [matrixctrl], it just outputs plain hitting throughout the sequence, rather than giving out the hit when it shows on the [matrixctrl]

here is an example. the main idea is so then i can have a full bloodied sequencer for drums, where you have to 'make' the sound, basically

this is not the final drum patch, but does play a part in what i need help with.

When a cell has been put in the top line of the [matrixctrl], it has to have the sound when it hits on that, rather than hitting throughout like it does when you turn it on

this is not the final drum patch, but does play a part in what i need help with.
When a cell has been put in the top line of the [matrixctrl], it has to have the sound when it hits on that, rather than hitting throughout like it does when you turn it on

fm-sequencer-problems

On Nov 27, 2008, at 12:29 PM, Lewis G. Edwards wrote:

> Just a quick question regarding a FM sequencer i am building.

You probably want a [sel 1] on each of the unpack outputs, so that the 

subsequent bang only fires when there is data in a cell.

You probably want a [sel 1] on each of the unpack outputs, so that the  
subsequent bang only fires when there is data in a cell.

Chris Muir
cbm@well.com	
http://www.xfade.com

Great, worked a treat. Thank you very much.

I was not going to sleep until i got that sorted, this means a lot. Most likely still wont go to sleep until i have the whole sequencer done now, hahaha.

Great, worked a treat. Thank you very much.
I was not going to sleep until i got that sorted, this means a lot. Most likely still wont go to sleep until i have the whole sequencer done now, hahaha.

one other thing with that patch, your counter should probably be [counter 0 31] rather than [counter 0 32] to give you 32 steps instead of 33 :)

true, because it always has that first output counted with it first, then the others follow suit

I would really like to look at your sequencer during the building process! What does it look like now?

Quote: Chris Muir wrote on Thu, 27 November 2008 13:39

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

> On Nov 27, 2008, at 12:29 PM, Lewis G. Edwards wrote:

> > Just a quick question regarding a FM sequencer i am building.

> You probably want a [sel 1] on each of the unpack outputs, so that the 

> subsequent bang only fires when there is data in a cell.

Ok, so I need 32 sel 1 objects, could you please explain again exactly why I need this?

Quote: Chris Muir wrote on Thu, 27 November 2008 13:39
----------------------------------------------------
>
> On Nov 27, 2008, at 12:29 PM, Lewis G. Edwards wrote:
>
> > Just a quick question regarding a FM sequencer i am building.
>
>
> You probably want a [sel 1] on each of the unpack outputs, so that the  
> subsequent bang only fires when there is data in a cell.
>
> -C
>
> Chris Muir
> cbm@well.com	
> http://www.xfade.com
>
>
>
>
>
>
>
----------------------------------------------------

Here is a picture of a the workstation i am building. So then i can now use this for most of my music making.

This is now in its 4th incarnation. It has gone under many faces lifts and have just finished making the interface much smaller and trying to conserve space.

I did have a sample player for drum hits before but that was just a test so then i can fit in the FM sequencer instead. I fancied a approach to actually making your sound, rather than using someone else's.

Soon i will incorporate built in synths and a few more surprises. More pictures will be posted up on my myspace page and also on the 'Max 5 is my Friend' group i also created on myspace

Here are a few, starting with the front page that pops up when you load it...

This is now in its 4th incarnation. It has gone under many faces lifts and have just finished making the interface much smaller and trying to conserve space.
I did have a sample player for drum hits before but that was just a test so then i can fit in the FM sequencer instead. I fancied a approach to actually making your sound, rather than using someone else's.
Soon i will incorporate built in synths and a few more surprises. More pictures will be posted up on my myspace page and also on the 'Max 5 is my Friend' group i also created on myspace

Here are a few, starting with the front page that pops up when you load it...


oooh sorry, no can do at this moment in time

i plan to give this away as a full program soon, but more when it is finished. I have plenty of things left before this can be used by the public at this time.

I plan to add 3 more audio inserts and the ability to choose each one at will. Take out the VSTi feature (or not), build some synths for it and some other stuff.

I am going to make a video of it in action mind, will post it on youtube, but will let you know when it is up there

i plan to give this away as a full program soon, but more when it is finished. I have plenty of things left before this can be used by the public at this time.
I plan to add 3 more audio inserts and the ability to choose each one at will. Take out the VSTi feature (or not), build some synths for it and some other stuff.

On Nov 28, 2008, at 5:04 AM, marlon brando wrote:

> Ok, so I need 32 sel 1 objects, could you please explain again 

Sure. What you are trying to do is to send a bang whenever a matrix 

cell is active. Hanging the [sel 1] after the unpack makes sure you 

only send a bang when there is an active cell. Otherwise the bang will 

fire every time it gets new data, whether it's a 0 or a 1.

> Ok, so I need 32 sel 1 objects, could you please explain again  
> exactly why I need this?

Sure. What you are trying to do is to send a bang whenever a matrix  
cell is active. Hanging the [sel 1] after the unpack makes sure you  
only send a bang when there is an active cell. Otherwise the bang will  
fire every time it gets new data, whether it's a 0 or a 1.

Actually, that unpack only needs to be eight wide, not 32, so you only 

need eight [sel 1] objects. There are only eight rows, so when you 

send the getcolumn message, there are only eight numbers returned.

Actually, that unpack only needs to be eight wide, not 32, so you only  
need eight [sel 1] objects. There are only eight rows, so when you  
send the getcolumn message, there are only eight numbers returned.

yes, i was wondering why there were 32 outputs on unpack rather than 8 :)

FM Sequencer Problems