Dave Smith Instruments SYNTHESIZERS group photo

Yahoo Groups archive

Dave Smith Instruments SYNTHESIZERS

Index last updated: 2026-04-28 22:43 UTC

Message

Re: [DSI Synths] Re: DSI Evolution?

2010-10-17 by Scott Lawlor

when you say the encoders jump, what does that mean from a sonic perspective?
----- Original Message -----
From: lesser_inc
Sent: Sunday, October 17, 2010 4:42 PM
Subject: [DSI Synths] Re: DSI Evolution?


Let's face it. In this day and age its what limits us, not enables us, that creates good music. Seriously, you have NO OTHER WAY to create a sequence to send to outboard gear? Is it THAT difficult to recreate the bassline you programmed on the Evolver to send to another synth? I just don't believe it.

What DSI has going for it is that Dave has some sort of vision for his instruments. I don't feel he's ever just tried to rip off Moog or whatever. He builds things he wants to use. For the most part, I agree with his choices. Sure, there are things I wish the Evolver could do (at this point, mostly that my rotary encoders wouldn't jump), but what I respect is the insane amounts of flexibility already included in the modulation sources - for that matter that has always been included in Smith Products (Seq Circuits, DSI, Wavestation, whatever).

Yes, the Evolver is not a Fantom Workstation, nor is it a swiss army knife. It does what it does and I am thankful for it.

I'd rather Mr. Smith spend his time engineering a next generation synthesizer than patching the software for a synth thats basically a decade old.

j

--- In DSI_Evolver@yahoogroups.com, James Elliott wrote:
>
> I think it would go without saying that if a manufacturer were to open up the
>; code to the public then the company would not support the altered product. I
> don't know of any software company that has, so why would we expect DSI to? I
> think opening up the software to the public would be a great idea. I'm totally
> with Tom in that I would be a DSI customer for 'life' if they did something like
> that. Hell, DSI could even make some spare change selling chips with the
> original OS on it if people F'ed up their code so bad that they couldn't even
> revert back to the original code base.
>
>; But whatever, I don't expect this to happen. This code is more than likely on
> all of his products, so he wouldn't want his competitors stealing his
> intellectual property.
>
> -Jim
>
>
>
>
>
> ________________________________
> From: Stefan Trippler
> To: DSI_Evolver@yahoogroups.com
> Sent: Sat, October 16, 2010 5:57:01 PM
> Subject: Re: [DSI Synths] DSI Evolution?
>
>
> > In a synth world where it becomes increasingly difficult to differentiate
> > your product from the next
> > guy's, open source software is one thing that could really set you apart.
> > How about it, Dave?
>
> This might indeed bring a few new customers. But most likely not enough to
> cover the cost of the additional people for the manufacturer's support
> department.
>
> Or do you really think that customers wouldn't expect support from the
> manufacturer for a third party OS or would not blame him for problems caused
> by 3rd party OSs?
>
> "Hey, Dave, OS 0.1 beta from well known list member X adds a lot of
> fantastic features to the PEK. Unfortunately it causes my PEK to
> occasionally freeze and sysex transfer to downgrade to an older OS was
> promised only for version 0.2.
> X unfortunately doesn't reply to my mails atm, I think he is on holiday /
> didn't pay his provider / is a little distracted after his divorce/his pet's
> passing/his boyfriend's unexpected pregnancy / can't be bothered with bug
> reports atm cause he's already developing another set of fantastic addons /
> ...
>
> So I thought that DSI could help for once. I suppose it takes only a few
> minutes to recompile, interpret and debug his uncommented C++ code" ;)
>
> Things like that have never happened in the past and will never happen in
> the future.
>

etc etc etc

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.