Audirvana Plus 2.5.1 with PCM->DSD Conversion

[RunHomeSlow]

Hello,

 

Is the activity of the CPU normal for a 2012 Mac Mini Core i7 2,6 GHz 4 Cores in DSD128?

 

 

[ATTACH=CONFIG]25781[/ATTACH]

 

It seems to me a little lot compared with Damien (Core i7 2.3GHz Dual Cores in DSD256)

And the noise of the ventilator disturbs me a lot!

 

 

I'm around 210% also with a Late Mini 2012 i5/2.5 with 16gb ram.

 

Using filter B2 with DSD128. i've put A+ memory buffer to the max...

 

All plays well no bug yet. At last no more changes with sample rates. THANK YOU DAMIEN !

[RunHomeSlow]

Hello again,

 

I've so no bugs, but it was for DSD upsampling...

 

I have the "loading first track" that appears often, had to stop than double click again,

and also the bug not counting the last track in an album as played... A+ 2.5.0.9

[RunHomeSlow]

Me? yes...

load a little bit faster than the song is playing :-)

was doing a refresh of playlist, but that made the song stop/sart...

same when copying files from my other mac to the mini while A+ is playing... too much demand i guess,

but memory to the max (yes completely at right)... no bug for me

 

Edit: memory at 15 360mb with 16gb

[RunHomeSlow]

Hello,

 

Why memory allocated for pre-loading tracks is max at 15360 MB when i have 16 GB of memory ??

Maybe it's something i don't understand in software, but track will be loading much faster

and then, let all the CPU for upsampling?? Since Damien tell to reserve 2.5 GB for the System,

why not use like 10 GB of memory (out of 16 GB for me) and then let the upsampling do is thing alone ?

[RunHomeSlow]

The key word here is... beta :-)

 

For me with beta 2.5.0.9 with upsampling at DSD128 gives me no trouble, no hiccups, no second stopping sound... I was trying since i had my DAC to upsample files at 352/384, but A+ was never stable and sample rates changes was not constant... plus that the El Capitan bug with DAC and USB... what a mess...

 

NOW ALL IS GOOD FOR ME :-) just the percentage of cpu that Damien should fix i guess with the release version.

[RunHomeSlow]

First couple of tracks played now with 2.5.0.11

seems faster now for loading tracks in memory (grey bar), but my CPU remains at 213%-224%

in Activity Monitor, even after track loaded completely...

DSD 128 Filter C

no bug, no skip for me, no fan noise, not hot when i touch the Mini just normally warm i guess.

no more sample rate changes skipping, i'm HAPPY, MERCI Damien!

[RunHomeSlow]

Can the software remember what it as done when upsampling a song in memory

for the next time you play that same song again it has no live upsampling to do??

[RunHomeSlow]

Since it plays the files live, could it be possible to create a text file with the 0 and 1 and save it to the directory of the file, like a log file that weight nothing... or it is too much information to write ?

[RunHomeSlow]

After listen to A+2.5.0.11 FLAC2DSD128 files with online conversion, I converted the same files with JRiver to 2xDSD and listen to them again with A+ and NO Upsamplig...

Why the offline converted files sound better? A more relaxed perspective!!!

Can someone explain that? Damien are you here?

 

Maybe now you have the sound of JRiver played in A+ :-)

 

i have mixed feeling with JRiver DSD converter... here is what i posted in JRiver thread:

 

The other day, i was making some tests, i found that output encoding 2xDSD was not that good finally with PCM Flac files at least for a one Peter Hammill song... the 2xDSD one was different in the left channel than the PCM one upsampling at 352. The acoustic guitar was more near in the left speaker than the 2xDSD output encoding... the DSD one that was not as clear...

 

With that example, i wasn't sure anymore that this was the best way to max out the capabilities of my DAC and JRiver. Maybe JRiver is not as good to do PCM to DSD, than Upsampling 44 PCM at 352 PCM.

With A+ that song sound as good as DSD or PCM...

[RunHomeSlow]

For me, with 2.5.1 released version, all is the same... PERFECT :-)

 

I was with the 10.11.5 beta software for all the time sinve 10.11.5b1

and it was playing perfectly with direct mode enabled too and still is.

 

I had problems with sample rate changing not locking my DAC with A+ and JRiver too.

But since DSD upsampling is done by Damien, no more JRiver and all playing without bug.

[RunHomeSlow]

Other minus things...

Loading first track is working now for me, i'm still at around 220% of CPU with these settings.

Copying files between iMac and Mac Mini is WAY faster with release version of 10.11.5,

it was already faster with the last beta than with older version even Yosemite, but double and more for me with the final 10.11.5. Even Screen Sharing is not opening a dialog window that i have to hit enter... open automatically :-)

 

[RunHomeSlow]

When A+ is stopped after a CD, sometimes i have the Direct Mode message when i click a new CD...

but, i just click the song again, and it start fine with Direct mode still enable...

[RunHomeSlow]

Could someone please describe the complete minimal requirements for Audirvana+ 2.5.1?

 

I have a MacBook Pro with OSX Snow Leopard (OSX 10.6.8), 8GB RAM.

 

Thanks.....

 

 

[h=4]On the MacUpdate.com page for Audirvana...

https://www.macupdate.com/app/mac/39199/audirvana-plus

 

Requirements[/h]

• Intel, 64-bit processor
  
• OS X 10.9 or later
  
• CoreAudio-compatible DAC
  
• 2 GB RAM (4 GB recommended)
  

[RunHomeSlow]

i don't know the differences... but A+ is at 2.5.1.1 now...

i thought i downloaded 2.5.1 this morning not sure :-)

[RunHomeSlow]

I still didn't have any bug with any version, now on 2.5.1.3 :-)

[RunHomeSlow]

Conversion to DSD128 was quite okay with direct mode and the SQ is satisfactory. As expected the app is memory hungry but CPU load is quite low as shown below.

 

Processes: 254 total, 2 running, 8 stuck, 244 sleeping, 1091 threads   21:01:16
Load Avg: 1.52, 1.76, 1.58  CPU usage: 1.95% user, 4.88% sys, 93.15% idle
SharedLibs: 157M resident, 21M data, 19M linkedit.
MemRegions: 60099 total, 4097M resident, 125M private, 1189M shared.
PhysMem: 11G used (1857M wired), 4827M unused.
VM: 704G vsize, 535M framework vsize, 384(0) swapins, 768(0) swapouts.
Swap: 3072K + 1021M free. Purgeable: 142M 54998(0) pages purged.
Networks: packets: 37475438/46G in, 34317870/20G out.
Disks: 1871142/56G read, 968011/48G written.

PID    COMMAND      %CPU  TIME     #TH   #WQ  #PORT MEM    PURG   CMPRS  PGRP
23654  sleep        0.0   00:00.00 1     0    12    308K   0B     0B     3211 
23652  mdworker     0.0   00:00.04 4     0    48    3332K  0B     0B     23652
23650  top          2.0   00:05.07 1/1   0    23    2436K  0B     0B     23650
23616  csh          0.0   00:00.03 1     0    17    952K   0B     0B     23616
23615  login        0.0   00:00.04 2     0    29    1196K  0B     0B     23615
23611  mdworker     0.0   00:00.03 3     0    40    2904K  0B     0B     23611
23609  mdworker     0.0   00:00.05 3     0    53    3580K  0B     0B     23609
23608  mdworker     0.0   00:00.21 4     0    48    13M    0B     0B     23608
23571  Audirvana Pl 1.0   11:21.74 11    5    313   1193M  43M    0B     23571
23513  diskimages-h 0.0   00:04.31 3     0    81    22M    0B     0B     23513
23414  hdiejectd    0.0   00:00.03 2     0    29    872K   0B     0B     23414
23381  ath          0.0   00:00.12 4     0    42    1672K  0B     0B     16575
23373  Image Captur 0.0   00:00.45 3     0    135   5496K  0B     0B     23373

 

Just FYI.

 

 

You sure A+ was converting in real time DSD128 at that time??

 

Here is mine while playing... :-(

 

[RunHomeSlow]

wow... you have the default setting for oversampling... i have put it like that too

and reduce buffer memory to 1 minute like you...

my CPU jump to 257-260% for short time thant like you fall in 1% :-)

[RunHomeSlow]

i've put back my setting for upsampling: 8/1,300,000/102/200/.72

and kept the 1 min. buffer

 

cpu back to normal at 223% and stays there... :-)

 

I'll try other setting for upsampling like less filter max lenght: 500,000 no change...

maybe A+ doesn't like different settings for upsampling different from the default ones??

[RunHomeSlow]

If i increase memory buffer to 4096mb out of 16 instead of 512mb, cpu stays at 258% with the default setting of upsampling,

so better default settings and low buffer memory for now... the is a big defference in cpu usage... :-)

[RunHomeSlow]

I was with 1.1 all the time, changing to 1.0 didn't change anything for me...

 

I've put the 1 min buffer memory and change upsampling to: 73/645,600/1,00/200/.33

still good for CPU... higher for short time (260%) than goes down again to 1% around... come up a bit than down again :-)

[RunHomeSlow]

i think (really not an expert) that midi set up is normal for a 16/44 file... being upsampled show 352800

if you put a 24/96 or 192 file it will show 384000 the max of my dac

than it is upsample to dsd128 by A+ to the dac with the filters you gave...

 

Damien will surely look at this for optimizing next versions :-) All good for me, still no bug, less cpu usage :-)

[RunHomeSlow]

Just looking at the syncing of my library in album view with nothing playing,

the activity monitor CPU usage is around 150% (100-200%)...

[RunHomeSlow]

I'm working on an important update on the database management for 2.6 that will strongly improve its performance.

 

Hello Damien, thanks for all your work...

 

If you are adding Replay gain in database, is it easy to add another tab in the views? Dynamic Range... all my database is dynamic range already done in JRiver... is it easy for A+ to just read that in the file... if it's in the file :-) i only miss that info in A+. thanks again.

[RunHomeSlow]

With 3 play tries, if A+ doesn't crash, direct mode will work even with 2.5.1.3/10.11.5, so sounds as it wasn't broken by Apple!

 

Me too, direct mode ON all the time... just sometimes clicking a song would get the error message at start...

So i just click it again and it start... never happen not working after two tries...

[RunHomeSlow]

Damien will get it to work again always i'm sure :-)