Okay...... It's 10/01.

[monads]

I know. It's not like they didn't know the release wasn't coming up, an updated editor should be available as a simultaneous release when the bank/upgrade started shipping.

[c7sus]

Huh? I thought you wanted to buy the field upgrade as mentioned in your original post.

If you move quickly, you could probably receive the upgrade within a week. You save money (over the factory install), you don't have to ship your Vger anywhere, and you get the 'latest and greatest' OS and additional capabilities. Isn't that what you want?

I called Moog this morning. I was told that no 3.0 boards have been shipped to any individual owners, only to authorized dealers.

12/01/05 was the availability date I was given to purchase the DIY upgrade.

Reason given is a backlog from supplier.

[GregAE]

A few members here reported ordering boards earlier this week, so presumably Moog is shipping at least a few to individual owners.

Concerning the backlog, I guess anything is possible. The supplier could've been affected by the recent hurricanes, didn't get the parts they needed, experienced quality issues - could be a lot of things. Since the version 3.0 boards go into production Voyagers, any shortfall in supply would affect the availability of DIY kits first.

Not good news, but understandable.

Private note to my wife: A v3.0 upgrade kit would make a very nice Christmas present!




Greg

[monads]

Don't you need the new OS software to use the new V3.0 boards for DIY option? How does this work if some users ordered boards but the software isn't posted, shipped along with the DIY kit? I'm confused now....

[GregAE]

Don't you need the new OS software to use the new V3.0 boards for DIY option? How does this work if some users ordered boards but the software isn't posted, shipped along with the DIY kit? I'm confused now....

OS3 is pre-installed on the upgrade board, along with six banks of factory patches.

According to another post here, version 3 won't work in a non-upgraded Voyager. If true, this means the firmware upgrade path for non-modified Voyagers ends at OS2.5.



Greg

[spade490]

I just wanna be the first one on my block, ya know?

Oh, that's so nice!

[MarkM]

The above is another spammer. He's also had a worthless comment on the Piano Bar forum.

[OysterRock]

This board needs to switch to some other type of new member format. Like one that you have to respond to an email sent to you after signing up. Maybe this would help cut down on spam? Hello, Moderators!

[SoundTower_Help_Desk]

Does anyone know how and or if the editor will work with the upgrade? I guess I wont be able to switch banks with the editor.

Hi

Yes the editor will work with the upgrade and will allow switching.

Derek

SoundTower Help Desk

[email protected]

[SoundTower_Help_Desk]

It's time for a editor upgrade for sure.

...

I wish the Soundtower people would put some time into listening to Voyager owners and make things a bit more easy to use.

Hi

Upgrade coming with full implement all presets.

The implementation of the Help Desk was decided on just for the purpose of having an active ear for Voyager owners. If we have missed a few of our customer's comments over time - my apologies - we hope that this help remedy this oversight.


all the best

[sir_dss]

Awesome

[corkyburger]

I wish the Soundtower people would put some time into listening to Voyager owners and make things a bit more easy to use.

Just like they did with Evolver owners!

[till]

...
According to another post here, version 3 won't work in a non-upgraded Voyager. If true, this means the firmware upgrade path for non-modified Voyagers ends at OS2.5.

Greg, this is plain nonsense !
I got a non upgraded Voyager here running an 3.0 beta since 5 month and 3.1 version (since it was released by Rudi) for more then 4 months.

read my lips:
OS 3.0 and 3.1 do run fine on non upgraded Voyagers !

But to use the 7 bank of patch memory, you will need the new hardware version that is refered to as "3.0 update" here sometimes. Please don't mix the hardware upgrade with the OS upgrade. Actually, the hardware update better should have been named: "Patch Memory Extention (to be used with OS 3.0 or newer)"

[GregAE]

...
According to another post here, version 3 won't work in a non-upgraded Voyager. If true, this means the firmware upgrade path for non-modified Voyagers ends at OS2.5.

Greg, this is plain nonsense !
I got a non upgraded Voyager here running an 3.0 beta since 5 month and 3.1 version (since it was released by Rudi) for more then 4 months.

read my lips:
OS 3.0 and 3.1 do run fine on non upgraded Voyagers !

But to use the 7 bank of patch memory, you will need the new hardware version that is refered to as "3.0 update" here sometimes. Please don't mix the hardware upgrade with the OS upgrade. Actually, the hardware update better should have been named: "Patch Memory Extention (to be used with OS 3.0 or newer)"

Til -

That message was posted nearly two months ago, before any of us had good info regarding 3.X. We now know that 3.X runs on stock Voyagers, so comments about old postings such as these is moot.

Sounds as if you must have an NDC with Rudi. True?

Greg

[till]

Sorry, Greg,

but I didn't noticed the date of your posting.
I just noticed this thread came to the section of latest posting.

Sounds as if you must have an NDC with Rudi. True?

I think you know the answer by my other posting at this thread and the postings here at the forum during the days when the new OS was only available at Rudi's page.