I just flipped on my Voyager (Performer Edition) and the LCD screen is totally black.. that is to say, it’s on and emitting lights, but all the pixels are activated. Everything else seems to be working fine.
Any ideas on what might have casued this and how to fix it?
Qwave could be right about the contrast thing, although I wonder how the contrast got screwed up if you didn’t do anything to it.
You may have to adjust the contrast ‘blind’. Here’s how:
Power up the Voyager.
Press the MASTER button. (The menu defaults to 1.1 - LCD contrast on power-up)
Press the ENTER button.
If the LCD is completely black, the contrast is set to the maximum negative value. Press the +1 button repeatedly. This will adjust the value towards the positive. You should begin to see a change in the contrast after just a few button presses. If the LCD is completely blank, the contrast is set to the maximum positive value. Press the -1 button repeatedly. This will adjust the value towards the negative.
If this doesn’t do the trick, definately contact Moog for assistance. Good luck!
I have to agree. A lot of high-quality stuff goes into a Voyager but the computer’s display and buttons are pretty chintsy. It’s like they cut corners on the most inexpensive component.
I was twiddeling some knobs and suddenly the display went black.
The display is still working but all the pixels are now ‘on’.
So I tried to fix it,by adjusting the contrast but now, it still has all the pixels on butt less.
Before the contrast level was arround -9 and perfect.
Now I had to put it on 2 and I can still see the whole pixel area ‘on’ in the background.
What can I do?
Can I keep on making music with it without damageing the machine until then?
Sure, I forgot the reason - I guess the Recall function clears the memory location of the LCD contrast. Not more - don’t use the Recall function and wait for the next update and:
Have fun,
Rudi
My screen when blank/all black and it was a biatch to find the contrast function in the dark. I’m running 3.0 right now. Should I upgrade to 3.2 for sure? What about storing my patches? Will they transfer. I have the editor but I hear it doesn’t work right with 3.2. Is this correct? I would like to get the bug fixed cuz I gig with my mme and I dont want to have to fix it mid set!! Please help.
You should upgrade to OS 3.2. Your patches will be fine, but I’d recommend archiving them before you do the upgrade just in case.
I assume your comments are about the Macintosh version of the Editor. There were a few problems with the Mac version, but SoundTower has fixed this in V2.01 and everything seems to be working fine.
Here are the details (copied from the SquareWave site):
SoundTower has posted an update to the Macintosh version of the Voyager Editor. This update (v2.01) has fixed the two issues reported by members:
Load User Bank files - You can now load your saved User Bank (.mvr) files.
Note: The .mvr file will always load into the bank it was saved from. This is important for those with the Voyager’s expanded memory option. For example, if you save Bank A, that .mvr file will go back into Bank A when you load it. For this reason, you should add a bank designation to the file name:
Example: My_Bank_A.mvr
The WRITE command now works correctly independent of the USE LOADED DATA checkbox status.
Also, go to the SquareWave site and download the latest Voyager OS Menu Reference Page. It’s a very handy resource and would have been a big help to you for resetting the Voyager display contrast ‘blind’. You can find it here:
Files/Voyager Reference Pages/OS 3_2 Menu Reference.zip