@NoahCarver On linux back in the days I was using an app called #avidemux. It worked fairly well.
I was also trying out #kdenlive however the version I was using has been crashing on my system so I've stopped playing with it.
Nowadays I am no longer dealing with videos and for simple cutting both audio and video I'm just using #losslesscut.

Linux Desktop

Ich bin immer wieder erstaunt über den mittlerweile so konsequenten switch zu Wayland. Da gibt es noch mit so vielen Programmen Probleme, sei es Fehler/Bugs oder auch generell keine Unterstützung.
Und Nvidia und Wayland sowieso sehr "speziell".

Aktuell grad Probleme mit Avidemux (built from source), Ausführung mit "--platform xcb" nötig, ansonsten unbenutzbar. 🤨
Bei anderen Programmen (z.B. FreeCAD) musste ich "QT_QPA_PLATFORM=xcb" als Umgebungsvariable verwenden.

Das hindert mich auch am Umstieg von Fedora 42 auf 43 (KDE-Plasma).

#Linux #Wayland #OpenGL #Avidemux #FreeCAD

📦🃏🎞️
Friedel entschuldigt sich schon mal vorab für die doofe Hinweisnervung.
Nobbie hat Friedel motivationsfördernd in den wärmeligen Heizungskeller gesperrt, ein neuerliches Hinweisvideo zu pfoteln.
...muss man nicht anschauen.
Friedel hängt ab...

#skipbo #avidemux #aegisub #audacity

@zahntron From all #Linux video editors that I assessed, the best seems to be #DavinciResolve (proprietary) and #KDEnlive, and with a somewhat different focus #Blender.
Contender #Shotcut.
Also available #OpenShot #Lightworks (proprietary) #Flowblade #Olive #Avidemux #Pitivi

PLEASE UPDATE: My assessment is from September 2024, if one of the video editors has progressed substantially, please respond!

@system76 @jorge #Davinci #videoeditor #videoeditors #videocut #floss #opensource

🪵🪓🔥
Susi und Friedel haben es wieder getan!
Hier ist eine weitere Bewegtbildaufbereitung mit friedelgepfoteltem Soundtrack.

Friedel meinte, sich diesmal bei den Effekten austobprobieren zu müssen..

#SusiRäumtAuf

#avidemux #aegisub #audacity

I've tried to embrace some of these new #linux technologies, such as #wayland and #pipewire

With #piprewire, there is sound glitching across all DEs and all common distros. Even if I tweak the out-of-the-box settings, such as default.clock.min-quantum as recommended in numerous forum posts/wiki articles, it only marginally improves it, and I still get random audio playback issues in various music players such as #rhythmbox and #audacious, although I will concede #kodi seems perfectly fine.

With #wayland, there are a couple of apps I use, such as #avidemux, that don't really work with it, even under #xwayland
I can 'force' around that with things like using --platform xcb on the command line, but it's less than ideal.

So for me, whether I'm using my normal setup of #debian #trixie with #xfce, or use #gnome or #kde on the same base, or indeed try the same on #fedora or arch-based distros such as #cachyos or #EndeavourOSArch, it is the same outcome.

Newer isn't always best. #X11 with the right conf file to sort out screen tearing, works with everything I ever use on any DE or distro.
#pulseaudio just works everywhere.

So I'm going to stay in the past with the tried-and-tested X11 and Pulseaudio, until these 'new' technologies have matured and fixed all the edge-case issues they have.

@OrionKidder @unixviking
Care to share what extensions you have installed and why?

I use #debian and despite playing around in a VM for multiple different distros, as well as #debian with multiple different DEs, I end up staying with #xfce on #debain stable (well in truth I am now on #trixie given the stability and imminent release).

I like a lot of things about #gnome, but struggle with a couple of key areas - the file manager in terms of customisation and fixed viewing styles, and strange as this may seem I'm against things like #flatpak because I feel things should be native and integrated.

That said, I'm having to use #distrobox and some containers as #trixie doesn't have two key apps for me - #dvbcut which was in #bookworm but isn't in #trixie, and #avidemux which hasn't been in #debian for years now.

I really want to move to either #gnome or #kde, but #kde is far too unstable for my liking and that's a showstopper. Often my desktop is on for weeks or months at a time.

A week ago I did a new install of #debian #trixie on my main desktop so that I was running what will become the new #stable release.

As part of that, I made a conscious effort to try and work with #wayland and also moved to the #plasma6 desktop.

Following a week of tweaks and trying to get a few applications like #avidemux to play nice, I have concluded my trial.

The idea that #wayland is ready for wholesale use by all user types is not yet a reality. Having to do tweaks to kernel boot parameters to fix AMD graphics issues, or having to force applications with --platform xcb, are signs that things have a way to go before they cover all common usage profiles.

Also, whilst I accept it is snappy and stable, #plasma6 for me isn't something I'm going to stick with. It is very configurable, which is good because you need to tweak it in all manner of ways to reduce its impact on workflow and user experience.

I will take time to consider my options and a new install sometime next week.

@resplendent606 @bitflipped

I've found #debian #bookworm with the #xfce desktop to be incredibly stable. Uptime in the months, it has been my main 24/7 desktop.

I have moved to #trixie now that it's 'almost here' and am trialling the #kde desktop. Whilst it looks good and is performant, the stability of #plasma6 isn't there yet, some features are not yet available that were in qt5, and I've had a couple of widgets crash.

I've also noted a few of the apps I ran in #bookworm are not available in #trixie, so I may need to look into more #docker images to run those.

The #avidemux app will not compile against #qt6 on #trixie for some reason, so I've had to compile that against #qt5, where it seems to work fine. Need this as #dvbcut is one of the apps I use that is not available in #trixie

Overall, #trixie is looking to be a stable release. I'm just not convinced I'll stay with #kde and may revert to #xfce again, or perhaps try the #CinnamonDesktop again.

@resplendent606

I finished my switch back to #debian #bookworm

I did still have some new issues that I didn't from when I'd originally installed #bookworm at release 12.1, and it seems since then some updates create a few niggles with certain self-compiles.

Resolved the last of my libqt5widget trackback errors by setting #qt5ct back to gtk2 rather than #kvantum. For whatever reason, that combination caused applications like #avidemux to fail to run. I had issues compiling that as well, but overcame them by fixing a typo in one of the cmake files.

Anyway, back to a stable and working environment.

Going to spend time in a virt-manager VM to test out #trixie as a clean install with #kde as the DE. I think having KDE as the base DE and then setting #gtk theme support is the better way around, and more of the apps I now run are Qt-based nowadays, and that seems to be a trend that is growing.