Audirvana Plus 3.5

[bnbayer]

Several people seem to have had syncing problems solved by 3.5.7 -  that's great! Unfortunately, I didn't have any syncing problems until 3.5.7, but now I'm missing probably 1000 albums.  Quite a number of them were albums I just played yesterday with 3.5.6, but that's probably a coincidence.

 

A very strange thing (to me, at least), is that when I quit 3.5.7 and tried opening 3.2.16, it was now missing the same albums.

 

I have tried quitting and re-syncing, and I've tried throwing away Library files (the database and preferences com.audirvana.Audirvana.plist) but no change. I think I missed something, though, as I didn't have to re-enter my license code. It did say it needed to migrate my database to the new version [again], however if it was taking the 3.2 db, that was missing the same albums.

 

What else do I need to try to get it to sync my whole library?

 

[DSD256]

3.57 killed my whole library. at start it says 3 migration needs to be made...click, but no library at all.

[DSD256]

 

A look at under library/application support/audirvana reveals the AudirvanaPlusDatabaseV2.sqlite has gone and is now 256kb, formerly 2,6GB. Copied a backup to this direction and now Audirvana finally sees my library again.

[bnbayer]

Another anomaly - not as serious as the missing albums, but indicative of some database malfunction: Sorting by "Last Played Date", I get the tracks I played yesterday (04/05/2019), then it jumps back a month, to 17/04/2019. In fact it was played AT LEAST 5 hours every day, so a bunch of data is lost. One symphony (13 tracks) I played on Friday evening, but it shows last played on 18 March. I'm sure it was played another couple of times between March and Friday as well, but that data is lost.

[OldBigEars]

On 5/3/2019 at 8:07 PM, OldBigEars said:

whenever I open up the home screen the columns are all messed up.  the library column on the left is invisible and the filter column on the right is half the entire screen.  first thing I have to do is adjust the screen, every time....wtf?

 

I'm sure there's a solution - just let me know, thanks

 

 

Just wondering if anyone can suggest why - whenever I restart A+ - the left hand side of the page (with the library, Tidal etc) is minimalized?  And the right hand side with the filters is extended to the whole right half of the screen.  So every time I turn on have to reset the home screen settings.

 

How do you set it so that it opens up in the 'normal way' ?  Thanks.

[alfamatt]

Given up on 3.5. Gone back to 3.2.16 & the issue, where several albums were split into most tracks one one album with 2 or 3 songs on another copy has gone.

Shame, but 3.5, even the latest version had too many bugs in it for me. Several hours of checking settings, re-syncing the library etc etc did not cure it.

Change for changes sake.

[Jud]

1 hour ago, alfamatt said:

Change for changes sake.

 

Many people experienced actual favorable changes and liked them. Quite sorry that didn't happen for you, because I feel the new version is excellent.

[alfamatt]

Point taken.

 I’ve  been an Audirvana user for a fair few years now. Always preferred it to the competition.

However, my tolerance for “one step forwards, Two steps backwards” is pretty limited.

Even if the newest iteration sounded better, if it mucks up the library & I can’t get it sorted out after a few good hours of trying, it’s not for me.

Disappointing & frustrating in equal measure.

[jimdukey]

"if it mucks up the library."

 

In Artist/Album View, mine is fine.

If I add a File to my Music Folder, ( Mac ), it appears on AV.

And Vice-Versa.

I don't have to Do anything, it's automatic.

 

[phosphorein]

I’ve encountered a strange condition with 3.5.7 when using the iOS app to search in Qobuz. After making a selection from the search results the screen goes dark with “loading” logo and never completes. Meanwhile Audirvana on the Mac (Mojave) freezes and continues playing until the memory is exhausted. The app must be restarted. I do not encounter this when searching in Tidal with the IOS app nor in Qobuz with the Mac app. I did not encounter this with 3.5.5.

 

[Jud]

1 hour ago, alfamatt said:

Point taken.

 I’ve  been an Audirvana user for a fair few years now. Always preferred it to the competition.

However, my tolerance for “one step forwards, Two steps backwards” is pretty limited.

Even if the newest iteration sounded better, if it mucks up the library & I can’t get it sorted out after a few good hours of trying, it’s not for me.

Disappointing & frustrating in equal measure.

 

Absolutely, I wasn't arguing at all with your experience, just disappointed along with you that it wasn't better, as mine and others' have been.

[Jud]

On 5/4/2019 at 2:24 PM, Nico said:

Do you ask me or Damien?

I am not sure about your question - but in 3.2 the PlayQueue never was sortable in any way and that was good so. Drag&Drop was perfect in 3.2.

 

Apologies, my mistake - the preference setting I remembered was to sort manual playlists, not (I assume) the PlayQueue.

[Piano Man]

1 hour ago, phosphorein said:

I’ve encountered a strange condition with 3.5.7 when using the iOS app to search in Qobuz. After making a selection from the search results the screen goes dark with “loading” logo and never completes. Meanwhile Audirvana on the Mac (Mojave) freezes and continues playing until the memory is exhausted. The app must be restarted. I do not encounter this when searching in Tidal with the IOS app nor in Qobuz with the Mac app. I did not encounter this with 3.5.5.

 

 

I have encountered the same freeze problem during Qobuz search on the remote app running on an iPad, controlling 3.5.7 on a Mac Mini with El Capitan.

[Piano Man]

Nevertheless, I very much appreciate the 3.5 version, in particular for it's greatly improved search in Qobuz. Bravo!

Although sound is the highest priority for most of us here, I can fully understand the approach to focus on the user interface for this update to compete with the iTunes Remote App and to attract more customers.

I am confident that library import issues (which I didn't encounter or realise yet) and the freeze problem will be solved.

I don't hear a significant change in sound compared to 3.2.x, probably since I still stick to iZotope with gentle filter steepness and a somewhat lower bandwidth. Thanks for keeping iZotope. To me it sounds more pure, cleaner though a bit less brilliant than SoX with standard settings. Didn't play with the SoX filter settings yet, but if I understand correctly, you cannot directly choose filter steepness there...

[jamesg11]

1 hour ago, Jud said:

 

Absolutely, I wasn't arguing at all with your experience, just disappointed along with you that it wasn't better, as mine and others' have been.

I also immediately liked the 3.5 sonics. I had been largely using hqp to dsd256 & I now prefer my pcm in A3.5 - but not the dsf64 files which I understand still just play as is (no upsampling?) ... /& I have a huge amount of them.

[Jud]

15 minutes ago, Piano Man said:

but if I understand correctly, you cannot directly choose filter steepness there...

 

See what the anti-aliasing setting does for you.

[pdvm]

I like the sound of 3.5, but I don't like the new interface at all. Look at all the real estate in the older version. You could actually read the whole title of a track.

 

Now look at the new thing. How much less information is visible. Why does everything need to take so much space? Why is there a 'cover flow' thingy right where track information should be? Why are the 'hidden' play/favorite/more options buttons taking up almost a quarter of the remaining horizontal space, where, again, track information should be visible? What's playing? I guess there's a 1-by-1 inch box in the lower left corner where, if you concentrate for 30 seconds, you can decipher the full title of a track, as it scrolls by. Why are all the play/next/stop buttons a different size?

I love Audirvana, but I don't like this Spotify-like UI at all. Please, Damien, don't turn it into Spotify.

[Nico]

1 hour ago, pdvm said:

I like the sound of 3.5, but I don't like the new interface at all.

+1 same here.

When working with tracks, much more mouse action and scrolling is necessary than with 3.2.

[Marten]

I have 4 NAS drives with music. 
Two of them are in the settings on AUTO and the others on MANUAL.
All drives are playing music but I can't sync these MANUAL drives.
What to do?

[bnbayer]

2 hours ago, pdvm said:

I like the sound of 3.5, but I don't like the new interface at all. Look at all the real estate in the older version. You could actually read the whole title of a track.

 

Now look at the new thing. How much less information is visible. Why does everything need to take so much space? Why is there a 'cover flow' thingy right where track information should be? Why are the 'hidden' play/favorite/more options buttons taking up almost a quarter of the remaining horizontal space, where, again, track information should be visible? What's playing? I guess there's a 1-by-1 inch box in the lower left corner where, if you concentrate for 30 seconds, you can decipher the full title of a track, as it scrolls by. Why are all the play/next/stop buttons a different size?

I love Audirvana, but I don't like this Spotify-like UI at all. Please, Damien, don't turn it into Spotify.

 

+1

[GrahamH]

5 hours ago, pdvm said:

I like the sound of 3.5, but I don't like the new interface at all. Look at all the real estate in the older version. You could actually read the whole title of a track.

 

Now look at the new thing. How much less information is visible. Why does everything need to take so much space? Why is there a 'cover flow' thingy right where track information should be? Why are the 'hidden' play/favorite/more options buttons taking up almost a quarter of the remaining horizontal space, where, again, track information should be visible? What's playing? I guess there's a 1-by-1 inch box in the lower left corner where, if you concentrate for 30 seconds, you can decipher the full title of a track, as it scrolls by. Why are all the play/next/stop buttons a different size?

I love Audirvana, but I don't like this Spotify-like UI at all. Please, Damien, don't turn it into Spotify.

+1

[pdvm]

Also, I'd like to report that version 3.5.7 crashes a lot, usually when I press the stop button or try to play another album when something is already playing.

 

My macbook is a retina 13inch late 2013 with 4GB RAM running macOS 10.14.4, no other programs save Safari running simultaneously with A+.

[Don Blas De Lezo]

47 minutes ago, pdvm said:

Also, I'd like to report that version 3.5.7 crashes a lot, usually when I press the stop button or try to play another album when something is already playing.

 

My macbook is a retina 13inch late 2013 with 4GB RAM running macOS 10.14.4, no other programs save Safari running simultaneously with A+.

 

+ 1.  I am having same problem ... worked perfect with 3.5.6 and before.  Crashes almost after every album ... app does not shut off ... just everything stops working like searching in Qobuz or playing next album and then works again after restarting App .

( macOS 10.13.6 )

[Cornell77]

Is anyone upsampling 44.1kHz (Tidal) to DSD256 on Audirvana 3.5 without issue?

 

I had been running a 2009 MacBook Pro  and upsampling successfully to DSD128.  I am now using a 2017 MacBook Pro I5 w/ 2.4 KabyLake processor and hoped to be able to upsample to DSD256.  But I have intermittent dropouts and pops. The dropouts are roughly every 30 seconds or so.  I haven't found any settings of Izotope or Sox that solve the problem.  My latest Izotope settings are:

 

Steepness     150dB

Filter Length 1,000,000

Cutoff freq    1x Nyquist

Antialiasing   200

Pre-ringing     0.75

Filter type      C

Safe vol         -4db

 

When running activity monitor, I see that the CPU is about 63% used and 37% idle. Is my new MacBook still too under-powered for DSD256 upsampling?

 

 

[Jud]

15 minutes ago, Cornell77 said:

Is anyone upsampling 44.1kHz (Tidal) to DSD256 on Audirvana 3.5 without issue?

 

I had been running a 2009 MacBook Pro  and upsampling successfully to DSD128.  I am now using a 2017 MacBook Pro I5 w/ 2.4 KabyLake processor and hoped to be able to upsample to DSD256.  But I have intermittent dropouts and pops. The dropouts are roughly every 30 seconds or so.  I haven't found any settings of Izotope or Sox that solve the problem.  My latest Izotope settings are:

 

Steepness     150dB

Filter Length 1,000,000

Cutoff freq    1x Nyquist

Antialiasing   200

Pre-ringing     0.75

Filter type      C

Safe vol         -4db

 

When running activity monitor, I see that the CPU is about 63% used and 37% idle. Is my new MacBook still too under-powered for DSD256 upsampling?

 

Hard for me to think a 2017 model wouldn't get it, since I'm upsampling Qobuz to DSD256 with what you used to have, a 2009 MacBook Pro.  I do have to wait awhile for the first track to convert and load completely into memory, but after that it's fine.

 

Suggestions: Try SoX with the shortest possible filter length. If it still happens, see if pausing for 20 seconds at the beginning of the first track to give the conversion a head start will work.