Ay, isn’t that the chocolate rain guy??

In my little slice of hell summer means it’s low to mid 90’s everyday with 60%+ humidity and it rains every fucking afternoon. You can’t go outside for more than 5mins without sweating profusely. It’s kinda ass.

I dicked around with the VM route for a while and could never really get it working 100% to my liking. There was always a trade-off. I ended up just getting a second PC and tucking it in a cabinet out of sight. When I need Windows I just use remote desktop to connect to it.

This picture broke my brain for a min. I thought the wall on the left was the floor and it was rotated.

I just recently had a wfh user ship me one of his monitors back because we had exhausted every thing I could think of troubleshooting-wise. When it arrived I unboxed it, plugged it in and the damn thing worked fine. I followed up with him and finally realized he had been trying to push the damn power LED instead of the actual power button.

I believe they created it before tap really took off in the US so scan was a better option for them at the time.

It’s scan to pay at Walmart because they gave their own payment system called “Walmart pay” and it sucks.

Do your friend a favor and install Windows back on his laptop for him.

Exactly. It’s pseudo code. It’s meant to be universally understandable, not language specific.

They have their uses. In particular they’re useful for easily getting applications your system repositories don’t have or getting more up to date version of applications. Downsides are certainly the space all the redundant dependencies take up and the sandboxing can be a PITA especially if you have an application that needs to run another application. Overall I think they’re the best “third party” package system available but they’re not great.

App Images do suck, but I don’t think flatpak is much better. It’s more of a lesser of two evils situation. Snap isn’t even in the conversation.

That seems like a bad faith argument, but I’ll indulge. Gasoline internal combustion engine aren’t made to run indefinitely and have many components that can wear over time and require regular maintenance. Modern computer hardware has no problem with the task and my “newest” computer which was built back in 2016 has run pretty much non-stop for 8 years now with 0 failure. At this point the hardware is more likely to be replaced due to age than failure. The only argument I can see making sense is maybe the cost of electricity aspect; but even then modern power supplies are so efficient I’d be surprised if it costs me more than $10/yr. to leave my PC on so I don’t it’s a very strong argument.

Nope, no issues in all these years.

Hmm. That’s interesting. The only thing I can think of that could potentially cause that is if for whatever reason there was an exisitng EFI partition on your linux drive. Windows will use whatever EFI it sees even if it’s on a separate drive from it’s primary NTFS partition. As you can imagine this can cause some fucky stuff to happen.

People who shutdown their desktop computer everytime they’re done using it are so bizarre to me. Why? What are you trying to protect? I only reboot when updates are needed and otherwise my computer is on 24/7. Been doing this since ~2004 and have never had an issue.

Edit: I’m not saying you’re wrong if you shutdown everytime. I’m just saying it’s weird to me because it hasn’t been necessary since the mid 2000’s or probably earlier.

Put a second hard drive In your PC and install Linux solely to it. Then you can use your BIOS boot menu to choose which OS to boot and Windows can’t wreck GRUB when updating.

Linux Mint might look outdated but it’s stable as hell. Especially LMDE. Any time I mess around with arch/arch-based derivatives or any rolling release distros I’m quickly reminded why I chose to run Mint as my primary OS. I’m long past my distro hopping days so having something that works without question and doesn’t require any mucking around is huge for me.

For anyone who’s curious, I went ahead and created a “default” project with the title I normally use already setup on the timeline. That way when I start a new project I can just copy the default template and my title with animations is already there ready to go. Just need to modify the text and it’s good. It’s not a perfect solution, and certainly wouldn’t work for someone who desires to use different or multiple titles per project, but it’s good enough for me. Here’s what it looks like: https://youtu.be/dlGUT0c46Ts

Nailed it. I didn’t even think to check that… I’ll have to see if I can find a workaround. Thanks!

haha, yeah figuring out those ffmpeg flags is an absolute nightmare. My problem there isn’t so much the output format from Resolve, but source format I’m using. My camera only has the option to record in H.264/H.265 (consumer grade, what can you expect?) which Resolve can’t properly import on Linux. I could take the time to transcode them with ffmpeg before editing, but I’m usually working with ~2 hours worth of video per project and I don’t really want to wait all day for a transcode job to finish before I can even begin editing. On top of that my camera (rather neatly) generates its own proxy files while recording, and I’ve found leveraging these is necessary for getting good timeline performance on my aging rig. Now I could let Resolve generate its own proxy clips like I have in the past, but that’s more time waiting around before editing. I was SUPER stoked to see Kdenlive can natively utilize the proxy clips my camera generates.