Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/693e48dd-ce3c-800a-b636-9b3efde0fdec
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: Good thinking. === Good thinking. A screen recording is actually the right artifact to check here — and there is useful metadata, but also an important limitation to be aware of. I’ll keep this precise and technical. ==== ### ==== From a screen recording file (on iOS), metadata can show: * Orientation changes (timestamps when rotation occurred) * Frame size / resolution * Color space (sRGB / Display P3) * Bit depth * HDR / tone-mapping flags * Frame timing irregularities * Dropped or duplicated frames This can confirm: * when the display pipeline was reset (rotation) * whether color processing mode changed * whether the GPU output itself was stable ===== A screen recording cannot capture: ===== * post-render display controller artifacts * local tone-mapping bubbles * panel-side inversion effects Because: : So the absence of the dots in the video is expected — and actually supports the diagnosis we’re on. ==== Here’s what would be meaningful to look for: ==== ===== If the recording metadata shows: ===== * a clean orientation change at the exact moment you rotated the phone * followed by normal frame timing That confirms: * the pipeline reset happened cleanly * the artifact disappearance lines up with orientation rebuild ===== If the metadata shows: ===== * consistent color space (e.g., Display P3) * no HDR toggling * no dynamic color profile switching That rules out: * software color filters * accessibility color transforms * app-level rendering issues ===== If there are: ===== * no massive frame drops * no corruption * no repeated frames during the artifact appearance That tells us: * the GPU output was stable * the issue is downstream (display controller / panel driving) ==== On iPhone: ==== # Open Photos # Open the screen recording # Swipe up on the video (ℹ️ Info panel) Look for: * Resolution * Color profile * Frame rate * Orientation info If you AirDrop the video to a Mac, you can also: * right-click → Get Info * or open in QuickTime → Inspector You’re mainly checking that nothing unusual changes except orientation. ==== Red flags would be: ==== * dots appearing inside the recording * artifacts encoded into frames * metadata showing frequent color-space flips * recording showing partial inversion regions You’ve already implied that none of that is happening. ==== If: ==== * screenshots are clean * screen recordings are clean * artifacts reset on rotation * artifacts drift back in afterward Then the only remaining layer is: : There is literally no other place in the rendering pipeline where this behavior can occur. ==== Just answer yes/no if you want: ==== * Does the recording show any visual anomaly at all? * Do the artifacts reappear after a few minutes of normal use? If you want, you can also paste: * resolution * color profile * frame rate from the video info panel, and I’ll sanity-check it — but don’t expect “hidden clues.” The absence of anomalies is the clue. You did the right diagnostic step.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)