Sequential circuits samplers group photo

Yahoo Groups archive

Sequential circuits samplers

Index last updated: 2026-04-28 23:40 UTC

Thread

P3k SCSI info

P3k SCSI info

2003-02-26 by Gerard FINK

info from Wyne Country    :


The Prophet 3000 cannot interface with a zip drive.. it requires a fixed
media drive no larger than 150 meg.  The hard disk drive must be APPLE
system
7 or lower compatible... meaning the drive must first be formatted with an
Apple computer using OS version 7 or lower.  At that point, the Prophet 3000
can initialize the HD for its own use... a 150 Meg drive provides about 70
files.. each file representing 2 meg of memory storage (one machine's
image).
 We can provide a similar HD system tested with a Prophet 3000 for $198.

RE: [prophet2000] P3k SCSI info

2003-02-26 by Brigman, Corley

>The Prophet 3000 cannot interface with a zip drive.. it requires a fixed
>media drive no larger than 150 meg. 

the rest is true, but this is not... i have used 200 meg syquest drives
with no problem (50 4-meg banks saveable) under 3.0B...

still have my syquest 88 available...

corley brigman
intel corp.
corley.brigman@...

Re: P3k SCSI info

2003-03-04 by sad_pierrot <sad_pierrot@yahoo.com>

ok, then i have another question for you guys:

"The only other item we would recommend for your Prophet 3000 is 
Operating 
System software disk WCP 1.6B SCSI for $19.98.  This is the last OS 
release 
for the Prophet 3000, and includes all known bug fixes as well as 
Sample Dump 
Standard and SCSI Hard Disk Drive capability."


is this disk just bogus or what?  i dont understand what exactly it 
is, or why it would be needed if the p3k can use scsi drives under OS 
3.0B.  and why are they saying its the last OS release if it's an 
earlier version than 3.0B ??    



--- In prophet2000@yahoogroups.com, "Brigman, Corley" 
<corley.brigman@i...> wrote:
> >The Prophet 3000 cannot interface with a zip drive.. it requires a 
fixed
> >media drive no larger than 150 meg. 
> 
> the rest is true, but this is not... i have used 200 meg syquest 
drives
Show quoted textHide quoted text
> with no problem (50 4-meg banks saveable) under 3.0B...
> 
> still have my syquest 88 available...
> 
> corley brigman
> intel corp.
> corley.brigman@i...

RE: [prophet2000] Re: P3k SCSI info

2003-03-04 by Brigman, Corley

>is this disk just bogus or what?  i dont understand what exactly it 
>is, or why it would be needed if the p3k can use scsi drives under OS 
>3.0B.  and why are they saying its the last OS release if it's an 
>earlier version than 3.0B ??    

ok, the gossip begins ;)

i only heard about all this AFTER i bought my P3000, had been using
it, and had posted 3.0B on the web. and i never talked to them myself.
but... there are some reports that 3.0B doesn't work as well on
a rev A P3000 (or should i say, rev 1... i am not 100% sure which it is).
so one guy had talked to them, thinking their 1.6A might work.

wine country told him some sob story about how someone had
stolen the source code to THEIR work, and that really 3.0B
was basically a 'pirate' product. and that their 1.6 was the
'real thing'. apparently they DO have the source code for it
at least. it's what i heard, but i never checked up on it. 

i do not know where 3.0 really came from, or who worked on it,
or if it was done at wine country or elsewhere, it really is
shrouded in a sort of mystery.  i DO know that
the person i bought my P3000 from originally was an ex-sequential
employee (he wrote the auto-pitch-finder and the auto-looper
in the P3000 OS - cool!), and he was the one who gave me 3.0,
so apparently he didn't care. if he didn't care, without knowing
more data, i don't see any problems.

like i said though, not all P3000s can run 3.0B and be stable, from
what a few people have told me. then the wine country OS will be what
you need. 

if someone from wine country is on this list (doubtful) maybe they
can set the record straight. 

corley brigman
intel corp.
corley.brigman@...

Re: P3k SCSI info

2003-03-04 by sad_pierrot <sad_pierrot@yahoo.com>

well, that's certainly intriguing..  i've actually opened my p3k up 
to have a look inside, and the revisions are in fact A or B and even 
C for some boards, apparently.  mine is revision B, and this i guess 
is a main determining factor for whether or not it can be upgraded to 
a 4 MB version.  however, i was using os 3.0b and did have a few 
crashes with the OS, basically freezing up on me when i'd do things a 
particular way, so i'm not sure what the deal is.  i might just get a 
copy of their OS to see if it makes any difference.  anyhow, i 
appreciate your info, very interesting!


