Here's an idea...

[iPassenger]

What if a number of us work together on a patch and variations. My idea is this, one of us, starts a patch with say 5 modules and wires however they see fit n then posts the patch up here, then someone else adds another 5 modules, re-patches and re-dials as they see fit and then post their version. We keep going, different people adding their own modules and touchs until there is no mem left.

(i think we would need to keep it mono)

What do u reckon?

Maybe we would need to agree a rough agenda for the patch (bass synth, sound fx, noodle etc)? And perhaps agree a number of members to take part (on a rota basis) or perhaps that each person only contributes one of the minor sections to the finished team effort (therefore we would need a lot of patchers involved)? Maybe 5 modules is too many, maybe it should be 3 or 4?

Just thought it might prove an interesting experiment and I am sure I might learn a thing or two in the process.

Cheers

R.

[cebec]

I think it's a cool idea. Count me in!

[G2DREAM]

Me too, I love this idea!
___________
cyber-evolution

[blue hell]

So where is the patch

I'm not set up yet (after Chateau Sonore), but sounds cool to me !

[Wout Blommers]

We did something like this during the top days of the NM Classic, only the rules were: Change one module and add one.

Wout

[cebec]

[iPassenger]

I just tried to post this and something went wrong, so am going try again.

As folks are keen to get started, lets just run with it and see what happens. You might say it is a modular approach, modifying as necessary.

Purpose:

Make ambient drone/noodle

Rules

1. Can add up to four modules (no less than 1), swapping a module for another counts as adding one.
2. Keep it mono.
3. May spread to performance if necesary.
4. This is a free for all no order of submissions, it if gets out of hand, we'll try and order next time.
5. you cannot modify again until two other people have modified it since your last modification.

Here is part one:

EDIT: No longer have this patch, sorry.

[Wout Blommers]

[iPassenger]

Yes i figured that this is a risk, which is why i sggest for the next one, we agree a running order and time limit.

[cebec]

Here's my submission. I made a variation and added a notch filter set at 24 kHz to remove the 24 kHz control rate bleed which occurs under certain conditions, especially when using a control rate module as an audio source. This notch attenuates the bleed, a 'spike', by about 25 dB. I adapted this building block from some elliptical filter thingy. It adds about 4% memory and processor load. It can always be removed once there's more going on, etc.

---

team drone 2.pch2
Description:		Download (listen)
Filename:	team drone 2.pch2
Filesize:	1.24 KB
Downloaded:	2276 Time(s)

---

[blue hell]

Added a frequency doubler (one and a half actually) and a filter.

(*)

---

team_drone_3.pch2
Description:		Download (listen)
Filename:	team_drone_3.pch2
Filesize:	1.46 KB
Downloaded:	2392 Time(s)

---

[iPassenger]

more lfos and some noise, wanted to patch it in to the audio stream as well but ran out of modules.

EDIT: No longer have this patch either, damn, I am too delete happy. Sorry folks.

[blue hell]

Nice one, can hardly wait to do a little to it

[dasz]

ok, my small contribution from the sequencer dept. the lookup sequencer concept may be familiar to some folks (who attended EME 2007).

No longer a drone I am afraid. Play at 120.

I like this idea of bouncing patches off-of each other. I always like that stuff, too bad it has not been more prevalent around here.
/Dasz

(note: restored the patch - Blue Hell)

---

team_drone_dz_490.pch2
Description:		Download (listen)
Filename:	team_drone_dz_490.pch2
Filesize:	3.07 KB
Downloaded:	1719 Time(s)

---

[blue hell]

erm ...

[iPassenger]

Nice patch tho.

They do say that rules are meant to be broken. 4 from now on.

So who's next?

[dasz]

[blue hell]

(*)

---

team_drone_5.pch2
Description:		Download (listen)
Filename:	team_drone_5.pch2
Filesize:	3.04 KB
Downloaded:	2294 Time(s)

---

[mosc]

---

team_drone_5_169-1.pch2
Description:		Download (listen)
Filename:	team_drone_5_169-1.pch2
Filesize:	3.46 KB
Downloaded:	2579 Time(s)

---

[Fozzie]

Cool topic

added 1, modded 3

---

team_drone_6.pch2
Description:		Download (listen)
Filename:	team_drone_6.pch2
Filesize:	3.55 KB
Downloaded:	1754 Time(s)

---

[iPassenger]

Awesome.

[iPassenger]

OK, so i am getting a bit lost now, so I just added some effects to space it out a bit.

And another variation, which i thought was a bit more spacey (just chanegd wiring and dials a bit on my first patch):

Don't believe i mentioned vars in the rules. ?

---

team_drone_7.pch2
Description:		Download (listen)
Filename:	team_drone_7.pch2
Filesize:	3.92 KB
Downloaded:	1772 Time(s)

---

---

team_drone_7_222.pch2
Description:		Download (listen)
Filename:	team_drone_7_222.pch2
Filesize:	3.92 KB
Downloaded:	1803 Time(s)

---

[iPassenger]

[blue hell]

Some great patches you people posted !

When I started my mod I lost track of what everything was doing after I added my four modules. So I totally deconstructed the thing and then rebuilt to attached. Some modules were left unused maybe they should have been deleted but I'm not sure about the deletion rules ...

(*)

---

team_drone_7_222_195-4.pch2
Description:		Download (listen)
Filename:	team_drone_7_222_195-4.pch2
Filesize:	4.54 KB
Downloaded:	2533 Time(s)

---

[cebec]

I changed one Osc to reduce DSP, added a Glide module, and changed some routings and settings.
Heh, I'm also finding it difficult to keep track of what I'm doing once I get going.

---

team_drone_8.pch2
Description:		Download (listen)
Filename:	team_drone_8.pch2
Filesize:	4.64 KB
Downloaded:	2327 Time(s)

---