Spectacle8011

joined 2 years ago
[–] Spectacle8011@lemmy.comfysnug.space 1 points 1 year ago (1 children)

Seriously though, a stable API is not the GTK/GNOME developers’ agenda here. Nobody wanting a stable API should write software with this toolkit.

This blog post doesn't mention GTK, but I've heard GTK will sometimes implement breaking changes in minor version bumps. I was thinking about writing some software with GTK, and I haven't been deterred so I guess I'll learn the hard way, but has GTK 4 had any of these stability problems yet?

The GNU kernel was not originally supposed to be called the Hurd. Its original name was Alix—named after the woman who was my sweetheart at the time. She, a Unix system administrator, had pointed out how her name would fit a common naming pattern for Unix system versions; as a joke, she told her friends, “Someone should name a kernel after me.” I said nothing, but decided to surprise her with a kernel named Alix.

Source: https://www.gnu.org/gnu/thegnuproject.en.html

I think Krita is a more viable competitor to Photoshop than Gimp at this point… It’s also great for pen tablet drawing and arguably superior in that category.

Absolutely agree it's there for artists. Krita is a very successful project and I hear mainstream artists talk about it often, while not being an artist myself. Well, technically I own a Cintiq...

I haven't been able to get it to work well with PSDs, though, and I find the interface clunky for the sort of image editing I'm doing. I find GIMP easy enough to use, but it unfortunately lacks some crucial features. 3.0 is right around the corner (for real this time), so I'm hopeful. Unfortunately, PSD is a must because of collaboration. GIMP's ingest of PSD is better. But Krita does have non-destructive effects.

What I'm really hoping for is Affinity Photo to work well in Wine. Most people can get it running now but I think it's a little buggy or lacking in performance. I'll have to give that a shot soon.

But yeah, video editors are lacking. Kden live is ok (and awesome for the price)

As it so happens, I've thought about this a lot.

Kdenlive is definitely the best free software option but the lack of hardware accelerated playback really kills it dead in the water for me. I'm hoping it will improve soon, given the success of the fundraiser. DaVinci Resolve is fantastic but needing to transcode footage if you have H.264/AAC source footage (geh, I know, but some of us do) and being stuck with H.264 hardware encode in the best-case scenario is not great. I found Lightworks was the best option in terms of professional features + workflow. Proprietary, but hey, at least it works really well on Linux.

Audio editors are behind too. Audacity is pretty good for 2 track. Bitwig is a great multitrack alternative to Ableton… But Ardour isn’t developed enough for a pro studio and I’ve never seen one that uses Linux. Part of this is poor support for vst plugins developed for Windows, mostly due to their copy protection.

That's a shame to hear! I don't work with audio on a very professional level, so Audacity is fine for my use cases. It's improved in a significant way since the Muse Group acquisition (mainly non-destructive editing, but plenty of other stuff). I'm also annoyed but unsurprised to hear that DRM has thwarted compatibility yet again.

[–] Spectacle8011@lemmy.comfysnug.space 2 points 2 years ago (3 children)

There are also Windows users who rely on niche business applications. Wine isn't great for that sort of software yet. Another big one is the creative industry. While the VFX industry is very Linux-focused, and 3D is very viable, other parts of video production are not. And GIMP needs non-destructive editing before it can even think of competing with Photoshop or Affinity Photo. Inkscape is a viable vector image tool. The many other Adobe programs don't have great alternatives, and if you need to collaborate, that means you all need to switch to a new program. Then there are the retraining costs to consider.

Gamers have the easiest time in switching to Linux. The amount of compromises and sacrifices you need to make in other industries are much greater right now.

