soundtower editor problem 3.4.1

cant get editor to receive/request patches from voyager, but have add configurations set properly, moog set to receive sysex, audio midi patched in osx, cables patched (obviously lol) everything seems right but it is dead no response at all, even when clicking on some of the presets within the editor, have some other soundtower products which are buggy to say the least but still work. am i missing something? read help file and tried other settings. still nothing. maybe it doesnt work with 10.5 leopard?

osx 10.5.5

editor 3.4.1

VGR os 3.4

Have you tried SysEx Libarian to receice and sned Voyager sysex data to check your interface and connection?

Is the SysEx divice ID set to the same number (“1” being the normal usage setting unless you own several Voyagers or RMEs)?

no, good idea. ill try that and post results

ok tested it with sysex librarian, works on both send and receive. Is anyone else using osx 10.5.x leopard with the soundtower editor? Ive emailed the tech support but they are very slow to respond.

I recently got my Voyager back from it’s 3.4 upgrade, so I purchased the Soundtower librarian software for my mac to manage the presets. I am running OS X 10.5.6 and using a MOTU micro lite Midi interface. I used SysEx Librarian to transmit presets from the Moog to the Mac and it worked like a charm. However, the Librarian software simply DOES NOT WORK when I try to retrieve presets or banks. I can transmit to the Moog, but the preset doesn’t get updated on it and I can play the moog keyboard with the V Piano.

I have contacted soundtower and they gave me version 3.4.3 to download but the problem remains. I am beginning to wonder if I wasted $79 on this software.

The Little Phatty forum is filled almost to the brim of Soundtower suckage posts. I don’t know about the Voyager editor, but the LP editor has a new programming company. the new (hopefully improved) editor for the LP will be out later this year. Again, not sure about the Voyager editor. :confused:

I found a Workaround. I downloaded version 3.0 for the Mac and this version works fine. I guess they broke something with the upgrade.

Wouldn’t surprise me a bit. :unamused:

Well almost two weeks, no response from soundtower after three emails. what a waste of money! i hate to say it but since we bought the software from moog, i think they are “partially” to blame as well; obviously its not their software but they should lean on this guy to get his act together and be more responsive to users who are using the software and having issues- not cool. Even a short note letting me know a timeline in getting back to me would be ok.

Thats like going to a store, buying something that doesnt work and trying to return it to the store and it being locked 24-7

anyways… i still love my moog!

Yep…heard it all before on the LP forums. Amos has had numerous conversations with Soundtower, and has had even more failed attempts to get ahold of them. :unamused:

I was once told that Soundtower is only a project done by someone with a full day-time job somewhere else. And that he is not able to react all the time.

“SoundTower prides itself in providing excellent support to all users of our programs, musicians and studio professionals since 1995. We try to be available at all times to answer questions that you may have.” From soundtower tech support page

TILL:
good to know, just wanted other users to know what to expect if they run into issues and are expecting a timely response. I defintely wouldnt have bought the software if i read a post like this…

Have you tried version 3.0? That seems to work (for me at least)

Moog have been helpful to me regarding my problem with 3.4.x and advise that Soundtower are ‘working on a new version’.

I’ve had this problem under OS X Leopard as well - Intel MacBook Pro, Voyager 3.4 OS, and I’ve tried 3.4.1 and a patched version. Libraries aren’t received but there’s no change in the Sysex traffic.

I think the fault may lie with changes to Apple’s CoreAudio framework - dim and distant memory suggests that certain parts were being brought up to date to remove deprecated code. When the problem first appeared they were very helpful and quick to respond so perhaps they’re working on it having isolated that the problem DOES exist rather than being a single user’s issue.

Frankly, I think Apple have really cocked up CoreAudio - the MIDI framework promises OMS-like flexibility and delivers nothing like it.

But many other programs still work fine under OS X Leopard.

I think the problem is the RealBasic compiler or the needed Midi plug-in for RealBasic. The plug-ins were changed a lot from Moog Voyager.app version 3.0.0 to 3.1.0

nope but ill give it a go shortly and see if that resolves my problems. im sure there might be other bugs though since that is an older version. did you find the installer on the soundtower site? or somewhere else?

thx

I did a search for it on Google and got a link.

Soundtower just sent me V3.4.4 to try. I haven’t had a chance to test it yet, hopefully I can try tonight and I will let you know the result.

this issue has apparently been fixed in the latest (released today) soundTower voyager editor.

Download it here… http://www.moogmusic.com/voyager/?section=product&product_id=21257 for PC

And here… http://www.moogmusic.com/voyager/?section=product&product_id=21258 for Mac

issue still exists on my setup. i am using a motu midi express 128. has anyone else been able to get it to work on 10.5.5 and above?

still NO response from soundtower after close to a month now, their tech support officially sucks in my book


R

I was out of town and I finally had time to come back and test the latest patch 3.4.4 that Soundtower sent to me.

Transmit/receive work perfectly again. So that’s both V3.0 and V3.4.4 that work for me on OSX 10.5.6.