Nice, thanks! Out of curiosity, what's the bug? I didn't even find out how to link to another library when compiling a metallib at runtime...
FrankSchlegel
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Potsdam, Germany
Post
Replies
Boosts
Views
Activity
Thanks for the reply!
You are right, but it will unfortunately still just stay at 0% until the timeout kicks in after 5 minutes. There is no way to detect that it's simply not possible to download the item due to a missing connection or the cellular option being disabled.
Unfortunately, this is still the case (macOS 12 beta 6 + Xcode 13 beta 5)...
Any chance that Metal support is coming at some point?
Can you please try creating a larger image (16x16, for instance) and try again? I was also observing strange behavior (see above) for small EXR images. It would be interesting if these issues are related.
To sample in the middle of the pixel. For instance, if your sampler would use linear sampling, the coordinate 1.0 would return a mix of the first and the second pixel since it's between those pixels. 1.5 would only return the color value of the second pixel.
Correct. But it also creates a Metal context by default if you just use CIContext(). You would need to have a Metal-based context anyways if you want to use Metal Core Image kernels.
Thank you! Yes, this is filed under FB10151072.
@miric2 How did you find the -CustomRenderer tag? When I set it, Photos still doesn't show the HDR badge.
Done: FB11650654
Thanks for your help!
Thanks for the reply, Quinn! Unfortunately, the issue still exists – even with the release version of 13.4.
Very strange indeed. The workaround works, thanks!
Via a private property on MLModelConfiguration: config.setValue(1, forKey: "experimentalMLE5EngineUsage") (1 = disabled, 0 = enabled if possible, 2 = force).
Do you have any advanced tips setup? How are you calling Tips.configure()?
Did you already file Feedback for this issue?