Dave Smith Instruments SYNTHESIZERS group photo

Yahoo Groups archive

Dave Smith Instruments SYNTHESIZERS

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

Thread

Evolver SoundEditor...scant documentation.

Evolver SoundEditor...scant documentation.

2007-06-07 by randy

(evolver mono dsktop, v3.0...PC computer, soundcard midi ports
)
No, I don't usually complain, but I have trouble understanding why
there aren't actual "instructions" ?....the "windows based help" is
but a brief overview. 
The 3.8 version (for PC) I just purchased, came with a PDF, but that
says  "Mac version"....maybe this applies for both the PC and Mac..??
(no mention about that)
Although again, this PDF is still just an overview, explaining what
can be done, but not HOW to do it.
I know how posts like this one are received..."dude, why don't you ask
a specific question? " Well I'm just frustrated that there might be so
many little questions....about what seems to be a relatively simple
program....if only the documentation took a FEW extra steps, this
would not be an issue (for me). This is why I am a fan of having
someone else write a manual -- not the software creator, because too
many things are taken for granted in operating the program.....what's
simple for him to understand, surely won't be, for a new user.
LOADing sysex, RECEIVing sysex :
I have .syx files wanting to get to the editor and the evolver. How?
I WAS able to dump/call evolver's old 2.0 presets up to the editor,
but no patch names. I discovered that I needed to enable "sysex
commands" for that.
This is as far as I got. I have the v3 banks (.syx) and some others.
How do I put these into the editor, and then to the evolver ??

Rant over (I know SoundTower put much work into this robust program,
probably with little profit, and that is greatly appreciated. I'm only
questioning the documentation (he's got to be tired of answering 
emails? maybe?)

=RR=

Re: [Evolver] Evolver SoundEditor...scant documentation.

2007-06-07 by SoundTower_Help Desk

Hi Randy,
Thanks for the comments on the documentation. I do appreciate the feedback actually as I have the honour of wiriting most of the documentation.
A couple points regarding the style of the documentation. It is scant on purpose. Since the programs are built to mirror the functionality of the hardware I make the (usually adequate) assumption that the directions I write out will twig an understanding based on what has already been learned on the keyboard (rack...whatever).
As I state in all the help files, the doc is not meant to teach about the hardware only give some pointers about the software.
Now, that being said, if I have missed the mark on the software in some areas PLEASE let me know. If you have the time send me a short list of the offending sections and why and I will get on it over the next few weeks.
We are dedicated to getting software out in a timely manner. We don't want to take 2 years when there is a need just becasue our documentation is not as polished as some.
again thanks greatly,
Derek
SoundTower Help Desk
PS. Yes the doc's apply to both PC and Mac. The bitmaps are sometimes from on or the other depending on which machine I start on. The slight differences between OS are highlighted as they are explained. I am sure someone will find an example where I missed though. For that I will nip off and slap my self.
best
d

randy wrote:
Show quoted textHide quoted text
(evolver mono dsktop, v3.0...PC computer, soundcard midi ports
)
No, I don't usually complain, but I have trouble understanding why
there aren't actual "instructions" ?....the "windows based help" is
but a brief overview.
The 3.8 version (for PC) I just purchased, came with a PDF, but that
says "Mac version"....maybe this applies for both the PC and Mac..??
(no mention about that)
Although again, this PDF is still just an overview, explaining what
can be done, but not HOW to do it.
I know how posts like this one are received..."dude, why don't you ask
a specific question? " Well I'm just frustrated that there might be so
many little questions....about what seems to be a relatively simple
program....if only the documentation took a FEW extra steps, this
would not be an issue (for me). This is why I am a fan of having
someone else write a manual -- not the software creator, because too
many things are taken for granted in operating the program.....what's
simple for him to understand, surely won't be, for a new user.
LOADing sysex, RECEIVing sysex :
I have .syx files wanting to get to the editor and the evolver. How?
I WAS able to dump/call evolver's old 2.0 presets up to the editor,
but no patch names. I discovered that I needed to enable "sysex
commands" for that.
This is as far as I got. I have the v3 banks (.syx) and some others.
How do I put these into the editor, and then to the evolver ??

Rant over (I know SoundTower put much work into this robust program,
probably with little profit, and that is greatly appreciated. I'm only
questioning the documentation (he's got to be tired of answering
emails? maybe?)

=RR=


Don't get soaked. Take a quick peak at the forecast
with theYahoo! Search weather shortcut.

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.