Jump to content
IGNORED

Audirvana Plus 3.5


Recommended Posts

If you are upsampling better put memory to 1024mb instead of higher, go low...

If You Got Ears, You Gotta ListenCaptain Beefheart

 

MacMini 2018, 4xi3 3.6GHz, SSD, 20Gb, macOS Sonoma > Audirvana Origin >

Wyred DAC2 DSD Special Edition > Proceed AMP2 > Focal Cobalt 826 Signature Series >

Audirvana Remote > iPhone 13

Link to comment
On 7/5/2019 at 9:39 PM, Russell_L said:

Not sure if this has been mentioned before, or if it’s even an issue for others, but scrolling in the main library window is not smooth at all, with lots of delays and hesitations as the window refreshes with all the album covers. This has been an issue for me with all iterations of 3.5 (and not a problem with 3.2.x). Now admittedly I’m using an oldish laptop (early-2011 MBP, High Sierra) but the scrolling should be smoother than this, I think.

 

Otherwise, I’m pretty satisfied with 3.5!

Same here, 3.5 looks great, but it's pretty slow in displaying the album covers when scrolling. I'm running El Cap. 

Link to comment

I also have found the main A+ 3.5 interface to be extremely sluggish.  I don’t think its a RAM issue, but rather a fault with the programming.  Both Roon and iTunes perform flawlessly in this regard on my same MacBook Pro, and Roon has far more eye candy than Audirvana.  I have a RAM meter which indicates there is plenty of leftover RAM when A+ is in use.  Hopefully Damien will fix this issue soon, as A+ is otherwise quite good.

Link to comment

Re: scrolling

 

If I can generalize from my own limited experience.

 

I have Audirvana 3.5.14 loaded on two Macbook Pros.  I find the speed of loading and scrolling is very dependent on which computer I use.  I use a 2009 MBP with a 2.56 GHz core 2 duo CPU and 8GB RAM as my music server.  Audirvana is slow to load (minutes) and slow to scroll (jerky) with tracks often stopping in progress unless this computer has been restarted before loading Audirvana.

 

My 2017 MBP uses a 2.86 GHz core i& CPU and 16 GB RAM.  Audirvana loads almost instantly with smooth scrolling.  Tracks do not stop short.

 

I use the same 1T SSD for music storage with either machine, so this hard drive doesn't contribute to the scrolling and stoppage issues, CPU speed and RAM do.  There could very well be other factors.

Link to comment

The current incarnation of A+ may be more cpu and RAM intensive. But the question is why?  Roon has way more eye candy and visual thrills, and iTunes packs a lot of graphics in.  So if those two operate fine on a given older machine, the question is why does A+ need so much more power for it’s updated look?  Following that reasoning, I feel it must be because of how A+ is programmed given the other two provide as much, or more visuals without the same need for power. I’ve run Roon for over a year, scrolling and loading is smooth and quick. 

Link to comment
11 hours ago, DPS said:

Re: scrolling

 

If I can generalize from my own limited experience.

 

I have Audirvana 3.5.14 loaded on two Macbook Pros.  I find the speed of loading and scrolling is very dependent on which computer I use.  I use a 2009 MBP with a 2.56 GHz core 2 duo CPU and 8GB RAM as my music server.  Audirvana is slow to load (minutes) and slow to scroll (jerky) with tracks often stopping in progress unless this computer has been restarted before loading Audirvana.

 

My 2017 MBP uses a 2.86 GHz core i& CPU and 16 GB RAM.  Audirvana loads almost instantly with smooth scrolling.  Tracks do not stop short.

 

I use the same 1T SSD for music storage with either machine, so this hard drive doesn't contribute to the scrolling and stoppage issues, CPU speed and RAM do.  There could very well be other factors.

 

You'll want to defragment your database by using the command in the Maintenance section of the preferences page.

MBP 15"/Mac Mini, Audirvana Plus, Audioquest Diamond USB, AMR DP-777, exD DSD DAC (for DSD), Pioneer N-70AE, Audioquest Niagara balanced/Viard Audio Design Silver HD, Accuphase E-560, Cabasse Sumatra MT420

