m0xEE @m0xee@librem.one

@newt @mischievoustomato
Making music and video games are relatively niche use cases compared to what most people use wireless audio peripherals for. In both of these cases wired would probably always be better. No need to apply some kind of universal solution for everything: you know me — I *despise* USB audio, but if it's a tiny machine hooked up to my amp that I can listen my digital collection on and that I can control remotely — why would I care?

@newt @mischievoustomato
Now that is a valid point indeed, I don't use wireless headphones at all, but I suspect it to be pretty much unusable.
I just don't see why you attempt to apply the same principle to audio *consumption*, I didn't even get it at first — what you were talking about and why buffering might be bad.

@newt
No need to! Buffering can defeat the deficiencies even of such a sorry ass of interface as USB. But of course that wouldn't even be necessary were superior DMA-capable hardware used.

@newt
Of course it is better! Might even allow you to implement audio decompression in JS — computing power well spent 😜

@newt
Sure, everyone knows that you need modern desktop-class hardware to play audio 😂

@newt
You obviously have no experience using low processing power machines, which use USB (an utter garbage of interface 😏) for audio, networking AND storage.
Dropouts are gay and lame and whatever, buffering is amazing!

@newt
Wat is wrong with buffering? Without it you're fucked in a lot of cases: network delays, physical media spun down on detecting vibrations to prevent damage, physical media having to be re-read due to errors, etc…
And 1.25 seems to be just right to be reading FLACs on average — studio recordings are often heavily compressed/filtered and use even lower bandwidth.

@AndyGER
Don't get me wrong though, I'm not a fan of everything AI in the slightest, but I won't say that it's bad just because it has "AI" in it in this particular case — it should be good enough in a lot of cases, and in those when it's not, it should provide a good starting point. But I'm afraid that some people would start submitting descriptions generated by it as is — adding a line of warning text seems reasonable.
@duco @3kh0 @mozilla

@AndyGER
Speaking of translation, the result would probably be very similar to attempting to translate a joke that is built on wordplay — lacking at best. Proper translation of such a joke might not exist at all, and automated one will only cause confusion.
@duco @3kh0 @mozilla

@AndyGER
Translation and describing the image are two separate tasks. Sure, if it's a photo of nature, this AI thing might do a pretty good job, better than a lot of us would be willing to put time and effort in, but if it's some humorous image, I'm afraid, it would do a very poor job — the description it would generate will have lots of unnecessary details: it simply doesn't know what to focus on.
@duco @3kh0 @mozilla

@j4n3z @mntmn
To a point that I was able to build and use it even on my old PowerMac G5.
I might be wrong about it, but I think Node.js is no longer even supported on Big Endian PowerPC architecture — wouldn't be a problem in this particular case, but this makes openrazer more portable.

@j4n3z
This one? https://github.com/the-via/app
Didn't know about it 😅 Considering it's specifically for QMK keyboards, it definitely makes sense.
To me Node and Chrome/Electron seem too heavy of a requirement though.
openrazer is completely opensource BTW, all parts of it: kernel modules, the daemon and the Python module.
@mntmn

@romin
Of course not! In fact, I'm three bitter old men, who don't love anybody, in a catsuit!

@kirby
You're just not in your supervillain arc… yet 😏

Boy is making a script that bans someone he does not like from all his accounts 👶🏿
Man is building giant robots that obliterate his enemies 👨🏿

@m0xEE

@mntmn
Making it compatible with OpenRazer might make sense… or not. AFAIK, they have a daemon and a Python API for interacting with it. On the one hand, it would enable people to use familiar tools and things they have built on top of them — on the other, striving for compatibility at this point would probably entail a lot of work with little immediate return 🤔

@tennoseremel
Так то без грибов была, а теперь — с ними родимыми! 😂
Рановато только начали что-то 🤔
@neural_meduza

@Forestofenchantment
To me it looks like they are just going crazy. All of them 😂
@mischievoustomato

@kirby @skylar
You could always unplug it and plug it back in again to fix that — but it was pissing me off as you might have other things connected, like USB storage — I had a Firewire audio card plugged into it. Just disconnecting stuff like that isn't good if you have software that is using that hardware — so it was pissing me off immensely.
This problem never got fixed 😂

@kirby @skylar
I have MacBook Pro that was one of the first laptops to get a Thunderbolt port — there was no USB-C at the time, it was a different port.
And I got an Apple Thunderbolt Display with it — also one of the first to get all that, it had everything built into it: a wired network adapter, a soundcard with speaker system (it had a subwoofer even), and of course it worked as an external display.
Sometimes on waking the machine from sleep the display didn't come back on.