Hi @ PD Forum

I'm just getting started in PD and naturally getting stuck ..... which seems the best way to learn (LOL).

1. Anyway, here's a patch - in the attachments - for a simple sequencer that I'd like to develop. I can't understand why when I duplicate the patch it doesn't work anymore (as I thought it would). I notice that the first patch plays the notes in the order they are attached to the 'select/sel' cell, yet when I duplicate the patch it (the 2nd patch) only plays middle C (60) continuously, why?

Can someone help me out with what I'm sure must be a simple problem and oversight on my part. I'm using a SimpleSynth for the midi sound if that's important.

2. To help me develop the idea how would I make these notes randomly play - order wise that is.

A big thanks in advance to anyone who can help this starter out.

http://www.pdpatchrepo.info/hurleur/__6_sequencer.pd

i think what you have isn't a pd problem at all, it's a midi problem.

if you try changing [noteout 1] on the second instance to [noteout 2] does that help?

oh, and there is an object called [random] to help you with the random thing

I tried 'noteout 2' didn't seem to change anything, I did actually wonder about that. As for the midi suggestion wouldn't it affect the both patches, no? As you'll notice the first patch keeps on working no matter what!

I tried the same thing with oscillators and it seemed to work fine - however they're not using the midi patches of course.

Any other suggestions? (I'll look at the midi problem but not sure where to look to solve the issue).

Big thanks anyhow.

Hi Joesh,

I'm not sure why this only happens for the duplicate, or why it is midi note 60. But it might be helpful to know that the last outlet of [select] outputs everything that does not meet the criteria given by the arguments. In your patch you have 8 arguments in the select, but 9 note messages connected. If your counter mod went any higher than 8 then the last note would occur a lot more.

I've attached a simple synth that plays random notes in a random pattern - Also included some abstractions from the rj library.

Hope that helps.

http://www.pdpatchrepo.info/hurleur/simpleSynth.zip

Thanks, I hadn't noticed that problem. I've changed it and set the system working to see what happens!

Thanks for the synth patch I'll look into shortly. Of course if you have any good suggestions please tell me - as I pointed out at the beginning I'm just starting so quite tiring trying to sort out all the little problems. As you know it's a little overwhelming at the beginning.

Thanks.

**** I'll post a 'solved' message if the above solution works.

Problem solved, thanks. It was indeed number of arguments not matching number of messages.

Thanks a lot @Jwif for noticing that. Now I just have to get my random bit up and running. This way I'll get my (kind of) Steve Reich thing going which I need for a solo sax recital ...... let's hope :-0.

Glad you solved it.

My suggestions are in the patch. Open _simpleSynth.pd

Actually I'm back again as I thought the problem was solved, not so!

It's not that important but if someone with a good knowledge of PD can look at the patch(es) and suggest why such a problem should occur I'd be most interested.

As already mention above the numbers boxes after the counter and 'bit twiddlers' may contain the answer as they always become + and -2, most strange. I don't think it's a midi problem either as it happens even without the running through a midi keyboard. It's almost as if there's a bug somewhere ..... but the patches are set up correctly, aren't they??!!

For the patch see the original question.

Your patch works fine for me. I even ran it into Logic and recorded the MIDI notes. There's no repeating middle C anywhere.

Wait a minute, I think I see what the problem is. If you're getting + in the number box, that means the number is too large to display. What I think is happening is that you're letting the patch run for so long that the numbers become too large to accurately represent as a 32-bit float. The highest integer you can get before it starts skipping values is 2^24. I just set [counter] to start on that number and started getting unreliable results. You should just set the arguments in [counter] to [counter 0 7]. That will keep it from getting too high.

Hi Maelstorm

Big thanks I'll try this, maybe the answer - thanks. I'll get back if it doesn't work.

Sorry for the late (thanks) reply ...... away on vacation etc.