In the meantime, its possible to use qjackctl to create a connection from input to the VST before it goes to the easyeffects sink. Its a bit kludgy but it should work well enough.
hollyberries
joined 10 months ago
Ooh damn. Mandrake was my first distro, I remember being sooo excited when the CDs came in the mail. It was I think 4 discs?
The experience was absolutely not good lol. At the time I only had one computer (some eMachines something or other) and a 56k line that only went to 14400 or 2600 baud depending on the weather. My NIC wasn't supported and after some banging my head on the desk I ended up going back to windows 98se after a few days because it was the family computer I messed up and caught sooo much flak for wiping.
Returned some years later when it was called Mandriva and had a better experience with a custom built AMD machine. The eMachines machine by then was still around as a network file server running a flavour of BSD that served media to my OG xbox played through XBMC (now Kodi).
Great post OP and thanks for the trip down memory lane!
Everything from this stop I've seen has been super special. I tried my hardest to make it there, by the time I managed to get enough money saved up the tickets were gone gone. TTPD has quite grown on me in recent weeks and it would have been sooo wonderful to catch a live set!
Media-wise, our news outlets raved about the performances, her donations to the food banks, and the positive impact to the local economy.
One day! 💖
Someone will likely share it for preservation purposes soon enough.
Apple confirmed that the Epic Games Store for iOS in the EU compiled with most of its guidelines, but it had an issue with the "a download button and related copy".
Apparently, Apple felt that the download button and related copy might mislead users into thinking they were made by the iPhone maker. While Apple has approved the app, it wants Epic to make the changes before the next app review.
There's the catch. Emphasis is from the original article.
I only see upsides here. Some people need expensive lessons in order to learn anything >.>
I'm one of those creatures that flattens out fizzy drinks before drinking xD
Air-up water bottles. When I bought mine it claimed to be a better water bottle all-around.
Its primary gimmick of tricking the brain into tasting the scent works well, I did drink a lot more water without needing actual flavouring. The fact that I could (unofficially) 3D print my own reusable flavouring pods to be a little more eco-friendly was a nice surprise and the reason I decided to try it.
The "better bottle" part is utter horse crap. It leaks when tipped over, even when tightly closed. Their marketing team went as far as adding "sip, don't tip" to the instructions instead of making the cap properly seal.
Drinking from it was a chore as there was no water pressure and the constant bubbling (lets be real, its more like wet fart) noises made it impossible to use in silent settings.
I ended up going back to reusing a disposable bottle until it leaks even though the thought and feeling of something flavourless being in my mouth is revolting (its a sensory thing).
To be honest, the extreme negative reaction was a surprise to me, as I thought interaction between disparate systems was the entire point, but clearly we didn’t navigate the culture correctly.
Noooo fucking shit? If they spent more than a minute on a proper instance and not ~~milquetoast~~ mastodon dot social, they would have realised that a good number of fedi users despise shenanigans like this?
I think about a feature or bugfix that I want to work on, then shoehorn it in by any means necessary. Once my code is confirmed working, the planning phase begins and I go through the module(s) I'm working with line-by-line and match the original author's coding style and usually by that point I pick up a trail or discover a bunch of helper functions/libraries that I can use to replace parts of my code, and continue from there.
As others have said, configuration files is a great way to learn that. Pick a config option you want to learn about, jump to the config loader, find where the variable gets set, then do a global search for that function. From there it starts to fall into place.
Sidenote: I also learned rust this way. It took me around 6 months to learn the rgit codebase solely from adding features that I wanted from cgit. Now I'm at the point where rebasing from upstream to my soft-fork doesn't mess up any of my changes, and am able add or fix things with relative ease. If memory serves, a proper debugger (firedbg is excellent!) was used on several occasions to track down an extremely annoying and ambiguous error message that was due to rust's trait system being a pain in my ass.
Have you looked at Duplicati? I use it and find it dead simple and reliable (I did a full recovery from a total data loss last year).