Dave Smith Instruments SYNTHESIZERS group photo

Yahoo Groups archive

Dave Smith Instruments SYNTHESIZERS

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

Thread

updating to 2.0 killed my evolver!

updating to 2.0 killed my evolver!

2003-10-26 by djchimchim

I was unsuccessfully trying to update to 2.0 using midi ox.  
Each time the evolver would either drop out of the first 32 step 
countdown or it would freeze during it, in which case I would need to 
unplug it.  I tried changing the output buffer to 1024/128 and other 
settings.  Well Finally it froze again during the 32 countdown but 
now when I plug it back in nothing happens, it doesn't load up, no 
lights except sometimes the 7 column light comes on.  I'm afraid it 
might need to get a new PIC or worse.....I was pretty dead sure that 
it wasn't doing a binary countdown when I unplugged it, it would stop 
during the 32 step countdown.......anybody got a clue whats up?  Many 
thanks...........

Re: updating to 2.0 killed my evolver!

2003-10-26 by spectralsequence

Hello, I updated yesterday using the Evolver Editor.
It is straightforward, quick and efficient.
During the update, you can see a message "Do not unplug your
evolver during the update". It seems that it is exactly what you have
done...
I would like to add that I am always reluctant to buy music sofware,
but in the case of this editor the price is not outrageous, although
not cheap.  It will help me a lot.
Emmanuel.


--- In DSI_Evolver@yahoogroups.com, "djchimchim" <djchimchim@h...> wrote:
Show quoted textHide quoted text
>      I was unsuccessfully trying to update to 2.0 using midi ox.  
> Each time the evolver would either drop out of the first 32 step 
> countdown or it would freeze during it, in which case I would need to 
> unplug it.  I tried changing the output buffer to 1024/128 and other 
> settings.  Well Finally it froze again during the 32 countdown but 
> now when I plug it back in nothing happens, it doesn't load up, no 
> lights except sometimes the 7 column light comes on.  I'm afraid it 
> might need to get a new PIC or worse.....I was pretty dead sure that 
> it wasn't doing a binary countdown when I unplugged it, it would stop 
> during the 32 step countdown.......anybody got a clue whats up?  Many 
> thanks...........

Re: updating to 2.0 killed my evolver!

2003-10-26 by privat_joy

Hi,
maybe the evolver Editor would help the next time, but with Midi-OX
the same thing was happened to me! Evolver was like dead, no light was
flashing during powering up again, nothing! I am sure that my evolver
was connected the whole time during the upgrade process, and it didn't
lost power. So it looks like that maybe there is another problem,
maybe the midi-interface or whatever. Next time i will try the editor,
which looks very helpfull and works very well.
So i gave Dave a phonecall and was recieving a new PIC and DSP in
THREE days ( i live in germany)! What a great service!
And it was fun to open evolver...
Now everything is working fine again.
So, get in contact with Dave, you need a new pic
Stefan

--- In DSI_Evolver@yahoogroups.com, "spectralsequence"
<spectralsequence@c...> wrote:
> Hello, I updated yesterday using the Evolver Editor.
> It is straightforward, quick and efficient.
> During the update, you can see a message "Do not unplug your
> evolver during the update". It seems that it is exactly what you have
> done...
> I would like to add that I am always reluctant to buy music sofware,
> but in the case of this editor the price is not outrageous, although
> not cheap.  It will help me a lot.
> Emmanuel.
> 
> 
> --- In DSI_Evolver@yahoogroups.com, "djchimchim" <djchimchim@h...>
wrote:
Show quoted textHide quoted text
> >      I was unsuccessfully trying to update to 2.0 using midi ox.  
> > Each time the evolver would either drop out of the first 32 step 
> > countdown or it would freeze during it, in which case I would need to 
> > unplug it.  I tried changing the output buffer to 1024/128 and other 
> > settings.  Well Finally it froze again during the 32 countdown but 
> > now when I plug it back in nothing happens, it doesn't load up, no 
> > lights except sometimes the 7 column light comes on.  I'm afraid it 
> > might need to get a new PIC or worse.....I was pretty dead sure that 
> > it wasn't doing a binary countdown when I unplugged it, it would stop 
> > during the 32 step countdown.......anybody got a clue whats up?  Many 
> > thanks...........

