Of course, in fact you do not have to change right now, or even next month. Instead you are in a great position when you already have a device because it means you can take the time you need to prepare for a transition without any rush. The problem IMHO is … if you repeat the cycle. If in few years, or whenever you do change phones you say, again “Switching isn’t necessarily easy or doable for everyone” while having done nothing to change your situation.

Please, don’t rush a change and make it painful. Take the time and use the resources you have… but do something, even if a small thing, to go where you want to be. Do not stay stuck in a place you do not even enjoy.

Honestly… I come from iOS, using for nearly a decade. Yes that stuff is secure, yes that stuff is (or at least was) stable, yes that stuff is slick to the point of being a status symbol… but DAMN does it suck for interoperability!

Every success of bringing the Apple ecosystem to interact with anything is just so ridiculously hard… for in the end bringing very little.

Do yourself a favor, switch to (deGoogled) Android to enjoy KDE Connect, adb, scrcpy, etc just working out of the box, copying normal files the normal way, however you want. Try “just” Linux if you can’t but on mobile that’s not for everyone.

Again, I celebrate this success and all ways, e.g. iSH or Homebrew, that help to tinker, manage, work with Apple hardware but honestly I suggest ignoring it entirely. Just rely on software and hardware that actually provides the bare minimum to be interoperable. Not this.

Instead use this, and iSH, Homebrew, libimobiledevice, and the rest to transition AWAY from that locked ecosystem.

FWIW rsync also works on mobile phones and VR standalone HMDs, via e.g. termux or ish … so it’s really on working fine on… pretty much anything with a terminal and a connection really.

Warmly recommended.

Also if you need more than solely the last version, check rdiff-backup.

yet to get my first. I had been considering the Meta Quest 3, but Meta.

Perfect then

You can also run kiwix-serve to provide offline Wikipedia, StackOverflow, Project Gutenberg and more. Even on a very basic device search works as indexing is well done.

Remove the battery.

One should hope, and the tinkerer community, me included, is eager for both of these features.

Regarding new content I posted https://www.uploadvr.com/valve-isnt-currently-working-on-a-new-vr-game/ countless times because to me that’s maybe the biggest bummer. I have several headsets so I don’t need “yet another one” that is roughly equivalent. I need something genuinely different. A flat SeamOS (no immersive features to KDE Plasma) is boring but understandable, no new content from the quality only Valve (unfortunately) seems to be able to produce makes me think I’m not in rush. Just like hand tracking or WebXR we can hope for surprises but it mostly shows it’s considered a thin terminal for Steam, nothing more, and I have already few of these (thanks to Alvr, Wivr, CloudXR, but also just Steam streaming).

• sure, it’s no a hardware problem so they might support hand tracking but for now at least officially they don’t and didn’t announce they would. There are even https://github.com/Lynx-MR/LynxOrbSlam3 that could be used. For now though it’s not supported. I remember the BT control of Base Station for the LightHouse systems NOT being supported on Linux for years in fact check https://github.com/ValveSoftware/SteamVR-for-Linux/issues/207 it’s a 6 years old issue. Being feasible does not mean it will be done.
• yep
• CPU/GPU aren’t better than other standalones HMDs already out
• there is no WebXR support on Linux, hasn’t existed for years. Firefox never supported it, neither does Chromium. It’s been confirmed by the Google developer implementing WebXR https://bsky.app/profile/toji.dev/post/3m5hm2aysg22d
• that Valve isn’t making a new VR like Alyx

A friend of my is a researcher working on large scale compute (>200 GPUs) perfectly aware of ROCm and sadly he said last month “not yet”.

So I’m sure it’s not infeasible but if it’s a real use case for you (not just testing a model here and there but running frequently) you might have to consider alternatives unfortunately, or be patient.

Yes but …

• no hand tracking
• no color passthrough
• no hardware upgrade
• no WebXR
• no new VR proper content

Still, it’s good obviously, not having to rely on BigTech. This was also possible before though as I pointed out in https://lemmy.ml/post/38899489/22202786 with e.g. Lynx XR1, as a rooted Android standalone HMD with no account required.

Anyway IMHO the big questions for VR on Linux more broadly is what changes upstream on KDE in terms of immersive UX? Is KDE Plasma becoming a VR graphical shell? Does it have 3D widgets? Does it impact freedesktop in any way?

Edit : I have a SteamDeck since its out, Lynx XR1, etc so I absolutely want Linux VR and FLOSS XR to succeed. In fact I even gave a talk at FOSSXR years ago about that, fact did it twice. Still it doesn’t mean I can’t be disappointed by those points. I like Valve, I want to give them money, that doesn’t mean I can’t be objective. You might have different requirements, that doesn’t mean you shouldn’t compare to alternatives which have existed for years.

Half-Life 3 release (not joking)

Sadly not, at least not VR first, cf https://www.uploadvr.com/valve-isnt-currently-working-on-a-new-vr-game/

I’m new to Linux from about 3 months ago, so it’s been a bit of a learning curve on top to learning VE haha. I didn’t realize CUDA had versions

Yeah… it’s not you. I’m a professional developer and have been using Linux for decades. It’s still hard for me to install specific environments. Sometimes it just works… but often I give up. Sometimes it’s my mistake but sometimes it’s also because the packaging is not actually reproducible. It works on the setup that the developer used, great for them, but slight variation throw you right into dependency hell.

I’ll be checking over the subtitles anyway, generating just saves a bunch of time before a full pass over it. […] The editing for the subs generation looks to be as much work as just transcribing a handful of frames at a time.

Sorry I’m confused, which is it?

doing this as a favour […] Honestly I hate the style haha

I’m probably out of line for saying this but I recommend you reconsider.

Exactly, and it works quite well, thanks for teaching me something new :)

There’s no getting around using AI for some of this, like subtitle generation

Eh… yes there is, you can pay actual humans to do that. In fact if you do “subtitle generation” (whatever that might mean) without any editing you are taking a huge risk. Sure it might get 99% of the words right but it fucks up on the main topic… well good luck.

Anyway, if you do want to go that road still you could try

• ffmpeg with whisper.cpp (but honestly I’m not convinced hardcoding subtitles is a good practice, why not package as e.g. .mkv? Depends on context obviously)
• Kdenlive with vosk
• Kdenlive with whatever else via *.srt *.ass *.vtt *.sbv formats

Related documentation https://develop.kde.org/docs/apps/dolphin/service-menus/

Oh…, that’s neat thanks!

So in my use case I made a template for prototype metadata, add a menu action could be to generate the file instead of creating from the template via Exec= field. This would prepopulate the metadatafile with e.g. the list of selected files thanks to %F.

None of your requirements are distribution specific. I do all (Steam, non Steam, Kdenlive, Blender/OpenSCAD, vim/Podman, LibreOffice, Transmission) of that and I’m running Debian with an NVIDIA GPU. Consequently I can personally recommend it.

FWIW from https://lmms.io/download#linux one can get as AppImage (so nothing to build, no repository to modify) either

• 1.3.0-alpha.1.102 alpha
• 1.3.0-alpha.1.894 nightly

so from what I understood you could consider alpha, not nightly.

Eh… not sure where you get your information but https://github.com/lmms/lmms last update was yesterday.