Link to comment
22 hours ago, damien78 said:

 

You'll want to defragment your database by using the command in the Maintenance section of the preferences page.

 

Thanks for the idea.  It seemed to fix the sluggishness initially, but after music was played, and then stopped, the sluggishness returned to an almost unstable extent.  Plenty of RAM, so its something else....  It took several minutes just to load a playlist....

Link to comment
5 hours ago, speavler said:

Gli artisti delle maree non si caricano completamente sul telecomando A +, rendendo l'integrazione di Tidal inutile per me. C'è una soluzione?

Me too Tidal does not load over the 50 covers on the remote app, but the annoying problem is the pause of the tracks at the end of the song.

iMac,Audirvana,Ampli-Dac RME ADI-2, Marantz SA-KI Pearl Lite, Primaluna PLTwo, Sennheiser HD800S e Focal Utopia, Adam S3V.

Link to comment

I enjoy the sound of 3.5+ quite a bit, and the new look interface is very nice.  But it has been so sluggish, even after defragging per Damien’s recommendation.  Local library is slow, Tidal is slow, and searching is slow.  For a search, I enter in a name and come back 5 minutes later to see if the result has appeared yet.  And the remote has many of these types of issues as well.

 

Is it possible to have the option to maintain the SQ of 3.5 but use the more simple pre 3.5 interface?  As much as I like the eye candy, and Roon has spoiled me this way, but I’d gladly sacrifice looks in A+ 3.5 in favor of smooth operation.

 

While I never thought I’d say this, and get a lump in my throat doing so, but for me currently, Amarra Luxe is less buggy than A+.....

Link to comment
1 hour ago, DancingSea said:

I enjoy the sound of 3.5+ quite a bit, and the new look interface is very nice.  But it has been so sluggish, even after defragging per Damien’s recommendation.  Local library is slow, Tidal is slow, and searching is slow.  For a search, I enter in a name and come back 5 minutes later to see if the result has appeared yet.  And the remote has many of these types of issues as well.

 

I'm thinking there has to be some sort of interaction going on with your setup. 

 

Now I've only got 10,000 or so tracks, and lots of people have many times more albums than that.  (I've only ripped about 10% of my collection - the rest will wait until a spare moment or until I retire.)  But using a mid-2009 MacBook Pro that's running a patched version of Mojave - so surely an underpowered situation compared to just about everyone else here - searches in 3.5 are instant.  Scrolling is just very slightly hesitant (with local library, though not Qobuz), but I'm sure that's due to the ancient hardware running a patched OS.

 

I assume you have more modern hardware, but might be dealing with more content.  AFAIK, there are people with more than 100K albums running Audirvana without issue.

 

Obviously this isn't helping your current situation.  But I don't think the UI slowness is something inherent in Audirvana itself.

One never knows, do one? - Fats Waller

The fairest thing we can experience is the mysterious. It is the fundamental emotion which stands at the cradle of true art and true science. - Einstein

Computer, Audirvana -> optical Ethernet to Fitlet3 -> Fibbr Alpha Optical USB -> iFi NEO iDSD DAC -> Apollon Audio 1ET400A Mini (Purifi based) -> Vandersteen 3A Signature.

Link to comment
4 hours ago, Jud said:

 

I'm thinking there has to be some sort of interaction going on with your setup. 

 

Now I've only got 10,000 or so tracks, and lots of people have many times more albums than that.  (I've only ripped about 10% of my collection - the rest will wait until a spare moment or until I retire.)  But using a mid-2009 MacBook Pro that's running a patched version of Mojave - so surely an underpowered situation compared to just about everyone else here - searches in 3.5 are instant.  Scrolling is just very slightly hesitant (with local library, though not Qobuz), but I'm sure that's due to the ancient hardware running a patched OS.

 

I assume you have more modern hardware, but might be dealing with more content.  AFAIK, there are people with more than 100K albums running Audirvana without issue.

 

Obviously this isn't helping your current situation.  But I don't think the UI slowness is something inherent in Audirvana itself.

 

