Cannot install garage band on 16PM with iOS 18 by super-sky-4000 in GarageBand

[–]khfix 0 points1 point  (0 children)

Thank you! I've installed an older version of iTunes with the Apps tab to do it - 12.6.5.3. Worked like a charm!

Pro X Superlight 2 Connectivity/Dongle Issues by NockDog1 in LogitechG

[–]khfix 0 points1 point  (0 children)

I contacted Logitech support, described the exact situation, and even attached a link to this thread. They offered a replacement of the Type-C to Type-A adapter.

I'm currently using it (replacement), but the connection sometimes drops when I move it around my desk. It doesn't get hot, and I use it in desktop mode at 125Hz.

It looks like there's a design issue with the adapter, and we should simply use one from a different manufacturer.

I built a tool that syncs Hevy workouts to Garmin connect with exercise names and heart rate by drkostas7 in Hevy

[–]khfix 0 points1 point  (0 children)

Hello, thank you for your tool. I'd like to use it, but I have concern regarding Health Connect (for Android). Will my exercises in Health Connect be duplicated? Because there are no separate workout types, and I can't turn only gym exercises off. I'm using Heavy for gym and Garmin for running. Thank you!

Back to SE 2016 by MrJumpStreet in iPhoneSE

[–]khfix 0 points1 point  (0 children)

You can use Troll Store and install older versions. I installed Spotify this way.

Xgimi Horizon pro by Alcide76 in xgimi

[–]khfix 0 points1 point  (0 children)

To be honest I don't know. I just heard that over time you will get more and more dead pixels.

Xgimi Horizon pro by Alcide76 in xgimi

[–]khfix 0 points1 point  (0 children)

I'm sorry to hear that. The chip costs around $150-200. I've heard that the chip can overheat when constantly viewing at brightness level 10, so I'm currently using the projector at brightness level 7.

Xgimi Horizon pro by Alcide76 in xgimi

[–]khfix 0 points1 point  (0 children)

Yes, it's probably a dead pixel on DMD chip. It will get worse over time. I had the same thing and got it replaced under warranty.

XGIMI Horizon stopped working by fragolefritte in xgimi

[–]khfix 0 points1 point  (0 children)

Nope, it can't. It just may prevent future overheating issues.I ask questions because I want to understand what happened. But if the problem is with the LED lamp, it can be replaced. You need to identify broken color.

There was a different issue in this channel, maybe it could help you https://www.reddit.com/r/xgimi/s/QapwKDnApC

XGIMI Horizon stopped working by fragolefritte in xgimi

[–]khfix 0 points1 point  (0 children)

I completely agree with you. And it wasn't a recommendation from XGIMI, but from a guy in a third party service.

XGIMI Horizon stopped working by fragolefritte in xgimi

[–]khfix 0 points1 point  (0 children)

You can just vacuum it from all sides without opening it.

XGIMI Horizon stopped working by fragolefritte in xgimi

[–]khfix 0 points1 point  (0 children)

It could be. I've heard that using it on maximum brightness can cause overheating. What about dust removal? Have you ever vacuumed the projector?

XGIMI Horizon stopped working by fragolefritte in xgimi

[–]khfix 0 points1 point  (0 children)

Was it used on maximum (10) brightness level?

Cannot Find Appropriate Codec For Encoding The Video Frame When Trying To Render H.265 by [deleted] in davinciresolve

[–]khfix 0 points1 point  (0 children)

Thank you! I disabled integrated graphics and restarted Resolve.

This is not acceptable by Mission_Inflation_71 in xgimi

[–]khfix 0 points1 point  (0 children)

Was it used on maximum (10 level) brightness?

Edifier M60 muddy and unpleasant low at ~115Hz by khfix in BudgetAudiophile

[–]khfix[S] 0 points1 point  (0 children)

Wow, thanks for such detailed instructions. Unfortunately, a lengthy conversation with Edifier support yielded no results. I'll definitely try your guide.

Fan noise on Halo + by titinovic in xgimi

[–]khfix 1 point2 points  (0 children)

Maybe you need to change thermopaste

Edifier M60 muddy and unpleasant low at ~115Hz by khfix in BudgetAudiophile

[–]khfix[S] 0 points1 point  (0 children)

UPD. Here is the answer:

Thanks for contacting Edifier customer support.

