07-07-2022, 05:42 PM
(07-07-2022, 03:06 PM)Reddo84 Wrote:(07-07-2022, 11:00 AM)TheOldPresbyope Wrote:(07-07-2022, 07:54 AM)Reddo84 Wrote:(07-07-2022, 02:22 AM)TheOldPresbyope Wrote: When you say "even if I disconnect the screen", does this include changing the Local UI Display setting to OFF in the System Config panel?
Hi Kent, that works as well to get rid of the distortion, even if the screen stays connected and switched on. [...]
Ah, but telling us the problem goes away when the Local UI Display setting is OFF is the vital clue.
If it's on, then the Chromium browser is running in moOdeOS and code is rendering the UI and the Allo Sparky's GPU is generating HDMI signals based on it. [...]
Hi Kent,
thanks for the insight, I'll get into contact with Allo about this (once more, this time linking this thread and my video). But if I'm not mistaken, my Allo USBridge Signature runs a standard RaspberryPi 3+ Compute Unit (@philrandal) including the onboard GPU. Keep in mind though the unit doesn't produce distorted sound whenever the Chromium Browser is running - when I'm displaying CoverView, everything is fine.
Sorry, I missed the "Signature" qualifier. The (original?) USBridge offering I found, https://allo.com/sparky/usbridge.html, discusses Sparky+USBridge+....
Then we're probably down to power supply and power cabling as Tim suggests.
FYI
1. Enabling the Local UI display (which starts a number of Chromium browser processes) increases the CPU and memory demands on the system generally.
2. The Chromium browser executes different branches of code in the loaded moOdeUI when you switch panels/views so instantaneous CPU and memory demands vary differently as well.
3. CPU demand and power demand are related.
Anyway, I'm out.
Good luck.
Regards,
Kent