Jump to content

damien78

Members
  • Content Count

    1270
  • Joined

  • Last visited

10 Followers

About damien78

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes, as it helps in the sending of audio data to the DAC. This is independent of upsampling.
  2. Yes to both. The only limitation when sending audio to a UPnP renderer is that realtime setup is not available, because of playback latency of such renderer. So for this, you need to setup the plugin in the audio settings page, and it'll process the audio signal during the track loading phase. And yes, Qobuz tracks are routed through the same signal processing as local files: loading/decoding, signal polarity, volume levelling, plugins, upsampling, format conversion to the most appropriate one for the audio device
  3. This looks like the TIDAL authorization data are not stored correctly in your library database, and thus not restored correctly upon next startup. Maybe this one is damaged? Can you check its integrity using the command in the Maintenance section of the preferences page?
  4. I have noticed that dsd or dsf playback is cracking.   Hopefully you will fix this as I do enjoy Audirvana .  Thank you.

  5. Nice move ;) thanks! I've already requested Qobuz these very same features, but the way Audirvana has integrated Qobuz is technically different than roon. Audirvana uses the Qobuz API to access Qobuz services, that is the recommended way to ensure always up to date data, and thus immediate access to latest albums as soon as they are available on Qobuz. These two features are currently missing in the Qobuz API. I've been told volume levelling is coming soon. The volume levelling one is even not available in their own player. Weird Qobuz have not implemented it first in their own player first. Hopefully you won't have to wait too long.
  6. Thanks for this report. This was not available in previous releases, but will be in next one.
  7. DoP 1.1is an iteration of DoP 1.0 designed for some DAC models (e.g. the Mytek Stereo 192 DSD DAC) that overcome their input sample rate limit by using 2x the number of audio channels to transmit a DSD signal at 2x rate. So for a normal stereo DAC, setting DoP 1.1 or DoP 1.0 makes no difference. Some other DACs offer 705.6kHz rate in their USB input only for DSD256 playback, while PCM at this rate is not handled by these..
  8. Can you check the Debug Info?
  9. Both. And the optimisations are in the low level playback engine, so for all cases
  10. There have been quite some added optimisations to the sound engine in 3.5 Integer, Direct modes are still present, though this last one requires the kext hack for recent macOS versions. If you are not upsampling, SoX is not used. Regarding INT display, you can check using the Debug Info while playing. The playing stream format is written there. If it says Integer non-mixable, then it is Integer Mode. Note that Integer Mode switch is not applicable for UPnP/DLNA playback, as it is an optimisation of macOS audio. BTW, the audio data sent to a network player is always in integer streams format. Regarding the UI issue, this is a bug/limitation of El Capitan where in some views, the differentiated scroll is not handled correctly. This is something Apple has fixed in Sierra. I've tried to implement as much workaround as possible for this, but it'll be too much work to redevelop a feature of the OS that is now working correctly in all the last 4 macOS released.
  11. This is quite surprising as it goes against the consensus on 3.5 SQ. I have even sound engineers that told me how there were astonished with the SQ achieved with 3.5, telling me there are now able to tell the model of microphone used when hearing a recording. Maybe there was some specific fit between 3.2 and your equipment? Have you tried tweaking the SoX parameters? Regarding the UI, @S.Magus, could you elaborate on "the newer version is too buggy compared to the old one"?
  12. There is unfortunately a bug in El Capitan that causes this crash. It is triggered when setting text for VoiceOver (the accessibility feature used by people with sight disabilities). I’ve found a workaround for getting Audirvana and VoiceOver work nicely with old El Capitan. You can then update to 3.5.28 I’ve just released.
  13. This will be in next release
  14. Be sure to have the latest Audirvana 3.5 running (e.g. 3.5.24 on the Mac). And all favorites are in the Favorites section (button in the tab bar at the bottom), including Qobuz ones.
×
×
  • Create New...