home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Hardware
Ambient Lighting System
Questions about new AtmoLight setup
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="ixdvc" data-source="post: 1084951" data-attributes="member: 92134"><p>I have just made a few tests with latest AtmoWin and AtmoLight versions, but without LEDs. So just the SEDU was connected.</p><p>For my old setup with 92 LEDs, low CPU was off with 100 ms between frames. Everything was fine: hardly dropped frames, render time at about 7 ms and CPU for AtmoWinA.exe at 10-12 %.</p><p></p><p>Then I setup AtmoWin with 244 LEDs. CPU for AtmoWin went up to 32-34 %, render time to about 35 ms. Higher frame rates than 25 fps where not possible which resulted in nearly half of the frames being dropped for live TV. BD rips with 24 Hz instead were fine.</p><p></p><p>After that I left all the settings the same and activated low CPU. Render time was at 5 ms, CPU for AtmoWin at 11-12 % and no dropped frames.</p><p>What does low CPU do? Only analyzes every second frame? Would low CPU with 100 ms then be the same as 200 ms without low CPU?</p><p></p><p>Then I have to decide if I want 244 LEDs with low CPU or either 120 (2812) or 130 (2801) without. Any suggestions? Meanwhile I also found out that 2812B (contrary to 2812 without B) often have ESD problems and should only be used with a protection circuit to avoid damaging the pixels.</p></blockquote><p></p>
[QUOTE="ixdvc, post: 1084951, member: 92134"] I have just made a few tests with latest AtmoWin and AtmoLight versions, but without LEDs. So just the SEDU was connected. For my old setup with 92 LEDs, low CPU was off with 100 ms between frames. Everything was fine: hardly dropped frames, render time at about 7 ms and CPU for AtmoWinA.exe at 10-12 %. Then I setup AtmoWin with 244 LEDs. CPU for AtmoWin went up to 32-34 %, render time to about 35 ms. Higher frame rates than 25 fps where not possible which resulted in nearly half of the frames being dropped for live TV. BD rips with 24 Hz instead were fine. After that I left all the settings the same and activated low CPU. Render time was at 5 ms, CPU for AtmoWin at 11-12 % and no dropped frames. What does low CPU do? Only analyzes every second frame? Would low CPU with 100 ms then be the same as 200 ms without low CPU? Then I have to decide if I want 244 LEDs with low CPU or either 120 (2812) or 130 (2801) without. Any suggestions? Meanwhile I also found out that 2812B (contrary to 2812 without B) often have ESD problems and should only be used with a protection circuit to avoid damaging the pixels. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
Ambient Lighting System
Questions about new AtmoLight setup
Contact us
RSS
Top
Bottom