it’s great to see the 301 growing and growing, I still don’t have one but often wonder when it will be “officially” released. Is that not really on the cards with such a great community going for those that have it and things being developed still?
I’m guessing by v1.0.0 he’ll have figured out a flux capacitor module along with some sorta bitcoin miner and / or Trump jargon translation matrix to cat vocalization translatron.
I only bought the ER-301 because I’d seen some early literature that promised just those things after the manual was done!
I doubt there will be a clear announcement stating “the ER-301 is officially released”. I expect more of a gradual realization or spreading of agreement among users.
By this metric, I would say that the 301 has already hit stable status and feels already pretty official. That it continues to get updates and new features is sort of the nature of the device to begin with and shouldn’t really be used to determine whether it is official or not. (at least not beyond the initial basic features promised that is.)
With an SDK and confirmed possible upgrade path in the future (and even the possibility of an expansion module for additional outs), I don’t see the feature set ever really coming to a halt. It will be an investment which keeps growing in value.
Seems popping is introduced around 80-85% CPU usage, which makes me excited for an upgraded CPU option in the future.
I guess the 301 is “ok” at this point. Meh…
So this unit has got me thinking, is anyone up to the challenge at making a morphagene unit?
Possibly from using some of this or from scratch?
I’ve thought about it, though it would be missing a few key things…No way to splice with custom control or cv. Or record to new splice. Not sure about the morph function either.
Yes, maybe if/when we have the ‘pedal looper’, the splicing will be doable. Morph seems somewhat possible…I don’t have a Morphagene (wish I did) but I understand that this is overlapping slices, so you could perhaps use a set of sample players. The start point and length can be changed so this would get you a more stuttery sound. Not sure about how the Morphagene’s envelope works.
I don’t have a morphagen nor a 301 (mines shipping at the end of November) but I feel like a simpler version could be achieved maybe a phonogene?
Just something fun to think about or watch the masters create while I impatiently wait to join the club
I hope my observation didn’t come across as critical of the 301 and the massive effort by all involved. I’m floored that there is meaningful dialog happening between ideas and technolgy here, both working to influence each other at an incredible pace. Humbled to be positioned such that I get to both witness and work with the materials generated by a brilliant group mind. Thanks again for this rad custom unit!
The sample player as-is comes pretty close to some of the features. Speed is pretty much the same as Vari-Speed, you can still enter splices manually and switch between the splices with cv, shift is close to slide (though I think slide has a wider range) and you can modulate the splice size by re-triggering the sample player.
i forgot about that vid! I think I’m going to try that one again with some banged piano strings!
FWIW, I didn’t read any criticism into what you said. Only excitement for the future.
Slightly off-topic, but this posted from Olivier about Clouds, seems we are one step ahead of the game with Ultraviolet
The last Clouds are being sent to dealers. The module is no longer in production.
To me, Clouds has always been a struggle, the ugly outcome of an entire year of inner battles during which nothing turned the way I expected.
Dyes started in January 2014 as a kind of phase vocoder/spectral freeze effect. Something really fun to play with in Pure Data, but which proved to be disastrous when put into a Eurorack case, because of latency and slow CV sampling rate issues. Throughout the year, my investigations followed two paths: How can we make things sound smudgy, frozen and weird without resorting to FFTs? And what on earth could we run on this bit of hardware with 7 knobs, stereo I/O, 6 CVs and 2 gate/triggers? These two tasks converged towards what is Clouds’ default granular processing mode. The enthusiasm of the beta testers confirmed that I was onto something and that I should absolutely release the module, but I was already getting way too conscious of its shortcomings to believe in its success.
One example: Originally the BLEND button controlled dry/wet balance and that was it. Feedback, pan randomization, reverb… had to be obtained through external modules. Then I tried adding those settings, and there was actually a point when these four parameters were still exclusive: if you wanted to use the reverb, then the output of the module was 100% wet and you had to use a mixer to do your dry/wet balance. But almost everybody requested independent, simultaneous control on all these parameters without resorting to external modules, and not in 24-HP please, so I compromised and we ended up with the current implementation of the BLEND knob, which I am not very proud of.
The testers got served a bunch of half-baked treats during the beta testing: delay and looper like functionality, a kind of SST-282 emulation, a reverb-based freeze effect, the original spectral freeze. And no matter how wonky this stuff was, no matter how arbitrary the chosen parameters were (after all everything had to fit in this 7-knob interface)… it still had a sentimental value to me and I could not totally let go of it. It ended up as hidden modes, the ultimate sin!
By the end of 2014 I was tired of the project, wanted to be over with it, so I decided to have 250 Clouds manufactured, which I hoped would simultaneously be the first and last batch. I predicted it would have the same destiny as Edges - something that a few people would totally get and love… and that would go unnoticed by the rest.
And then, in what could be seen as a very meta plot twist, the deity decided to use Clouds to process all the beliefs and perceptions surrounding the module, got confused with this damned BLEND knob, feedback and reverb got stuck to the maximum setting, resulting in a never-decaying smudgy howl of hype. And I felt awful about it.
- Explaining at least once a day that Clouds won’t make clouds unless you patch attenuated random sources to its CV inputs (corollaries: your Doepfer mini-case with Clouds and an Intellijel audio interface is not what I would call a good starter system).
- Clouds as a simple “end of chain effect” (one jack in, two jacks out), with the heavy lifting often done by the internal reverb and not much else.
- Richard Devine still running the December 2014 firmware.
- That the jokes were always about "Rings into Clouds”, but never “Clouds into Rings”.
Let’s take a break.
Clouds has shown that live granular transformation is an important sound design tool in a modular system. There ought to be a distraction-free device to perform it. I’m currently building it.