> Null at 300Hz - this may not be as ominous as it looks. This is where Audiolense shines in using impulse response to time align everything! Is the sub closer to you than the mains or are the mains closer in which case they may need delaying. > Sub timing based on distance alone is likely not accurate due to group delay caused by the sub's electronics. Try changing the toe-in (or is it tow-in?) amount. > your high freq roll off may be a result of speaker toe-in. Can you please confirm that the chart is without Audiolense FIR filter correction? Thanks for sharing your REW freq response chart. music signal+freq response corrections+time domain corrections) to the DAC where its processed and then spits out 6 channels to my biamped mains and pair of subs Then a USB connection takes 6 parallel channels of info (e.g.
MINIDSP TIDAL CONNECT SOFTWARE
I map the JRiver channels to the AL ones, turn off JRiver when taking AL measurements and then use JRiver to invoke the AL created FIR filter within the JRiver DSP area of the software - dirt easy. In my case I run a HP Laptop as my music server that also has on it both JRIver and Audiolense. I think you will find that most of us (I'm guessing here) use multi-channel DACs with either software like JRiver or ROON etc (or multi-channel miniDSP models) that can also handle multiple channels independently for freq and time domain corrections. This is a sub optimal approach in my opinion unless you have REW or some other tool to help get you the delay times you require. You can keep the subs on with the monitors and measure each channel separately but you'd have to do the sub timing outside of Audiolense and have it ready to go before taking a AL measurement. Further updates will not bring any improvement other than Tidal connect, maybe memory consumption will be optimized, but I do not expect significant major changes.You are realizing the constraint of having multiple sound sources but only two channels to do measurements and corrections via Audiolense. I have the impression that the R26 streamer is designed especially for Roon.
MINIDSP TIDAL CONNECT LICENSE
Theoretically, Gustard could prepare two versions of the update: one for Roon users and the other for non-Roon but Tidal users, etc.Īfter all this, I even bought a Munich M1T but eventually returned it because for the same money or even less I will buy a lifetime Roon license and I will not need a separate streamer. BubbleUPnP, Linn Kazoo, Linn app…) without a BubbleUPnP server. This is a compelling advantage because you can use (e.g. If Roon is not in use it is possible to disable Roon Bridge and save 30MB of RAM.Īdditionally, I found that in nf you can enable Open Home Renderer. I also tested Tidal connect, it uses a lot of memory but it works. A special application inside the R26 streamer - Roon Bridge, made rather by Roon programmers, is responsible for playback. R26 uses about 50% of memory and plays HiRes flac and DSD without problems. I haven't used Roon yet but installed it on a Synology DS220+ and I'm surprised how it plays. In addition, information about decoding the DSD file is not displayed and the 1-bit decoder will not work. With Media Render configuration in BubbleUPnP "Decode Audio to PCM for: All audio formats + constraints below" HiRes flac files play without stops but there is a problem with DSD playback because DSD64 files are decoded with a sampling frequency of 352kHz, DSD128 with 764kHz and DSD256 files are up to 1.4MHz and this is too high. I updated mpd player to the latest version but the result was even worse.
"alsa_output: Decoder is too slow playing silence to avoid xrun" So I logged in via SSH to R26 and when playback was stuttering, memory usage was at 100%, this is what I saw in mpd.log: So this would workaround any eventual flaw in the HiRes FLAC decoding of the Gustarender." If you set "Audio decode is PCM for: All audio formats + constraints below" this makes BubbleUPnP Server convert input audio to WAV (with no loss of quality) It is possible its FLAC decoder has a problem with HiRes (assuming you can play 44.1/16 FLAC fine). "The log shows that your Gustarender is becoming unresponsive to UPnP commands just after being instructed to play a 96 kHz / 24-bit FLAC from MinimServer. I thought it was a BubbleUPnP problem and wrote to them and attached the logs. I also had trouble playing 24-96 and 24-192 files via BubbleUPnP server.
0 kommentar(er)
