Prophets in peril! First run of Prophet-5 and Prophet-10 has a flaw says Sequential
Dave Smith has discovered a problem with some of the first batch of the new Rev4 Prophet synthesizers but says they can fix it or replace it for you to make it right.
Loss of high end
As synthesizer enthusiasts have been receiving their fabulously new Prophet-5s and Prophet-10s there’s been some concerns that something isn’t quite right when compared to the originals. A few users have been expressing their concerns to Dave Smith which has been documented in a thread on the Gearslutz forum. The gist of the problem is that there’s something wrong with the high-end frequencies. It’s not something you would necessarily notice in YouTube demos or if you weren’t personally acquainted with the original instrument – but it’s there, or rather not there.
Dave was quick to respond:
“As some users have noticed, there is a drop in high frequencies on the current units in the field. I checked into it yesterday, and I’m highly embarrassed to say that we screwed up. Short story is there are some capacitors that were not meant to be installed, but did in fact get installed, causing the frequency drop.
Yikes! Dave said that his ears have taken so much abuse at concerts over the years that he just can’t hear that high anymore and so didn’t notice the error. It sounded great to him!
Saved by whatever it takes
Obviously, Dave is mortified but their investigation has revealed that it’s only two capacitors that are getting in the way of those dog-whistle frequencies. He says that you can simply desolder them and the job is done. This may be asking a lot of users who have paid so much money for a premium instrument and so he’s also happy to replace the circuit board or the entire synth if that’s what it takes to get it fixed and restore the faith of the user.
This affects serial numbers 1 to 195 on Prophet 5s, and 1 to 159 on Prophet 10s.
I owe everyone a deep apology for this; it’s not how we normally work, and I’m really sorry this fell through the cracks. Thank you for your understanding.
The full details are contained in this post on the forum.
The originator of the discussion “cbmd” also posted some pictures of the offending capacitors. They are surface mount components which makes it that little bit trickier.
Prophet-5 PCB
I can’t confirm whether this image is accurate so your best bet if you have one of the Prophets with a problem, is to talk to Sequential directly.
I can only imagine the disappointment early owners must be feeling and it’s one of those things that plenty of people wouldn’t have noticed but, of course, once you know then it has to be fixed. Just goes to show that manufacturing errors can happen to anyone. Massive respect to Dave Smith for offering to do what it takes to sort it out.
More information
- Prophet-5 PCB: https://www.gearslutz.com/board/showpost.php?p=15068302&postcount=1275
This might also interest you
10 responses to “Prophets in peril! First run of Prophet-5 and Prophet-10 has a flaw says Sequential”
Just growing pains. It’ll be fine in the log run. Glad I didn’t get one of the very first production units.
Spoke to Sequential and its not even the full first batch. Just some of the eariler units already shipped. My pro-10 on order is from the same batch but ok. They listed the serial numbers affected.
I bet that’s a relief for you! The serials are listed in the article.
These guys can’t release a product without problems. Tempest, Pro2, OB6, now this.
Does this new prophet have a mono out?
Yes
The originator is actually someone called “javd007” – an owner of a Rev 3.2 Prophet 5, who noticed, by comparison, that the high end was missing from their new Rev 4 Prophet 5.
“Cbmd” appears to be a DSI / Sequential engineer who gets involved in the discussion at a later stage, along with another DSI engineer.
Aside from the subject matter – which is quite a compelling read anyway – this GS thread offers a fascinating insight into how people get treated on forums like this, for raising a perfectly valid issue, yet at the same time risk being mocked by ‘fanboy’ mentality for daring to speak out about such a revered company’s new product.
The manner in which many forum members dismissed the originators’ revelations as “user error”, evident in part by the way they sycophantically ‘like’ every comment made by the DSI engineers – who initially appear to suggest this could be the case – is really quite fascinating and would serve as a thought-provoking article in human psychology!
The only DSI engineer who comes across as having any sort of modesty here, is Dave Smith himself – whose apology appears genuine and heartfelt. The other engineers involved in the discussion did, for me at least, come across a little disparaging – which helped to fuel the frenzy of hostility towards the poor, brave originator of the discussion!!
Great comment and insight, thank you.
As usual, the story is not that simple. javd007 surely deserves credit. However, he was also rude and obnoxious in the process, and managed to accuse Sequential of being corporate and not caring about their customers.
“managed to accuse Sequential of being corporate and not caring about their customers.”
In my experience, this is quite accurate. I started off as a fan of this company but have had a string of horrid experiences over the years (fool my twice, I know). I wouldn’t recommend it, but you can go back to the Tempest forums and see evidence of users begging for bug fixes and promised features for years. Even Roger Linn had to get involved to actually push DSI to do something about it. CMDB and PIM have been talking down to users with legitimate concerns for years.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information