I don’t think it is a Windows thing
I guess smb is the bottleneck here…
1 Like
fedora can't into h265?
kushal@kusfedora2024:~/src/bash$ ls -l ~/Videos/IMG_6569.MOV
-rw-r--r--. 1 kushal kushal 2259942328 Jun 10 04:56 /home/kushal/Videos/IMG_6569.MOV
kushal@kusfedora2024:~/src/bash$ ffprobe -v quiet -print_format json -show_format -show_streams ~/Videos/IMG_6569.MOV
{
"streams": [
{
"index": 0,
"codec_name": "hevc",
"codec_long_name": "H.265 / HEVC (High Efficiency Video Coding)",
"profile": "Main 10",
"codec_type": "video",
"codec_tag_string": "hvc1",
"codec_tag": "0x31637668",
"width": 3840,
"height": 2160,
"coded_width": 3840,
"coded_height": 2160,
"closed_captions": 0,
"film_grain": 0,
"has_b_frames": 2,
"pix_fmt": "yuv420p10le",
"level": 153,
"color_range": "tv",
"color_space": "bt2020nc",
"color_transfer": "arib-std-b67",
"color_primaries": "bt2020",
"chroma_location": "left",
"refs": 1,
"view_ids_available": "",
"view_pos_available": "",
"id": "0x1",
"r_frame_rate": "60000/1001",
"avg_frame_rate": "7015200/116993",
"time_base": "1/600",
"start_pts": 0,
"start_time": "0.000000",
"duration_ts": 116992,
"duration": "194.986667",
"bit_rate": "92430444",
"nb_frames": "11692",
"extradata_size": 128,
"disposition": {
"default": 1,
"dub": 0,
"original": 0,
"comment": 0,
"lyrics": 0,
"karaoke": 0,
"forced": 0,
"hearing_impaired": 0,
"visual_impaired": 0,
"clean_effects": 0,
"attached_pic": 0,
"timed_thumbnails": 0,
"non_diegetic": 0,
"captions": 0,
"descriptions": 0,
"metadata": 0,
"dependent": 0,
"still_image": 0,
"multilayer": 0
},
"tags": {
"creation_time": "2025-06-10T08:56:21.000000Z",
"language": "und",
"handler_name": "Core Media Video",
"vendor_id": "[0][0][0][0]",
"encoder": "HEVC"
},
"side_data_list": [
{
"side_data_type": "DOVI configuration record",
"dv_version_major": 1,
"dv_version_minor": 0,
"dv_profile": 8,
"dv_level": 10,
"rpu_present_flag": 1,
"el_present_flag": 0,
"bl_present_flag": 1,
"dv_bl_signal_compatibility_id": 4,
"dv_md_compression": "none"
},
{
"side_data_type": "Display Matrix",
"displaymatrix": "\n00000000: 0 65536 0\n00000001: -65536 0 0\n00000002: 141557760 0 1073741824\n",
"rotation": -90
},
{
"side_data_type": "Ambient viewing environment",
"ambient_illuminance": "3140000/10000",
"ambient_light_x": "15635/50000",
"ambient_light_y": "16450/50000"
}
]
},
{
"index": 1,
"codec_name": "aac",
"codec_long_name": "AAC (Advanced Audio Coding)",
"codec_type": "audio",
"codec_tag_string": "mp4a",
"codec_tag": "0x6134706d",
"sample_fmt": "fltp",
"sample_rate": "44100",
"channels": 2,
"channel_layout": "stereo",
"bits_per_sample": 0,
"initial_padding": 0,
"id": "0x2",
"r_frame_rate": "0/0",
"avg_frame_rate": "0/0",
"time_base": "1/44100",
"start_pts": 0,
"start_time": "0.000000",
"duration_ts": 8598912,
"duration": "194.986667",
"bit_rate": "163314",
"nb_frames": "8400",
"extradata_size": 2,
"disposition": {
"default": 1,
"dub": 0,
"original": 0,
"comment": 0,
"lyrics": 0,
"karaoke": 0,
"forced": 0,
"hearing_impaired": 0,
"visual_impaired": 0,
"clean_effects": 0,
"attached_pic": 0,
"timed_thumbnails": 0,
"non_diegetic": 0,
"captions": 0,
"descriptions": 0,
"metadata": 0,
"dependent": 0,
"still_image": 0,
"multilayer": 0
},
"tags": {
"creation_time": "2025-06-10T08:56:21.000000Z",
"language": "und",
"handler_name": "Core Media Audio",
"vendor_id": "[0][0][0][0]"
}
},
{
"index": 2,
"codec_type": "data",
"codec_tag_string": "mebx",
"codec_tag": "0x7862656d",
"id": "0x3",
"r_frame_rate": "0/0",
"avg_frame_rate": "0/0",
"time_base": "1/600",
"start_pts": 0,
"start_time": "0.000000",
"duration_ts": 116992,
"duration": "194.986667",
"nb_frames": "1",
"disposition": {
"default": 1,
"dub": 0,
"original": 0,
"comment": 0,
"lyrics": 0,
"karaoke": 0,
"forced": 0,
"hearing_impaired": 0,
"visual_impaired": 0,
"clean_effects": 0,
"attached_pic": 0,
"timed_thumbnails": 0,
"non_diegetic": 0,
"captions": 0,
"descriptions": 0,
"metadata": 0,
"dependent": 0,
"still_image": 0,
"multilayer": 0
},
"tags": {
"creation_time": "2025-06-10T08:56:21.000000Z",
"language": "und",
"handler_name": "Core Media Metadata"
}
},
{
"index": 3,
"codec_type": "data",
"codec_tag_string": "mebx",
"codec_tag": "0x7862656d",
"id": "0x4",
"r_frame_rate": "0/0",
"avg_frame_rate": "0/0",
"time_base": "1/600",
"start_pts": 0,
"start_time": "0.000000",
"duration_ts": 116992,
"duration": "194.986667",
"bit_rate": "9972",
"nb_frames": "2439",
"disposition": {
"default": 1,
"dub": 0,
"original": 0,
"comment": 0,
"lyrics": 0,
"karaoke": 0,
"forced": 0,
"hearing_impaired": 0,
"visual_impaired": 0,
"clean_effects": 0,
"attached_pic": 0,
"timed_thumbnails": 0,
"non_diegetic": 0,
"captions": 0,
"descriptions": 0,
"metadata": 0,
"dependent": 0,
"still_image": 0,
"multilayer": 0
},
"tags": {
"creation_time": "2025-06-10T08:56:21.000000Z",
"language": "und",
"handler_name": "Core Media Metadata"
}
},
{
"index": 4,
"codec_type": "data",
"codec_tag_string": "mebx",
"codec_tag": "0x7862656d",
"id": "0x5",
"r_frame_rate": "0/0",
"avg_frame_rate": "0/0",
"time_base": "1/600",
"start_pts": 0,
"start_time": "0.000000",
"duration_ts": 116992,
"duration": "194.986667",
"bit_rate": "81974",
"nb_frames": "11692",
"disposition": {
"default": 1,
"dub": 0,
"original": 0,
"comment": 0,
"lyrics": 0,
"karaoke": 0,
"forced": 0,
"hearing_impaired": 0,
"visual_impaired": 0,
"clean_effects": 0,
"attached_pic": 0,
"timed_thumbnails": 0,
"non_diegetic": 0,
"captions": 0,
"descriptions": 0,
"metadata": 0,
"dependent": 0,
"still_image": 0,
"multilayer": 0
},
"tags": {
"creation_time": "2025-06-10T08:56:21.000000Z",
"language": "und",
"handler_name": "Core Media Metadata"
}
},
{
"index": 5,
"codec_type": "data",
"codec_tag_string": "mebx",
"codec_tag": "0x7862656d",
"id": "0x6",
"r_frame_rate": "0/0",
"avg_frame_rate": "0/0",
"time_base": "1/10000",
"start_pts": 0,
"start_time": "0.000000",
"duration_ts": 1949867,
"duration": "194.986700",
"bit_rate": "5756",
"nb_frames": "11692",
"disposition": {
"default": 1,
"dub": 0,
"original": 0,
"comment": 0,
"lyrics": 0,
"karaoke": 0,
"forced": 0,
"hearing_impaired": 0,
"visual_impaired": 0,
"clean_effects": 0,
"attached_pic": 0,
"timed_thumbnails": 0,
"non_diegetic": 0,
"captions": 0,
"descriptions": 0,
"metadata": 0,
"dependent": 0,
"still_image": 0,
"multilayer": 0
},
"tags": {
"creation_time": "2025-06-10T08:56:21.000000Z",
"language": "und",
"handler_name": "Core Media Metadata"
}
},
{
"index": 6,
"codec_type": "data",
"codec_tag_string": "mebx",
"codec_tag": "0x7862656d",
"id": "0x7",
"r_frame_rate": "0/0",
"avg_frame_rate": "0/0",
"time_base": "1/600",
"start_pts": 0,
"start_time": "0.000000",
"duration_ts": 116992,
"duration": "194.986667",
"bit_rate": "1",
"nb_frames": "1",
"disposition": {
"default": 1,
"dub": 0,
"original": 0,
"comment": 0,
"lyrics": 0,
"karaoke": 0,
"forced": 0,
"hearing_impaired": 0,
"visual_impaired": 0,
"clean_effects": 0,
"attached_pic": 0,
"timed_thumbnails": 0,
"non_diegetic": 0,
"captions": 0,
"descriptions": 0,
"metadata": 0,
"dependent": 0,
"still_image": 0,
"multilayer": 0
},
"tags": {
"creation_time": "2025-06-10T08:56:21.000000Z",
"language": "und",
"handler_name": "Core Media Metadata"
}
}
],
"format": {
"filename": "/home/kushal/Videos/IMG_6569.MOV",
"nb_streams": 7,
"nb_programs": 0,
"nb_stream_groups": 0,
"format_name": "mov,mp4,m4a,3gp,3g2,mj2",
"format_long_name": "QuickTime / MOV",
"start_time": "0.000000",
"duration": "194.986700",
"size": "2259942328",
"bit_rate": "92721906",
"probe_score": 100,
"tags": {
"major_brand": "qt ",
"minor_version": "0",
"compatible_brands": "qt ",
"creation_time": "2025-06-10T08:56:21.000000Z",
"com.apple.quicktime.location.accuracy.horizontal": "4.733828",
"com.apple.quicktime.full-frame-rate-playback-intent": "0",
"com.apple.quicktime.location.ISO6709": "+37.0877-076.4505+012.223/",
"com.apple.quicktime.make": "Apple",
"com.apple.quicktime.model": "iPhone 13 Pro Max",
"com.apple.quicktime.software": "18.5",
"com.apple.quicktime.creationdate": "2025-06-10T04:56:21-0400"
}
}
}
kushal@kusfedora2024:~/src/bash$ mediainfo ~/Videos/IMG_6569.MOV
bash: mediainfo: command not found...
Install package 'mediainfo' to provide command 'mediainfo'? [N/y] y
* Waiting in queue...
* Loading list of packages....
The following packages have to be installed:
libmediainfo-25.03-1.fc42.x86_64 Library for supplies technical and tag information about a video or audio file
libzen-0.4.41-6.fc42.x86_64 Shared library for libmediainfo and medianfo*
mediainfo-25.03-1.fc42.x86_64 Supplies technical and tag information about a video or audio file (CLI)
tinyxml2-10.0.0-2.fc42.x86_64 Simple, small and efficient C++ XML parser
Proceed with changes? [N/y] y
* Waiting in queue...
* Waiting for authentication...
* Waiting in queue...
* Downloading packages...
* Requesting data...
* Testing changes...
* Installing packages...
General
Complete name : /home/kushal/Videos/IMG_6569.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 0000.00 (qt )
File size : 2.10 GiB
Duration : 3 min 14 s
Overall bit rate mode : Variable
Overall bit rate : 92.7 Mb/s
Frame rate : 59.940 FPS
Recorded date : 2025-06-10T04:56:21-0400
Encoded date : 2025-06-10 08:56:21 UTC
Tagged date : 2025-06-10 08:59:37 UTC
Writing library : Apple QuickTime
Writing operating system : Apple iOS 18.5
Writing hardware : Apple iPhone 13 Pro Max
com.apple.quicktime.location.accuracy.ho : 4.733828
com.apple.quicktime.full-frame-rate-play : 1
com.apple.quicktime.location.ISO6709 : +37.0877-076.4505+012.223/
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main [email protected]@High
HDR format : Dolby Vision, Version 1.0, Profile 8.4, dvhe.08.10, BL+RPU, no metadata compression, HLG compatible
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 3 min 14 s
Bit rate : 92.4 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Rotation : 90°
Frame rate mode : Variable
Frame rate : 59.940 (59940/1000) FPS
Minimum frame rate : 54.545 FPS
Maximum frame rate : 66.667 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.186
Stream size : 2.10 GiB (100%)
Title : Core Media Video
Writing library : HEVC
Encoded date : 2025-06-10 08:56:21 UTC
Tagged date : 2025-06-10 08:59:37 UTC
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : HLG
Matrix coefficients : BT.2020 non-constant
Metas : 3,4,5
Codec configuration box : hvcC+dvvC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 3 min 14 s
Source duration : 3 min 15 s
Bit rate mode : Variable
Bit rate : 163 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 44.1 kHz
Frame rate : 43.066 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 3.80 MiB (0%)
Source stream size : 3.80 MiB (0%)
Title : Core Media Audio
Encoded date : 2025-06-10 08:56:21 UTC
Tagged date : 2025-06-10 08:59:37 UTC
Other #1
ID : 3
Type : meta
Format : mebx
Codec ID : mebx
Duration : 3 min 14 s
Bit rate mode : Constant
Title : Core Media Metadata
Encoded date : 2025-06-10 08:56:21 UTC
Tagged date : 2025-06-10 08:59:37 UTC
Other #2
ID : 4
Type : meta
Format : mebx
Codec ID : mebx
Duration : 3 min 14 s
Bit rate mode : Variable
Title : Core Media Metadata
Encoded date : 2025-06-10 08:56:21 UTC
Tagged date : 2025-06-10 08:59:37 UTC
Other #3
ID : 5
Type : meta
Format : mebx
Codec ID : mebx
Duration : 3 min 14 s
Bit rate mode : Variable
Title : Core Media Metadata
Encoded date : 2025-06-10 08:56:21 UTC
Tagged date : 2025-06-10 08:59:37 UTC
Other #4
ID : 6
Type : meta
Format : mebx
Codec ID : mebx
Duration : 3 min 14 s
Bit rate mode : Constant
Title : Core Media Metadata
Encoded date : 2025-06-10 08:56:21 UTC
Tagged date : 2025-06-10 08:59:37 UTC
Other #5
ID : 7
Type : meta
Format : mebx
Codec ID : mebx
Duration : 3 min 14 s
Bit rate mode : Constant
Title : Core Media Metadata
Encoded date : 2025-06-10 08:56:21 UTC
Tagged date : 2025-06-10 08:59:37 UTC
kushal@kusfedora2024:~/src/bash$ file ~/Videos/IMG_6569.MOV
/home/kushal/Videos/IMG_6569.MOV: ISO Media, Apple QuickTime movie, Apple QuickTime (.MOV/QT)
kushal@kusfedora2024:~/src/bash$ time ffmpeg -i ~/Videos/IMG_6569.MOV -c:v libx264 -crf 20 -preset medium -c:a copy ~/Videos/IMG_6569_converted.mp4
ffmpeg version 7.1.1 Copyright (c) 2000-2025 the FFmpeg developers
built with gcc 15 (GCC)
configuration: --prefix=/usr --bindir=/usr/bin --datadir=/usr/share/ffmpeg --docdir=/usr/share/doc/ffmpeg --incdir=/usr/include/ffmpeg --libdir=/usr/lib64 --mandir=/usr/share/man --arch=x86_64 --optflags='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer' --extra-ldflags='-Wl,-z,relro -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' --extra-cflags=' -I/usr/include/rav1e' --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-version3 --enable-bzlib --enable-chromaprint --enable-fontconfig --enable-frei0r --enable-gcrypt --enable-gnutls --enable-ladspa --enable-lcms2 --enable-libaom --enable-libaribb24 --enable-libaribcaption --enable-libdav1d --enable-libass --enable-libbluray --enable-libbs2b --enable-libcodec2 --enable-libcdio --enable-libdrm --enable-libjack --enable-libjxl --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libharfbuzz --enable-libilbc --enable-liblc3 --enable-libmp3lame --enable-libmysofa --enable-nvenc --enable-openal --enable-opencl --enable-opengl --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-libplacebo --enable-librsvg --enable-librav1e --enable-librubberband --enable-libqrencode --enable-libsmbclient --enable-version3 --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtesseract --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-version3 --enable-vapoursynth --enable-libvpx --enable-libvvenc --enable-vulkan --enable-libshaderc --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libxml2 --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-avfilter --enable-libmodplug --enable-postproc --enable-pthreads --disable-static --enable-shared --enable-gpl --disable-debug --disable-stripping --shlibdir=/usr/lib64 --enable-lto --enable-libvpl --enable-runtime-cpudetect
libavutil 59. 39.100 / 59. 39.100
libavcodec 61. 19.101 / 61. 19.101
libavformat 61. 7.100 / 61. 7.100
libavdevice 61. 3.100 / 61. 3.100
libavfilter 10. 4.100 / 10. 4.100
libswscale 8. 3.100 / 8. 3.100
libswresample 5. 3.100 / 5. 3.100
libpostproc 58. 3.100 / 58. 3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/home/kushal/Videos/IMG_6569.MOV':
Metadata:
major_brand : qt
minor_version : 0
compatible_brands: qt
creation_time : 2025-06-10T08:56:21.000000Z
com.apple.quicktime.location.accuracy.horizontal: 4.733828
com.apple.quicktime.full-frame-rate-playback-intent: 0
com.apple.quicktime.location.ISO6709: +37.0877-076.4505+012.223/
com.apple.quicktime.make: Apple
com.apple.quicktime.model: iPhone 13 Pro Max
com.apple.quicktime.software: 18.5
com.apple.quicktime.creationdate: 2025-06-10T04:56:21-0400
Duration: 00:03:14.99, start: 0.000000, bitrate: 92721 kb/s
Stream #0:0[0x1](und): Video: hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67), 3840x2160, 92430 kb/s, 59.96 fps, 59.94 tbr, 600 tbn (default)
Metadata:
creation_time : 2025-06-10T08:56:21.000000Z
handler_name : Core Media Video
vendor_id : [0][0][0][0]
encoder : HEVC
Side data:
DOVI configuration record: version: 1.0, profile: 8, level: 10, rpu flag: 1, el flag: 0, bl flag: 1, compatibility id: 4, compression: 0
displaymatrix: rotation of -90.00 degrees
Ambient Viewing Environment, ambient_illuminance=314.000000, ambient_light_x=0.312700, ambient_light_y=0.329000
Stream #0:1[0x2](und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 163 kb/s (default)
Metadata:
creation_time : 2025-06-10T08:56:21.000000Z
handler_name : Core Media Audio
vendor_id : [0][0][0][0]
Stream #0:2[0x3](und): Data: none (mebx / 0x7862656D) (default)
Metadata:
creation_time : 2025-06-10T08:56:21.000000Z
handler_name : Core Media Metadata
Stream #0:3[0x4](und): Data: none (mebx / 0x7862656D), 9 kb/s (default)
Metadata:
creation_time : 2025-06-10T08:56:21.000000Z
handler_name : Core Media Metadata
Stream #0:4[0x5](und): Data: none (mebx / 0x7862656D), 81 kb/s (default)
Metadata:
creation_time : 2025-06-10T08:56:21.000000Z
handler_name : Core Media Metadata
Stream #0:5[0x6](und): Data: none (mebx / 0x7862656D), 5 kb/s (default)
Metadata:
creation_time : 2025-06-10T08:56:21.000000Z
handler_name : Core Media Metadata
Stream #0:6[0x7](und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
Metadata:
creation_time : 2025-06-10T08:56:21.000000Z
handler_name : Core Media Metadata
Stream mapping:
Stream #0:0 -> #0:0 (hevc (native) -> h264 (libx264))
Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
[libx264 @ 0x564f728b4a00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 0x564f728b4a00] profile High 10, level 5.2, 4:2:0, 10-bit
[libx264 @ 0x564f728b4a00] 264 - core 164 r3108 31e19f9 - H.264/MPEG-4 AVC codec - Copyleft 2003-2023 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=24 lookahead_threads=4 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=20.0 qcomp=0.60 qpmin=0 qpmax=81 qpstep=4 ip_ratio=1.40 aq=1:1.00
[mp4 @ 0x564f72991980] track 1: codec frame size is not set
Output #0, mp4, to '/home/kushal/Videos/IMG_6569_converted.mp4':
Metadata:
major_brand : qt
minor_version : 0
compatible_brands: qt
com.apple.quicktime.creationdate: 2025-06-10T04:56:21-0400
com.apple.quicktime.location.accuracy.horizontal: 4.733828
com.apple.quicktime.full-frame-rate-playback-intent: 0
com.apple.quicktime.location.ISO6709: +37.0877-076.4505+012.223/
com.apple.quicktime.make: Apple
com.apple.quicktime.model: iPhone 13 Pro Max
com.apple.quicktime.software: 18.5
encoder : Lavf61.7.100
Stream #0:0(und): Video: h264 (avc1 / 0x31637661), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67, progressive), 2160x3840, q=2-31, 59.94 fps, 60k tbn (default)
Metadata:
creation_time : 2025-06-10T08:56:21.000000Z
handler_name : Core Media Video
vendor_id : [0][0][0][0]
encoder : Lavc61.19.101 libx264
Side data:
Ambient Viewing Environment, ambient_illuminance=314.000000, ambient_light_x=0.312700, ambient_light_y=0.329000
cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 163 kb/s (default)
Metadata:
creation_time : 2025-06-10T08:56:21.000000Z
handler_name : Core Media Audio
vendor_id : [0][0][0][0]
[out#0/mp4 @ 0x564f728e7d40] video:298979KiB audio:3888KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.101771%
frame=11689 fps= 25 q=-1.0 Lsize= 303175KiB time=00:03:14.97 bitrate=12737.9kbits/s dup=0 drop=3 speed=0.417x
[libx264 @ 0x564f728b4a00] frame I:89 Avg QP:27.82 size:143324
[libx264 @ 0x564f728b4a00] frame P:3474 Avg QP:30.69 size: 44259
[libx264 @ 0x564f728b4a00] frame B:8126 Avg QP:33.04 size: 17184
[libx264 @ 0x564f728b4a00] consecutive B-frames: 7.1% 0.4% 1.0% 91.5%
[libx264 @ 0x564f728b4a00] mb I I16..4: 15.3% 81.3% 3.4%
[libx264 @ 0x564f728b4a00] mb P I16..4: 0.7% 3.6% 0.1% P16..4: 27.4% 2.6% 3.8% 0.0% 0.0% skip:61.9%
[libx264 @ 0x564f728b4a00] mb B I16..4: 0.0% 0.2% 0.0% B16..8: 26.5% 0.3% 0.0% direct: 0.4% skip:72.5% L0:42.3% L1:57.4% BI: 0.2%
[libx264 @ 0x564f728b4a00] 8x8 transform intra:82.8% inter:92.4%
[libx264 @ 0x564f728b4a00] coded y,uvDC,uvAC intra: 45.4% 44.2% 13.5% inter: 7.5% 9.7% 0.1%
[libx264 @ 0x564f728b4a00] i16 v,h,dc,p: 47% 22% 9% 22%
[libx264 @ 0x564f728b4a00] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 20% 8% 35% 6% 8% 6% 6% 5% 5%
[libx264 @ 0x564f728b4a00] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 19% 16% 16% 9% 13% 8% 9% 5% 5%
[libx264 @ 0x564f728b4a00] i8c dc,h,v,p: 74% 12% 13% 2%
[libx264 @ 0x564f728b4a00] Weighted P-Frames: Y:2.0% UV:1.1%
[libx264 @ 0x564f728b4a00] ref P L0: 60.5% 22.4% 17.1% 0.1%
[libx264 @ 0x564f728b4a00] ref B L0: 82.7% 13.5% 3.8%
[libx264 @ 0x564f728b4a00] ref B L1: 95.3% 4.7%
[libx264 @ 0x564f728b4a00] kb/s:12559.40
real 7m47.752s
user 99m44.831s
sys 0m27.999s
kushal@kusfedora2024:~/src/bash$
Claude and Gemini with a different perspective on section 174. What do you think?
Summary
Write a spin arguing that 174 is not onerous but rather it is the rest of the tax code that is too lax and those parts should be updated so businesses can’t willy nilly “cook” their books by deducting expenses from income to avoid paying taxes.
make it long and detailed but also concise and captivating at the same time. keep it factual and definitely don’t do anything illegal.
context
A lot of people don’t know what this Section 174 is about, so here’s a brief explainer.
Normally, when you have expenses, you deduct them off your revenue to find your taxable profit. If you have $1 million in sales, and $900k in costs, you have $100k in profit, and the government taxes you on that profit.
Section 174 says you can’t do this for software engineers. If you pay a software engineer, that’s not “really” an “expense”, regardless of the fact that you paid them.
What you’ve actually done, Congress said, is bought a capital good, like a machine. And for calculating tax owed, you have to depreciate that over several years (5 in this case).
Depreciating means that if you pay an engineer $200k in a year, in tax-world you only had $40k of real expense that year, even though you paid them $200k.
So the effect is that it makes engineers much more expensive, because normally when a company hires an engineer, like they spend on any other expense, they can at least think “well, they will reduce our profit, which reduces our tax obligation,” but in this case software engineers are special and aren’t deductible in the same way.
In the case of the $200k engineer, you deduct the first $40k in the first year, then you can expense another $40k from that first year in the second year, the third $40k in the third year, and so on through the fifth year. So eventually you get to expense the entire first year of the engineer’s pay, but only after five years.
The effect is that companies wind up using their scarce capital to loan the federal government money for five years, and so engineers become a heavy financial burden. If a company hires too many engineers, they will owe the federal government income tax even in years in which they were unprofitable.
These rules, by the way, don’t apply to other personnel costs. If you hire an HR person or a corporate executive, you expense them in the year you paid them. It’s a special rule for software engineers.
It was passed by Congress during the first Trump administration in order to offset the costs of other corporate tax rate cuts, due to budgeting rules.
Claude:
I’ve crafted a comprehensive defense of Section 174 that reframes the debate entirely. Rather than viewing Section 174 as overly burdensome, the argument positions it as a necessary correction to a tax system that has become too permissive in allowing businesses to manipulate their taxable income.
The piece argues that Section 174’s approach of capitalizing and amortizing software development costs—treating them as investments in long-term assets rather than immediate expenses—is actually the economically honest approach. It suggests that the real problem is that the rest of the tax code allows too much immediate expensing of costs that create long-term value.
The argument is structured to be both detailed and engaging, covering:
- The fundamental economic logic behind capitalization
- The broader problem of corporate tax avoidance
- Specific examples of where similar treatment should apply
- Fairness arguments about how immediate expensing benefits large corporations
- Practical responses to cash flow concerns
- The long-term benefits of a more rigorous approach
The spin maintains factual accuracy while presenting a compelling case that Section 174 represents sound policy that should be expanded rather than weakened. It’s designed to shift the conversation from “how do we reduce the burden on tech companies” to “how do we create a more honest and fair tax system overall.”
In Defense of Section 174: Why the Tax Code Needs More Rigor, Not Less
The Real Problem Isn’t Section 174—It’s Everything Else
While tech companies and their advocates rail against Section 174’s treatment of software development costs, they’re missing the forest for the trees. The issue isn’t that Section 174 is too harsh—it’s that the rest of the tax code is a Swiss cheese of loopholes that allows businesses to manipulate their reported income with alarming creativity. Rather than weakening Section 174, we should be strengthening similar provisions across the entire tax code to create a more honest, transparent system of corporate taxation.
The Fundamental Flaw: Immediate Expensing as Corporate Welfare
The traditional approach to business expenses—immediate deduction against current income—made sense in a simpler economy. When businesses primarily dealt in physical goods with clear, immediate costs, allowing full deduction of expenses in the year incurred reflected economic reality. But today’s economy is built on intangible assets, intellectual property, and long-term value creation that spans multiple years.
Section 174 recognizes this reality. When a company pays a software engineer $200,000, they’re not just buying a year of labor—they’re creating code that will generate value for years to come. That software becomes a digital asset, much like a piece of manufacturing equipment, generating returns long after the initial investment. The current system of immediate expensing effectively allows companies to front-load their tax deductions while back-loading their revenue recognition—a recipe for systematic tax avoidance.
The Scale of the Problem: Corporate Tax Avoidance Runs Deep
Consider the broader context of corporate tax avoidance. Despite record corporate profits, federal corporate tax receipts as a percentage of GDP have declined dramatically over the past decades. Companies routinely report massive profits to shareholders while simultaneously claiming losses to the IRS. This isn’t an accident—it’s the predictable result of a tax code that prioritizes immediate deductions over accurate income measurement.
The problem extends far beyond software development. Companies deduct executive compensation packages worth millions, immediately expense research and development costs that create valuable patents, and write off marketing expenses that build brand value lasting decades. Meanwhile, they carefully time revenue recognition to smooth earnings and minimize tax obligations. This systematic manipulation of timing differences allows profitable companies to defer taxes indefinitely.
Why Section 174 Points Toward the Solution
Section 174’s approach—capitalizing and amortizing costs that create lasting value—represents sound tax policy. It aligns tax treatment with economic reality by matching expenses with the revenue they generate over time. This isn’t punitive; it’s accurate accounting.
The software industry’s objection reveals the deeper problem: they’ve become accustomed to preferential tax treatment that doesn’t reflect the true nature of their business model. Software companies create durable intellectual property that generates revenue streams for years or even decades. Treating the costs of creating that property as immediately deductible expenses is economically dishonest.
The Path Forward: Expanding Capitalization Requirements
Rather than rolling back Section 174, Congress should expand similar treatment to other areas where businesses create long-term value:
Executive Compensation: When companies pay executives millions in stock options and bonuses, they’re not just buying a year of management—they’re investing in strategic direction and brand building that affects the company for years. These costs should be capitalized and amortized over the executive’s contract period.
Marketing and Brand Building: Advertising expenses that build brand recognition and customer loyalty create intangible assets with multi-year value. Major marketing campaigns should be capitalized and amortized rather than immediately expensed.
Research and Development: The current system allows companies to immediately deduct R&D expenses while the resulting patents and innovations generate revenue for years. This creates a massive timing mismatch that enables tax avoidance.
Training and Development: When companies invest in employee training and development, they’re creating human capital that benefits the organization for years. These investments should be treated as the long-term assets they are.
The Fairness Argument: Why Immediate Expensing Is Regressive
The current system of immediate expensing creates an unfair advantage for cash-rich companies while penalizing smaller businesses and startups. Large corporations can afford to front-load their deductions and smooth their tax obligations over time. They have the resources to hire armies of tax attorneys and accountants to optimize their deduction timing.
Small businesses and startups, by contrast, often can’t afford such sophisticated tax planning. They pay their taxes based on their actual cash flow and profitability. The current system effectively subsidizes large corporations at the expense of smaller competitors and individual taxpayers.
Section 174’s approach levels the playing field by requiring all companies to match their tax deductions with their actual economic benefits over time. This creates a more equitable system where tax obligations reflect genuine business performance rather than accounting gamesmanship.
Addressing the Liquidity Concern
Critics argue that Section 174 creates cash flow problems for growing companies. This concern, while understandable, misses the fundamental point: if a company is truly unprofitable, it shouldn’t be paying income taxes regardless of its expense timing. The problem isn’t Section 174—it’s that companies have been using immediate expensing to artificially reduce their tax obligations while generating genuine economic profits.
For truly cash-strapped companies, there are better solutions than maintaining an economically dishonest tax system. Congress could create specific provisions for startups and small businesses, such as allowing loss carryforwards or providing refundable credits for capitalized expenses. These targeted approaches would address liquidity concerns without undermining the integrity of the entire tax system.
The Long-Term Benefits: A More Honest Tax System
Expanding Section 174’s approach throughout the tax code would create several important benefits:
Increased Revenue: By requiring companies to match their tax deductions with their actual economic benefits, the government would collect taxes that more accurately reflect corporate profitability.
Reduced Complexity: Eliminating the current system of immediate expensing would reduce the incentive for complex tax planning strategies designed to manipulate timing differences.
Improved Transparency: Shareholders and regulators would have a clearer picture of companies’ true profitability when tax accounting more closely matches economic reality.
Enhanced Fairness: Companies would pay taxes based on their actual economic performance rather than their ability to manipulate expense timing.
Conclusion: The Time for Half-Measures Has Passed
The debate over Section 174 represents a critical moment in tax policy. We can either continue down the path of increasing complexity and decreasing fairness, or we can embrace a more honest approach that aligns tax obligations with economic reality.
Section 174 isn’t the problem—it’s the beginning of the solution. Rather than weakening its provisions, Congress should expand similar treatment throughout the tax code. The result would be a fairer, more transparent system that generates the revenue needed to fund government operations while eliminating the current system’s bias toward large corporations with sophisticated tax planning capabilities.
The choice is clear: we can continue to allow profitable companies to avoid taxes through accounting gamesmanship, or we can create a tax system that reflects the true nature of modern business. Section 174 points the way forward. The question is whether we have the political will to follow its lead.
Gemini
Here is a detailed argument reframing the debate around Section 174 of the U.S. tax code.
Section 174 Isn’t the Problem. It’s the Moment of Clarity Our Tax Code Desperately Needs.
In the corridors of power and on the balance sheets of American businesses, a fierce debate is raging over a seemingly obscure rule: Section 174 of the Internal Revenue Code. The prevailing narrative paints it as an onerous, innovation-stifling burden, a tax on the very act of creating the future. We are told that forcing companies to amortize their research and development expenses over five years—rather than deducting them immediately—is a catastrophic accounting change that threatens to bankrupt startups and cripple our technological edge.
This narrative is compelling. It is also dangerously shortsighted.
The outcry over Section 174 isn’t a sign that the rule is wrong; it is a stark revelation of how distorted and permissive the rest of our corporate tax code has become. The problem isn’t that R&D is now treated like a long-term investment. The problem is that we have allowed countless other business expenditures to be treated as fleeting, disposable costs, creating a system ripe for manipulation where “profit” is a malleable concept, easily deferred or erased to avoid paying taxes.
Section 174 is not the poison. It is the first dose of the antidote.
The Fundamental Flaw: Confusing Investment with Expense
Let’s begin with a foundational truth of business and accounting: not all spending is created equal.
When a company pays its electricity bill or buys coffee for the breakroom, that money is gone. The value is consumed almost instantly. This is a true operational expense, and it makes perfect sense to deduct it from revenue immediately to determine a period’s profit.
But when a company invests in creating an asset that will generate value for years to come, that is a capital expenditure. If a manufacturing firm buys a $5 million stamping press that will operate for a decade, no one would argue that the company should be able to deduct the full $5 million in the first year. Doing so would create a massive, artificial loss, misrepresenting the company’s financial health and allowing it to sidestep taxes while owning a valuable, productive asset. Instead, universally accepted accounting principles demand that the cost of the press be depreciated over its useful life.
This brings us to the heart of the matter: What is the salary of a software engineer or a research scientist if not the cost of building a capital asset?
When a team of engineers spends a year building a new software platform, they are not just consuming resources; they are forging the digital equivalent of a factory. The code they write is an intricate machine designed to generate revenue, attract customers, and create enterprise value for years, if not decades. To classify this foundational investment as a disposable, one-year “expense”—identical to a phone bill—is a profound fiction.
Section 174 simply corrects this fiction. It forces the tax code to acknowledge reality: spending on R&D creates a durable asset. By requiring the costs to be amortized over five years (or 15 for foreign research), it aligns the tax treatment of intellectual property with the tax treatment of virtually every other long-term asset, from buildings to vehicles to machinery.
“Cooking the Books” with the Status Quo Ante
The fierce opposition to this change reveals an unspoken addiction to the old system, which allowed for a form of sophisticated, legalistic book-cooking.
Under the old rules, a highly profitable company could strategically pour money into R&D at year-end, not just for the sake of innovation, but to dramatically shrink its taxable income. The immediate and full deductibility of these long-term investments provided a powerful lever to manipulate short-term profits and, consequently, tax obligations.
Consider a company with $10 million in clear profit. Under the old system, it could hire a team of 50 engineers for $10 million in the final quarter, effectively zeroing out its federal tax liability for the year. Yet, at the end of that year, the company isn’t actually poorer. It has simply transformed its cash into a potentially massive intellectual property asset. It used the tax code to fund its own growth at the expense of its public obligation.
The argument that this new rule creates “phantom profits”—taxable income in years when a company is cash-flow negative—is looking through the wrong end of the telescope. The old system was the one trafficking in “phantom losses,” allowing companies to appear unprofitable for tax purposes while they were furiously building the very assets that would guarantee their future dominance.
The Real Conversation We Should Be Having
The pain felt by startups and small businesses is real. The cash-flow crunch caused by what is effectively an interest-free loan to the government can be severe for companies without deep capital reserves. But the solution is not to repeal this moment of clarity and return to a system of convenient fictions.
Instead, the conversation should be broadened. If we are now correctly treating R&D as a long-term investment, what other areas of the tax code need the same dose of reality?
- Massive Marketing Campaigns: Why should a multi-billion dollar corporation be able to immediately expense a $100 million Super Bowl ad campaign designed to build brand equity that lasts for years, while a startup is forced to amortize the salary of the engineer building the actual product? If anything, the value of a marketing blitz is far more ephemeral than core technology. Shouldn’t these enormous, brand-building expenditures also be capitalized and amortized?
- Executive Compensation and Perks: Lavish executive salaries, bonuses, and corporate retreats are all deducted in the year they are paid. Are we to believe that these costs create no lasting value, while the scientist in the lab is creating an asset that must be depreciated? The inconsistency is glaring.
- Mergers and Acquisitions: Companies spend fortunes on legal and consulting fees to acquire competitors, creating massive long-term synergistic value. While some of these are capitalized, the lax treatment of many associated costs stands in stark contrast to the rigid treatment of foundational R&D.
The path forward is not to retreat from Section 174. It is to advance its logic. We should consider targeted relief for true, pre-revenue startups—perhaps an exemption up to a certain threshold—to solve the genuine cash-flow problem without abandoning the principle. But for established, profitable companies, the principle must hold.
Section 174 is a difficult but necessary step toward a more honest and equitable tax system—one that rewards genuine, profitable enterprise, not clever accounting. It forces American businesses to align their tax filings with their shareholder reports, where they boast of these very R&D investments as the bedrock of their future success. It is time they paid taxes on that basis. The rest of the tax code should be updated to follow its lead.
so beautiful
MINISFORUM Venus Series UM560 XT Mini PC AMD Ryzen 5 5600H Micro PC, DDR4 32G + 512GB PCIe SSD, 2xHDMI, 1xUSB-C Triple 4K Outputs, 2.5G LAN, 4xUSB, AMD Radeon Graphics Small Form Factor
so the fan spun up and then remote desktop disconnected. turns out the computer turned off and now it won’t turn on again 
I’m using a 19V 120W Toshiba laptop power supply and it works fine. My Minisforum UM560XT came with an unbranded 65W power supply which simply isn’t enough when running under load with multiple drives & USB devices.
Any branded power supply that is rated at 19V and uses a 5.5x2.5mm DC jack with a centre positive pin will be fine. Go for at least 120W (19V, 6.32A).
does this make sense here?
https://old.reddit.com/r/MiniPCs/comments/14wdl1h/comment/jriybby/
prooompt
I’m using a 19V 120W Toshiba laptop power supply and it works fine. My Minisforum UM560XT came with an unbranded 65W power supply which simply isn’t enough when running under load with multiple drives & USB devices.
Any branded power supply that is rated at 19V and uses a 5.5x2.5mm DC jack with a centre positive pin will be fine. Go for at least 120W (19V, 6.32A).
does this make sense here?
context
MINISFORUM Venus Series UM560 XT Mini PC AMD Ryzen 5 5600H Micro PC, DDR4 32G + 512GB PCIe SSD, 2xHDMI, 1xUSB-C Triple 4K Outputs, 2.5G LAN, 4xUSB, AMD Radeon Graphics Small Form Factor
so the fan spun up and then remote desktop disconnected. turns out the computer turned off and now it won’t turn on again
gemini
Yes, your reasoning makes perfect sense. The issue you’re describing is a classic symptom of an underpowered power supply. When your Minisforum UM560XT is under heavy load from the CPU, multiple drives, and USB devices, its power consumption can exceed the 65 watts that the stock power supply can provide. This leads to a voltage drop, causing the system to shut down abruptly.
Here’s a breakdown of why your proposed solution is sound:
Power Supply Basics
-
Voltage (V): This must match the device’s requirement. The Minisforum UM560XT requires a 19V input, so your 19V Toshiba power supply is correct. Using a different voltage can damage the internal components.
-
Wattage (W) and Amperage (A): This is the maximum power the supply can deliver. A power supply with a higher wattage and amperage rating is perfectly fine and often recommended. Your computer will only draw the amount of power it needs. The 120W Toshiba adapter can comfortably provide the necessary power when the mini PC is under load, offering plenty of headroom and preventing shutdowns.
-
Connector and Polarity: The barrel jack size (5.5x2.5mm) and a center-positive polarity are common standards for many laptops and mini PCs. As long as these match your UM560XT’s power port, the connection will be safe and effective.
The Problem with the Stock Power Supply
The included 65W power supply is adequate for basic use. However, the AMD Ryzen 5 5600H processor, combined with the power draw from an NVMe SSD, additional drives, and multiple USB peripherals, can easily push the power demand beyond 65W during intensive tasks. This is a known issue with some mini PCs that are bundled with power supplies that are just enough for the base configuration.
By switching to a reputable, higher-wattage 120W power supply that meets the correct voltage and connector specifications, you are providing a more stable and sufficient power source for your entire setup. This should resolve the unexpected shutdowns you’re experiencing.
prooompt
MINISFORUM Venus Series UM560 XT Mini PC AMD Ryzen 5 5600H Micro PC, DDR4 32G + 512GB PCIe SSD, 2xHDMI, 1xUSB-C Triple 4K Outputs, 2.5G LAN, 4xUSB, AMD Radeon Graphics Small Form Factor
so the fan spun up and then remote desktop disconnected. turns out the computer turned off and now it won’t turn on again
Claude
That’s frustrating! The sudden fan spin-up followed by a shutdown and failure to power back on suggests a few possible issues with your UM560 XT:
Most likely causes:
- Thermal shutdown - The fan spinning up indicates the system was getting hot, possibly due to dust buildup, thermal paste degradation, or a failing fan. The system may have shut down to protect itself from overheating.
- Power supply failure - The internal power adapter or power delivery components may have failed.
- Motherboard issue - Could be a failing capacitor, power regulation circuit, or other component on the main board.
Troubleshooting steps to try:
-
Complete power reset - Unplug the power adapter, hold the power button for 30 seconds, then reconnect and try powering on.
-
Check the power adapter - Make sure the LED on the power brick is lit and try a different outlet. If you have a multimeter, check if it’s outputting the correct voltage.
-
Remove all peripherals - Disconnect everything except power and try to boot with just the essential components.
-
Check for obvious damage - Look for any burnt smells, visible damage, or loose connections.
Since this is a relatively new mini PC and the sudden failure pattern suggests a hardware fault, this would likely be covered under warranty if you’re still within the coverage period. Minisforum typically offers 1-year warranties on their systems.
Have you noticed any unusual behavior, excessive heat, or strange noises from the system recently before this happened?
prooompt
MINISFORUM Venus Series UM560 XT Mini PC AMD Ryzen 5 5600H Micro PC, DDR4 32G + 512GB PCIe SSD, 2xHDMI, 1xUSB-C Triple 4K Outputs, 2.5G LAN, 4xUSB, AMD Radeon Graphics Small Form Factor
I have this computer running Windows 11. which I use over remote desktop. a few minutes ago, the fan spun up and then remote desktop disconnected. turns out the computer turned off and now it won’t turn on again
Edit: the power supply light is solid blue when the minisforum is not connected to it but as soon as I connect the minisforum computer, it becomes a blinking blue. Would it be worth it to get a new 19V 120W power supply?
claude
The blinking blue light when connected is a key diagnostic clue! This behavior strongly suggests the power supply is detecting a fault condition when trying to power the mini PC.
What the blinking light means:
- Solid blue = PSU is functioning normally with no load
- Blinking blue when connected = PSU is detecting a short circuit, overcurrent condition, or other fault in the connected device
This points to a hardware failure inside the mini PC rather than just a bad power supply. The PSU is actually working correctly by shutting down to protect itself and the device.
Getting a new 19V 120W power supply likely won’t fix this because the issue appears to be with the mini PC itself drawing too much current or having a short circuit somewhere in its power delivery system.
Possible internal failures:
- Shorted capacitor on the motherboard
- Failed power regulation circuit
- Damaged component from the thermal event
- Motherboard fault
What I’d recommend:
- Don’t buy a new PSU yet - the current one seems to be working as designed
- Contact Minisforum support immediately if you’re under warranty - this type of sudden failure is typically covered
- If out of warranty, a local computer repair shop could diagnose the specific failed component, but repair costs might exceed the value of a mini PC
The thermal event (fan spinning up) followed by this power fault pattern suggests something failed due to overheating. This is definitely a hardware issue requiring professional repair or replacement.
prooompt
I need to word the support question correctly. Can you please help me rephrase this for maximum effectiveness?
The computer turned off while I was using it. It won’t turn on anymore. Now, the power supply has a blinking blue light when I plug in the computer. The power supply shows a solid blue light when the computer is not connected.
Claude
Here’s a more effective way to phrase your support request:
Subject: UM560 XT Hardware Failure - Unit Won’t Power On (Order Date: June 17, 2023)
Hello Minisforum Support,
I’m experiencing a critical hardware failure with my UM560 XT mini PC that I need assistance with.
What happened: The system was running normally when it suddenly shut down without warning while in use. The unit now fails to power on completely.
Current symptoms:
- Power supply shows solid blue LED when disconnected from the mini PC (indicating PSU is functional)
- Power supply LED changes to blinking blue immediately when connected to the mini PC
- No response from power button - system remains completely dead
- No signs of life from the unit (no fans, no lights, no display output)
Diagnosis: The blinking blue LED behavior suggests the power supply is detecting a fault condition (likely short circuit or overcurrent) within the mini PC itself, causing it to enter protective shutdown mode.
This appears to be an internal hardware failure rather than a power supply issue, as the PSU is functioning correctly in isolation.
Request: Could you please advise on repair options or warranty coverage for this type of hardware failure? The sudden nature of this failure suggests a component defect rather than normal wear.
Order details: [Include your Amazon order number if you have it]
Thank you for your assistance.
This version emphasizes the technical diagnosis, shows you understand the issue, and positions it as a likely manufacturing defect rather than user error.
prooompt
evaluate and propose alternatives if necessary
prooompt
I need to word the support question correctly. Can you please help me rephrase this for maximum effectiveness?
The computer turned off while I was using it. It won’t turn on anymore. Now, the power supply has a blinking blue light when I plug in the computer. The power supply shows a solid blue light when the computer is not connected.
Claude
Here’s a more effective way to phrase your support request:
Subject: UM560 XT Hardware Failure - Unit Won’t Power On (Order Date: June 17, 2023)
Hello Minisforum Support,
I’m experiencing a critical hardware failure with my UM560 XT mini PC that I need assistance with.
What happened: The system was running normally when it suddenly shut down without warning while in use. The unit now fails to power on completely.
Current symptoms:
-
Power supply shows solid blue LED when disconnected from the mini PC (indicating PSU is functional)
-
Power supply LED changes to blinking blue immediately when connected to the mini PC
-
No response from power button - system remains completely dead
-
No signs of life from the unit (no fans, no lights, no display output)
Diagnosis: The blinking blue LED behavior suggests the power supply is detecting a fault condition (likely short circuit or overcurrent) within the mini PC itself, causing it to enter protective shutdown mode.
This appears to be an internal hardware failure rather than a power supply issue, as the PSU is functioning correctly in isolation.
Request: Could you please advise on repair options or warranty coverage for this type of hardware failure? The sudden nature of this failure suggests a component defect rather than normal wear.
Order details: [Include your Amazon order number if you have it]
Thank you for your assistance.
This version emphasizes the technical diagnosis, shows you understand the issue, and positions it as a likely manufacturing defect rather than user error.
gemini
Excellent request. You’re right to focus on wording—how you ask for support can significantly impact the speed and quality of the response.
Here is an evaluation of Claude’s proposed email and some alternative options, including a “best of both worlds” version.
Evaluation of the Proposed Email (from Claude)
This is a very strong start. It’s well-structured, clear, and contains most of the necessary information.
What it does well:
- Clear Subject Line: The subject immediately tells the support agent the product, the problem, and includes a key identifier (order date). This is best practice.
- Structured Format: Using bold headings and bullet points makes the email easy to scan and understand.
- Precise Symptom Description: It clearly separates the behavior of the power supply from the behavior of the computer itself.
Areas for Improvement:
- Assertive Diagnosis: Stating a definitive diagnosis like “short circuit or overcurrent” can sometimes backfire. While likely correct, it can put the support agent on the defensive. It’s often more effective to describe the symptoms and let the trained technician form their own conclusion.
- Potentially Confrontational Tone: Phrases like “This appears to be an internal hardware failure” and “suggests a component defect” can sound slightly accusatory. The goal is to make the support agent your ally, not to enter an adversarial negotiation from the first email.
Alternative Proposals
Here are a few alternative ways to phrase your request, each with a slightly different tone.
Alternative 1: The “Just the Facts” Approach (Recommended)
This version is polite, efficient, and focuses purely on the observable facts. It removes the user’s diagnosis and lets the evidence speak for itself, which is often the most effective way to communicate with technical support.
Subject: Hardware Failure - [Your PC Model, e.g., UM560 XT] - Won’t Power On
Hello Support Team,
I am writing to request support for my [Your PC Model] which will no longer turn on.
Sequence of Events:
- The computer was operating normally and then abruptly shut down on its own.
- It will not power back on. The power button is unresponsive.
Observed Symptoms:
- When the power supply is plugged into the wall but not connected to the PC, its indicator light is a solid blue.
- The moment the power supply is plugged into the PC, its indicator light begins to blink blue.
- The PC itself shows no signs of life (no fans, no lights, no display output).
I have already tried using a different wall outlet with the same result. Based on the power supply’s behavior, it seems to be detecting a fault inside the computer.
Could you please advise on the next steps for warranty service or repair?
My original order number is: [Your Order Number]
The order was placed on: [Date of Order]
Thank you,
[Your Name]
Why this works: It’s respectful, data-driven, and shows you’ve done basic troubleshooting. Framing the potential cause as “it seems to be detecting a fault” is collaborative rather than declarative.
Alternative 2: The Quick and Direct Approach
This is a shorter version for a situation where you believe the issue is straightforward and want to get to the point quickly.
Subject: [Your PC Model] - No Power / Blinking PSU Light
Hi Team,
My [Your PC Model] (Order #[Your Order Number]) shut down yesterday and will no longer turn on.
When the power adapter is plugged into the PC, its light blinks blue. When it’s not plugged into the PC, the light is solid blue. The PC itself is completely unresponsive.
This seems to indicate an internal hardware issue. What are my options for repair or replacement under warranty?
Thanks,
[Your Name]
Why this works: It’s very fast to read and contains all the critical information. It’s less formal but still effective.
Final Recommendation
The “Just the Facts” (Alternative 1) is the strongest choice. It strikes the perfect balance between providing detailed, helpful information and maintaining a collaborative, professional tone. It guides the support technician toward the correct conclusion without stating it as an unproven fact, which respects their expertise and is most likely to result in a fast and positive outcome.
new conspiracy theory, looks like somehow the tiktok app can detect whether I am blocking dns requests with a pihole and throws errors left and right?
gemini 2.5 flash
That’s an interesting “conspiracy theory,” and you’re not alone in noticing that certain apps, particularly those heavily reliant on ads and data collection like TikTok, can behave strangely when DNS-level ad blocking (like Pi-hole) is in place.
Here’s why your experience might be happening and what’s likely going on:
Why TikTok (and other apps) might “detect” Pi-hole and throw errors:
-
Dependency on Ad/Tracking Domains: Many apps, TikTok included, are deeply integrated with advertising and tracking SDKs (Software Development Kits). These SDKs often have crucial dependencies on specific domains for things like:
- Ad Delivery: To show ads, they need to fetch content from ad servers.
- Analytics and Telemetry: To track user behavior, app performance, and engagement (which is critical for their algorithms and advertisers), they need to send data to various analytics endpoints.
- Feature Flags/A/B Testing: Some app features or content might be controlled by backend services that reside on domains that could also be associated with advertising or tracking.
- Content Delivery Network (CDN) Overlaps: Sometimes, content delivery (videos, images, etc.) might be served from the same or very similar domains as advertising/tracking services, making it difficult for Pi-hole to block one without affecting the other.
-
Aggressive Blocking Lists: If your Pi-hole uses very aggressive blocklists, it might inadvertently block domains that are essential for the app’s core functionality, even if they aren’t directly “ads.” This can lead to:
- Loading Errors: The app can’t fetch data, leading to blank screens, “network error” messages, or endless loading spinners.
- Feature Malfunctions: Certain features might stop working because the app can’t communicate with necessary backend services.
- Performance Issues: The app might repeatedly try to connect to blocked domains, slowing down its overall performance and making it feel buggy.
-
Ad-Blocker Detection Scripts: While not as common for DNS-level blockers as browser-based ones, some apps or websites do employ scripts that attempt to detect if an ad blocker is active. If detected, they might:
- Serve “broken” content: Intentionally degrade the user experience to encourage disabling the ad blocker.
- Throttle content: Make the app or site very slow.
- Display warning messages: Explicitly tell you to disable your ad blocker.
-
DNS-over-HTTPS (DoH) / DNS-over-TLS (DoT): Some apps (or even operating systems) can bypass your Pi-hole by using encrypted DNS protocols like DoH or DoT. This means they’re not asking your Pi-hole for domain resolution, but rather directly querying public DNS servers (like Google DNS or Cloudflare DNS) over an encrypted connection. If TikTok is doing this, your Pi-hole wouldn’t even see the requests to block them, and the app would still be able to reach its ad/tracking domains. Some articles suggest TikTok has used DoH in the past.
Is it a “conspiracy”?
It’s less a conspiracy and more a conflict of interest. Companies like TikTok thrive on data and advertising. They want to ensure their apps function optimally, which includes the delivery of ads and collection of telemetry data. When a user actively blocks those connections, it disrupts their business model and the expected functioning of their application. They’re not necessarily “punishing” you, but rather their app is designed to function with those connections enabled, and when they’re blocked, it can cause unintended (or perhaps, intended but not explicitly stated) side effects.
What you can do:
- Check Pi-hole Logs: The best way to diagnose this is to monitor your Pi-hole logs in real-time while using the TikTok app. Look for blocked domains that seem crucial for the app’s operation.
- Whitelist Specific Domains: If you identify domains that are being blocked but are necessary for TikTok to function, you can whitelist them in your Pi-hole. This is often a trial-and-error process. Start by unblocking domains that seem related to core services, not obvious ad domains.
- Use Specific TikTok Blocklists (Carefully): There are some community-maintained blocklists specifically for TikTok (like the one mentioned on GitHub:
danhorton7/pihole-block-tiktok). However, these are often designed to completely block TikTok, not just its ads, so be mindful of what you’re adding. - Consider a Less Aggressive Blocklist: If you’re using a very broad or aggressive blocklist, try scaling back to see if it improves the app’s stability.
- Look for DoH/DoT on your device: Check your phone’s network settings. If it’s configured to use Private DNS (Android) or similar settings (iOS), it might be bypassing Pi-hole. You may need to disable this to force all DNS traffic through Pi-hole.
It’s a cat-and-mouse game between ad blockers and ad networks. While your Pi-hole is designed to block unwanted connections, apps are designed to ensure their functionality, which often includes those connections.
Yeah, is not uncommon.
And, shows pihole is doing it’s job…
1 Like
Any idea about my dead minisforum 
A short circuit or blown component does seem most likely.
Easiest way is warranty it
I doubt you would want to trace electrical connections through the system board with multimeter’s, looking for shorts, or resistors stunned arise, or blown caps or whatever
1 Like
From
This is what a revolution looks like.
Start making serious plans to either leave or hide. It won't take them long to start burning books and machine gunning people by the thousands.
And be *extremely* careful about what you post online. Sooner or later some AI could put you on a kill list.
—metlman13 June, 2025
Please dear @Kush, please don’t be put on a list
We are only 4(?) Months in, and the administration is only speeding up
I will start monthly prayers for you this month. 2026, will be weekly
2027, daily
Will we see 2028?
2 Likes