TIL something new… My hate for MacOS took over common logic. 2.8GB, 3 seconds file transfer on USB was to beautiful to be true. After some further investigation and hints from @JonnyRobbie@lemmy.world @nanook@friendica.eskimo.com I learned that Linux writes to cache before writing it to the device, to see whats happening in the background: sync & watch -n 1 grep -e Dirty: /proc/meminfo.
Still, the transfer speed on Linux was slightly faster than on MacOS. My rant was unjustified, It just my fault for being clueless on some more advanced Linux stuff. But I learned something new today, so this post was actually helpful !
Howerver, I still hate MacOS and will probably give Asahi remix a try.
Thanks to everyone !
Hey guys ! I’m getting tired/bored of MacOS’ shenanigans… Yesterday was the last drop that make me think of trying an alternative.
While trying to upload a 2.8 GB file over to an USB-C stick it took like 8 minutes? Okay that’s “good” enough if you only do it from time to time… But 25 files takes literally 1h30min… Are we in 2001?
I mean the exact same 2.8GB file, with the exact same USB-C stick took FU***** 3 seconds on Linux !!
Ohh and don’t think I didn’t tried to “fix” the issue, after a long search on the web I came across a lot of people having similar issues that aren’t fixed since 2 major updates? With a total radio silence from the shiny poisonous Apple…
Among other things I tried:
- Disable Spotlight indexing
sudo mdutil -a -i off - Reformat the USB stick from Mac
- All available filesystem FAT32, exFAT…(yes even MacOS native
APFS) - Another USB stick
- …
Enough is enough. I was willing to learn their way of thinking for my personal experience and somehow always got my way around to reproduce what I learned on Linux to Mac. But now that there is an alternative OS, I think I’m ready to get back home.
So does anyone here already gave Asahi Remix a try? If so what was your experience with it?
I read their FAQ and most of their documentation and it seems good enough for daily drive (except for some quirks here and there) but I wanted to hear from people who already made the jump and how was their personal feeling.
PS: I got that MacOS for my birthday from a family member with good intentions. That wasn’t a personal choice. While I’m more than happy and thankful for the gift, I totally hate it more and more… Especially because MOST of my self-hosted services, applications, scripts, are open source.
That’s good to hear ! Nowadays a play a lot with ffmpeg and mkvtools to encode my media library mostly to SVT-AV1/opus. I read somewhere in the documentation that they only playback H.264-encoded content. Does that mean that AV1 isn’t supported OTB yet?
Also video decoder/Encoder is WIP. Are they only talking about hardware or also software decoding/encoding?
Thanks for your response !
I ran into issues while exporting (rendering) with kdenlive, where you will notice available formats being different between the Mac version of kdenlive and the Linux one.
But to me it was a matter of compatibility, I don’t really care as long as I get useable files of sufficient quality, so I didn’t pay much attention, works-for-me style I’m afraid.
Same applies to hardware vs software encoding/decoding - the M chipset is quite powerful enough you shouldn’t have to worry about it in a pro context where encoding is something you gotta do and it’s doing it reasonably fast.
Just try it out, it doesn’t kill your mac install, and you can compare.
@reallyzen @N0x0n kdenlive uses ffmpeg so formats it has available depend upon what is compiled into your ffmpeg which for many linux distros is minimal. However, if you grab FFmeg from github, then configure it for every possible option and install all of the necessary libs (some of which you will also need to compile because most Linux distros do not include all of them), THEN kdenlive will have all possible output formats presently supported by opensource, but there are literally several hundred libraries and options needed, this and the configure file is a real piece of shit that rather than telling you every library that is missing so you can go chase them down all in one shot, instead tells you the first one missing and aborts, so you chase that down, run it again, and this literally takes about 300 iterations. But if you go through the trouble of doing all this and then put YOUR FFmpeg in the $PATH ahead of the system one, kdenlive will now show all the available formats for both input and output.
Eww. I ran into similar trying to build a meson app on Asahi. Fuck that. Since the point of the Fedora-Asahi partnership is to have a max of stuff upstream, I guess it leaves you with whatever fedora is shipping - which may not be good enough for you.
Again, depends in your use case; since the horrible business of having a full ffmpeg on one machine is done, you can use any sync software between them & not care further. I use syncthing to keep my mastering device (mbp 14, Asahi) in sync with a playback machine and a backup machine.
But it is my use case: I use different, dedicated devices for dedicated tasks as to spread out wear, risks and improve redundancy in case of failure.
@reallyzen Since I built the computer, I’m not too worried about hardware failures, I am competent in repairing them.
So you own a perfect mastering device at home, now you get the ultrathin laptop to wander about. One isn’t so portable, and the other may not be able to hardware-encode AV1 files. It only matters if it can play them decently.
Also, the M chips are good, but not that good. My M2 pro is about like a 12th gen i7, not like thrice quicker in any everyday way.