HN Simulatornew | past | comments | lists | submit | diskzero's commentslogin

There is/was; the Muse Research Receptor. It might be overly complex for what you are thinking of, but it existed.

https://www.soundonsound.com/reviews/muse-research-receptor

https://www.soundonsound.com/reviews/muse-research-receptor-...

You can pick them up, often fully loaded with plugins, for a few hundred dollars. I wrote parts of the system. They were running Linux and fun to hack on.

I currently work in the professional audio industry and know of a few modern efforts underway to produce modern version of this, but I am not convinced there is market for such a device anymore.


That's a really cool. It doesn't look overly-complicated, just perfect actually. I might keep my eyes peeled for one of these things, I love scrounging around for old MIDI gear. Used to be a lot cheaper than it is these days, ironically. Build quality on most everything was top notch too.

I'm sure a lot of professional musicians would probably prefer to use something less fragile than a laptop, something you can rack up, with no pesky desktop OS niggles to worry about during a show. As you know many instruments today are simply dedicated VST runners with a handy physical interface, see Roland's Boutique and Aira synths. I have an MPC One which I love, it can run proprietary VSTs. Maybe such convergences have killed the need for a dedicated box.


They are super cool! Look on Reverb. As I said, you sometimes end up with some fully licensed, expensive plugins as well. A lot of us can probably survive being a couple of versions behind.

I know for a fact new devices like this are on the horizon, but it just might not be the form factor that you are looking for.


For me the main issue is the VST-as-a-service model which is already taking over. I don't sub or micro-transact. The Roland VariOS thing I have had very expensive instruments too, luckily mine came with the CF card with all the ones which exist. I've never hooked my MPC up to the Internet to get VSTs either, I'm quite happy with what I have actually. I have been fiddling with electronic music for a long long time, and I remember when VSTs hit the scene, I got VST-itis and must have pirated everything under the sun but that leads to choice paralysis (same as getting all the MAME ROMs back in the day). Now I'm happier getting more out of what I have by using my brain a bit. Having generic USB MIDI on the MPC has been amazing though, everything is so much tighter without having to daisy-chain and even Roger Linn is impressed by how tight the timing is. 9 ins and outs is incredible, if I need more I just attach another generic USB MIDI interface.

It's actually a golden age for the MIDI fan but there's a lot of complaining to be done too about aspects of it. Cheapness and hooking you to a store being two big ones.


It is interesting you make the observation about GNOME and Apple. In 1999, GNOME had the involvement, and financial resources, of some of those Apple people due to Eazel. Andy Hertzfeld, Bud Trimble, Susan Kare, Mike Boich and more all gave improving GNOME and Linux some work.

This wasn’t a hostile takeover attempt; we all tried very hard to be team players, many times to what I think was our detriment. A very nice version of Nautilus was rejected because it was in C++ and we ended up doing all the work in GTK.

We had some very good ideas about distributed objects but they were pushed aside and we ended up using CORBA/ORBit/Bonobo and those distributed object systems ended up being replaced.

The dotcom crash caused a lot of Eazel people to end up at Apple. Nat and Miguel moved onto their dot NET Xamarin effort and many others ended up at Red Hat. There was an experience vacuum and this is one reason why the GNOME UX had so many issues IMHO.


Yes, it was humbling and one reason was many of them had developed their skills in tandem with the growing complexity of the hardware and software. They had an amazing advantage of being there when it was all happening and being built up around them.

As for design patterns, I would never accuse Andy of using them. He was a coding wild man and super impressive, but his real skill was coming up with cool ideas and willing them into existence. Working with him, I always felt he was going through the jungle making paths with a machete and the rest of us had to actually build the roads behind him.


You can still get this experience by trying to do some things the old ways. One that's come up to me recently: program an ATMega328 (the famous Arduino chip) in assembly to output a waveform with tight timing requirements.

That is, as opposed to using a timer interrupt or a delay routine, arrange instructions so that the processor naturally gets to the instruction to change the output pin at the correct time, within the acceptable tolerance. These processors have no caches or predictors so instruction timing is reliable.

I think people are doing it these days on the Raspberry Pico chips, but any "old school" microcontroller will do.


Multifinder could be thought of as a spiritual successor to Switcher but it shared no code with Switcher and took a different approach to solving the problem of allowing a user to interact with multiple running applications.

Erich Ringewald, the author of Multifinder, and Andy weren’t done with this problem at, or with, Apple. I got to work both of them, Erich at Be and Andy at General Magic/Eazel.


Maybe or maybe not. I would say in general most of us here are not fans of subscription services. Those of use who have sold software and tried subscription services are very aware of the hate received by many of those paying for the subscriptions. I assure you that Ableton management is extremely aware of the general unfavorable opinion users have of subscription software. This rent-to-own model is an attempt to provide a quality product to as many users as possible and still manage to operate a going concern. Almost no one gets into the creative software space with the intention of gouging their users. There are much better outlets for people with those intentions.

Now, if Ableton ends up being acquired by a private equity firm, you may very well see a shift in their pricing model where extracting revenue from customers at the expense of product quality becomes primary.

If you have worked with any of the people currently, or formerly, running Ableton, you will know that they worked hard to regain their financial independence from their outside investors and I doubt becoming a predatory software subscription service is on their roadmap.


It also wouldn’t work because I can just keep using the current version indefinitely.

There is very little reason to upgrade to the latest versions IMO


Substance was also really cool company with the same model and Adobe bought them out.

> if Ableton ends up being acquired by a private equity firm

That 'if' really is doing a lot of heavy lifting and I hope it really is nothing more than an 'if'. PE feels like the Sith in Star Wars, a dark force that works in the dark and wants to take everything that is good and extract money from it until it inevitably dies.


