Starting work on a documentary project that will heavily feature the PX.
I love synths. I love destroyed robot sounds and squashed, dystopian percussion. Lets get that out of the way
But the Prophet X made a lot of sense to me because a lot of times I also need some sounds like these. Using it as a bog standard “Rompler” was an intended use-case from jump.
I get pretty serious option paralysis so there was something appealing about having and using only whats onboard the PX when I wanted these more pedestrian “real instrument” type sounds. No giant libraries to download and update, etc.
Also every simple sound is only a few tweaks from mayhem, which I just love.
I will say, just to add balance to the conversation, the ongoing “Bricking” issues give me some cause for concern about the longevity of the PX.
There’s always a vocal minority when issues pop up, but I’ve seen a disproportionally large percent of people who’s PX journeys I followed pre issues, end up with issues.
If its just a battery swap and maybe some light firmware re-flashing, that’s one thing, but with the unit no longer officially in production, I’m not sure how long I could count on any kind of sustained support or hand holding through a fix.
My experience with Sequential’s tech support has been top notch on several issues big and small: very detailed, very responsive, their attention never flagged, etc.
Yeah I just got confirmation on that. I was mistaken. They are still in production.
And yeah, I’ve gotten great service from them on my Rev2. I mentioned being decently handy so instead of having to ship the entire synth back and forth, they just sent me a new board to install. Worked great and I sent back the old one.
I guess I don’t have much reason to worry.
I’ll be real about it. I’m going through a kind of reckoning with my gear. I’m taking the whole year to assess what I have and what I’ll keep.
I still feel like there is a lot of crossover between the PX and P6 and I don’t think I want both. So little things like these software issues have been weighing on my mind when it comes to long term ownership.
I don’t have a ton of other pieces, so maybe in the end I decide two prophets is fine heh. It’s tough on the muscle memory though, switching back and forth. The custom knobs were an attempt to smooth that process and make them feel even further apart.
I have the Prophet 10 and the Prophet X, not too much cross over as they are quite different in synthesis.
If anything, the prophet 5/10 sounds closest to the OBX8 (minus stereo stuff). Since the PX uses samples + subtractive synthesis, the only comparisions are the Iridium and the Quantum. I can’t think of any other hardware that can do that.
At least on the Prophet X itself, this is not possible.
The SoundTower Editor can do some “genetics” stuff with patches, so maybe it would be possible through that (no idea, I don’t have any use for it). It doesn’t seem to be a standard feature of the patch management portion on there either.
You could probably dump the patches and manually change things around the data to get this functionality.
I got my Prophet X last night… I’ve had it for little over 24 hours and I love this thing already… it feels like all my to-ing and fro-ing over the last few years with lots of different polys has finally got me to the right one.
Obviously it’s the honeymoon phase for me, but I come to it on the back of owning the Rev2, Prophet 6, Prophet 12, Pro 2 and Pro 3 SE, so it feels instantly familiar.
It’s weird how I never really considered the P-X up until recently, I never thought it was for me… until I spent the first 10 minutes on it.
I’ve spent some time reading back in this thread to get up to speed on the PX (great work @philroyjenkins btw ) and I haven’t read much on user sample implementation… are there any good tutorials or resources covering this?
Thanks for the links… I was just looking for instructions for how I sample my Analog Four and get those files into the PX… Mapping Utility seems to be the way then? My Macbook isn’t letting me open it though;
’ “Mapping Utility” cannot be opened because the developer cannot be verified.’
I grabbed the Model D and Prophet 5 sample packs from 8DIO today too… really good… I’m amazed how great a workstation the PX seems to be.
I’ve had my Prophet 12 out alongside it today… first thing that struck me is how lush the PX’s stereo filter is compared to the P12. There are a lot of nervous looking synths in my studio at the moment…
I’ll keep digging, I thought this is what I did… I’ve got a feeling that my PX only sees new imports for empty slots at the moment.
This is really rough and I’m just playing it live, no sequencing (which will be obvs ), but this is a sound I’ve just been working on from samples imported from my A4 mk2… so the PX lets me play it poly too.
I think you should delete the old samplebank first ( in the px menu), before you import the new samples. (I once managed to have two samples per number after importing new ones over old ones)
The px should always recognize new samples on the usb stick. (if it fails, plug the usb stick in after you turn it on, or turn it on and off again
Do you have a notename or number in the filename or metadata?
Px toolkit searches for rootnote in the wav metadata and in the filename and places them accordingly.
Shift and ctrl alters that behavior (look it up in the px toolkit manual)
The px also recognizes looppoints in the metadata.
Also don’t forget to download the vco pack, it is great.
Sequential forum has some more info.
When I finally get my own user samples organized and uploaded, I will drop a link here.
) and I haven’t read much on user sample implementation… are there any good tutorials or resources covering this?
)
), but this is a sound I’ve just been working on from samples imported from my A4 mk2… so the PX lets me play it poly too.