ZILtoid1991 @ ZILtoid1991 @lemmy.world

He/Him | Hu/En/some Jp | ASD | Bi | C/C++/D/C#/Java

---

Read more

Posts

83

Comments

2,347

Joined

1 yr. ago

No, you can peddle hate speech, if you also make videos on why taxes should be eliminated, and how worker's movements and unions are "negatively affecting the right to work" (according to a former Google employee I knew).

He does not have a heart in metaphorical sense, only in the physical sense.

Now I want to create a nation called Sugonda, and its official language will be Sugondese, where we create a drug for Ligma called Bofadis.

That's why you self-host!

Basically by transpiling, I'm converting commands to a format with absolute time position rather than the current relative one, so I don't have to deal too much with the relative wait commands, seeking would be easier to implement rather than one using relative positions, and I wouldn't really have the issue with inserting extra commands when relative jump commands exist. As I said, the textual format already have some macros that function in similar vein, such as the [0]: note 0 0x7FFF s.:a-5 macro, that automatically inserts noteon and noteoff commands at the appropriate places when processed, and also jump commands use labels similar to some unstructured programming stuff.

I think I'll try to work on a game for a while, then peek into someone else's code that had similar problems on how they actually did it.

As for the MIDI 1.0 limitations:

• More than 16 channel implementation is a bit tricky, and I really didn't want the composer to rely on automatic polyphony handling real time (which would likely conflict with sound effects, etc.), nor wanted to deal with that too on top of everything else.
• Precision issues with Control Change commands, and I wanted most if not all things to be controlled via MIDI easily rather than aggressive preset swapping or SysEx commands. Some special functionality still uses SysEx, like global waveform changing in the FM synth, where you basically command to change one of the 128 possible waveforms to be changed to a custom parameter-generated one. The only thing that cannot be done from MIDI is specifying path for files, which is intentional since it would mess with real-time features.
• Adaptive soundtracks. To my knowledge, there's not a whole lot of formats for this, let alone ones that are known to be open, and even then many don't go much farther than maybe mixing a few extra tracks they can swap-in, mute, etc., while mine could manipulate instrument parameters, pitch, etc. Instead of going the route of downloading easymp3playback.dll and easymp3playback.h (originally I used sdl-audio), I went with my own audio solution, and since my engine already was custom tailored for "retro pixelart", I doubled down in that direction, and went with a pretty lo-fi sampler and an FM synth so far.

LLMs can recite code when asked properly, with a lot of errors. Trying to put code together with it without understanding how said code works is a greater insanity, than making random numbers with mathematics.

The real reason why there's a downtick in coding jobs is due to Xitter not imploding immediately after the mass firings. Now coders are working overtime with skeleton teams on the same problems, while being overburdened and making more mistakes.

AI likes to hallucinate details it cannot decypher to something else when used for upscaling, but otherwise it's now plausible that it is AI.

I personally needed the Pi for its Arm architecture.

Sopposotoro

I checked it closer, and it still has a lot of awful artifacting. This could be a result of some really shoddy AI upscaling, which likes to melt details, especially if they just put it into some image generator, and ask it to upscale it. There's some actual usable AI driven image upscalers for lineart, etc., but they're obviously not good for photos, and even mess up some lineart stuff.

If it were those Direct Drive washing machines, it didn't really had that issue.

Most of this is due to Xitter didn't collapse spectacularly after only a skeleton crew were left working overtime (crunch), so others followed suit, then kept pointing at AI. What we need is strikes, building alternatives so we can actually boycott, etc.

That is an underestimate, since it doesn't factor in the knockdown effect of the more lax regulations having, so people will try to sell all kinds of crap as "medicine".

This will just lead to more low-quality code.

I instead recommend using more productive languages. I've heard many good things about Rust, if you can deal with the OCaml-like syntax and the functional paradigm by default. As an alternative I can also recommend D, it doesn't have the "const by default" issue of Rust (functional paradigm is still possible, you just have to opt-in), a very C-like syntax except more refined, memory safety features (3 levels of memory safety + arrays with bounds checking), at the cost of a bit hard to opt-out garbage collector (you also have to opt-out from many D features and the already scarce library ecosystem).

Issue is, rape is already not being taken seriously as a crime, so they don't really have to care.

Reality:

The AI was trained to answer 3 to this question correctly.

Wait until the AI gets burned on a different question. Skeptics will rightfully use it to criticize LLMs for just being stochastic parrots, until LLM developers teach their models to answer it correctly, then the AI bros will use it as a proof it becoming "more and more human like".

Actual reality: Right-wing grifters are already on a "whitelist", as long as they also talk about lower taxes, lessening regulations and worker's protections, and also got popular enough. Source: knew a former moderator for Google.

Programming: that book was printed a month ago, and it's already obsolete.

If it was lemmy dot ml, then you likely criticized Xi Jinping, and apparently Xi Jinping is equal to all Chinese people.