I'd push this further: I install what I need now, and then install anything else when needed. Old installs get bloated because of shit we pull over time. A new one has to be fresh. When testing a new distro you wanna see it at its (default) best.
Thanks! I don't know GB, but I've seen people around me use it heavily.
I've been working with macs since a long time - goes with the job. I know they'll work great also with my stuff like midi keyboards (I have so many...) and Live and, and.
I'll see tomorrow if what's on the counter is actually available. Thanks again, your enthusiasm is heartwarming!
I'll be still mixing and mastering (and lighting) on Linux, as I've been on anything from Slackware to SuSE to Arch since 2006 ; I believe my current showstoppers are bad luck with secondhand hardware, and pebkac on pipewire software. It just happens that for live, real-flesh-on-stage-and-audience, I can't afford the risks. It hurts.
Me too. Stock from the install guide, Linux and linux-lts kermels
What doesn't work :
ftdi chipsets over usb aren't recognized by the software anymore.
The menu to switch on/off WiFi hangs, crashes the subsystem (and the menu panel), must reboot.
Laptop goes asleep when and if it feels like, sometimes doesn't even shut down the screen when I close the lid (dell 7389). And wakes up randomly of course.
Impossible to get snapper-rollback to work ; snapshots work, rebooting in an earlier config doesn't (and that part of the wiki is a mess).
Helvum doesn't show the audio hardware and software, no way to route stuff like we used in Jack.
I already installed 6 (the Tree) on my... Gnome laptop. As opposite to one of the feedbacks on the competition page said about the Night version, I don't care about legibility of my desktop items huhuhu.
The Tumbleweed installer is great, the general feel of the distro is polished, modern, up-to-date and efficient.
As other people have said, use the terminal to update both flatpaks and packages.
One main reason I went back to Arch BTW is that there aren't, contrary to the old self a declaration by Suse, that many software available for my use case, so I ended up with tons of ppa's, sorry, Suse Vendors who relied on each others for libraries, and it eventually broke down my system when some stuff wasn't available but was required, while some may be available from 4 different, private, repos.
So I found software management a nightmare: where to find, which one to choose from? Looking for stuff in yast, then in gnome-software, then in software.opensuse.org, then on the Build Service... Clicking bliindly to trust keys from people with personal repos titled "Use At Your Own Risk". Updating that mess then was complicated, and slow because gnome-software would lock yast while checking stuff in the background. I had to kill it, even just to relaunch it to search for stuff.
But Tumbleweed installs Snapper on Btrfs by default, so rolling back shouldn't be a problem? True, and I did it and it's just delicious, fuck up your system, wind back in two clicks... That is, unless btrfs snapshots didn't got unruly, and in it's default settings ate up all my disk space, forcing me to destroy that great system.
What annoyed me most here wasn't the software all-over-the-place mess, but that the default, factory setting of a great system they themselves contributed to the Linux world wouldn't be working 6 months down the line on a small disk (30Gb). Thanks to the Arch Wiki I know better now, and it is easily manageable, but it was too late for me.
Went back to Arch, with snapper, snap-pac, grub-btrfs, snapper-rollback. Can't yet wind back like in Suse at all, currently at VM number 9, trying again, wish me luck.
TL;DR: a rolling release from a reputable company with one-click rollback is a perfect solution if you keep your system relatively standard.
Which is the perfect premises for a Colonial Invasion by a "superioristic" neighbor. Like the Belgians bringing Civilization to Congo, or France shining the lights of the Republic to North Africa (and S-E Asia). Or the Spanish, saving South America through Religion.
Please, Lizards Overlords, make haste; I have a feeling it is a matter of emergency right now.
There are different ways, and the personal preference of the bassist / of their sound person matters. If they like their current amp (for their sound qualities), a lot of sound engineers will just put a microphone in front of it to pickup "their" acoustic sound ; if the amp itself is decent, it's going to feature a line output on the amp itself, that they can use to plug into the sound system and get the amp feed up to it. And, lastly, inserting a DI box between the instrument and the amp allows for a split output of one line towards the sound system and another towards the amp, so they can still hear "their" sound while the sound engineer has full control of how it will sound on the system (DI's are usually provided by the stage, rarely by the musician, and using them is a lot of time the choice of the engineer).
In a cool setup, sound engineers like to have both a microphone in front of the cabinet and from the amp output or a DI, allowing them to mix between both.
In a modern (bigger) system, the amp is entirely removed, replaced by a DI, or the cabinet is out backstage to avoid noise pollution on stage, and the musicians only hear themselves through the monitors.
Am I answering your question? No I'm not!
Talk to your friend. They may like their current amp to the death, they may very well know what they would like to buy next, or not.
Why not finding a pretext to go to a music shop and try several "just to have fun / just to have a look"? If an obvious preference arises, you just pop your credit card and Bob's their uncle!
105 days. Was yesterday for the first time in a restaurant that serves alcohol, with people drinking, was OK. I hated the giant TVs with football, the loud music, the smoke-filled athmosphere. And the French fries where cold.
I didn't mind the booze. I know I will always crave it, day in day out, from waking up till falling asleep, and also that it is not the answer.
ReallyZen @ reallyzen @lemmy.ml Posts 46Comments 621Joined 2 yr. ago
I'd push this further: I install what I need now, and then install anything else when needed. Old installs get bloated because of shit we pull over time. A new one has to be fresh. When testing a new distro you wanna see it at its (default) best.