By Akrow
Thu May 20, 2010 3:24 pm
Hi all,
I'm on a 1k running jj os2 v1.30 and I'm having some weird stuff happen.
First off maybe once a week or so when I power up the mpc it just sits on the jj os screen and does nothing. Sometimes if I cycle the power a few times it will work, sometimes if I start up os1 it will work then, and sometimes if I just let the thing sit for a while it will figure it out.
Second, just as frequently as the freeze up problem I load up a project and the mpc puts out no sound. Neither sample playback nor input thru will give me anything. If I cycle the power once or twice it seems to work.
I might be imagining things but it seems like I get these bugs when I haven't powered up the mpc for a few days.
Any ideas out there for this? I might have read somewhere that a hard drive on its way out can cause the freeze on start up. Hopefully that's the issue as it's relatively cheap to replace. By the way the no-sound problem was happening on os1, os2 1.29 and 1.30, so I don't think it's an os issue. The startup issue seemed to come up with os2 but I might be remembering that wrong...
Thanks!
-AK
I'm on a 1k running jj os2 v1.30 and I'm having some weird stuff happen.
First off maybe once a week or so when I power up the mpc it just sits on the jj os screen and does nothing. Sometimes if I cycle the power a few times it will work, sometimes if I start up os1 it will work then, and sometimes if I just let the thing sit for a while it will figure it out.
Second, just as frequently as the freeze up problem I load up a project and the mpc puts out no sound. Neither sample playback nor input thru will give me anything. If I cycle the power once or twice it seems to work.
I might be imagining things but it seems like I get these bugs when I haven't powered up the mpc for a few days.
Any ideas out there for this? I might have read somewhere that a hard drive on its way out can cause the freeze on start up. Hopefully that's the issue as it's relatively cheap to replace. By the way the no-sound problem was happening on os1, os2 1.29 and 1.30, so I don't think it's an os issue. The startup issue seemed to come up with os2 but I might be remembering that wrong...
Thanks!
-AK