--- In prophet2000@yahoogroups.com, "Brigman, Corley" 
<corley.brigman@i...> wrote:
> >is this disk just bogus or what?  i dont understand what exactly 
it 
> >is, or why it would be needed if the p3k can use scsi drives under 
OS 
> >3.0B.  and why are they saying its the last OS release if it's an 
> >earlier version than 3.0B ??    
> 
> ok, the gossip begins ;)
> 
> i only heard about all this AFTER i bought my P3000, had been using
> it, and had posted 3.0B on the web. and i never talked to them 
myself.
> but... there are some reports that 3.0B doesn't work as well on
> a rev A P3000 (or should i say, rev 1... i am not 100% sure which 
it is).
> so one guy had talked to them, thinking their 1.6A might work.
> 
> wine country told him some sob story about how someone had
> stolen the source code to THEIR work, and that really 3.0B
> was basically a 'pirate' product. and that their 1.6 was the
> 'real thing'. apparently they DO have the source code for it
> at least. it's what i heard, but i never checked up on it. 
> 
> i do not know where 3.0 really came from, or who worked on it,
> or if it was done at wine country or elsewhere, it really is
> shrouded in a sort of mystery.  i DO know that
> the person i bought my P3000 from originally was an ex-sequential
> employee (he wrote the auto-pitch-finder and the auto-looper
> in the P3000 OS - cool!), and he was the one who gave me 3.0,
> so apparently he didn't care. if he didn't care, without knowing
> more data, i don't see any problems.
> 
> like i said though, not all P3000s can run 3.0B and be stable, from
> what a few people have told me. then the wine country OS will be 
what
Show quoted textHide quoted text
> you need. 
> 
> if someone from wine country is on this list (doubtful) maybe they
> can set the record straight. 
> 
> corley brigman
> intel corp.
> corley.brigman@i...

RE: [prophet2000] Re: P3k SCSI info

2003-03-04 by Brigman, Corley

>well, that's certainly intriguing..  i've actually opened my p3k up 
>to have a look inside, and the revisions are in fact A or B and even 
>C for some boards, apparently.  mine is revision B, and this i guess 
>is a main determining factor for whether or not it can be upgraded to 
>a 4 MB version. 

yes, if you have a rev B the upgrade from 2M to 4M is 'trivial',
very simple to do. the key is the I-627 chip, it must say 'I-627B'.

> however, i was using os 3.0b and did have a few 
>crashes with the OS, basically freezing up on me when i'd do things a 
>particular way, so i'm not sure what the deal is.  

the P3K OS is, in a sense, beta. and doesn't have very good error
recovery. meaning: as long as you don't do anything wrong, it always
worked fine for me. but it won't try to catch if you do something
wrong, and i've gotten weird results (including crashes) when i tried
to do something 'illegal'; it's been a while, but for instance once
a sample had its sloop set to the entire sample (0...length of sample),
and the rloop set off. i forgot and went to set up the rloop, and when
i tried to change the start/end, i got really strange results, and no
error messages. but as long as you're careful, i didn't have any problems.

there are some weirdnesses i discovered though, that i'm not sure if
they were just my machine or not. one particularly galling one was that
if you are in mode 3, and assign pitchbend to pitch like normal, it works
fine on all 8 voices. but if you go to mode 4 (multi, i think that's right?),
the pitchbend only works on voice 1 (even if say voices 1-3 were all assigned
to the same midi channel, only voice 1 would respond to pitchbend, so it wasn't
like 'only the first multi part' or anything like that). 

but it's still an incredible sounding machine; i wish i had mine back.
i'm not sure i'm not still too lazy to really use it ;) but it is
the best sounding sampler i've heard so far...

corley brigman
intel corp.
corley.brigman@...

Re: P3k SCSI info

2003-03-05 by sad_pierrot