However, Adobe is trying to bring some of their programs, like Photoshop, to the web. It's unlikely we'll see stuff like After Effects on the web, but Photoshop, Illustrator, maybe even inDesign could possibly, maybe be there in a few years. Photoshop web is already in beta (though it's garbage). The web continues to be the great equalizer.

I don’t know if they’re still 720p locked on the free version.

Yes, it's still locked to 720p on the free version, but the Create plan is very competitive at $9.99 a month. It has all of the features of Pro except encoding is limited to H.264/AAC and AV1 on Vimeo/YouTube, and you have no control over the encode aside from resolution. That was enough for me, though. I'm not doing anything super professional but I'm doing more than you can do easily with most of the NLEs on the list above.

I’ve tried LW before but I never really liked the workflow.

The workflow kind of broke my brain when I first looked at it a few years back but after acclimating to it I quite like it. The cutting is keyboard-based in a way most other NLEs aren't, but yeah, it can definitely be annoying without some tweaks. Were you using Lightworks when they didn't have a Fixed Layout option? The Flexible Layout pretty much leaves you to it, but the Fixed Layout is very reminiscent of Resolve. What I love most about Lightworks is definitely the speed. It's the fastest and most responsive NLE I've ever used (Cinelerra probably comes a close second). And it gives you good Color tools and many other powerful features! Not a common combination. The community is also full of knowledgeable people, but that's true of Resolve too.

Anyway, if you're happy with Resolve, there's no reason to consider switching. Pricing wise Resolve beats out Lightworks after two years of Pro license ownership and the licenses are less annoying. Main reason I went for Lightworks is I didn't want to be forced to keep a NVIDIA GPU forever. It seems less disruptive to my workflow in the long run. How is Resolve stability-wise for you? I'm still trialing Lightworks but the ownership cost is leading me to re-consider Resolve...

Having a look at the Resolve 18 Codec manual, I see they've moved from CentOS 7 to Rocky Linux 8.6. I'm glad they didn't kill the GNU/Linux version or something along with CentOS, lol...

[–] Spectacle8011@lemmy.comfysnug.space 10 points 2 years ago* (last edited 2 years ago) (2 children)

I like Kdenlive and used it for a few months, but I also really like Lightworks. Lightworks is proprietary, but it's also a professional tool. Unlike DaVinci Resolve, it will decode and encode H.264/AAC, and most people don't need much more than that, though AV1 is also supported. The color correction tools in Lightworks are better than Kdenlive's and the cutting tools, while they take a while to get used to, are quite nice when paired with they keyboard. Best of all, Lightworks is a lot faster to startup, doesn't crash as easily and it's always responsive.

The most annoying part has to be dealing with licenses. If you use up your two licenses, you need to contact their support via email to shuffle them around. It's a great program, but this is super annoying. It also discourages you from purchasing the perpetual license because you don't want to get stuck in this situation. Mind you, their support is very friendly so I have no doubt they'd help you out, but it's an issue of needing to ask them in the first place. DaVinci Resolve's licensing system at least works perfectly fine, no matter what, or so I've heard. If you activate a new computer, it will just deactivate an old installation, and that's it. No need to wrangle customer support while everyone's on holiday...

The other professional option on GNU/Linux is DaVinci Resolve.

DaVinci Resolve is a very nice NLE at a very nice price, though proprietary. But $500 is a lot better than the $800,000 it used to cost. Annoying to install although fat-tire's containerization project is worth a look for easy installation. However, it doesn't work for my source footage, even with Studio. The free version doesn't support H.264 decode/encode or AAC decode/encode, which are the two main codecs you'll see with MP4, the most ubiquitous (and patent-encumbered) video format in the world. The Studio version supports H.264 decode/encode only with NVIDIA GPUs, but it still doesn't support AAC decode/encode. It can encode H.264 though, which will leave you with an MP4 file with no audio track.

To use DaVinci Resolve with H.264/AAC in a livable way, you need a NVIDIA GPU, you need to purchase the Studio edition, and you need to transcode your audio from AAC to something Resolve can ingest. There are scripts to automate this. Optionally, you should also purchase a third-party AAC encoder plugin for Resolve so you don't need to transcode again after rendering, assuming you're targeting H.264/AAC on render. If you're not, you can just render to Quicktime/PCM .mov.

As much as I love DaVinci Resolve, I kind of didn't think that was worth it for me at the time so I went with Lightworks which supports H.264/AAC encode fine with their Free/Paid licenses. I think I'll come back to DaVinci Resolve after 2028, when the patents for H.264 and AAC have finally expired (hopefully), and DaVinci Resolve includes decode support for AAC (hopefully). I might still use the Fusion tab for creating some VFX, but I'm trying to see if I can work with Natron first.

As for other NLEs:

  • Cinelerra-GG: I quite like this editor, but damn it is particular and some things are just annoying to do. I've also heard it has color management issues... that was the main reason I stopped using it. That, and I can't actually get it to build anymore, haha. The manual is super amazing and beats out almost every other NLE mentioned here except DaVinci Resolve. It's not a bad read even for just generally learning video editing.
  • Blender VSE: It works okay but the workflow is very slow and the lack of sequences (only projects) only makes things more annoying.
  • Openshot: I'm not a fan of the interface and found the workflow, at least initially, slow.
  • Shotcut: Seems nice enough but it didn't work for me. I forget why.
  • Pitivi: It crashed the instant I tried working with 4K footage.

Edit: Olive is nice too but very early stages. Color tools are very basic. And unfortunately development is winding down.

Ah...sorry, I just realized this probably isn't the response you're looking for. But I've spent a lot of this week trying to find a professional NLE on GNU/Linux and that was what I came up with. For the record, I'm a GNOME user and I liked Kdenlive the most out of free software NLEs. I'm looking forward to the new improvements to come from the fundraiser to improve workflow!

TIL Firefox could use the updated GNOME File Picker with thumbnails. Just set widget.use-xdg-desktop-portal.file-picker to 1 instead of 2.

For KDE.

Ah, I can see how that might be useful. I first learned about the command pallette when I needed to instruct everyday users on taking a full-page screenshot on Chrome...it's far more complicated than Firefox's method of Right-Click > Take Screenshot. Just another odd thing, lol. Interestingly, Firefox is considering implementing this feature: https://github.com/firefox-devtools/ux/issues/101

I don't think it would make much sense in my workflow right now but I can see how it would benefit others. Quickly turning on accessibility constraints I'm sure would be very useful. One thing Firefox's dev tools is desperately missing is search. I get along fine without it, but it would be nice to have.

Photoshop Web (Beta) only supports Chromium-based browsers, Descript only supports Chromium-based browsers (well, Firefox still seems to work but you're on your own), and many new webapps are only supporting Chromium-based browsers. Now, these are beta products, so that might change, but it seems unlikely. So I've been switching to Chromium-based browsers to use some of these apps, but I'd really rather not. It's the way everything is going, unfortunately.

A lot of developers target the web because it means they can have one codebase that is supported on multiple operating systems. Imagine how much harder it would be to develop a macOS, ChromeOS and GNU/Linux version in concert with the Windows version. In reality, some browser engines support more web features than others, and Google has by far the most resources to keep up with those standards. So Firefox is an afterthought. Google Chrome is on every operating system worth supporting anyway, so why bother supporting another browser? It's a lot less work and testing.

MDN is the best place to read about those standards, though.

I like Firefox:

  • userChrome.css lets me make Firefox look like a GNOME program
  • I much prefer the developer tools. Everything is a lot easier. I always use Firefox when doing web development.
  • I can easily customize the browser. For me, this means having a separate dedicated URL bar and search engine bar.
    • The search engine bar lets me swap between search engines very quickly and keep my previous search terms for new tabs. Switching search engines is really annoying in Chromium-based browsers because you need to use shortcuts, and there's no autocomplete for shortcuts. It also doesn't tell you whether you typed the shortcut correctly, so you're guessing every time! It's really under-developed. The Android Chromium-based browsers are even worse. You can't change search engines at all when searching; you need to change your default engine. Firefox lets you search any search engine easily on iOS, and slightly less easily on Android.
  • I can...turn off history? Apparently this is an amazingly complex feature that Chromium-based browsers just can't handle. The best you can do is clear it when exiting, but you can't just turn history off.

Okay, it's mostly the search engine thing, to be honest.

But Firefox still doesn't use the new GNOME thumbnail view when you're uploading files, for example...

[–] Spectacle8011@lemmy.comfysnug.space 2 points 2 years ago (2 children)

I also prefer chromium dev tools, though it isn’t that bad to switch to Firefox’s dev tools.

I actually vastly prefer Firefox's dev tools to Chromium's. There are keyboard shortcuts to open every tab, it has a color picker, it has a multi-line Javascript console, and in general I find it more intuitive. Chromium developer tools seem to be less complete than Firefox and harder to use.

I just learned Chromium technically has a color picker tool, but you need to scroll through CSS propetries to find a color selector, click the color, then click the color picker. With Firefox, I tap CTRL+SHIFT+I to open dev tools, click the color picker which is front-and-center, and it copies the hex code to my clipboard. This is a microcosm of my overall experience with Chromium's developer tools. Everything is slower or further out of reach.

I don't know how it ended up this way.

I wish I'd known how to use node-based compositors like Natron to produce VFX so I don't have to keep going back to macOS to use After Effects.

[–] Spectacle8011@lemmy.comfysnug.space 3 points 2 years ago (1 children)

Oh my goodness, I’m sorry to hear that this is happening to others but I am so glad its not just me. This has been something that’s driving me crazy, because I knew it wasn’t a cable / GPU issue due to the fact that it doesn’t occur in Windows.

I know right! I thought it was something I did! You don't know how many times I've gone into the back of my monitor and tried to shove the HDMI cable in just a bit further, to no effect. I thought I'd broken it by trying to run Sway or something...

Nope, the driver is just that bad. Ughhh.

KDE is worse, but GNOME isn't great either. It's been going on for months! Additionally, I have "Prefer Maximum Performance" set, but it hasn't helped much. I've seriously been considering an AMD card next year... I have an RTX 2060S with 535.98.

 

What if your dev experience was entirely in the cloud?

These days, launching applications means navigating an endless sea of complexity. We felt this pain at Google, so we started Project IDX, an experimental new initiative aimed at bringing your entire full-stack, multiplatform app development workflow to the cloud.

Project IDX gets you into your dev workflow in no time, backed by the security and scalability of Google Cloud.

Project IDX lets you preview your full-stack, multiplatform apps as your users would see them, with upcoming support for built-in multi-browser web previews, Android emulators, and iOS simulators.

As a Vim fanatic, I can't say I'll ever feel comfortable working in a browser, but some parts of IDX seem interesting. I wonder what the implications are for proprietary code.

I do think it solves an interesting problem where you're working on your desktop and decide to move to your laptop and continue working on the same codebase, but don't want to commit early so you can pull down the changes to your laptop.

It reminds me vaguely of Shells.

 

cross-posted from: https://lemmy.comfysnug.space/post/138679

We've been working on a guide to help players on all major GNU/Linux distributions play visual novels for the past few weeks. This guide is designed to be used by both beginners and experts, with minimal need to touch the command line.

openSUSE wins the award for "never had to touch the terminal" and "simplest setup instructions", but Fedora is a close second.

While there are a few existing visual novel guides for GNU/Linux around, we've tried to fill in the gaps we noticed. We've put a lot of research into this guide and ensured it is accurate while remaining simple and approachable.

If you're interested, start here!

We have an extensive Troubleshooting section on our Problems page if you're having trouble getting visual novels to work, too.


I wrote this guide with a lot of help from two other people, including /u/neo@lemmy.comfysnug.space. It’s available on our community wiki, https://wiki.comfysnug.space. As with all pages on our wiki, it’s licensed under Creative Commons Attribution-ShareAlike 4.0, meaning you’re free to share, remix, and build on the content as long as you credit us.

We also have some other pages you may find useful:

  • If you're looking for something to play, check out our Recommendations page.
  • If you want to know where and how to buy a visual novel you want to play, our comprehensive Buying page will help you out.
  • And if you want to read a visual novel in Japanese, our Reading in Japanese page offers a lot of advice and points you to some useful software to make the process easier.
 

cross-posted from: https://lemmy.comfysnug.space/post/138679

We've been working on a guide to help players on all major GNU/Linux distributions play visual novels for the past few weeks. This guide is designed to be used by both beginners and experts, with minimal need to touch the command line.

openSUSE wins the award for "never had to touch the terminal" and "simplest setup instructions", but Fedora is a close second.

While there are a few existing visual novel guides for GNU/Linux around, we've tried to fill in the gaps we noticed. We've put a lot of research into this guide and ensured it is accurate while remaining simple and approachable.

If you're interested, start here!

We have an extensive Troubleshooting section on our Problems page if you're having trouble getting visual novels to work, too.


I wrote this guide with a lot of help from two other people, including /u/neo@lemmy.comfysnug.space. It’s available on our community wiki, https://wiki.comfysnug.space. As with all pages on our wiki, it’s licensed under Creative Commons Attribution-ShareAlike 4.0, meaning you’re free to share, remix, and build on the content as long as you credit us.

We also have some other pages you may find useful:

  • If you're looking for something to play, check out our Recommendations page.
  • If you want to know where and how to buy a visual novel you want to play, our comprehensive Buying page will help you out.
  • And if you want to read a visual novel in Japanese, our Reading in Japanese page offers a lot of advice and points you to some useful software to make the process easier.
 

cross-posted from: https://lemmy.comfysnug.space/post/138679

We've been working on a guide to help players on all major GNU/Linux distributions play visual novels for the past few weeks. This guide is designed to be used by both beginners and experts, with minimal need to touch the command line.

openSUSE wins the award for "never had to touch the terminal" and "simplest setup instructions", but Fedora is a close second.

While there are a few existing visual novel guides for GNU/Linux around, we've tried to fill in the gaps we noticed. We've put a lot of research into this guide and ensured it is accurate while remaining simple and approachable.

If you're interested, start here!

We have an extensive Troubleshooting section on our Problems page if you're having trouble getting visual novels to work, too.


I wrote this guide with a lot of help from two other people, including /u/neo@lemmy.comfysnug.space. It’s available on our community wiki, https://wiki.comfysnug.space. As with all pages on our wiki, it’s licensed under Creative Commons Attribution-ShareAlike 4.0, meaning you’re free to share, remix, and build on the content as long as you credit us.

We also have some other pages you may find useful:

  • If you're looking for something to play, check out our Recommendations page.
  • If you want to know where and how to buy a visual novel you want to play, our comprehensive Buying page will help you out.
  • And if you want to read a visual novel in Japanese, our Reading in Japanese page offers a lot of advice and points you to some useful software to make the process easier.
 

Participation in open source requires you to surrender your monopoly over commercial exploitation. This is a profound point about free and open source software which seems to be causing a lot of companies to struggle with their understanding of the philosophy of FOSS

This is an essential, non-negotiable requirement of free and open-source software, and a reality you must face if you want to reap the benefits of the FOSS ecosystem. Anyone can monetize your code. That includes you, and me, all of your contributors, your competitors, Amazon and Google, and everyone else.

It’s quite common for people other than you to make money from your free and open source software works. Some will incorporate them into their own products to sell, some will develop an expertise with it and sell their skills as a consultant, some will re-package it in an easy-to-use fashion and charge people for the service. Others might come up with even more creative ways to monetize the software, like writing books about it. It will create wealth for everyone, not just the original authors. And if you want it to create wealth for you, you are responsible for figuring out how. Building a business requires more work than just writing the software.

This seemed like a relevant post to link, given recent events.

view more: next ›