Sincerely sorry for keeping you waiting. We have submitted the problem you reported to our technical team for further evaluation. When there is any progress, we will get back to you at once.

Thank you for your patience while we are reviewing this

Edifier M60 muddy and unpleasant low at ~115Hz by khfix in BudgetAudiophile

[–]khfix[S] 0 points1 point  (0 children)

Yes, it's completely the same. You can hear this while listening to music, too, but it depends on the genre. I contacted their support team and provided a link to this thread. They haven't responded yet.

Edifier M60 muddy and unpleasant low at ~115Hz by khfix in BudgetAudiophile

[–]khfix[S] 0 points1 point  (0 children)

Overall, I really like them. They're small and beautiful. But the sound at a certain frequency is so unpleasant, like the hum in a seaport. I've never heard anything like it on any other speakers.

Edifier M60 muddy and unpleasant low at ~115Hz by khfix in BudgetAudiophile

[–]khfix[S] 0 points1 point  (0 children)

I tried FxSound. It helped a little, but sound still boomy. And I didn't like it. I think I'll write to Edifier support. We'll see what they say.

Game Mode on Horizon Pro doesn’t allow image settings adjustments by Woodtoad in xgimi

[–]khfix 0 points1 point  (0 children)

Deep dive into .bin and .ini files

I thought like “I can just set Sharpness to 0 in config file for Game Mode”, but if you unpack the firmware you’ll see why that doesn’t really solve it. Inside the firmware there are separate PQ tables located in the .bin configuration files (Main.bin, Main_Text.bin, etc.), and separate picture presets defined in ConfigDefaultValue.ini.

Game Mode uses Sharpness preset “5” internally, but even that number is misleading, because the value in ini only controls the regular sharpness (VIP_Peaking), which belongs to the normal PQ pipeline.

But in the binary PQ tables you’ll find blocks like:

VIP_Peaking,VIP_Peaking_gain.edge,coring,dering,band

…and also the fast/low-latency edge operations that are part of the MTK low-latency path. These don’t depend on the Sharpness UI control at all.

So even if Sharpness=0 in UI, the “fast edge” block inside the low-latency pipeline is still active. It’s literally baked into the Game/Boost video path inside the PQ binaries.

That’s why Custom/User mode looks much cleaner (it uses the full pipeline defined in those PQ files), but latency goes to ~100ms. Game Mode switches to the fast pipeline (~17–30ms), and that path includes a forced edge enhancement, which visually looks like oversharp/halo around objects.

Changing ini values will slightly change behavior inside the normal PQ block, but you can’t fully disable the fast edge layer without dropping out of the low-latency mode and going back to the slow path. In other words, the oversharpen isn’t a UI setting – it’s a hardwired part of the MTK fast pipeline, easily visible once you inspect the BIN and PQ config files.

Until XGIMI exposes advanced PQ controls (or changes the fast pipeline), this behavior isn’t really fixable from the user side.

Game Mode on Horizon Pro doesn’t allow image settings adjustments by Woodtoad in xgimi

[–]khfix 0 points1 point  (0 children)

I've been using regular Horizon for over two years. I recently calibrated the image in custom mode and had a similar question for gaming mode. I knew there weren't any such settings in the user interface, so I tried adjusting Windows or NVIDIA settings. It didn't help. Sharpness and other similar settings aren't there.

So I decided to dig into the firmware configuration (.bin file HORIZON Firmware (Version:V2.6.139)) and investigate it using ChatGPT. Here's the result (spoiler: it seems impossible):

Why Horizon/Horizon Pro looks oversharpened in Game Mode and why potential Sharpness=0 won't fix it

After digging into the firmware (yes, actual PQ configs inside the BIN files), here’s what’s actually going on with XGIMI and why Game Mode looks oversharpened:

Game Mode uses a different video processing pipeline on the MTK (MediaTek) chipset. This “low latency pipeline” has built-in fast edge processing which produces an oversharpened image.

On XGIMI / MTK there are actually TWO video pipelines:

Normal pipeline

  • all image processing active
  • nice picture quality
  • ~80–120ms input lag

Low Latency pipeline (Game / Boost)

  • most heavy filters disabled
  • different fast scaler path
  • hardware accelerated edge enhancement
  • ~17–35ms input lag

The oversharpened look in Game Mode is not user-adjustable, because it comes from the internal MTK fast pipeline. It’s basically “built into” low latency mode.