Audirvana+ and AU plug-in problems

[aechmea]

Out of curiosity I downloaded the trial version of Audirvana Plus 1.5.latest which is supposed to allow AU plug-ins.  I particularly wanted to try the TT DR OnlineMeter plug-in so that I can watch some moving pictures whilst listening.

 

However 2 problems arose that you may be able to help me with.  Perhaps these are the way its supposed to be, then again maybe I have something wrong somewhere.

 

Some background.

MacBookPro (OSX10.6.maximum) ==> USB ==> Audiophilleo 1 ==> Coax ==> DEQX

Currently use Audirvana Free, which does all that I really want (no iTunes, simple playlist, no hirez, no DSD, but plays FLAC).

I believe that everything is set to 24/96 max.

 

1.  Audirvana 1.5 failed to produce a signal that the Audiophilleo recognised; resulting in silence.  There was no incoming signal display on the AP.  Checked USB connection (OK).  Rebooted (no change).  Removed Audirvana Free (no change).  Checked AudioMidiSetup (OK) (not that I expected that to work since it is largely bypassed by A+).  Eventually I started to remove 'features' in the A+ preferences panes.  By removing 'integer mode' music started as normal.  Neither type 1 nor type 2 integer mode seem to work with my AP1.  System 10.6 is supposed to allow integer mode.

 

I know integer mode is only handled by some DACs, but the AP is supposed to be one of the compatible ones.  I have Audirvana Free with integer mode set to 'on' and it works fine.

 

Why would the ancient free version work and the latest paid for version not?

Does the DEQX have to be integer mode compatible as well as the AP1?  If so why does integer mode work with Audirvana Free?

 

2.  A+ would not recognise the TTDROnlineMeter plug-in.  I downloaded a miscellaneous other AU plug-in from another developer and installed that (no problems).  It could be seen by A+ and worked fine.  Tried 2 versions of the TT plug-in (different sizes and dates in 2009; both labelled as v1.0).  The only difference that I could see between the plug-in that worked and the one that didn't was that the plug-in that worked was 'Intel' code and the TT one was 'universal' code.

 

Could it be that A+ will only recognise Intel-only coded plug-ins?  Could it be something to do with 32bit and 64bit architecture in the Mac or in OSX10.6 or in A+?

 

All a bit confounding.  Whoever said that computer audio is easy isn't reading from my script.

 

Anyone-else been here and done that?

[kdoot]

Whew, complex.

Couple of tidbits which might help.

1. "Integer mode" only goes as far is the USB audio device. What comes out SPDIF is the same data regardless.

2. You may be on to something with the 32/64 bit question. If you "Get Info" on the Audirvana+ app you can elect to open it in 32-bit mode. Maybe then your plugin will work.

[aechmea]

Thanks Kdoot, I pursued the 32bit lead.

 

Some good news and some bad news.

 

Switched Audirvana+ to 32 bit mode.  The TT plug-in can now been seen and configured. Unfortunately though it won't display a realtime window.  Then after about 30 seconds A+ freezes.  So even though 32bit mode allows a tiny bit of function, it doesn't really work.  Also, in 32bit mode A+ seems to lose track of its file play list and is unable to locate files.  So all in all, 32bit is best forgotten.

 

There is a certain set of circumstances when plugging in the Audiophilleo, where it is not recognised by the Mac or vice versa and USB communication is not established.  The lights are on and everything looks OK, but they just aren't talking.  I expect that it is something to do with 'sleep' mode timing in the PP hardware/firmware or Mac.  Disconnecting the USB cable, waiting for say 15 seconds and then reinserting seems to re-establish a connection.  However in the meantime A+ has automatically switched to alternative audio devices when it couldn't find the AP, and I suspect that integer mode is switched off or goes into limbo or is generally stuffed.  Even after real communications are re-established things must be still a bit confused in A+.  The only clean way out seems to be to start all over again - ie. reboot Mac with USB devices pre-connected; then start A+.  Its all just a bit too fragile for my liking.

 

So the problem is not that integer mode won't work per se, but that it is a bi-product of USB communication problems before that.

 

Now I have an AudioMidiSetup window open to ensure that the AP is properly connected before starting A+ - a bit messy but seems to allow things to work as expected.

 

Thanks again for the hint.

[kdoot]

Is your AP1 firmware up to date?

Is your Mac running 10.6.8 with no outstanding firmware updates of its own to do?

[aechmea]

Hi Doot.

 

Sorry about the delay - was away yesterday trying to avoid the fires and smoke.

 

The Pure Power firmware is up-to-date.  I suspect that the firmware in this is what answers the Mac during USB negotiation - but not sure at all.

The Audiophilleo itself is 1 behind.  The latest is quite new and appears to be for an 'se' model???

The Mac is up-to-date.

 

It all worked perfectly this morning when I switched it on for a look-see.  So I don't know what the set of circumstances are that caused my problems.

 

I can remember another post earlier this year when a new AP owner with Mac couldn't get it to work.  I advised him to start again ie. the re-connect re-boot etc.  He replied that that corrected his problem.  Now it has happened to me, so there must be some particular sequence of events that causes this.  But what.  I'm now on the look-out for clues.

 

[i like the sound when doubled to 88.2.  Close enough to identical to the 88.2 out of the MSB transport.

Running all sorts of applications beside A+ seems not to make any difference.

Using the AC adapter on the MacBookPro seems not to make any difference.

Using a USB drive for the music files seems not to make any difference.

Is it worth paying for, compared to the free version? - that, I am not sure of - but I'll probably buy anyway to encourage the developer.

Still prefer to play CDs, though.  Computer audio is too fiddly.]