That is the beta firmware isn't it?Everything seemed to be working well on my end here too. I don’t this feature is on beta anymore. IOS app is updated as well.
Mine never had beta in parentheses. That definitely isn't official firmware the release date is 23 October.Initially it said beta in parentheses. I did a reboot and checked for a software update and it started working. The parentheses went away idk
Two features I'm waiting the most, along with replaygain metadata support on local filesI hope before the end of this year independent peq rc and auto level will be out on public release. If not, I’m also interested on simultaneous usb with sub.
I was just thinking that, and that it'd be a good excuse for a decent headphone setup or a smaller 2nd systemIt might seem that the sound would be tragic from the side of the speakers
Here are a couple of speed and measurement facts to digest while considering the treatment of subwoofer latency:
- Sound travels at 1.13ft/millisecond - indicating that latencies within the low milliseconds range that WiiM addresses are well within the dimensions of a normal listening environment
- Peak-to-peak distance of sound at 60hz is 18.83ft - meaning that the wavelength of Subwoofer output rarely fits within a listening room
- Human Ears usually first detect latencies at about 5-10milliseconds - trained ears can do much better when specific notes are overlaid
I have always applied time correction prior to any room correction. However the setup I use is rather complex, using outdoor 'anechoic' measurements for time alignment of all individual speaker (driver)s and subs, then alignment between all of these at the listening position followed by room correction with lower bass frequencies only (the room is acoustically treated including corner bass traps so very little RC is required)Do you run auto timing first before rc or doesn’t matter?
What I find ironic was when I got the update I run it and got 27ms. I run it twice and got same result. Today I run it I got 7ms and run it again and got 7ms. What’s causing this variation?I have always applied time correction prior to any room correction. However the setup I use is rather complex, using outdoor 'anechoic' measurements for time alignment of all individual speaker (driver)s and subs, then alignment between all of these at the listening position followed by room correction with lower bass frequencies only (the room is acoustically treated including corner bass traps so very little RC is required)
This should be addressed directly to WiiM.What I find ironic was when I got the update I run it and got 27ms. I run it twice and got same result. Today I run it I got 7ms and run it again and got 7ms. What’s causing this variation?
I always got 8ms unless I moved the sub.What I find ironic was when I got the update I run it and got 27ms. I run it twice and got same result. Today I run it I got 7ms and run it again and got 7ms. What’s causing this variation?