![]() ![]() If the transfers are lossless, then you have no issue and no sound difference, also no cable / USB transport issue. ![]() then you only need to find out what it caused. Then you would see, whether one of the audio chains (Windows or Apple) has loss. This you simply play back, and then you can see in the display of the ADI-xxx whether audio has been received lossless. wav format from RME, that are available for different sample rates. If you had an ADI-2 DAC or ADI-2 Pro or ADI-2/4 Pro SE, then you could easily validate, whether your complete audio chain from the player (or DAW) up to the DAC is lossless. But there are surely settings, which enable you to listen lossless. MacOS has no ASIO, so the application has no driver with direct access to the audio HW. To completely exclude these Windows sound enhancements and the audio subsystem of Windows and the mixer, you should use the ASIO driver, which completely bypasses it. Windows and Apple are both operating systems that are capable to playback audio lossless.īut surely on both systems you can make mistakes that you do not hear lossless, and you should find out what is causing this. ![]() Is there a way to post the entire log file? Will this help in any way? Later in the log I see things back to 48k. ![]() In a debug log file, I see that despite RME hardware and drivers running at 48k, the system reports 44.1k. I've been experiencing the exact same issue, though still with the latest 3.x drivers, and have been back and forth with Rogue Amoeba's support. When I run it at 48k with the old driver, no problem. When I run AudioHijack when my drivers are at 48k, lots of stuttering, dropouts, and odd repeats. Not sure if it's an RME problem or an AudioHijack problem. Getting some odd behavior with the new DriverKit offering. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |