The Official Sequential/Oberheim Forum
SEQUENTIAL/DSI => Prophet => Sequential Prophet X => Topic started by: REwire on December 27, 2018, 09:16:15 PM
-
I have been using the 8DIO sample loader fine for a week and loaded about 4 soundsets onto the PX with success and played them fine.
Tonight I added 4 more soundsets and they loaded from USB to the PX fine but when I restarted the PX it is frozen with the startup bar at maximum and frozen. I have restarted it a few times and it won't get past that screen.
How do I get this running again? Hope I don't have to lose all my patches in the process if it needs a factory reset. The Last Prophet is in there too.
Edit: I did submit a support ticket but also realized the last update I did to the PX was PxUpdate_V1.2.2.0.1.
Well, can't update now its frozen :-\
Dan
-
I have been using the 8DIO sample loader fine for a week and loaded about 4 soundsets onto the PX with success and played them fine.
Tonight I added 4 more soundsets and they loaded from USB to the PX fine but when I restarted the PX it is frozen with the startup bar at maximum and frozen. I have restarted it a few times and it won't get past that screen.
How do I get this running again? Hope I don't have to lose all my patches in the process if it needs a factory reset. The Last Prophet is in there too.
Edit: I did submit a support ticket but also realized the last update I did to the PX was PxUpdate_V1.2.2.0.1.
Well, can't update now its frozen :-\
Dan
I know they have a way to update from the bootloader with a combo keypress at startup. A few people here with early units had issues resolved by this,but I can't remember the steps. I bet one of the early posts in here have details. Otherwise DSI support should be able to help.
-
I know they have a way to update from the bootloader with a combo keypress at startup. A few people here with early units had issues resolved by this,but I can't remember the steps. I bet one of the early posts in here have details. Otherwise DSI support should be able to help.
Carson has emailed me bootloader OS and then FPGA and nothing has unbricked it yet.
-
Hi,
Same to me.....but on a Pc.
Freezed at the maximum.
I'm waiting for an answer from Sequential....
-
Same problem for me...
I'm waiting for an answer and can't use the Prophet X...
-
Mine is bricked as well after loading user samples !!!! Not Happy
Ive raised a ticket.
instagram.com/synthjam (http://instagram.com/synthjam)
-
I have notified 8DIO as well ... their email to contact is support@8dio.com
-
I have notified 8DIO as well ... their email to contact is support@8dio.com
And according to what you said on Gearslutz, 8DIO has already responded that it's DSI's PX software that's the issue?
-
Yep that was after i posted here ... shooting at it from all angles ....
-
I’ll hold off attempting it until this is resolved.
-
Sequential contact me this night for informationa....
I must wait for the answer.
Holidays are over.....
I hope the best for people like me....with a freeze Prophet.....
I can't wait to fix everything.
So frustrated....
-
OK ATTENTION !!!
Everyone who has a bricked PX please also raise a ticket with 8Dio or chat with them on their site chat, they've told me I'm the only person to have raised the issue with them, I feel its to do with the sample import as only users that have used this are the ones who have bricked machines. So thats why i've been in contact with them. but the more info they have the better picture they will have as to what is happening. 8Dio have been very responsive but we are still without a solution
Still not heard a peep from DSI Seq
-
You're right.
I've done it.
Many thanks Man!
-
I’ll hold off attempting it until this is resolved.
Indeed
-
Something must be lost in communication because Sequential literally just did a video showing how to do sample import. This will get worked out soon enough. Remember guys it's Jan 3. Most businesses don't open up shop again until the 7th. Give Dave and company some time to enjoy themselves. The PX's will be fixed and the sample import will work and the BETA software will turn into official software with more features. Just got to have patience.
-
Something must be lost in communication because Sequential literally just did a video showing how to do sample import. This will get worked out soon enough. Remember guys it's Jan 3. Most businesses don't open up shop again until the 7th. Give Dave and company some time to enjoy themselves. The PX's will be fixed and the sample import will work and the BETA software will turn into official software with more features. Just got to have patience.
I take it you haven't got a bricked PX that you've paid thousands for that is just sat there?
-
I take it you haven't got a bricked PX that you've paid thousands for that is just sat there?
I understand this is hard and you feel anxious. From my years of experience with DSI/Sequential support, everything is going to get sorted out. What I think the _worst_ case for you might be they have to mail you an internal board that you swap. Worst case. That's my own personal worst case scenario for you. Hopefully they can fix it remote.
Unfortunately, you've fallen victim to having the very small company out of the office for year end vacation. But once they get caught up, your issue will be handled.
I hope that helps. I'm just a dude on the internet, but I've dealt with these guys for years now.
-
DSI is going to send me a new hard drive to swap. I sent them the last sample ZIPs that I uploaded to the PX that bricked it and they loaded and booted up fine on the DSI shop PX
Whether this is a hardware or hard drive issue will certainly be tested in the next week as I'll upload those same samples the second the PX turns on successfully (if it does).
Dan
-
Something must be lost in communication because Sequential literally just did a video showing how to do sample import. This will get worked out soon enough. Remember guys it's Jan 3. Most businesses don't open up shop again until the 7th. Give Dave and company some time to enjoy themselves. The PX's will be fixed and the sample import will work and the BETA software will turn into official software with more features. Just got to have patience.
I take it you haven't got a bricked PX that you've paid thousands for that is just sat there?
No but I've experienced something similar with my P6 and a faulty board that needed to be replaced. What did I do? Played my other instruments while it was in the shop. Sequential isn't going to dismiss you or what's happening, they are good people and you are in good hands.
-
I can only echo that sentiment. They care a great deal about their customers and getting things right, so rest assured they’ll take care of this. I know it’s frustrating to be without in the meantime.
-
Well i've had contact from DSI, they've asked me to try the OS from boot loader mode if that doesn't work to try the FPGA file they've sent. I'm not holding out much hope that will fix it as others have tried this to no avail ... will report back in a bit ...
-
Well as I suspected it didn't work ...
-
What can I say (while thinking back to the Tempest sample import soap opera) ... I'm glad I did not buy a PX yet... it also underlines what I've always been saying regarding DSI/Sequential devices... WAIT buying until you absolutely know what you get from the get go, and what is "promised" down the road... if you purchase with "down the road" in mind, you might get burned... you'll have to live in Limbo while you wait on either a fix or a "expected behavior" or "low bug visibility" statement... this is not to piss anyone off, I'm just stating the obvious.
-
What can I say (while thinking back to the Tempest sample import soap opera) ... I'm glad I did not buy a PX yet... it also underlines what I've always been saying regarding DSI/Sequential devices... WAIT buying until you absolutely know what you get from the get go, and what is "promised" down the road... if you purchase with "down the road" in mind, you might get burned... you'll have to live in Limbo while you wait on either a fix or a "expected behavior" or "low bug visibility" statement... this is not to piss anyone off, I'm just stating the obvious.
True... and let's also remember that bricked machines (unless I've missed something) are all the result of people using the Beta software.
The vast majority of owners have had zero issues -- even many using the Beta software. [insert conversation about two subsets using the exact same tools, PX and beta software, and getting different results -- logically, statistically, user error has to be considered as a reason].
My PX works as advertised by DSI/Sequential. I downloaded and installed the "Last Prophet" Add-On -- no issues there either.
I feel bad for the folks with bricked machines. But it's a bit unfair to start bashing Sequential over the holiday season for a mistake of Beta software.
-
What can I say (while thinking back to the Tempest sample import soap opera) ... I'm glad I did not buy a PX yet... it also underlines what I've always been saying regarding DSI/Sequential devices... WAIT buying until you absolutely know what you get from the get go, and what is "promised" down the road... if you purchase with "down the road" in mind, you might get burned... you'll have to live in Limbo while you wait on either a fix or a "expected behavior" or "low bug visibility" statement... this is not to piss anyone off, I'm just stating the obvious.
True... and let's also remember that bricked machines (unless I've missed something) are all the result of people using the Beta software.
The vast majority of owners have had zero issues -- even many using the Beta software. [insert conversation about two subsets using the exact same tools, PX and beta software, and getting different results -- logically, statistically, user error has to be considered as a reason].
My PX works as advertised by DSI/Sequential. I downloaded and installed the "Last Prophet" Add-On -- no issues there either.
I feel bad for the folks with bricked machines. But it's a bit unfair to start bashing Sequential over the holiday season for a mistake of Beta software.
The problem here is both 8DIO and DSI deny there's any problem with the Beta Software. I sent DSI my USB Drive contents that I uploaded to cause my bricking. It was sampling before that just crashed on a new batch of samples I edited. DSI says it all loaded into the shop PX without issues.
So all signs point to the PX OS processing these samples.
It's unacceptable that naming or numbering errors can brick any synth. They need to revise the OS to halt any formatting errors before they load into the machine and not let them upload and freeze when restarting.
Sample loading is hardly new tech, I was sending sample sets via SCSI to my EMU ESI-32 in 1993. That ever crash? NO
-
DSI is going to send me a new hard drive to swap.
and....
The problem here is both 8DIO and DSI deny there's any problem with the Beta Software.
Sorry, but these statements seem inconsistent. DSI has both denied that there's any problem and provided you a solution by sending you a new hard drive?
Regardless, I'm sure they will get it fixed and get you back to making music again.
-
DSI is going to send me a new hard drive to swap.
and....
The problem here is both 8DIO and DSI deny there's any problem with the Beta Software.
Sorry, but these statements seem inconsistent. DSI has both denied that there's any problem and provided you a solution by sending you a new hard drive?
Regardless, I'm sure they will get it fixed and get you back to making music again.
They are inconsistent because I have not received the hard drive yet so can't retry sample loading and DSI haven't gotten my old drive back to analyze what crashed. If the same set of user samples crashed one machine and not another what does one make of that?
Warning that user samples must be exactly named, numbered and formatted is ludicrous as I've loaded bad files to samplers hundreds of times and they just give error messages and skip, not kill the machine.
-
In France, 2 people than I know and I also have a planted Px .... I'm waiting a SSD from Sequential by the middle of next week....
-
What can I say (while thinking back to the Tempest sample import soap opera) ... I'm glad I did not buy a PX yet... it also underlines what I've always been saying regarding DSI/Sequential devices... WAIT buying until you absolutely know what you get from the get go, and what is "promised" down the road... if you purchase with "down the road" in mind, you might get burned... you'll have to live in Limbo while you wait on either a fix or a "expected behavior" or "low bug visibility" statement... this is not to piss anyone off, I'm just stating the obvious.
True... and let's also remember that bricked machines (unless I've missed something) are all the result of people using the Beta software.
The vast majority of owners have had zero issues -- even many using the Beta software. [insert conversation about two subsets using the exact same tools, PX and beta software, and getting different results -- logically, statistically, user error has to be considered as a reason].
My PX works as advertised by DSI/Sequential. I downloaded and installed the "Last Prophet" Add-On -- no issues there either.
I feel bad for the folks with bricked machines. But it's a bit unfair to start bashing Sequential over the holiday season for a mistake of Beta software.
My problem with this thing is that Sequential once again decided to "outsource" the software/sample part of a device to a third party company... I'm not sure I can say that Sequential should be forgiven for this, and either not for accepting a release of a beta right before their holidays... they SHOULD know that as soon as that software got out, users would throw themselves at it, as this is what probably made them buy the darn thing in the first place... I'm not willing to give the blame to the users of a beta for being impatient... simply because i feel that Sequential should have made that software themselves, and they should have had it ready when they launched the PX, fully tested! ... what they've done (again) is to launch something unfinished, and then "throw the dice" that everything turns out right... and now, for the second time (Tempest was the first), that proves not to be the case.
I'm sure that they'll fix it... and probably fast and elegant, but I can certainly not see why users do not have the right to be pissed, that they are now sitting here, waiting for a fix, with a bricked 3000 dollar machine... if quality testing had been done before launch, and the software was finished from the get go, this would probably not even have happened.
I'd be pissed if I had gotten a bricked PX too... and I would certainly not feel ashamed of being pissed knowing that it's bricked because Sequential obviously did not want to do the software themselves and proper quality testing. I would have expected of them to have learned from the Tempest farce.
-
If I was in Sequential’s shoes I’d be very tired of people talking about the mythical user sample support on the Tempest. To the best of my knowledge they never indicated that it would happen, and it didn’t. I’ve asked on several forums if anyone has a shred of evidence otherwise, and the answer is always no.
The situation for Prophet X owners who are currently affected is very unfortunate and I hope it gets resolved quickly. I also have no doubt that it will be, and that the solution will be no more complex than a SysEx delivered OS update via the bootloader. The hard part is determining the exact nature of the problem and having a high-confidence fix to roll out.
I do completely agree that the Prophet X itself should be validating everything it loads. Relying on external software to format everything correctly 100% of the time, and on users not to tinker with the result in an in unsupported way is asking for trouble.
-
what they've done (again) is to launch something unfinished
And there was not only the history of the Tempest ...
The first series (Not PE) of Prophet 8, monoevolver, polyevolver with the problems of knobs ...
At the time, I was a seller in a music store, we had stopped in order, too much after-sales service problem.
Between this, the Tempest and now this PX, it is shameful to treat customers who pay expensive equipment and who serve beta tester.
Just to sell the equipment as quickly as possible without it being perfectly checked, perfectly controlled and try to win money quick, quick, quick.
I really love the Prophet X (when it does not freeze ...) but finaly, they should have waited to perfectly check everything before going out even if it cost them more expensive ... And even more with their 8dio partnership...
-
I think from all the comments here about the sample related issue is that whoever allowed the release of the beta compiler before a major holiday period, where support would be off line, should really be brought too account. Clearly the compiler was late, unfinished, unpolished whatever BUT you just do not release this type of product in such away and at such a time. I come from a software / operating system development back and you would never, never, nerver do such a thing without having all the support and contingency inplace (whether you were a big or small company.). The PX for all of us is a big investment and to trust this beta release from 8Dio who have hardly covered themselves in much glory to date beggars belief. But what's happened has happened, Sequential are a company that has demonstrated good commitment to customers, I've had numerous firmware update problems with my PX since the offset and they've always been top nouch in responding to the issues. At the moment I don't think I have the same confidence with 8dio and there part of the story. But perhaps judgement should be resevered until we discover the source real problem here. Anyway I do wish the best and speedy fix for all PX owners with the problem. I will be holding off any more sample loading until there is an outcome, given my own history of firmware update related issues!
-
Interestingly 8Dio told me that they had been told that DSI would take over ...
This is from my chat transcript 2 days ago with 8Dio
“Alright, we have been told that DSI will need to take over this support request as it sounds more like a software problem that the DSI Support can fix.”
-
Hi everybody. Brick now after added the neutron vco samples. I downloaded the file, create a directory px, put the U02 in it. Copy to an USB key. Added user samples. It worked perfectly, good sound the neutron and turn off the PX. When turning on ...
:(
Another brick .... :o >:(
Thanks mister Dave, find us a solution ... please
-
If I was in Sequential’s shoes I’d be very tired of people talking about the mythical user sample support on the Tempest. To the best of my knowledge they never indicated that it would happen, and it didn’t. I’ve asked on several forums if anyone has a shred of evidence otherwise, and the answer is always no.
The situation for Prophet X owners who are currently affected is very unfortunate and I hope it gets resolved quickly. I also have no doubt that it will be, and that the solution will be no more complex than a SysEx delivered OS update via the bootloader. The hard part is determining the exact nature of the problem and having a high-confidence fix to roll out.
I do completely agree that the Prophet X itself should be validating everything it loads. Relying on external software to format everything correctly 100% of the time, and on users not to tinker with the result in an in unsupported way is asking for trouble.
There were no direct promise of the Tempest user sample option, but they talked about including it in a later update... if you are a clever developer you do NOT talk about such possibilities unless you're prepared to deal with pissed off customers when they find out it never happened anyway... especially when the stock samples are mostly crap and have bugs in the samples as well... but even if we take that one feature away in the equation, the Tempest STILL suffer from several bugs that should have been fixed... one being the very clicky single cycle waveforms, the MIDI DIN SysEx bugs, and several other... a great deal of those bugs should have been fixed, and they should never have released that drummachine until it had been thoroughly tested and finished it before release... this is why I compare this to the PX now since it's the exact same stupid thing... they release the PX saying that a user sample feature will be out in december, and then outsource the software programming to other companies, just like they outsourced the sample part to a third party chip developer for Tempest.
I really do not care if Sequential do not like critique... I'll give it when I feel it's relevant, and I feel it is that right now... they should stop being so lazy when it comes to software development and hire someone to do their OWN software development... many still do not get why they have no interest in developing editors for their synths, as any other developer out there does this these days... to me it seems like they really do not give a shit about people who prefer editors, or anyone who would want to use their own samples when they constantly give the job away to people who can clearly not deliver.
Had this been the first time, i might have let it pass... but this is the second time they've outsourced user sample features that has given users trouble.
Anyone is of course intitled to their own opinion on this matter... but this is mine.
-
Hi everybody. Brick now after added the neutron vco samples. I downloaded the file, create a directory px, put the U02 in it. Copy to an USB key. Added user samples. It worked perfectly, good sound the neutron and turn off the PX. When turning on ...
:(
Another brick .... :o >:(
Thanks mister Dave, find us a solution ... please
Sorry you've had to join our club :(
-
Hi everybody. Brick now after added the neutron vco samples. I downloaded the file, create a directory px, put the U02 in it. Copy to an USB key. Added user samples. It worked perfectly, good sound the neutron and turn off the PX. When turning on ...
:(
Another brick .... :o >:(
Thanks mister Dave, find us a solution ... please
Was this the first time you had loaded user samples?
-
Well sh*t. Double plus not good.
Do you recall what version of the OS you were on?
Hi everybody. Brick now after added the neutron vco samples. I downloaded the file, create a directory px, put the U02 in it. Copy to an USB key. Added user samples. It worked perfectly, good sound the neutron and turn off the PX. When turning on ...
:(
Another brick .... :o >:(
Thanks mister Dave, find us a solution ... please
-
To SynthJam - yes the first time. The file was downloaded in this forum ::)
To blewis - The version of the os was the last 2.0.0.0.1
-
To blewis - The version of the os was the last 2.0.0.0.1
Do you recall if you saved any presets with the loaded Neutron samples? And if you saved that preset, did you set that as the default preset by entering the global menu? i.e. Did you setup the newly saved preset using the Neutron samples as the default preset to be loaded on boot?
FWIW, I've loaded these Neutron projects repeatedly on my PX as part of collaboratively building them and haven't seen any issues.
-
To blewis - The version of the os was the last 2.0.0.0.1
Do you recall if you saved any presets with the loaded Neutron samples? And if you saved that preset, did you set that as the default preset by entering the global menu? i.e. Did you setup the newly saved preset using the Neutron samples as the default preset to be loaded on boot?
FWIW, I've loaded these Neutron projects repeatedly on my PX as part of collaboratively building them and haven't seen any issues.
No, no nothing out of that, just listening the neutron vco. All the samples worked perfectly until the re-ignition of the PX.
But what I noticed before all this is that to update the firmware in 2.0.0.0.1, I had copied from my Mac on a USB 3.0, then inserted in the PX and it took that I turn the PX off and on again for it to be recognized (USB error). I did not do it with bank u02. My friend lyynk had the same problem to recognize his USB keys. Turn off and turn back on ??? Maybe a USB sync problem with the PX ???
-
they should stop being so lazy when it comes to software development and hire someone to do their OWN software development...
Yep, I've been saying this for a while now.
-
My heart goes out to everyone affected by this. Now that we've seen samples that load just fine on several Prophet Xs cause problems on another, that would seem to eliminate the Mapping Utility and the content of the samples themselves (naming, size, number of samples, etc.) from being direct causes. Is there a pattern in the affected serial numbers that could point to some factory setup issues with the way the SSD is formatted? Or a pattern of OS upgrade paths that left systems in a vulnerable state?
I haven't had any issues and I've installed user samples dozens of times. My serial # is 040, and I've installed every beta and production OS since 1.0.
-
My heart goes out to everyone affected by this. Now that we've seen samples that load just fine on several Prophet Xs cause problems on another, that would seem to eliminate the Mapping Utility and the content of the samples themselves (naming, size, number of samples, etc.) from being direct causes. Is there a pattern in the affected serial numbers that could point to some factory setup issues with the way the SSD is formatted? Or a pattern of OS upgrade paths that left systems in a vulnerable state?
I haven't had any issues and I've installed user samples dozens of times. My serial # is 040, and I've installed every beta and production OS since 1.0.
I agree. If there was an issue with the mapping software or OS EVERY single machine would be affected not just some. There’s a piece of the puzzle missing here.
-
My heart goes out to everyone affected by this. Now that we've seen samples that load just fine on several Prophet Xs cause problems on another, that would seem to eliminate the Mapping Utility and the content of the samples themselves (naming, size, number of samples, etc.) from being direct causes. Is there a pattern in the affected serial numbers that could point to some factory setup issues with the way the SSD is formatted? Or a pattern of OS upgrade paths that left systems in a vulnerable state?
I haven't had any issues and I've installed user samples dozens of times. My serial # is 040, and I've installed every beta and production OS since 1.0.
Until the time your Px will freeze like ours ......
I ask me if it's a problem on the 8dio mapping software but if it is not the USB controller of the Px that is not stable enough and if there is the slightest cut of it during the transfer samples in the synth, it frize the Px ... Already, when I installed the add on the Prophet 5, I had to do it twice because the first time, it was missing some samples ... Despite this problem, the synth was not blocked but there already, there was a problem during the first loading of this add on ...
-
My heart goes out to everyone affected by this. Now that we've seen samples that load just fine on several Prophet Xs cause problems on another, that would seem to eliminate the Mapping Utility and the content of the samples themselves (naming, size, number of samples, etc.) from being direct causes. Is there a pattern in the affected serial numbers that could point to some factory setup issues with the way the SSD is formatted? Or a pattern of OS upgrade paths that left systems in a vulnerable state?
I haven't had any issues and I've installed user samples dozens of times. My serial # is 040, and I've installed every beta and production OS since 1.0.
Until the time your Px will freeze like ours ......
I ask me if it's a problem on the 8dio mapping software but if it is not the USB controller of the Px that is not stable enough and if there is the slightest cut of it during the transfer samples in the synth, it frize the Px ... Already, when I installed the add on the Prophet 5, I had to do it twice because the first time, it was missing some samples ... Despite this problem, the synth was not blocked but there already, there was a problem during the first loading of this add on ...
So after you added the samples, did it freeze right away? Or did it simply freeze when you tried to turn it on again? Or could you turn it on and off and play it and then one day it froze?
-
Until the time your Px will freeze like ours ......
No sign that it will do so, and others have been afflicted pretty much immediately.
I ask me if it's a problem on the 8dio mapping software but if it is not the USB controller of the Px that is not stable enough and if there is the slightest cut of it during the transfer samples in the synth, it frize the Px ...
Every person I've heard from so far has reported problems turning the unit on after installation, not freezing during installation. That would suggest that something on the SSD that gets read during the initial boot has been corrupted in one way or another that prevents the system from reloading to its normal power-on state. The part even Sequential won't know for certain until they get someone's disk in for testing is whether it's strictly the SSD, or some combination of what they store in preset memory in conjunction with the SSD.
-
Could all this be the result of a faulty or improperly formatted USB Drive?
-
Could all this be the result of a faulty or improperly formatted USB Drive?
Don't think so, any problems I had with having the right folders or hierarchy on the drive resulted in "Drive has no Samples" kind of message. Everyone I see so far has had the PX find the drive and upload samples from it.
-
Could all this be the result of a faulty or improperly formatted USB Drive?
Don't think so, any problems I had with having the right folders or hierarchy on the drive resulted in "Drive has no Samples" kind of message. Everyone I see so far has had the PX find the drive and upload samples from it.
So did the freeze happen after you turned the machine off and froze when you tried to turn it on again or did it freeze after calibration or did it freeze randomly after a few sessions with the new samples?
-
Could all this be the result of a faulty or improperly formatted USB Drive?
Don't think so, any problems I had with having the right folders or hierarchy on the drive resulted in "Drive has no Samples" kind of message. Everyone I see so far has had the PX find the drive and upload samples from it.
So did the freeze happen after you turned the machine off and froze when you tried to turn it on again or did it freeze after calibration or did it freeze randomly after a few sessions with the new samples?
Froze on restart after samples were uploaded. I had samples already in there that were working well a week or so but my last attempted upload froze upon restart and has not started since. As said earlier, that last upload I sent to Support and Carson said it loaded fine in their machine.
I'll be getting the new drive Jan 7 so will first see if startup, immediately upload my last samples and restart a few times. Then send my old drive to DSI so they can see if it freezes their machine and if anything's wrong with it.
-
Until the time your Px will freeze like ours ......
No sign that it will do so, and others have been afflicted pretty much immediately.
Before it finally freeze on my Px, I did a lot of loading without problem like you...
I think it can really happen randomly because I think that the USB controller of the synth is not stable and that just a bug during the transfer for the freeze synth next.
I have a friend who has not had a freeze for the moment after having done a lot of loading but who prefers not to charge anything to take no risk.
-
Could all this be the result of a faulty or improperly formatted USB Drive?
Don't think so, any problems I had with having the right folders or hierarchy on the drive resulted in "Drive has no Samples" kind of message. Everyone I see so far has had the PX find the drive and upload samples from it.
So did the freeze happen after you turned the machine off and froze when you tried to turn it on again or did it freeze after calibration or did it freeze randomly after a few sessions with the new samples?
Froze on restart after samples were uploaded. I had samples already in there that were working well a week or so but my last attempted upload froze upon restart and has not started since. As said earlier, that last upload I sent to Support and Carson said it loaded fine in their machine.
I'll be getting the new drive Jan 7 so will first see if startup, immediately upload my last samples and restart a few times. Then send my old drive to DSI so they can see if it freezes their machine and if anything's wrong with it.
Me, when I receive mine, I just reinstall my add on Prophet 5 and that's it! I'm waiting for Sequential to find the root of the problem and come up with a serious solution before reloading samples into the machine. With the 150 GB of 8dio + add on and all the synthesis it offers, there is plenty to have fun with, create lots of interesting sounds ...
-
I probably won't even put the Last Prophet-5 back in. That was an impulse to see if those waves were better than the VA ones. My minimoog, synthacon and modular oscs were more lively before bricks, even those Neuron osc demos sounded better. That's why my samples go first or keep fixing.
-
I probably won't even put the Last Prophet-5 back in. That was an impulse to see if those waves were better than the VA ones. My minimoog, synthacon and modular oscs were more lively before bricks, even those Neuron osc demos sounded better. That's why my samples go first or keep fixing.
Personally, I programmed very good presets with the samples of the add on Prophet5.
I will try to publish a demo of these sounds when the Prophet X will be functional again
-
I recall with the Tempest, that DSI thought it would be possible to flash new samples into the 3rd party sample chip... Even when the third party developers were put on the task they gave up, forever burrying that feature.
This time they put a third party PC board into the PX... What if that board show up having a nonstable USB/SSD part? Will they be able to fix that then, or will users end up with a ROMpler like the Tempest?
Well... I hope for Sequential that they find a working solution... Would hate to see the PX end up like the Tempest also... But I asume they are sweating at work right now to solve this... They are quite silent in this thread.
I just wonder; why have no one had any problem loading the 8DIO commercial banks? It is their beta software, and I assume they are using it as well... Why are their PX not freezing when they load the samples? They must have loaded them several times during design.
USB is only used while loading the samples, so if freezing first happen when rebooting after samples was loading fine, then I doubt it is a faulty USB thing... It must be an erroneous saving to the SSD drive that is the culprit, happening when the samples are saved to the drive.
I bet it has to do with the samples themselves... 8DIO probably know what format .wav files must be in, but if some of the header data in the samples confuse the PX, maybe it screws up... Question is if the 8 DIO software needs to clean up the samples and their headers when writing them with their software, or if the PX is taking .wav header info and other data into account when loading/saving.
It may be that the secret lies in how much and what meta data is saved with the samples, plus maybe even the format of the wav files (bit depths, sample rates etc.)
-
I just wonder; why have no one had any problem loading the 8DIO commercial banks? It is their beta software
Very logical observation.
-
I would suggest that people who have had their PX freeze, look closely at the metadata of their wave files, and start to compare them with others who had a freeze too... See if there is any similarities... Maybe even send these to Sequential too if they would want to look at them... Because if 8DIO uses the same beta software, then the problem HAS to be the samples themselves somehow... I think.
-
I would suggest that people who have had their PX freeze, look closely at the metadata of their wave files, and start to compare them with others who had a freeze too... See if there is any similarities... Maybe even send these to Sequential too if they would want to look at them... Because if 8DIO uses the same beta software, then the problem HAS to be the samples themselves somehow... I think.
That's almost certainly not the case.
We've seen an owner whose PX is currently unusable send the contents of their USB drive to Sequential, who were able to install the same samples without issues. We've also seen an owner have problems after installing the Neutron VCO samples, while several of us have installed them without problems. There's something else at work here.
I also don't believe the USB port on the PX has anything to do with it. In every instance I've seen described the issues arise after installation, not during.
-
In that case it must be the loading/writing to the SSD that is the problem... Hope for DSI's sake that it is software related.
-
I agree something else is at work here. If Sequential can install their own samples with no issues and 8Dio can install their sound packs with no issues and if only some users are having their PXs bricked while others are having no issues then there is something left out of the picture here.
-
I agree something else is at work here. If Sequential can install their own samples with no issues and 8Dio can install their sound packs with no issues and if only some users are having their PXs bricked while others are having no issues then there is something left out of the picture here.
yes... proper quality testing before launch :-X
... anyway... what are the main differences that could possibly exist then between Sequential/8DIO and users? ... the only physical difference I can see is the actual USB Stick used... but that would not be logical since everyone loads fine... this (luckily) hints at a software problem that 8DIO and Sequential and some other users simply have not run into ... yet...
-
In that case it must be the loading/writing to the SSD that is the problem... Hope for DSI's sake that it is software related.
Quite. The Intel SSDs should be incredibly reliable, so I'd be shocked if those were at fault. It's likely either a problem with the filesystem used, or something about the way units were formatted at the factory. That's part of why I tried to get a list of affected / unaffected serial #s going earlier in the thread in case there were changes to the process used during manufacturing that would bar implicated.
-
In that case it must be the loading/writing to the SSD that is the problem... Hope for DSI's sake that it is software related.
Quite. The Intel SSDs should be incredibly reliable, so I'd be shocked if those were at fault. It's likely either a problem with the filesystem used, or something about the way units were formatted at the factory. That's part of why I tried to get a list of affected / unaffected serial #s going earlier in the thread in case there were changes to the process used during manufacturing that would bar implicated.
Well we should know tomorrow if its the SSD side of things that are causing the issue as Rewire gets his tomorrow ...
Then it will be the question of SSD hardware (unlikely) or code thats causing our strife .....
-
My x has a broken instrument oled? It’s not bricked it’s hosed, they want me to put up a 200 dollar deposit for a replacement board, and fix it myself what a bunch of bs
-
My x has a broken instrument oled? It’s not bricked it’s hosed, they want me to put up a 200 dollar deposit for a replacement board, and fix it myself what a bunch of bs
broken how?!?
-
My x has a broken instrument oled? It’s not bricked it’s hosed, they want me to put up a 200 dollar deposit for a replacement board, and fix it myself what a bunch of bs
This is a physical problem, not software. Start a new thread.
-
My x has a broken instrument oled? It’s not bricked it’s hosed, they want me to put up a 200 dollar deposit for a replacement board, and fix it myself what a bunch of bs
Seems reasonable if you want to fix it yourself.
Alternative is take it back to the store you bought it from and have them fix it under warranty.
I'd always choose an at home repair personally, if thats an option for me.
-
My x has a broken instrument oled? It’s not bricked it’s hosed, they want me to put up a 200 dollar deposit for a replacement board, and fix it myself what a bunch of bs
Or you could talk to the store you got it from and assuming you got warranty on it, they will fix it for you at no cost.
-
Please welcome me to the club. My XL bricked yesterday evening. Serial number 129.
I have this synth for a few weeks now and I am really in love with the possibilities and the sound that is coming out of it, but this is unacceptable. Hey, Sequential, we are not in the '90s anymore.
I had the latest firmware installed (2.0.0.0.1) and both 8DIO packs, along with some of my own samples. It worked for days. I changed nothing, and yesterday evening I wanted to switch it on and it just stopped starting at the end of the progress bar. As far as I can see in this forum and over at Gearslutz, Sequential has not found a way to unbrick the devices for more than a week. Please just release a firmware that lets the user reset the sample storage with a key combination on startup. This should be a quick interim-fix until you figured the cause of the problem. But we could go on using our synth in the meantime.
Or is it a hardware problem we are talking about?
Best,
TheMM
-
Please welcome me to the club. My XL bricked yesterday evening. Serial number 129.
I have this synth for a few weeks now and I am really in love with the possibilities and the sound that is coming out of it, but this is unacceptable. Hey, Sequential, we are not in the '90s anymore.
I had the latest firmware installed (2.0.0.0.1) and both 8DIO packs, along with some of my own samples. It worked for days. I changed nothing, and yesterday evening I wanted to switch it on and it just stopped starting at the end of the progress bar. As far as I can see in this forum and over at Gearslutz, Sequential has not found a way to unbrick the devices for more than a week. Please just release a firmware that lets the user reset the sample storage with a key combination on startup. This should be a quick interim-fix until you figured the cause of the problem. But we could go on using our synth in the meantime.
Or is it a hardware problem we are talking about?
Best,
TheMM
Welcome to the club TheMM !!! :-\
-
Welcome to BC... Bricked Club....
We gonna make a football team....
but not a band yet....
Still waiting for Sequential...
-
Please welcome me to the club. My XL bricked yesterday evening. Serial number 129.
I have this synth for a few weeks now and I am really in love with the possibilities and the sound that is coming out of it, but this is unacceptable. Hey, Sequential, we are not in the '90s anymore.
I had the latest firmware installed (2.0.0.0.1) and both 8DIO packs, along with some of my own samples. It worked for days. I changed nothing, and yesterday evening I wanted to switch it on and it just stopped starting at the end of the progress bar. As far as I can see in this forum and over at Gearslutz, Sequential has not found a way to unbrick the devices for more than a week. Please just release a firmware that lets the user reset the sample storage with a key combination on startup. This should be a quick interim-fix until you figured the cause of the problem. But we could go on using our synth in the meantime.
Or is it a hardware problem we are talking about?
Best,
TheMM
Welcome to this decreasingly exclusive club .....
-
As far as I can see in this forum and over at Gearslutz, Sequential has not found a way to unbrick the devices for more than a week.
Best,
TheMM
12 Days and counting ....
-
wow this is making me so afraid now. Bricked Prophet X's everywhere!
-
As far as Sequential not getting back to people. Remeber this happened over the holidays. Yeah it’s unfortunate timing but they do deserve some r&r and personal time. Does it suck for those affected? Yeah. Is it the end of the world? Well, unless the PX is the only synth you own then no it’s not. Just do what I did when my P6 was in the shop, play your other gear while you wait. Until Sequential announce there’s a solution or no solution, there’s no sense in moaning about it or being pessimistic. This will get resolved fairly soon. I’m positive. There is no way Dave would allow the PX to become a rompler or shrug off defective $5k synths.
-
I've send all my instruments to buy my Prophet X.
One and only......
So....
I'm naturally upset.
Solution will come.
The more we love Px the more we are going mad!!!!!
-
As far as Sequential not getting back to people. Remeber this happened over the holidays. Yeah it’s unfortunate timing but they do deserve some r&r and personal time. Does it suck for those affected? Yeah. Is it the end of the world? Well, unless the PX is the only synth you own then no it’s not. Just do what I did when my P6 was in the shop, play your other gear while you wait. Until Sequential announce there’s a solution or no solution, there’s no sense in moaning about it or being pessimistic. This will get resolved fairly soon. I’m positive. There is no way Dave would allow the PX to become a rompler or shrug off defective $5k synths.
Maybe with a bit of hindsight they should of not released it the week before a 2 week holiday .....
-
As far as Sequential not getting back to people. Remeber this happened over the holidays. Yeah it’s unfortunate timing but they do deserve some r&r and personal time. Does it suck for those affected? Yeah. Is it the end of the world? Well, unless the PX is the only synth you own then no it’s not. Just do what I did when my P6 was in the shop, play your other gear while you wait. Until Sequential announce there’s a solution or no solution, there’s no sense in moaning about it or being pessimistic. This will get resolved fairly soon. I’m positive. There is no way Dave would allow the PX to become a rompler or shrug off defective $5k synths.
Maybe with a bit of hindsight they should of not released it the week before a 2 week holiday .....
As far as I’m aware, that was 8Dio that released it, not Sequential.
-
As far as Sequential not getting back to people. Remeber this happened over the holidays. Yeah it’s unfortunate timing but they do deserve some r&r and personal time. Does it suck for those affected? Yeah. Is it the end of the world? Well, unless the PX is the only synth you own then no it’s not. Just do what I did when my P6 was in the shop, play your other gear while you wait. Until Sequential announce there’s a solution or no solution, there’s no sense in moaning about it or being pessimistic. This will get resolved fairly soon. I’m positive. There is no way Dave would allow the PX to become a rompler or shrug off defective $5k synths.
Maybe with a bit of hindsight they should of not released it the week before a 2 week holiday .....
As far as I’m aware, that was 8Dio that released it, not Sequential.
Oh so that makes it alright .... ::)
-
Hi all,
i read somewhere a few hundred had non formatted user area for sampling, maybe be those gone black. Just an idea.
Hope all yours will boot fine soon.
Martin
-
I suggested it earlier and others as well to make sure the default preset is not one with user samples (Hit Global in a default preset)
My new drive from Sequential will arrive in the next 8 hours and by 12 hours from now be installed and tested. I will see if it boots up with clean drive - Should, with no samples or presets saved. I'll install the same samples that froze before but make sure it boots up on a non sample patch.
The fact that a few others froze after using samples for a while points to something about the restart that's freezing. The best variable answer we have now is that default patch. Pretty sure that happened to me; I was always starting on a patch that used the PVS internal samples but think it was trying to restart on a user sample saved patch when it froze.
-
I suggested it earlier and others as well to make sure the default preset is not one with user samples (Hit Global in a default preset)
My new drive from Sequential will arrive in the next 8 hours and by 12 hours from now be installed and tested. I will see if it boots up with clean drive - Should, with no samples or presets saved. I'll install the same samples that froze before but make sure it boots up on a non sample patch.
The fact that a few others froze after using samples for a while points to something about the restart that's freezing. The best variable answer we have now is that default patch. Pretty sure that happened to me; I was always starting on a patch that used the PVS internal samples but think it was trying to restart on a user sample saved patch when it froze.
You're a brave lad !!! If when my drive arrives it loads up i'm not loading any user samples into it till a new OS is out addressing the issue !!!
Looking forward to hearing what happens ... :o
-
My new drive from Sequential will arrive in the next 8 hours and by 12 hours from now be installed and tested. I will see if it boots up with clean drive - Should, with no samples or presets saved. I'll install the same samples that froze before but make sure it boots up on a non sample patch.
I believe at some point Sequential clarified that presets are stored in the same system flash storage as the operating system, which is distinct from the SSD. If true, that’s good news in that you shouldn’t lose any presets with the swap, but raises somewhat concerning possibilities if the failure to boot isn’t strictly related to what’s on the SSD. It will be an important learning experience for all concerned, so please do keep us posted!
-
My new drive from Sequential will arrive in the next 8 hours and by 12 hours from now be installed and tested. I will see if it boots up with clean drive - Should, with no samples or presets saved. I'll install the same samples that froze before but make sure it boots up on a non sample patch.
I believe at some point Sequential clarified that presets are stored in the same system flash storage as the operating system, which is distinct from the SSD. If true, that’s good news in that you shouldn’t lose any presets with the swap, but raises somewhat concerning possibilities if the failure to boot isn’t strictly related to what’s on the SSD. It will be an important learning experience for all concerned, so please do keep us posted!
But the OS flash has been refreshed surely when we Sysex'ed the OS in Bootloader mode.
-
But the OS flash has been refreshed surely when we Sysex'ed the OS in Bootloader mode.
While it’s likely the same physical flash storage device as the OS, it is subdivided so that an OS upgrade leaves presets alone (much like partitioning a hard disk but without as much formality and all behind the scenes from our perspective.)
-
The most viable thing I've heard so far is a patch calling for a missing sample on power up. I'd be willing to test this theory but I'm too nervous. I have to use this for a concert in a few months.
-
But the OS flash has been refreshed surely when we Sysex'ed the OS in Bootloader mode.
While it’s likely the same physical flash storage device as the OS, it is subdivided so that an OS upgrade leaves presets alone (much like partitioning a hard disk but without as much formality and all behind the scenes from our perspective.)
I know the update OS leaves presets alone but what about the Hold Sample Stretch Boot Loader I used? Since the synth never actually restarted its hard to know if it actually updated.
Guess I'll know in 6 hours as I have the replacement drive in hand but at work now.
-
But the OS flash has been refreshed surely when we Sysex'ed the OS in Bootloader mode.
While it’s likely the same physical flash storage device as the OS, it is subdivided so that an OS upgrade leaves presets alone (much like partitioning a hard disk but without as much formality and all behind the scenes from our perspective.)
I know the update OS leaves presets alone but what about the Hold Sample Stretch Boot Loader I used? Since the synth never actually restarted its hard to know if it actually updated.
Guess I'll know in 6 hours as I have the replacement drive in hand but at work now.
I think you’ve come over quite ill all of a sudden .... ;) :o :P ;)
-
I know the update OS leaves presets alone but what about the Hold Sample Stretch Boot Loader I used? Since the synth never actually restarted its hard to know if it actually updated.
People have used the bootloader technique to update before as directed by Sequential and I don’t remember any warnings about losing user presets in the process. Anything’s possible, of course. There are also SysEx files for restoring the user preset space to its original state but I’ve only ever seen directions about how to use those after booting normally. It’s possible but probably not likely that the bootloader is also capable of doing that update. If it was possible, I would have expected Sequential to ask one of the affected owners to try it by now.
-
I think you’ve come over quite ill all of a sudden .... ;) :o :P ;)
I was going to leave early but a co-worker beat me to a sick day leaving me covering. >:(
-
The only bootliader action I did that wiped presets was having to re-image my FPGA. That wiped all presets. All of them. Had to re-install the factory.
All other boot loader Sysex OS updates left the preset memory in place.
I did some Add On “A-bank” manual initialization when I heard of users having to do this with Add On packs. Wanted to be ready should I install them. Can’t recall how I did it, but it was in a special menu. Just FYI.
Mine currently works after losing user samples. Have not saved a patch with new samples yet.
-
I did some Add On “A-bank” manual initialization when I heard of users having to do this with Add On packs. Wanted to be ready should I install them. Can’t recall how I did it, but it was in a special menu. Just FYI.
I had done the same thing back when The Last Prophet 5 pack gave me some trouble. I documented the workaround at the time as follows:
Go into the debug menu by holding both transpose buttons and pressing Global. Scroll down to the Initialize Add-On menu item, and perform this task which was skipped at the factory. This wipes out the A bank presets, but it also ensures that the unused slots are harmless. Press Global again to return to normal operation, and re-install the sample pack to restore the presets. Before the reinstall I used the normal Global menu option to delete the installed samples, but I believe this isn't actually necessary.
-
OK. Opened up, changed the drive. Started up the way it did first time. And, my presets are still there! YAAAY. The one's that called for samples or the P5 library show no samples but are playing some sound.
Updated to 1.2.1 through USB and still good restart.
Crucial moment - put in the USB drive of samples I last used before bricking. Baited breath while the start bar moves up................SUCCESS! All samples are loaded and patches that used them got em.
I hope further restarts are successful but nothing new gets loaded until Sequential sorts it out. Also hitting Global on U1 with generric oscs so it starts always there, I'll send the drive back in a day or so so maybe that'll give some clues.
Dan
EDIT: Woops! updated to 1.2 not 2.0, doing it now...........Still good. Phewwww
-
OK. Opened up, changed the drive. Started up the way it did first time. And, my presets are still there! YAAAY. The one's that called for samples or the P5 library show no samples but are playing some sound.
Updated to 1.2.1 through USB and still good restart.
Crucial moment - put in the USB drive of samples I last used before bricking. Baited breath while the start bar moves up................SUCCESS! All samples are loaded and patches that used them got em.
I hope further restarts are successful but nothing new gets loaded until Sequential sorts it out. Also hitting Global on U1 with generric oscs so it starts always there, I'll send the drive back in a day or so so maybe that'll give some clues.
Dan
CONGRATS!
-
Indeed, congratulations on getting back up and running. I'm sure that won't be the preferred way of dealing with the situation long term but at least there's an apparent fix for those affected while Sequential investigates further.
-
How long can I keep it on now? :)
-
As far as Sequential not getting back to people. Remeber this happened over the holidays. Yeah it’s unfortunate timing but they do deserve some r&r and personal time. Does it suck for those affected? Yeah. Is it the end of the world? Well, unless the PX is the only synth you own then no it’s not. Just do what I did when my P6 was in the shop, play your other gear while you wait. Until Sequential announce there’s a solution or no solution, there’s no sense in moaning about it or being pessimistic. This will get resolved fairly soon. I’m positive. There is no way Dave would allow the PX to become a rompler or shrug off defective $5k synths.
Maybe with a bit of hindsight they should of not released it the week before a 2 week holiday .....
As far as I’m aware, that was 8Dio that released it, not Sequential.
Oh so that makes it alright .... ::)
No but you are directing your frustration at the wrong party. Sequential stated months ago that the PX was ready to go and they were waiting on 8Dio to deliver the mapping software and 8Dio did release it before the holidays so why turn around and point fingers at Sequential for the software?
-
OK. Opened up, changed the drive. Started up the way it did first time. And, my presets are still there! YAAAY. The one's that called for samples or the P5 library show no samples but are playing some sound.
Updated to 1.2.1 through USB and still good restart.
Crucial moment - put in the USB drive of samples I last used before bricking. Baited breath while the start bar moves up................SUCCESS! All samples are loaded and patches that used them got em.
I hope further restarts are successful but nothing new gets loaded until Sequential sorts it out. Also hitting Global on U1 with generric oscs so it starts always there, I'll send the drive back in a day or so so maybe that'll give some clues.
Dan
EDIT: Woops! updated to 1.2 not 2.0, doing it now...........Still good. Phewwww
Phew ... excellent news REwire !!!
Roll on Friday when my drive should arrive. Interestingly I’ve been asked to NOT load user content ... which I wasn’t going to anyway.
-
My x has a broken instrument oled? It’s not bricked it’s hosed, they want me to put up a 200 dollar deposit for a replacement board, and fix it myself what a bunch of bs
broken how?!?
The instrument oled went out, I’m sending it back for repair. No problem it’s under warranty, the initial quick fix just didn’t work :(
-
I just received the SSD exchange for my Prophet X who was frize and everything works normally! :-)
I would reinstall my add on Prophet 5. By cons, no installation of user sample in the PX until sequential does not offer a serious update that definitely fixes this freeze problem when there is a sample / file that has a problem on the SSDs.
Anyway, with all the sound material sampled 8Dio already present in the PX, I already have a life of sound creation with ... I'm not n the urgency to put other samples inside for the moment, there is already so much to do with ....
-
I just received the SSD exchange for my Prophet X who was frize and everything works normally! :-)
I would reinstall my add on Prophet 5. By cons, no installation of user sample in the PX until sequential does not offer a serious update that definitely fixes this freeze problem when there is a sample / file that has a problem on the SSDs.
Anyway, with all the sound material sampled 8Dio already present in the PX, I already have a life of sound creation with ... I'm not n the urgency to put other samples inside for the moment, there is already so much to do with ....
Great, super pleased another user has fixed their PX ... My SSD should be here in the UK Friday ...
-
They just told me by email that they are actively working to identify the cause of the crash we have encountered. They will be releasing an updated OS as soon as possible...
-
BAD NEWS! BRICKED AGAIN!
After a few days of working synth with my samples, I had patches that used the Last Prophet-5 Library so I added it back tonight. It took it and loaded all sounds and played them without needing a restart and my patches found them and played fine. All was going well until I tried the restart. Then same freeze as before, at top of the startup bar
I just tried the 2.0 Bootloader - NO, then The FPGA Updater - NO, Then 2.0 Bootloader again, nothing.
The Prophet-5 was loaded and working fine before my first crash but adding samples froze that first drive. With the new drive this time it was adding Prophet after I had working samples that did it.
-
BAD NEWS! BRICKED AGAIN!
After a few days of working synth with my samples, I had patches that used the Last Prophet-5 Library so I added it back tonight. It took it and loaded all sounds and played them without needing a restart and my patches found them and played fine. All was going well until I tried the restart. Then same freeze as before, at top of the startup bar
I just tried the 2.0 Bootloader - NO, then The FPGA Updater - NO, Then 2.0 Bootloader again, nothing.
The Prophet-5 was loaded and working fine before my first crash but adding samples froze that first drive. With the new drive this time it was adding Prophet after I had working samples that did it.
Oh man that sucks ... what have DSI said ?
-
:(
-
BAD NEWS! BRICKED AGAIN!
After a few days of working synth with my samples, I had patches that used the Last Prophet-5 Library so I added it back tonight.
Hmmm, didn't Sequential tell you not to use custom samples for the moment?
It's still the old firmware, the bug is not fixed, so why should it not freeze again if you do the same thing?
-
Well.. if someone was told that Sequential is working on it at the moment, and that a new OS will be uploaded as soon as possible, then you should be able to conclude that the problem is with the OS software...
I just really do not understand why 8DIO have never experienced such a crash case then with all of those packs they've created, and now people are getting bricked machines even after having installed ONLY the Prophet pack from 8DIO themselves!? ... why in the h*** will that bank brick someones PX, but not 8DIO's!? ... they are running the same darn OS versions I suppose.
-
So... for the moment... what should we do ?
Change SSD, do not import samples and do not import the 2 adds on !!?
I'm a bit lost again.....
-
So... for the moment... what should we do ?
Change SSD, do not import samples and do not import the 2 adds on !!?
I'm a bit lost again.....
Yeah basically that is what you have to do... see the PX as a temporary ROM'pler, and cross your fingers that Sequential will resolve this fast.
-
To you guys who already exchanged the SSD: which screws do I need to loosen to open the XL. Just the ones on the left and right pieces, or any others?
Just received the SSD but without any further description...
-
Plenty of onboard content in the PX already that one can work with until a new OS gets released.
-
To you guys who already exchanged the SSD: which screws do I need to loosen to open the XL. Just the ones on the left and right pieces, or any others?
Just received the SSD but without any further description...
This should help you:
A repair of a Prophet X
https://www.youtube.com/watch?v=Q8QDCocnt0M
-
This should help you:
A repair of a Prophet X
Thanks!!!
-
Careful !
I think the SSD is under the keyboard !
Don't to take off all the buttons !
-
Sorry TheMM !!
I've got problem with the file I have to send You !!
I gonna try again !
-
The process to install the hard drive is relatively easy and requires no more than a screwdriver to perform. Start by removing any power, audio, MIDI/USB, and/or pedal connectivity from the synth.
1. Remove the 3 screws in each wood end. Remove the wood ends.
(see attached WoodSideLeft.jpeg, Wood SideRight.jpg)
2. Place a piece of soft material down and flip the instrument over face down on top of the material.
3. Remove the 2 screws which hold the wheel box to the metal underside. The first screw is located immediately to the right, and slightly down, from the left front rubber foot.
(see attached WheelToMetalScrews.jpeg)
4. Remove the 4 screws which hold the hard drive to the metal work.
(see attached HardDriveScrews.jpg)
5. Flip the instrument back over. Remove the 3 screws on the left side, and the 2 screws on the rights side of the synth.
(see attached ScrewsLeftSide.jpeg, ScrewsRightSide.jpeg)
6. The front panel can now be flipped open. The panel is hinged at the rear and has a lanyard to keep the top panel in place.
7. Remove the SATA and power cable from the hard drive and replace the hard drive.
Reassemble the synth in the reverse order of disassembly.
-
We've confirmed the probable cause of the crash and are awaiting a faulty hard drive to be returned to verify our fix. We expect one hard drive to arrive for testing in the office today. Barring any unforeseen problems, we anticipate having an OS update with a fix by the end of this week or early next week.
Other PX users, please hold tight on loading any new content to the synth until we get this new OS out.
Our apologies to all who are having troubles in this regard. Rest assured we are working hard to resolve the issue.
-
We've confirmed the probable cause of the crash and are awaiting a faulty hard drive to be returned to verify our fix. We expect one hard drive to arrive for testing in the office today. Barring any unforeseen problems, we anticipate having an OS update with a fix by the end of this week or early next week.
Other PX users, please hold tight on loading any new content to the synth until we get this new OS out.
Our apologies to all who are having troubles in this regard. Rest assured we are working hard to resolve the issue.
Carson, when you issue the new OS update can you please make this available in sysex format as well as the standard bin file method.
Thanks.
-
BAD NEWS! BRICKED AGAIN!
After a few days of working synth with my samples, I had patches that used the Last Prophet-5 Library so I added it back tonight.
Hmmm, didn't Sequential tell you not to use custom samples for the moment?
It's still the old firmware, the bug is not fixed, so why should it not freeze again if you do the same thing?
No. Instead I sent my User Samples to Sequential and they were tested and had no issues. So i put them immediately into my new drive 10 minutes after confirming it worked. Couple of days later I got back into using the PX in production and realized I needed the P5 patches I created when I had the pack installed before. Didn't suspect that would be the crash catalyst this time.
Carson, a new drive is required to be swapped before running the new update? This update I assume then won't unbrick a machine, just prevent future bricking?
thanks! Dan
-
New SSD....
Everything works!!!!
For the 2 adds....I'll waiting!!!
Presets are still there.
I limit the use for the moment but I can breath a little....
I hope it will be ok for everyone.
-
Glad to hear there’s another affected owner up and running again, and I look forward to seeing the updated firmware to set everyone else’s minds at ease.
-
We've sent REwire two replacement hard drives today. One contains the latest DSP OS with the bug fix. If all goes well with this drive, we should have an updated OS available to download tomorrow.
Thanks again for everyone's patience while we have been working to fix this! Hopefully y'all can get back to loading user sample content to the PX this weekend :)
-
Thanks Carson. If I get the drives Friday it'll be in the evening PST that I'll have uploaded samples and a number of power cycles and saving patches to see if all is OK
Dan
-
We've sent REwire two replacement hard drives today. One contains the latest DSP OS with the bug fix. If all goes well with this drive, we should have an updated OS available to download tomorrow.
Thanks again for everyone's patience while we have been working to fix this! Hopefully y'all can get back to loading user sample content to the PX this weekend :)
perfect
-
Thank you Sequential support! I received a new SSD yesterday per UPS Express, unbricked my system and will return the buggy SSD today. This was very good service. I hope you will find the cause and eliminate the problem quite soon.
-
My new SSD just arrived, gonna give it an hour or two to warm up before fitting as its as cold as ice ...
-
It will be ok !!!!!
I've received mine yesterday and it was ok !
Sequential guy told me to wait a bit to reload the 2 adds on and of course external samples....
Apparently the super new OS will come soon...!!!
-
https://www.instagram.com/p/Bsg1ivdhH5S/?utm_source=ig_share_sheet&igshid=103xqecncbd6h (https://www.instagram.com/p/Bsg1ivdhH5S/?utm_source=ig_share_sheet&igshid=103xqecncbd6h)
-
Congratulations! Now for the main event: firmware to ensure that nobody else fails prey to the malaise.
-
Yesterday happened the same....BTW great Sequential support; new SSD is already on the way to Italy! :)
Ciao, Maurizio
-
Allegriaaaa!!!!!!
Things getting very good.....!!!!
-
Well, SSD arrived today, very fast shipment!
Already changed it and the Prophet is back to work!!! Programs still there ;)
Waiting for the new OS before to download something...
Grazie Sequential!
-
The OS update is online!
https://forum.sequential.com/index.php/topic,2656.0.html
-
V2.1 works for me so far. Updated the firmware without any problems. Then added my 8dio libraries, played around with them, restarted several times, no problem. Did the same with my own library. Worked so far. Fingers crossed this episode is history. Thanks Sequential for the prompt and good service.
-
This is all great news. Will update mine as soon as I can and prep some more samples.
Thank you.
-
My x has a broken instrument oled? It’s not bricked it’s hosed, they want me to put up a 200 dollar deposit for a replacement board, and fix it myself what a bunch of bs
This is a physical problem, not software. Start a new thread.
Wrong, it was a software issue. At the last minute he requested that I wait for the update and try that before sending it back in. So it ends up (Fixed Bug: Fringe timing issue which would cause small OLED to display only white) . What a great way to start the weekend :D just to remind anyone with a white instrument display the new update fixed it. Thank you Mark at DSI support
-
One more good news !!!!!!!!!!!!!!!!!!!!!!!
:)