By eimermusic
Thu Feb 09, 2006 6:08 pm
I just got an MPC1000 and have so far found two (and a half) seriously annoying problems where features do not work as stated in the manual, this forum or "the faq".
The first thing I did with the MPC was to listen to the demos for 2 minutes... Then I Installed the OS2.1 upgrade and put in my own CF card and formatted it.
1. Autoload refuses to stop loading on power on. Autoload IS set to off in Load/Window and the CD card does not have an Autoload folder. On each power on the scrteen reads something like "Demo..." and starts loading from internal flash memory. As I understand it I ahould not have to erase the internal sounds just to make them stop autoloading.
2. Pad sensitivity page (Other/Pad) reads garbage values.
"Pad sensitivity:???" (as in three question marks that wont change)
"Velocity curve:@" (this value can at least be changed to A, B C, D after scrolling through a bunch of other symbols)
This can't be right? Punching the pads does not get the bar-graphic higher than a few pixels so I would like to increse the sensitivity.
1/2. Half a bug... It is known that OS2.1 can mess up the levels of programs.. but that it messes up the internal (perpetually loading) demos so that nothing can be heard other than faint static was more than I had imagined.
So, gloat and tell me how simple these problem are... please... better that than a faulty sampler, right.
The first thing I did with the MPC was to listen to the demos for 2 minutes... Then I Installed the OS2.1 upgrade and put in my own CF card and formatted it.
1. Autoload refuses to stop loading on power on. Autoload IS set to off in Load/Window and the CD card does not have an Autoload folder. On each power on the scrteen reads something like "Demo..." and starts loading from internal flash memory. As I understand it I ahould not have to erase the internal sounds just to make them stop autoloading.
2. Pad sensitivity page (Other/Pad) reads garbage values.
"Pad sensitivity:???" (as in three question marks that wont change)
"Velocity curve:@" (this value can at least be changed to A, B C, D after scrolling through a bunch of other symbols)
This can't be right? Punching the pads does not get the bar-graphic higher than a few pixels so I would like to increse the sensitivity.
1/2. Half a bug... It is known that OS2.1 can mess up the levels of programs.. but that it messes up the internal (perpetually loading) demos so that nothing can be heard other than faint static was more than I had imagined.
So, gloat and tell me how simple these problem are... please... better that than a faulty sampler, right.



