BTW, my firmware version is 1.22.
PS Audio PWT software bugs
I purchased a PS Audio PWT about a year ago and have had some strange transport/software bugs since new.
If I put in a CD and then let it sit for more than about 10 minutes, the transport will refuse to play the disc when "play" is entered. The Icons on the front panel will change as if the disc is playing but no output. I am using the AES/EBU digital output to a Brystom BDA-1. The unit will freeze and I can "skip" to the next track but still no output. Often I cannot even eject the disk. I have to do a hard power shut down and cycle. After power up, it recognizes the disc and plays normally.
Same thing happens if I start a track, then stop it and go away for more than about ten minutes. When I try to resume the mode changes to icons showining "play" but no sound and the track will be frozen. Almost no response from any input after that.
When I contacted PS Audio (Marcus Iezzi), he replied in an email:
"There is a bug in the firmware that is causing this issue and our software team is working on fixing it."
Has anyone else had this problem and do you know if a firmware version has been released to fix the issue?
If I put in a CD and then let it sit for more than about 10 minutes, the transport will refuse to play the disc when "play" is entered. The Icons on the front panel will change as if the disc is playing but no output. I am using the AES/EBU digital output to a Brystom BDA-1. The unit will freeze and I can "skip" to the next track but still no output. Often I cannot even eject the disk. I have to do a hard power shut down and cycle. After power up, it recognizes the disc and plays normally.
Same thing happens if I start a track, then stop it and go away for more than about ten minutes. When I try to resume the mode changes to icons showining "play" but no sound and the track will be frozen. Almost no response from any input after that.
When I contacted PS Audio (Marcus Iezzi), he replied in an email:
"There is a bug in the firmware that is causing this issue and our software team is working on fixing it."
Has anyone else had this problem and do you know if a firmware version has been released to fix the issue?
- ...
- 16 posts total
- 16 posts total