@RyanWithWiiM close this thread please, so much stuff that have nothing to do with the title of the thread.
Given that much of it is in response to what WiiM posted in comment #18, I see no need to do that. Like conversations in real life, they can often naturally branch off into other areas@RyanWithWiiM close this thread please, so much stuff that have nothing to do with the title of the thread.
Given that most of the computational stuff around room correction is done on your phone or in the cloud, the mini doesn’t analyse any differently. Again, there’s been no suggestion that the Mini can’t handle playback of the resulting 10 band peq settings.It would be great to have more discussion / confirmation about Room Correction in the Mini. Does the Mini analyze the room identically, and do its stereo 10-band PEQs perform identically afterwards, to its larger brethren with more processing power (Pro, Ultra, etc.)?
But surely it has to be able to keep up with real-time music, so I would be surprised, otherwise it'd be like listening to music at 0.9 speedmaybe it just induces a little latency due to calculations in use, more than others wiim? (I don't know....but I wouldn't be surprised)
But surely it has to be able to keep up with real-time music, so I would be surprised, otherwise it'd be like listening to music at 0.9 speed
Unless you were referring to the correction process itself rather than applying the 10 band peq.
I’d rather postulate, as I have above, that they took the decision to do the room correction computation in the app and in the cloud (there’s evidence of this as at points in the beta, the algorithm changed without a change in firmware or app), so the computational power between different models became less relevant. As for applying the PEQ values, even the Mini had GEQ out of the box so perhaps applying PEQ wasn’t an excessive leap forward.It would be great to have some empirical testing. Given that Wiim originally announced that the Mini did not have the computing horsepower to do 2*10 PEQ. It's conceivable that they implemented a simpler (quick 'n dirty) algorithm for the Mini than for the other devices. I am not saying there is evidence that this is the case -- but there's no evidence the other way either, unless Wiim explicitly tells us. I think one could test in the digital domain, by implementing the same PEQs on a Pro and Mini and comparing their digital SPDIF output for various inputs. Then repeat for other PEQs.
Recent firmware upgrades for other devices did stateIt would be great to have some empirical testing. Given that Wiim originally announced that the Mini did not have the computing horsepower to do 2*10 PEQ. It's conceivable that they implemented a simpler (quick 'n dirty) algorithm for the Mini than for the other devices. I am not saying there is evidence that this is the case -- but there's no evidence the other way either, unless Wiim explicitly tells us. I think one could test in the digital domain, by implementing the same PEQs on a Pro and Mini and comparing their digital SPDIF output for various inputs. Then repeat for other PEQs.
Yes, I'm specifically referring to applying the PEQ values during playback, which is where Wiim computing horsepower is most relevant, as you explained. I've edited my original post to clarify.I’d rather postulate, as I have above, that they took the decision to do the room correction computation in the app and in the cloud (there’s evidence of this as at points in the beta, the algorithm changed without a change in firmware or app), so the computational power between different models became less relevant. As for applying the PEQ values, even the Mini had GEQ out of the box so perhaps applying PEQ wasn’t an excessive leap forward.
That does sound on point.Recent firmware upgrades for other devices did state
"Optimized CPU Performance: Reduced CPU usage for EQ processing and USB output, improving efficiency."
Maybe that helps.