I sympathize with your opinion on the prices and I really appreciate how FL Studio has managed their lifetime upgrades. When you look at the monthly amortized cost of the $600 spent on Ableton, it is right in the range of monthly audio and video streaming services and way less than a monthly phone plan that a lot of us are paying for. I wouldn't say they are gouging their users, and if they are like any other small software company, they are probably on the knife edge of profitability any given quarter.

The cost of audio (or any) software has been something people have been complaining about for decades. When I started in the audio software industry, the prices (amazingly!) were just as high or higher as the prices today. Some of this cost was due to physically creating boxes, manuals, storage media and paying to get the product into sales channels. Viewed historically, you might see that you are getting a much better deal today with Ableton for $300 than Opcode Studio Vision 1.0 in 1990 for $995. In 1990, you had to call into Opcode for support and there was no online community for support and information sharing.

It is real conundrum running a company that sells creative tools; the very users you want to bring in as new customers might be the ones that are the most resistant, or unable, to paying the full price. The industry has tried to come up with various ways to assist the people, including the $79 version of Ableton that you are not a fan of.

When you are actually deriving your income from the use of the product, the pricing becomes less of an issue and I clearly remember Warner Brothers buying dozens of copies of our software to support a Danny Elfman project because he was using our software. I also remember struggling composers begging for education pricing or even free copies of the software at our booth at the NAMM trade show.

FL Studio is not unprofessional noob software by any means. Ultimately, a talented singer, songwriter, composer, DJ, etc. will use any means they have on hand to be creative.


It is an integrated environment, but https://www.opusmodus.com is worth checking out if you are into algorithmic compositions and Lisp.

There have been several Scheme-like live coding systems that have become popular and faded away over the years. https://tidalcycles.org and its web-based friend https://strudel.cc are Haskell-like and were also getting some good attention a while go.


Once opening the door to Strudel.cc, there's no coming back. Its approach to patterns and sequencing is so ingenious, I can see a whole generation embracing it as modern way, modern notation for music, which is not played physically, but performed digitally. Further on - strudel is so easily plug-able that it easily integrates with DAWs and even a simple Mainstage + VSTs (or VCV rack) is more than enough to go totally berserk with both sound design or/and pattern sequencing.

True, but this is how we used to do it in the old days, when track limitations forced us to bounce with all the outboard effects baked into the track. Producers might not physically ride the faders anymore, but a lot of them are very reluctant to even track vocals through compression onto disk. They want to keep everything available for processing later on.

Now, is this a good idea? There is a lot to be said about having an upfront plan about the usage of effects and placement of parts on the soundstage and committing. This might be a lost art, as I keep seeing Pro Tools files with hundreds of tracks, with stacks and stacks of effects.


Freezing/bouncing also lets you have more determinism.

Plugins with (often intentional) indeterminism in them, variations in OS and CPU architecture, variations in how fast their CPU is (a billion plugins on a track may run smoothly for one person and destroy someone else's machine), variations in sample rate, etc. can subtly or substantially affect how something sounds.

And in general it just makes things way easier to share even ignoring the issues of getting people to install the same plugin at the same version and the IP issues.


I mean, as an older fart, I do think there's value in committing to an idea. Though, I could also see benefit in having the processing be malleable until the last possible second. I mean, imagine if you're working with an egomaniac artist who keeps being wishy-washy on which sound they like best. If the effects are being printed and they want to go back, it could become a huge pain in the ass. AT THE SAME TIME, I think there's merit in telling someone 'no' so the project can move forward. I dunno, I guess it depends. I can see it both ways.

Many of the producers of the plugins are against a central repository for reasons you can guess; licensing and revenue generation. One annoying part of working with various plugins is the companies tend to have gatekeeper applications the user needs to interact with to get plugins authorized and installed on their system.

You will find applications like this one, https://www.pluginhubapp.com, show up frequently to try and manage this complexity. I am in no way at all recommending this application, but it is an example. This application does ship with all of its python code in the app under (possibly a mistake) so you can see the hoops they have to jump through to try and make their system work.


The main argument to me in creating your own DAW is that you have some workflow that simply can't be done with the other tools. Otherwise, you are going to spend massive amounts of time just to replicate Ableton 1.0, let alone Live 13.

Thanks for sharing the song. This is material proof that your program can generate a composition. Did you come up with some new ideas about how to create and produce?


I don't think I have anything groundbreaking yet.

Blending lots of ideas from other places (unsurprising I'm sure). I first used FL Studio, and am more recently an owner of Ableton. Some things I like and dislike about both, so what I tried to do with my app is blend what I like.

E.g. FL Studio = step sequencer. Ableton = more intuitive (I think) for whole song composition. Of course, now Live 13 has a Step Sequencer...

The other areas I'm exploring is sound design. One goal in this effort is to remove dependencies on other tools as much as possible. So every sound you heard in my song is from the app alone - not some external sample or other synth/VST tool.

So, then suppose you sit down with a blank slate and draw a wave. Preview it. Now add bits and pieces on top. But more of a visual design canvas rather than the Reason-style rack wiring.

PS: Thank you for checking out the song!


How did you implement the side-chain compression? (I think I am hearing that.) We can also move offline of HN if you would rather discuss there. gene at semitone dot audio.

Happy to do both!

But answering here if I understand correctly: I use (at the moment) a mostly serial chain architecture.

I think what you're asking is whether I'm using signals from one instrument (or other component) to drive another. Not as much as a first class feature similar to what you'd find in Ableton.

So, for example, I don't have today something that will drive low-pass cutoff frequency on a synth based on the kick drum sine wave decay.

Same idea you're mentioning?

On my list to get to but not there yet! I tend to add things as they come up in the process of making music, rather than approach this as a software-first-music-second project.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: