Audirvana Plus 2.6

[RunHomeSlow]

I saw that stopping before ending happened to me also if i remembered before 2.6.6 or change i've made...

but i'm upsampling to DSD128 form my DAC that can do DSD128...

 

I was playing with the izotope settings with users settings and maybe changing the settings from basic may interfered,

but the big difference from my knowledge, is in the memory you give to A+ (for my case) i give in the preferences 13 824mb to A+ out of 16gb of memory from my MacMini.

 

I still upsampling everything always to DSD128 with DSD filter C 7th, my izotope settings are from Damien settings in the Manual window pref picture... I NEVER experienced any not ending song at the end, or hiccups while playing, my loading bar is ALWAYS in one color and always go to the end of the song.

 

Maybe it is on the user end to find the right one to use with the software at is max settings like yours at 24/96 or mine DSD dac to 128, if not found, play your songs at regular sample rate... then if you have bugs...you can complain :-)

 

Maybe v3 will end all of that, but...

[Speed Racer]

It makes no difference if I send upsampled signal or native format. 24/96 is just maximum rate my DAC accepts. Isotope in theory does better job upsampling than DAC, which automatically upsamples everything to 24/192.

It’s the software stalling for whatever reason.

 

If your DAC is going to upsample no matter what, I suspect it is better to have only one upsample done instead of one by Audirvana and one by the DAC.

[RunHomeSlow]

It makes no difference if I send upsampled signal or native format. 24/96 is just maximum rate my DAC accepts. Isotope in theory does better job upsampling than DAC, which automatically upsamples everything to 24/192.

It’s the software stalling for whatever reason.

 

the software does not upsample everything to 192 if you don't say it to do so...

[rickca]

I never know when Audirvana will stall and I will hear loud noise trough my speakers.

If you're hearing noise, the A+ playback position is overrunning the amount of data loaded. I haven't seen this bug since long ago while testing Qobuz integration. I don't think other people who are reporting this 'stall bug' are hearing noise.

[Daudio]

I am mildly disappointed that you should knock Apple's proprietary system...

I find it a bit unfair to denigrate iTunes which has been the historic music player on which your software has been piggy-backing once upon a time.

I don't think you would be quite so solicitious of Apples iTunes if you had spent any time with the latest, atrocious, release. I've spent over 6 years with iTunes. I used to be a fan, even with it's glaring problems. But not anymore !

I was ripping discs for a friend onto his Mini, when the Update poped up. 12.5.5 was only for little stuff it said, so OK. But the U/I changes were drastic, my productiviy dropped, and my temperature rose ! I rate it unusable for anything more then very light library management. His Mini is getting JRiver/Mac anyway (DLNA).

 

But nevermind, I'm stuck on iTunes 10. Works great ! For now...

[Jud]

If your DAC is going to upsample no matter what, I suspect it is better to have only one upsample done instead of one by Audirvana and one by the DAC.

 

That's the wonderful thing about digital audio, it runs so counter to many folks' intuition.

 

It is better to have better upsampling, no matter where it is done.

[astrostar59]

Any word on the MQA V3 release guys?

[odelay]

Stall bug...

I used to have the stall accompanied by that awful 'white noise'. As mentioned, likely due to running out of memory. Haven't had noise for a long time 5+ months?).

 

Still getting the stalling bug when upsampling (has happened either just with iZotope or up with Mans' DSD).

 

Helps bring A+ RAM down to below 1gb. Still having issues with really large hi-rez PCM files.

 

Recent updates has made it happen much less frequently, but it still happens.

 

Fingers crossed 3.0 works some magic on that front for those of us still suffering with this one [emoji868]

 

 

Mac mini -> Regen -> Burson CV2+ -> HD560

[astrostar59]

It makes no difference if I send upsampled signal or native format. 24/96 is just maximum rate my DAC accepts. Isotope in theory does better job upsampling than DAC, which automatically upsamples everything to 24/192.

It’s the software stalling for whatever reason.

 

If your DAC is not NOS, it makes sense to feed it the resident 44.1 and take any pressure of your Mac Mini. Are you using your Mac Mini to surf or do other tasks? Are there other USB divvies attached. Try a different USB port (look in system spec and pick the best bus). I have no dropout on my Mac Mini.

[Speed Racer]

It makes no difference if I send upsampled signal or native format. 24/96 is just maximum rate my DAC accepts. Isotope in theory does better job upsampling than DAC, which automatically upsamples everything to 24/192.

It’s the software stalling for whatever reason.

If the DAC is going to upsample the content to 24/192 no matter what and accepts only 24/96, it makes no sense to upsample in software before you send it to the DAC.

[Jud]

If the DAC is going to upsample the content to 24/192 no matter what and accepts only 24/96, it makes no sense to upsample in software before you send it to the DAC.

 

It does mean software upsampling very likely has *less* effect, but there's a difference between that and *no* effect.

 

If you can add a single higher quality ingredient to something you're making for dinner, does it make sense to do so?

 

 

Sent from my iPhone using Computer Audiophile

[mevdinc]

I have just created a playlist in TIDAL desktop app and the order of tracks seem to be all jumbled up ,n Audirvana+, and I couldn't find a way to restore it to the order that I created the list in TIDAL.

Is this a new problem, I don't remember seeing this before? Is there a fix for this? The track order seems to be fine with Albums.

[astrostar59]

Damian just posted on FB, it is really close, few days now... but down to Tidal.

[bobbmd]

Jud: Agree am listening to a playlist of Joan Osborne-her own albums and a neat set of albums where she appeared with others made from TIDAL(surprisingly ROON had next to nothing to offer).The SQ from TIDAL with their new upgrade of something doesn't compare to A2+ ver 2.6.6. I have 24/192 and 3 white lights on my ME2 nothing close to that from TIDAL desktop.

If you are interested there is an article on Osborne in today's NYTs-she is a cabaret singer doing Bob Dylan at the Carlyle Hotel too bad she hasn't put an album of this out.

[Speed Racer]

That's the same story we have heard the last 4 weeks. First, the software was done but the new licensing system needed work. Now it is MQA.....who cares about MQA?

[Musicophile]

That's the same story we have heard the last 4 weeks. First, the software was done but the new licensing system needed work. Now it is MQA.....who cares about MQA?

 

MQA is pretty much the main point of 3.0. If you don't care about it (like I do), you can just happily use v2

[Speed Racer]

MQA is pretty much the main point of 3.0. If you don't care about it (like I do), you can just happily use v2

MQA is the publicized feature, that's for sure. But it would be crazy to make that the only change. Damien has already said there is a big improvement in SQ for people not using MQA. I hope he has improved his library management features too.

[jamesg11]

If the DAC is going to upsample the content to 24/192 no matter what and accepts only 24/96, it makes no sense to upsample in software before you send it to the DAC.

OTOH, if you have a dac that auto upsamples to 24/192 & also accepts 24/192, it's worth clarifying what is happening - the techs confirmed for me that my dac was bypassing any upsampling when its input was at the max rate. So, confirming what I'd heard for a while - always feeding it 24/192 from A+ etc was always better.

[Speed Racer]

OTOH, if you have a dac that auto upsamples to 24/192 & also accepts 24/192, it's worth clarifying what is happening - the techs confirmed for me that my dac was bypassing any upsampling when its input was at the max rate. So, confirming what I'd heard for a while - always feeding it 24/192 from A+ etc was always better.

 

That is how my Schiit Modi Multibit works. I had A+ send iZotope upsampled 24/176.4 data to the Modi Multibit. I didn't like the sound. It seemed more compressed and muddled. The sound stage was smaller. The Yggdrasil I have does not have a NOS mode.

[OneHandWaving]

who cares about MQA?

I do.

 

I'd rather wait a week or two and have it right that have it now but wrong.

[Jud]

That is how my Schiit Modi Multibit works. I had A+ send iZotope upsampled 24/176.4 data to the Modi Multibit. I didn't like the sound. It seemed more compressed and muddled. The sound stage was smaller. The Yggdrasil I have does not have a NOS mode.

 

True. You can oversample to the Yggy's max input rate in software if you happen to prefer it, or just let the Yggy do everything if you like that better.

 

 

Sent from my iPhone using Computer Audiophile

[Jud]

That's the same story we have heard the last 4 weeks. First, the software was done but the new licensing system needed work. Now it is MQA.....who cares about MQA?

 

For those who do care (and for Damien, who surely wants the "most publicized feature" of the update to work as well as possible), I am content to wait. And remember, I heard test builds (which are no longer operative), so I know that what I'm missing is quite good.

 

 

Sent from my iPhone using Computer Audiophile

[mevdinc]

For those who do care (and for Damien, who surely wants the "most publicized feature" of the update to work as well as possible), I am content to wait. And remember, I heard test builds (which are no longer operative), so I know that what I'm missing is quite good.

 

 

Sent from my iPhone using Computer Audiophile

 

I also care for MQA support as it is one of the main features of V3.0 that I'm waiting for.

But Roon V1.3 was released without the TIDAL MQA decoder in place with lots new features including up-sampling.

 

I think Audirvana+ V3.0 could be released to so we can enjoy the added SQ and also help iron out any problems/bugs which may have escaped the test builds.

MQA update would come when TIDAL is ready.

 

Just a thought but we have to respect Damien's decision if he wants to release with MQA feature.

[rickca]

Just like with MQA-enabled DACs, MQA has to approve a product with their licensed code before it can be shipped. So if MQA wants to make further refinements prior to release, Damien has to wait unless he wants to remove MQA support from V3.0. Since he already has the MQA integration work done, it makes sense to just wait for the MQA library update.

[astrostar59]

Everything comes to he who waits....