Re: [Evolver] Re: updating to 2.0 killed my evolver!

2003-10-26 by bob hanna

I couldn't get MIDI-ox to load the PIC or DSP files to
my Evolver. It would start the count down and freeze
up at 31 every time. I tried several MIDI interfaces
with my PC (MOTU-MTPAV & MPU-401 cable via soundcard)
but no luck with either one. Loading the program files
was a different story. They always loaded successfully
using either of the methods described above.

What finally worked is firing up my old Macintosh and
using a shareware bulk sysex utility along with the
MOTU interface. It worked the first time. Now I'm in
2.0 land :) Sure was a long day getting there.

Yeah, I know...not exactly the fix for those that
don't have a Mac at their disposal. Not sure what it
means when you can load programs but not Pic data
using MIDI-ox.

Anyone???

Bob

P.S. I was using the recommemded output buffers in
MIDI-ox (1024/128)

--- privat_joy <privat_joy@...> wrote:
> Hi,
> maybe the evolver Editor would help the next time,
> but with Midi-OX
> the same thing was happened to me! Evolver was like
> dead, no light was
> flashing during powering up again, nothing! I am
> sure that my evolver
> was connected the whole time during the upgrade
> process, and it didn't
> lost power. So it looks like that maybe there is
> another problem,
> maybe the midi-interface or whatever. Next time i
> will try the editor,
> which looks very helpfull and works very well.
> So i gave Dave a phonecall and was recieving a new
> PIC and DSP in
> THREE days ( i live in germany)! What a great
> service!
> And it was fun to open evolver...
> Now everything is working fine again.
> So, get in contact with Dave, you need a new pic
> Stefan
> 
> --- In DSI_Evolver@yahoogroups.com,
> "spectralsequence"
> <spectralsequence@c...> wrote:
> > Hello, I updated yesterday using the Evolver
> Editor.
> > It is straightforward, quick and efficient.
> > During the update, you can see a message "Do not
> unplug your
> > evolver during the update". It seems that it is
> exactly what you have
> > done...
> > I would like to add that I am always reluctant to
> buy music sofware,
> > but in the case of this editor the price is not
> outrageous, although
> > not cheap.  It will help me a lot.
> > Emmanuel.
> > 
> > 
> > --- In DSI_Evolver@yahoogroups.com, "djchimchim"
> <djchimchim@h...>
> wrote:
> > >      I was unsuccessfully trying to update to
> 2.0 using midi ox.  
> > > Each time the evolver would either drop out of
> the first 32 step 
> > > countdown or it would freeze during it, in which
> case I would need to 
> > > unplug it.  I tried changing the output buffer
> to 1024/128 and other 
> > > settings.  Well Finally it froze again during
> the 32 countdown but 
> > > now when I plug it back in nothing happens, it
> doesn't load up, no 
> > > lights except sometimes the 7 column light comes
> on.  I'm afraid it 
> > > might need to get a new PIC or worse.....I was
> pretty dead sure that 
> > > it wasn't doing a binary countdown when I
> unplugged it, it would stop 
> > > during the 32 step countdown.......anybody got a
> clue whats up?  Many 
> > > thanks...........
> 
> 


__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/

Re: updating to 2.0 killed my evolver!

2003-10-26 by djchimchim

Well, in the documentation it specifically says not to unplug it 
during the binary countdown, which I'm almost certain I didn't do 
because it never made it past the first 32 step countdown.....during 
the 32 countdown the documentation says it is merely recieving and 
checking the sysex and doesn't start overwriting until the binary 
countdown.......so I didn't "exactly" unplug it when it said not 
to..........The evolver editor may be straightforward, quick and 
efficient but that won't do me any good now that the unit won't power 
up.......Regardless of when I unplugged it, my guess is that the PIC 
still got screwed up in which case I will need a 
replacement.........I think the editor looks very useful and i'm sure 
I will get it one day, but one of the reasons I got the evolver was 
to get away from software synthesis 


