Jump to content

kohmelo

Members
  • Content Count

    11
  • Joined

  • Last visited

About kohmelo

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I have iFi Pro iDSD DAC that is capable of outputting either fixed 4.6V signal or 11.2V for studio use (as iFi calls it). Pro iDSD is feeding my Hegel H360 integrated amp via XLR. I was wondering is there any obvious downsides when feeding standard consumer hifi amp with 11.2V signal ? I'm testing 11.2V right now and my first impression is that there is a tad more dynamics in low frequencies, but mid/high frequencies lose some resolution compared to 4.6V signal. I need more listening, but probably I'll go back feeding my amp with the usual 4.6V signal. Just decided to test it out of interest because convolution filters can attenuate the signal level a lot, and therefor create large sound level differences between sources where convolution is not used. Using 11.2V output, these differences would not be an issue. There is obviously other ways to compensate this difference... Edit. It's not really resolution that is lost. I can't really put my finger what changed in higher frequencies, but for example cymbals sound little bit too "metallic" to my ears. That of course is a strange thing to say about metallic instrument
  2. One thing you could try is to play with your players CPU affinity and priority settings through DietPi-Launcher -> DietPi-services. I finally managed to get rid of pops with HQPlayer network audio daemon changing that player to higher priority and making one of the cores just dedicated for NAA (it's not possible completely via dietpi-services tool, but it seemed to help). Unfortunately I don't have DietPi installed at the moment, so can't check exact settings. However, I didi this with DietPi 6.26.X version and only had NAA installed, no other players and everything possible uninstalled. I would remove those force_turbo and freq setting and just use default "performance" mode when doing those dietpi-services changes... edit. I remember that I also changed some schedule setting to FIFO method.
  3. Is there a way to have ramdisk active with only one player installed and nothing else ? Just trying ramdisk mode for the first time on USBridge Sig and I can't figure out a way to remove unnecessary players as I only need Networkaudiod...
  4. Just informing everyone that my crashing issues with Windows version of the plugin has been solved. I believe Thierry will release new Windows version of the plugin "SOON".
  5. Thank you so much for this tip randytsuch! This seems to be only combination that actually fixes my faint pops with USBridge Signature connected to iFi Pro iDSD DAC. I think I've tried every combination with 4.14 kernels and none of those worked and was just about to give up... I've been getting faint pops with even DietPi versions that are supposed to work.
  6. Thanks for the tip, but doesn't seem to be a memory leak. Memory usage goes up by ~1% when I start playback via Jriver and doesn't really increase after that. Total memory usage is 25-27% at that point. 16GB of RAM.
  7. How are Room Shaper license owners finding its stability on Windows ? I just can't get it to be stable. Plugin keeps crashing eventually every time. I can sometimes get it to work 2h straight, but end result is always the same, plugin crash. Crashing is so random and I think I have tried everything there is to try. First I thought plugin crashes only when streaming content, but that's not the case after all. I had some email exchange with Thierry, but unfortunately he doesn't seem to figure out what the root cause is. Some things I've tried: - 2 different PC's (both very powerful, for example CPU's are 9900K and 4790K) - Roon and directly via Tidal app - Jriver, Audirvana, Foobar and standalone - Buffers from SW players and DAC ASIO drivers - 2 different DAC's - WASAPI, ASIO and Kernel streaming I really appreciate what the plugin can do in acoustically problematic rooms, but it's just unusable for me as it's just too annoying with this crashing issue...
  8. Forgot to mention that I did notice one negative side effect, soundstage depth has gotten smaller in my case. However cause for that can be so many things as my audio path is now so much more complicated than before. Overall improvement means more to me than losing some depth, so I can live with it for now.
  9. You can still use Roon UI. Just enable JRiver ASIO output in Roon and set JRiver up correctly. It's bit fiddly I must say. I have had several Jriver crashes, but it might be due to too short buffer. I've now maxed it out in Jriver (500ms) and no crashes in few hours. WASAPI output seems to be more stable...
  10. Thanks Mitchco for this fantastic review/article! One question, is there a reason why one would record impulse responses for Room Shaper with DRC filters enabled ? I did that (Audiolense filters), but in my (simple) head I think it should be other way around... At the moment I'm so sick of taking measurements, but I need to test that. Not sure if it's possible with Audiolense, but maybe it's doable if one uses Jriver asio output in Audiolense (with Room Shaper enabled in Jriver). I'm in the middle of fairly comprehensive acoustic project for my listening room, but most of my bass traps aren't arriving until mid december and this Thierry's genius plugin really helps the wait. Got to say if this was released a week earlier I might have skipped purchasing most of those traps I can't believe how well this thing actually works (at least for my room & equipment). I have ended up using effect/sense at 40-50%.
  11. I can confirm that 48k rates work with my Pro iDSD and Linux NAA. 1.60 firmware is required for that so you lose MQA capability. Pro iDSD will also output some "crackles and pops" when switching from audio format to another, so there's that and few other minor bugs related to 1.60 firmware that are not there with latest MQA capable FW versions >2.XX. As far as I know 1.60 is the last FW that handles 48k rates and it's available via iFi support.
×
×
  • Create New...