In the first file image, the dynamic-range of the recording may have been limited in mastering or in the production… In the second file image, it appears to be a 24-bit remaster or up-sample of a 16-bit/44.14kHz encoding… Not a lot of harmonic energy beyond 20kHz and the dynamic-range (96dB) has been revealed by the 24-bit bit-depth of the remaster or up-sampled iteration of the source 16-bit/44.14kHz encoding.
Still have problem!
I realize I’m getting off track, but wanted the input of the knowledgeable people on this thread. Saw a video on dcc reclockers that brought up some questions. Is there an advantage to using one with Audirvana? It seems most don’t have USB out which would be a disadvantage using optical/coaxial to a dac that has a 24/192 limit through those inputs. Thanks
In all likelihood it will make clocking worse unless you have a really bad one in your DAC.
USB inputs in modern DACs have the clocking control in the DAC itself closest to where the processing takes place. This gives more precise clocking control than SPDIF input, which relies on communication back and forth between the DAC and the external clock.
A Digital to Digital Converter (DDC) ‘translates’ one digital-audio signal format/protocol to another digital-audio signal… These are used in particular scenarios where there is need for digital-audio format interface congruence… For example, when a DAC only supports S/PDIF coaxial or optical input, or when a streamer (DDC) can produce an I²S output to a DAC that supports that interface.
If you are sending 24/192kHz signals to the DDC, it will output this 24/192kHz on the connected interface (S/PDIF coaxial or optical, I²S)… If the DDC supports Sample-Rate Conversion (SRC) it matches the output signal to the DAC interface format bit-depth and sample-rate.
Typically a streamer (DDC) will provide a USB output to a DAC…
If your DAC supports USB, then you should employ the shortest possible USB interconnect to the DAC… this is presuming the DAC is in close proximity to the computer platform. Otherwise, if only 192kHz and DSD64 signals are being transmitted, then using an optical interconnection will provide more freedom in DAC placement and an added advantage of electro-mechanical isolation that will prevent ground-differential noise (loops).
When the DAC supports higher sample-rates, then USB or Ethernet UPnP protocol is the right choice.
A ‘re-clocker’ is typically applied as a means to mitigate the influence of noise (jitter) accumulation induced in the transmission of a digital-audio signal, by refreshing the signal timing and shape before sending the output to the DAC… Most modern DAC’s do this in the DAC topology, however, there may be audible gains in applying such ‘filtering’ in the playback system digital pathway.
is there any news on this issue I posted weeks ago?
I get multiple times the alert: “Playback volume close to maximum” or “Are you sure you want to play this loud”, and though I click “do not show the next time” regularly it shows up again
Are you switching DAC’s?
I get this message when I am using the headphone output of my Mac Studio DAC and I have both software and device volume control disabled, where I manage the volume from the powered speakers attached to the headphone output… In the case of the Mac headphone output… I have not disabled the warning message, just to remind me to make sure the volume of my desktop speakers is set properly…
But I do not get this message when my reference system DAC is the selected output device, where software and device volume control is not engaged and have selected to disable the warning message.
Yes I do.
But I have no problem with the message. I understand the safety warning behind it.
BTW when I use the DAC in my Audio GD R27HE doesn’t show up. It shows up when I use other output devices. I never use MAC headphone output, just airplay (besides the USB C for the Audio GD)
I’d just like the program to do what it promises: “click here to not show it the next time”.
I click and it shows it again the next time anyway.
That’s the only problem I have
Works for me, in both the pop-up warning and the Device Volume Control windows.
You can only make changes to settings configurations when the audio-engine is stopped and unlocked… The alert status for each connected device is independently retained when you close Audirvāna… So be aware of this when switching Devices and which device is selected when exiting Audirvāna.
I am able to do that Agoldnear.
I just do not understand why, keeping the DVC active and clicking the box “do not show the next time”, that box pops up again “the next time”.
Hope I explained myself.
I expect that, if I click “do not show the next time”, I do not see the same pop up “the next time”.
It’s not a big deal, I love the software anyway, it’s just a minor issue, but probably easy to fix.
Before version 3 and before the trail versions 2.99.XX, when I clicked that, it would never showed up again, until the following software update.
Read carefully…
Read completely the attached screenshot of the Device Volume Control parameter descriptions…
Let’s use your own files then, can you send them to me at [email protected]?
I am afraid that this is not an issue with only my files my friend… The same symptoms happen when using the HRTC files, which are included with the HLC plugin, as a demonstration…
I was thinking this may be an issue with the MacOS Monterey V 12.7.6 I run… Or maybe that I am using upnp to a streamer… And Audirvana’s own built-in colvolver seems to have issues with .cfg files as well… I stand corrected… .cfg files seem to work now with Audirvana… It was the .zip files that didn’t work as expected…
Please also note that this used to work correctly in the last 2.x versions of Audirvana…
I think it’s been about a month since the final version of v.3 was released. What I can’t quite understand is that discussions about the beta version are still going on non-stop. Am I missing something, or is there another reason for this?
Look at the time between posts. It has gone from tons of posts per hour to not even one post per day. Serious progress.
But if I turn it off every time is shows up, no matter what device is connected, it should, one device at a time, memorise my choice, but it doesn’t…
whatever…I’ll keep on clicking
it’s just one action (actually two actions) more to do, while the spinning wheel is turning and I wait 3 days for my sync to be completed…
great sound, but definitely not the best user friendly SW in the world…
If you got that from the latest Hang Loose DSP Software Suite Version 2.1.5, then yes…
I don’t know about the others… And I got tired of asking questions that never got answered and tired of dealing with Agoldenear…
Update:
Works for me, in both the pop-up warning and the Device Volume Control windows.
