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

help-circle
  • 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












  • Happened to me with another brand and model (can’t recall which to be honest). It did pair but appeared as a generic BT device, not headphones, and thus was totally useless.

    I was pissed.

    Then… I pair with something else, not a computer but something simpler, maybe a phone, I can’t remember, and it worked. So I was shocked, how can for this it works, clearly no driver installed on top and not my desktop?!

    Anyway long story short I tried again few more times and it worked. Headphones were now pairing as headphones.

    I can’t explain why but my point is, I wouldn’t give up. I would retry to pair few times (I know, sounds ridiculous, and yet…) without changing anything.

    PS: if you know the ins and outs of the BT stack and it makes sense to you, please do explain! I’d love to learn


  • FWIW not only is the project alive (last commit 17 hours ago) but distribution too (cf links above) and project management too (cf e.g. https://github.com/orgs/LMMS/projects/1 as example of complex set of tasks mostly done toward a major release).

    So… I’m not going to give people working on LMMS any advice, but of course I hear you, and OP, when it shows for people who aren’t deep into it a project that seems abandoned.

    I do not know no why the project is in that state but what I hope I have shown is that for sure it’s very much active.




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