One of the weird things mine would do is not be able to save or load 
data properly, if i made several copies of sections of a sample--for 
instance, if i sampled a few seconds of a breakbeat from a record, 
then chopped it up in the sampler into its constituent parts (by 
setting start and end points for the first drum tone then copying the 
sample and setting the start and end of that one so it was the second 
drum tone in the break, and so on...).  then i could stick all the 
parts back into one patch, all layed out on my keyboard/sequencer in 
order, and at that point delete all the duplicates.    but when i'd 
try to save this kind of patch, it would apparently think it was 
using way more memory than it actually was (since each drum tone was 
basically coming from the same initial sample, and all the duplicates 
had been erased).  so it would still work, i could still save and 
load it, but it would get progressively screwier every time i'd make 
adjustments and save it, until after awhile it'd start freezing up on 
me.  those were the only times data would never be correctly verified 
after loading.  i figured it was just the tricky sort of method i was 
using to edit samples that was messing with the sampler and causing 
errors.

i agree though, it's a great sounding machine, has really nice 
modulation capabilities.  i do however, dislike the filter on it, 
because its the kind of filter that thins out the audio below the 
resonance peak, more and more, the higher the resonance is..  so 
anything being filtered with any fair amount of resonance ends up 
much lower in overall volume than everything else coming out of the 
sampler.  a lot of filters are like that though i guess, so i 
shouldn't complain. 





 


--- In prophet2000@yahoogroups.com, "Brigman, Corley" 
<corley.brigman@i...> wrote:
> >well, that's certainly intriguing..  i've actually opened my p3k 
up 
> >to have a look inside, and the revisions are in fact A or B and 
even 
> >C for some boards, apparently.  mine is revision B, and this i 
guess 
> >is a main determining factor for whether or not it can be upgraded 
to 
> >a 4 MB version. 
> 
> yes, if you have a rev B the upgrade from 2M to 4M is 'trivial',
> very simple to do. the key is the I-627 chip, it must say 'I-627B'.
> 
> > however, i was using os 3.0b and did have a few 
> >crashes with the OS, basically freezing up on me when i'd do 
things a 
> >particular way, so i'm not sure what the deal is.  
> 
> the P3K OS is, in a sense, beta. and doesn't have very good error
> recovery. meaning: as long as you don't do anything wrong, it always
> worked fine for me. but it won't try to catch if you do something
> wrong, and i've gotten weird results (including crashes) when i 
tried
> to do something 'illegal'; it's been a while, but for instance once
> a sample had its sloop set to the entire sample (0...length of 
sample),
> and the rloop set off. i forgot and went to set up the rloop, and 
when
> i tried to change the start/end, i got really strange results, and 
no
> error messages. but as long as you're careful, i didn't have any 
problems.
> 
> there are some weirdnesses i discovered though, that i'm not sure if
> they were just my machine or not. one particularly galling one was 
that
> if you are in mode 3, and assign pitchbend to pitch like normal, it 
works
> fine on all 8 voices. but if you go to mode 4 (multi, i think 
that's right?),
> the pitchbend only works on voice 1 (even if say voices 1-3 were 
all assigned
> to the same midi channel, only voice 1 would respond to pitchbend, 
so it wasn't
> like 'only the first multi part' or anything like that). 
> 
> but it's still an incredible sounding machine; i wish i had mine 
back.
Show quoted textHide quoted text
> i'm not sure i'm not still too lazy to really use it ;) but it is
> the best sounding sampler i've heard so far...
> 
> corley brigman
> intel corp.
> corley.brigman@i...

RE: [prophet2000] Re: P3k SCSI info

2003-03-05 by Brigman, Corley

>...then i could stick all the 
>parts back into one patch, all layed out on my keyboard/sequencer in 
>order, and at that point delete all the duplicates.  
>...i figured it was just the tricky sort of method i was 
>using to edit samples that was messing with the sampler and causing 
>errors.

quite possibly. depends on what you are doing... when you do
'copy sample', afaik it doesn't actually create a new sample,
just a new pointer to the old one (pretty clever, but...) however
i doubt that in 1988 they took into account what you were trying
to do; it's more designed to use the same sample sets with different
analog parameters (which does work well). 

especially, if you optimized the memory like this... who knows
what it would do? if you had a sample _begin A B C D end_ where
ABCD were points in the sample, and patch 1 set begin/end to
A B, and patch 2 set begin/end to C D, instead of doing it 
'properly' it might have trimmed it to just A and B, with weird
results after that. who knows. 

it seems though that for things that work properly, they always
work properly (never saw a 'random' type crash), and things that
don't are easy to find out :) 

i like the filters myself :) but i know what you mean...

corley brigman
intel corp.
corley.brigman@intel.com

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.