Could be.  I have a 2013 MacBook Pro running the latest Mojave.  My library is around 40K songs or so.  Roon handles it no problem, so does iTunes.  Audirvana is super slow, like it is for others in this thread.  I’m in no position to say why, only that it is.

 

Not only slow.  For instance, if I’m playing a Tidal playlist and use the A+ remote to skip ahead to not the next track, but a track several tracks away, A+ plays an entirely different song, and from that point forward, continues to play different songs than are displayed on the remote.  The desktop A+ doesn’t do this.

 

Just have been lots of issues.

Link to comment

Hi! New problem here, occurred suddenly today, without any changes that I’ve made to my knowledge. Audirvana 3.5.13 was running fine, then today, suddenly crashes immediately on startup. Even before audirvana page is loaded. It is immediate.

I updated to 3.5.14 thinking that might help, still same behaviour.
I trashed all the prefs, cache, launchdaemons etc., as instructed on the forums and reinstalled. Same behaviour

I’m on imac macOs mojave 10.14.5, 24gb of RAM.

Again, to my knowledge, it was working fine yesterday, and suddenly today, crashes immediately after clicking on the icon.

Here is the crash report:

Process: Audirvana [626]
Path: /Applications/Audirvana.app/Contents/MacOS/Audirvana
Identifier: com.audirvana.Audirvana
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Audirvana [626]
User ID: 501

Date/Time: 2019-07-13 01:53:54.345 -0400
OS Version: Mac OS X 10.14.5 (18F132)
Report Version: 12
Anonymous UUID: 09E5A248-D393-4ED9-2A0F-6B376BD5EAAF

Time Awake Since Boot: 37 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x1

kernel messages:

VM Regions Near 0 (cr2):
–>
__TEXT 0000000100000000-0000000100c14000 [ 12.1M] r-x/rwx SM=COW

Thread 0 Crashed:
0 0x000000010df96000 _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffeefbffbf0
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x000000010df96000 rfl: 0x0000000000000200 cr2: 0x0000000000000000

Logical CPU: 0
Error Code: 0x00000000
Trap Number: 0

Binary Images:
0x100000000 - 0x100c13f27 + (0) <84A97B15-178A-3697-ADF4-C8BD2B80B101>
0x10df95000 - 0x10dfff6ef + (655.1.1)

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 2
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=13.0M resident=0K(0%) swapped_out_or_unallocated=13.0M(100%)
Writable regions: Total=8444K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8444K(100%)

                            VIRTUAL   REGION 

REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
STACK GUARD 56.0M 1
Stack 8192K 1
__DATA 852K 4
__LINKEDIT 532K 2
__TEXT 12.5M 2
shared memory 8K 2
=========== ======= =======
TOTAL 77.9M 12

Model: iMac17,1, BootROM 166.0.0.0.0, 4 processors, Intel Core i5, 3.2 GHz, 24 GB, SMC 2.33f10
Graphics: kHW_AMDRadeonR9M390Item, AMD Radeon R9 M390, spdisplays_pcie_device, 2 GB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x484D54343531533642465238412D52442020
Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1867 MHz, 0x85F7, 0x48363431475536374733313836470000
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x484D54343531533642465238412D52442020
Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1867 MHz, 0x85F7, 0x48363431475536374733313836470000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x14A), Broadcom BCM43xx 1.0 (7.77.61.2 AirPortDriverBrcmNIC-1305.8)
Bluetooth: Version 6.0.12f1, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: APPLE SSD SM0256G, 251 GB
USB Device: USB 3.0 Bus
USB Device: My Book 1230
USB Device: 4-Port USB 3.0 Hub
USB Device: 4-Port USB 3.0 Hub
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
USB Device: 4-Port USB 2.0 Hub
USB Device: LE850G
USB Device: 4-Port USB 2.0 Hub
USB Device: D50
Thunderbolt Bus: iMac, Apple Inc., 28.1

Link to comment
22 hours ago, Jud said:

 

I'm thinking there has to be some sort of interaction going on with your setup. 

 

