- This topic has 1 reply, 2 voices, and was last updated 1 year, 4 months ago by Stan.
- AuthorPosts
- 17 July 2023 at 02:56 #47691
I’m not a software developer, but I was wondering if the sound delay problem (between TV and Besound speakers or a combination of new beosound speakers and older Beolab speakers in a network) can be remedied by adjusting the Mozart software.
It seems like Mozart API is open source (https://bang-olufsen.github.io/mozart-open-api/), and if that is the case, wouldn’t it be possible to manipulate the connected devices to synchronise their sounds through a Believing Hub for example?
17 July 2023 at 04:18 #47692It is my understanding that the delay is an artifact of both digitizing and DSP’ing the audio on the Mozart speaker and the latency from transmitting over NL/ethernet (and then decoding/DSP’ing on the receive end).
For older speakers, there’s already a “NL/ML delay box” which delays the ML audio to account for the processing time required on the NL side. However, this doesn’t work for ML sources with directly attached speakers because there is no way to delay the audio between the ML source and its directly connected speakers, only ML distributed audio is delayed.
If I understand prior discussions on this topic, the ability to use Mozart speakers as “surround” speakers will require by-passing some of Mozart’s internal audio engine processing to minimize the delay to avoid lip synching issues as well as software changes on the BV to also account for this, now minimized, delay. I doubt if any of this is just API settings (at least until the underlying software supports this).
I must say, it seems pretty cool of B&O to publish this API.
- AuthorPosts
- You must be logged in to reply to this topic.