![]() ![]() I don't see any reason why should we close the issue in any way.īecause this answer is based on the hdr principle, in theory, hdr is high contrast, which means peak brightness. I think this is just a workaround than a permanent fix. GL_ARB_blend_func_extended GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_ES2_compatibility GL_ARB_explicit_attrib_location GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader5 GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_occlusion_query2 GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_subroutine GL_ARB_shading_language_include GL_ARB_tessellation_shader GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_vertex_attrib_64bit GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_texture_compression_s3tc GL_EXT_texture_filter_anisotropic GL_EXT_texture_sRGB_decode GL_APPLE_client_storage GL_APPLE_container_object_shareable GL_APPLE_flush_render GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_texture_range GL_NV_texture_barrier ![]() Shaper: FriBidi 1.0.10 (SIMPLE) HarfBuzz-ng 2.7.2 (COMPLEX) Run command: enable-section, flags=64, args= Run command: define-section, flags=64, args= selected audio output device: SMSL AD18 AMP (58) loading 0.011] loading 0.011] loading 0.011] loading 0.012] reading options for ytdl_hook Set property: gpu-hwdec-interop="auto" -> 1 Loading lua script 0.010] Loading lua script 0.010] Loading lua script 0.010] Loading lua script 0.010] Exiting. ![]() Input config file /Applications/IINA.app/Contents/Resources/config/nf parsed: 69 binds Parsing input config file /Applications/IINA.app/Contents/Resources/config/nf resize stream to 131072 bytes, drop 0 bytes Opening /Applications/IINA.app/Contents/Resources/config/nf user path: '/Applications/IINA.app/Contents/Resources/config/nf' -> '/Applications/IINA.app/Contents/Resources/config/nf' mpv edca1e8 Copyright © 2000-2020 mpv/MPlayer/mplayer2 projects List of enabled features: 51deb asm bsd-fstatfs build-date cocoa coreaudio cplayer cplugins ffmpeg gl gl-cocoa glob glob-posix gpl iconv javascript jpeg lcms2 libarchive libass libavdevice libbluray libdl libm libmpv-shared lua macos-10-11-features macos-10-12-2-features macos-10-14-features macos-touchbar optimize osx-thread-name plain-gl posix posix-or-mingw pthreads rubberband stdatomic uchardet videotoolbox-gl videotoolbox-hwaccel zlib Configuration: waf configure -prefix=/opt/homebrew/Cellar/mpv-iina/0.32.0-dev -enable-javascript -enable-libmpv-shared -enable-lua -enable-libarchive -enable-uchardet -enable-libbluray -disable-swift -disable-debug-build -disable-macos-media-player -confdir=/opt/homebrew/etc/mpv -datadir=/opt/homebrew/Cellar/mpv-iina/0.32.0-dev/share/mpv-iina -mandir=/opt/homebrew/Cellar/mpv-iina/0.32.0-dev/share/man -docdir=/opt/homebrew/Cellar/mpv-iina/0.32.0-dev/share/doc/mpv-iina -lua=51deb Measured CPU time was about halved (2x as efficient) for the native app vs emulated app. I sanity tested by checking CPU usage while playing a 4K AV1 clip on an M1 Air. Tapped iina's formulas and modify mpv-iina to point to build: fix macOS arm builds mpv-player/mpv#8288.Modify rubberband formula to remove x86-specific flags from its Makefile.Modify ant and libbluray formulas to use the native Zulu JDK.Get aarch64-specific homebrew up and running.arch -x86_64 pod install but with Sparkle 1.24.0.New AV codecs like AV1 are not cheap to decode and require as much processing headroom as possible.įWIW, I managed to successfully compile a native ARM app from your guys's instructions with these changes:. ![]() Non-native software decode raises CPU usage and lowers battery life.Runs on AS Macs through Rosetta's x86 translation. Provide an Apple Silicon native build or Universal binary. ![]()
0 Comments
Leave a Reply. |