Now I've only got 10,000 or so tracks, and lots of people have many times more albums than that.  (I've only ripped about 10% of my collection - the rest will wait until a spare moment or until I retire.)  But using a mid-2009 MacBook Pro that's running a patched version of Mojave - so surely an underpowered situation compared to just about everyone else here - searches in 3.5 are instant.  Scrolling is just very slightly hesitant (with local library, though not Qobuz), but I'm sure that's due to the ancient hardware running a patched OS.

 

I assume you have more modern hardware, but might be dealing with more content.  AFAIK, there are people with more than 100K albums running Audirvana without issue.

 

Obviously this isn't helping your current situation.  But I don't think the UI slowness is something inherent in Audirvana itself.

 

The same here, Audirvana running without problems, under Mojave !

 

What I have found over the years, is that it is not the best to run the different audio players within the same HD.

 

What I do is have several partitions within the HD, each with the audio player that I want to evaluate, thus avoiding any possible interaction between the different audio players.

 

I consider that at least, when changing from one audioplayer to another there must be a restart of the PC, in case the partitions that I mentioned are not used.

 

I have also found that sometimes it is necessary to relate a clean OS installation.

 

Roch

Link to comment
19 hours ago, DancingSea said:

 

Could be.  I have a 2013 MacBook Pro running the latest Mojave.  My library is around 40K songs or so.  Roon handles it no problem, so does iTunes.  Audirvana is super slow, like it is for others in this thread.  I’m in no position to say why, only that it is.

 

Not only slow.  For instance, if I’m playing a Tidal playlist and use the A+ remote to skip ahead to not the next track, but a track several tracks away, A+ plays an entirely different song, and from that point forward, continues to play different songs than are displayed on the remote.  The desktop A+ doesn’t do this.

 

Just have been lots of issues.

 

Notice I'm not saying anything like "Oh yeah, this must be your problem because...." It just appears you've been 'lucky' enough that something in your setup interacts badly with Audirvana. Would love to know what it is (I'm sure you would too), since as you say the sound is really nice.

 

Perhaps start by using only your largest music volume/directory with 3.5, and add until you have a problem?

One never knows, do one? - Fats Waller

The fairest thing we can experience is the mysterious. It is the fundamental emotion which stands at the cradle of true art and true science. - Einstein

Computer, Audirvana -> optical Ethernet to Fitlet3 -> Fibbr Alpha Optical USB -> iFi NEO iDSD DAC -> Apollon Audio 1ET400A Mini (Purifi based) -> Vandersteen 3A Signature.

Link to comment
27 minutes ago, Jud said:

 

 

Perhaps start by using only your largest music volume/directory with 3.5, and add until you have a problem?

 

Yes, I agree, would be nice to know what’s going on.  To my way of thinking, and it may not be entirely correct, but if the same library is handled easily on my system by iTunes, Roon, Swinsian and Amarra, then its difficult to think of my system or library as being the problem.  This same logic applies to those of you who have no problem running A+ on Mojave, and therefore the problem can’t be A+, it has to be my system.

 

My counter would be that the onus is on A+ to smoothly on a variety of systems.  My Mac is stripped down and is pretty much music only.  But still, none of us have the exact same system, and if there is some peculiar interaction with my system and A+, its at some relatively esoteric level beyond the casual user.

 

Which leads me to conclude that Roon, iTunes and Swinsian are better programmed than A+ when it comes to the aspect of broader compatibility with a variety of, in this case, Mac systems.  I’m purposefully setting aside Amarra, because I’m sure it will act up soon enough.

 

A search in Roon, iTunes and Swinsian yields instantaneous results.  Using the same system that A+ lumbers with.  I’ve done Damien’s defrag routine, using Onyx, my Mac’s maintenance is totally up to date.  I paid my $75 for 2.6 + $40 upgrade to 3.5.  While willing to do whatever else I can, I’m remain settled that this is more a limitation of the new 3.5 UI than anything else as previous versions were not sluggish.  And its Damien’s responsibility to provide a fix!

 

 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...