• 0 Posts
  • 146 Comments
Joined 4 years ago
cake
Cake day: January 17th, 2022

help-circle


  • 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.



  • 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.




  • 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






  • I recommend a different consideration than the usual design, battery life, OSHW, etc : connectivity.

    So typically you get BT but that’s not enough, you need a bit more since it’s not a well recognized device, unlike e.g. headphones. Typically you would need a companion app, for GrapheneOS, Android more broadly, iOS or a Linux phone. This is where GadgetBridge comes in. The goal of the project is to… bridge gadgets that are not standalone. Instead of having a myriad of (usually proprietary) apps that basically all do the same thing (pair, configure, handle notifications both ways) have 1 that does it for all such device.

    From that standpoint, namely GadgetBridge support, at the moment the recommendation is Pebble (which is how the project started) or PineTime.

    PS: I personally have a Pebble (with hardware issue, so not sure were), a PineTime (also hardware issue, touch on screen AFAIR) and finally a Watchy and… honestly I don’t wear any anymore. I don’t get enough benefit from it as typically I have a phone nearby and when I don’t it means I do NOT want notifications.