--- In DSI_Evolver@yahoogroups.com, "spectralsequence" 
<spectralsequence@c...> wrote:
> Hello, I updated yesterday using the Evolver Editor.
> It is straightforward, quick and efficient.
> During the update, you can see a message "Do not unplug your
> evolver during the update". It seems that it is exactly what you 
have
> done...
> I would like to add that I am always reluctant to buy music sofware,
> but in the case of this editor the price is not outrageous, although
> not cheap.  It will help me a lot.
> Emmanuel.
> 
> 
> --- In DSI_Evolver@yahoogroups.com, "djchimchim" <djchimchim@h...> 
wrote:
> >      I was unsuccessfully trying to update to 2.0 using midi ox.  
> > Each time the evolver would either drop out of the first 32 step 
> > countdown or it would freeze during it, in which case I would 
need to 
> > unplug it.  I tried changing the output buffer to 1024/128 and 
other 
> > settings.  Well Finally it froze again during the 32 countdown 
but 
> > now when I plug it back in nothing happens, it doesn't load up, 
no 
> > lights except sometimes the 7 column light comes on.  I'm afraid 
it 
> > might need to get a new PIC or worse.....I was pretty dead sure 
that 
> > it wasn't doing a binary countdown when I unplugged it, it would 
stop 
> > during the 32 step countdown.......anybody got a clue whats up?  
Many 
> > thanks...........

Re: [Evolver] updating to 2.0 killed my evolver!

2003-10-27 by Robert Shanks

Hi -

Email Dave.  He will send you a new PIC chip with instructs on how to put
it in.  The exact same thing happened to me (and I was a synth tech for 10
years!).  Where are you?  If you're near by (Raleigh, NC) I'll help you do
it.  If not I can talk/email you through it.

Cheers - Robert
Show quoted textHide quoted text
>     I was unsuccessfully trying to update to 2.0 using midi ox.
>Each time the evolver would either drop out of the first 32 step
>countdown or it would freeze during it, in which case I would need to
>unplug it.  I tried changing the output buffer to 1024/128 and other
>settings.  Well Finally it froze again during the 32 countdown but
>now when I plug it back in nothing happens, it doesn't load up, no
>lights except sometimes the 7 column light comes on.  I'm afraid it
>might need to get a new PIC or worse.....I was pretty dead sure that
>it wasn't doing a binary countdown when I unplugged it, it would stop
>during the 32 step countdown.......anybody got a clue whats up?  Many
>thanks...........
>
>
>
>To unsubscribe from this group, send an email to:
>DSI_Evolver-unsubscribe@yahoogroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Re: [Evolver] Re: updating to 2.0 killed my evolver!

2003-10-27 by mr julian

From: "bob hanna" <bobhanna@...>

> I couldn't get MIDI-ox to load the PIC or DSP files to
> my Evolver. It would start the count down and freeze
> up at 31 every time.

you need to set the buffers in MIDI-ox to get the sysex updates to go to the
evolver..... voice dumps from MIDI-ox work fine, because they're relatively
small, but as you can probably imagine, the file size of the evolver OS, or
the evolver DSP code is actually quite a bit larger than your standard SYSEX
dump.




julian

[Evolver] Re: updating to 2.0 killed my evolver!

2003-10-27 by privat_joy

Hi,
i am sure that most of us done this. I was setting the buffers exactly
how mentioned EX5Tech-Forum from ski! Also i have to say that Evolver
isn't very lonely at my home and there are some other Manufactors
which update their products.
This no critic against evolver or Dave, which are, like i mentioned
fantastic and Dave gave me a great support.
I am only wondering if there could be another problem, maybe with
older builds (my Evo is serial # 50) or the PIC's itselves, or some
Midi-Interfaces (i used RME Multiface), because there are quiet a lot
of people which had an damaged PIC after upgrade.
So we should search and help Dave to find out what's wrong...
Stefan


--- In DSI_Evolver@yahoogroups.com, "mr julian" <jujulilianan@f...> wrote:
> From: "bob hanna" <bobhanna@y...>
> 
> > I couldn't get MIDI-ox to load the PIC or DSP files to
> > my Evolver. It would start the count down and freeze
> > up at 31 every time.
> 
> you need to set the buffers in MIDI-ox to get the sysex updates to
go to the
> evolver..... voice dumps from MIDI-ox work fine, because they're
relatively
> small, but as you can probably imagine, the file size of the evolver
OS, or
> the evolver DSP code is actually quite a bit larger than your
standard SYSEX
Show quoted textHide quoted text
> dump.
> 
> 
> 
> 
> julian

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.