[–] 2 points 6 months ago (1 child)

The cynical possibility: perhaps due to being Firefox/Gecko-based, which usually entails being privacy-oriented

The statistical possibility: market share for Chromium browsers is so much bigger than Gecko's that developers didn't bother to implement compatibility after an update - or are experimenting to see if it's worthy it

The hopeful possibility: it was a glitch, the site or the browser having updated something that changed the user-agent or the expected one, and the site didn't know what to do with the current one.

  • source
  • parent
  • context
  • [–] 1 point 6 months ago (5 children)

    Might want to specify that it didn't work with Midori, but it worked with Brave.

    Also that the "not powerful enough" error be updated to the actual issue. I seriously don't believe power is part of the reason here, but I'm open to being proved wrong.

  • source
  • parent
  • context
  • [–] 1 point 6 months ago* (last edited 6 months ago) (7 children)

    Midori is indeed Firefox based. As @lordbritishbusiness@lemmy.world mentioned, it might be worth quickly trying to switch to desktop mode (in the browser menu).

    If that doesn't work, try switching to Brave.

    If that doesn't work either, consider finding a new service, honestly, as this kind of user unfriendliness shouldn't be acceptable. try open an issue here.

  • source
  • parent
  • context
  • [–] 13 points 6 months ago* (16 children)

    "Not powerful enough" lol - BS excuse for wanting you to use the app. A different browser (most likely chromium due to compatibility reasons) would most likely fix it.

    What browser do you use? If it needs a chromium browser, Brave would be sufficient, most likely. You might have to select it as a default browser app on your phone too.

  • source
  • [–] 41 points 6 months ago

    You have an option in your settings to request "desktop mode" which may change this.

    They probably want to increase the number of users on their app and are trying to force mobile users over, the "not powerful enough" statement is likely a lie.

  • source
  • [–] 2 points 6 months ago* (last edited 6 months ago) (1 child)

    I really only edit the odd video, but I can try and answer as it seems no one else has.

    1. Is it worth it to buy server MOBOs and employ one, then two or more CPUs? Does KDEnlive or other Linux apps make use of multiple CPUs? Do I need to buy i7-i9 CPUs from the start, or a couple of i5 is okay? Where is the golden middle there?

    I would not go with a dual socket system, most Linux apps will schedule themselves fine but you will get quite some stuttering if the app wasn't expecting the latency of being scheduled between 2 seperate NUMA nodes. Kdenlive isn't too demanding so you can realistically go with any somewhat modern CPU. Kdenlive also does let you use multiple cores in the render menu, but it recommends against it as it can cause artifacts. So if you're going to buy a new CPU, look for single core performance.

    1. What about double vCards? Can any software use these dupletes or is it more beneficial to just buy the top single vcard? Do I need to purchase some compatible vcards for that?

    Not a lot of apps support using 2 cards at the same time, and I don't think Kdenlive needs anything too special. As long as the card supports VAAPI (AMD/Intel) or NVENC (NVIDIA) then Kdenlive can use it for encoding.

    1. If you use KDEnlive on AMD, what are lifehacks to boost it's performance? What do you use for preview, render, proxy clips, do you use another hard drive for cache, etc? What options do you choose for preview and render?

    Just render using VAAPI and it should be fairly fast. There also used to be an experimental option for GPU accelerated effects, but I couldn't find it last time I looked.

    1. Have you tried VFX software like Natron (native), emulated Resolume, Nuke or Houdini via Proton or Wine, and how it went? What suffixes to use there?

    No, but you could try CrossOver too if Wine doesn't work.

  • source
  • view more: ‹ prev next ›