Specifically, for a movie with a 2.39:1 aspect ratio... without distorting the picture.
I tried vlc, I tried infuse (v5.x.. I refuse to give these assholes more of my money.. long story..).. nothing works.
Came across a concerning issue with my neo a couple of days ago.. when playing a video full screen, I noticed it would occasionally flicker black when playing with vlc. I asked the claude llm (as one is wont to do these days..) and it concluded it was likely a vlc bug.
ok, fine..
.. fast forward to today, and I got similar flickering when connected to a remote windows machine (on my home network) using the windows app.
Try as I might, I can't reproduce the latter, but I can for the former.
VLC version: 3.0.23 (downloaded from vlc website).
Specific video: https://www.youtube.com/watch?v=kR3HdC1ojHY&pp=ygULbWljaGFlbCBtamQ%3D downloaded in .webm format using yt-dlp. Technical details:
% ffprobe Exploring\ an\ Almost\ Steam\ Machine\ from\ 2013\ \[kR3HdC1ojHY\].webm ffprobe version 8.1.2 Copyright (c) 2007-2026 the FFmpeg developers built with Apple clang version 21.0.0 (clang-2100.0.123.102) configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/8.1.2 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gpl --enable-libsvtav1 --enable-libopus --enable-libx264 --enable-libmp3lame --enable-libdav1d --enable-libvmaf --enable-libvpx --enable-libx265 --enable-openssl --enable-videotoolbox --enable-audiotoolbox --enable-neon libavutil 60. 26.102 / 60. 26.102 libavcodec 62. 28.102 / 62. 28.102 libavformat 62. 12.102 / 62. 12.102 libavdevice 62. 3.102 / 62. 3.102 libavfilter 11. 14.102 / 11. 14.102 libswscale 9. 5.102 / 9. 5.102 libswresample 6. 3.102 / 6. 3.102 Input #0, matroska,webm, from 'Exploring an Almost Steam Machine from 2013 [kR3HdC1ojHY].webm': Metadata: ENCODER : Lavf62.12.102 Duration: 00:28:35.82, start: 0.007000, bitrate: 6274 kb/s Stream #0:0: Video: av1 (libdav1d) (Main), yuv420p(tv, bt709), 3840x2160 [SAR 1:1 DAR 16:9], 59.94 fps, 59.94 tbr, 1k tbn, start 0.007000 Metadata: HANDLER_NAME : ISO Media file produced by Google Inc. DURATION : 00:28:35.789000000 Stream #0:1(eng): Audio: opus, 48000 Hz, stereo, fltp, start 0.007000 Metadata: DURATION : 00:28:35.819000000
Panic-bought this machine "like new" used (1 battery cycle) from Amazon just after the major price increase (before it applied on third party sellers).. so my concern is there might be a hardware issue with my particular machine?
All I did was tell it to play a song. It can't play a fucking song through Siri?
What kinda of ghetto shit app is this?
Just got a firestick 4k max. And when I saw fucking ads on the fucking homescreen.. I wanted to throw up. This thing is going back to Amazon if I can't get around it. I will not tolerate it.
So, that means my top priority is getting the projectivy launcher installed and working. I've done this before on the nvidia shield, so I know it's not completely straight forward to get it set up *properly* (meaning.. runs on startup, is tied to the home button on the remote.. etc.)
Can someone point me in the right direction?
FIX YOUR FUCKING WEBSITE, I'M NOT DOING FUCKING CAPTCHAS.
Early 2013 15" Macbook Pro running MacOS Sonoma through OLCP for several months now.
First symptom: My internet connection seemed to stop working suddenly. Still appeared connected to wifi, but nothing would load. Internet worked fine on other devices.. so I figured a reboot would do the trick.
Second symptom: Upon login, black background and taskbar. When I try to launch an app, returned to the login screen. Try login again, and error message saying WindowServer crashed.
Tried troubleshooting with a LLM.. it suggested I needed to reinstall root patches. Held option while rebooting, selected "EFI boot".. and then.. rebooted back into MacOS (same issues) and not the OLCP menu (which the LLM said I'd end up at)
At this point, I wanted to stop, and get human input in case copilot was leading me astray.
Please help!
I did not (willingly, intentionally) install any MacOS updates..
EDIT:
Update: issue resolved.
Turns out my system became stable enough (somehow?) that I was able to open opencore-patcher and apply root patches from there.
Specifically, near the beach?
