1767958465_maxresdefault.jpg

Switching to Linux the 30 day challenge, Day 5 out of the challenge was challenging.

Error Message from KDenLive:
Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.

Fix:
Disable GPU Processing in Settings – Kdenlive Settings – Playback .

►► Digital Downloads ➜ https://www.cttstore.com
►► Patreon ➜ https://www.patreon.com/christitustech
►► Twitch ➜ https://www.twitch.tv/christitustech
►► Website and Guides ➜ https://christitus.com

source

18 thoughts on “Switching to Linux | Part 3 | 30 day challenge

  1. LMAO Dev Librarys and drivers -HAHAHAHA been there… done that…. re-install OS ….. seams faster lol

    So video cards with linux:

    if you are using an nVidia graphics, the open source are about 9 times slower than the proprietary, but nVidia does not release proper proprietary drivers untill the card has been replaced (i.e. works decently on old cards). The open source drivers are reversed engineered since nVidia will not share its "proprietary source code" with the open source group. Can still use the Cuda cores for cpu calculations (physics and science industry mainly) and GPU processing.

    If you are using AMD graphics, the proprietary driver is usually released with the card. But the open source drivers are released before the cards are released on the market. This is because AMD works with the open source community, and, because of this, once the cards have been out for a while, the open source drivers will not only run faster, but have the potential to unlock more capabilities on the cards they are made for. Also, never use "GPU processing" on amd graphic cards on window as well as linux

  2. LMAO Dev Librarys and drivers -HAHAHAHA been there… done that…. re-install OS ….. seams faster lol

    So video cards with linux:

    if you are using an nVidia graphics, the open source are about 9 times slower than the proprietary, but nVidia does not release proper proprietary drivers untill the card has been replaced (i.e. works decently on old cards). The open source drivers are reversed engineered since nVidia will not share its "proprietary source code" with the open source group. Can still use the Cuda cores for cpu calculations (physics and science industry mainly) and GPU processing.

    If you are using AMD graphics, the proprietary driver is usually released with the card. But the open source drivers are released before the cards are released on the market. This is because AMD works with the open source community, and, because of this, once the cards have been out for a while, the open source drivers will not only run faster, but have the potential to unlock more capabilities on the cards they are made for. Also, never use "GPU processing" on amd graphic cards on window as well as linux

  3. I've once spent hours on making a mod for a game & wondering why it doesn't work. Long story short is, I was editing the backup files of my mod not the actual files what the game was loading up :I My mod was fine, I just edited the wrong file.

  4. The essential nightmare in any compu-detective sleuthing is remembering, there is not necessarily any external (ie human) logic behind your problem – only internal computer logic. This is true of any OS, program, etc. and figuring out the often trivial solution can take days. And the answer is NOT the old saw "re-install a clean version of your OS." EX: My Win 7 would simply not backup with good old Macrium Reflect – crashing every single time, online suggestions about diving deep into registry settings to fix, etc. Finally stumbled upon one person's advice – remove the drive letter from RECOVERY partition. Duh. Instantly resolved the issue. Go figure. Or not, as the case may be.

  5. In Kdenlive, at your Render settings, you can create a custom profile (Klick create new profile). For example I use this for UHD and Nvidia GTX980:
    Group – Ultra-High Definition (4K)
    Profilname – h264_NVENC (80MBit)
    mp4
    Parameter
    acodec=aac ab=1024k ar=48000 vcodec=h264_nvenc vb=80000k

    For this to work, you have to install the Nvidia proprietary driver and you need ffmpeg with nvenc enabled (which is default in Arch Linux).
    I have also created a profile to create 1080p proxy clips from my 4K recordings:

    h264_NVENC
    -vf scale=1920:1080 -vb 2500k -vcodec h264_nvenc -ab 128k -acodec aac

    GPU is way faster then CPU, even I have i7 6900K.

  6. GPU processing in KDENLIVE never worked. It crashed on me aswell (Nvidia + Amd). Myabe you want to try the free version of Davinci Resolve ? It's a way better video editor with super fine color control, AND..it uses Gpu Processing by default in linux (Nvidia + Amd). You need to install the Amd Pro drivers when you're using a Vega card, because the app requires you to. Give it a shot..i'm very happy with it!

  7. Yeah, GPU rendering takes much longer with movit… Tried it and many others as well, the result is always the same – longer rendering times… This is a complete failure option… But I never got an error. I wonder if devs know bad this movit thing is? Did someone report it? This should be pulled off a long time ago.
    In fact, I doubt that even works, because in hybrid GPU setup it doesn't matter if you use intel or nvidia, rendering times stay EXACTLY the same on moving (longer) and without it (shorter), which suggests that GPU has nothing to do with it or with the movit option…
    So basically GPU rendering on kdenlive doesn't exists and movit option is just a scam.

  8. Thanks for the funny, but honest, review of your foray into Linux. As a full time Linux user I appreciate the style in which you are conducting your challenge.

Comments are closed.