I agree with most of your points, but saying you shouldn't work in audio if you can't tell the difference between 192khz and 44.1khz is a bit elitist imo. And saying you're color blind if you can't tell the difference is like saying you're blind if you don't have 20/20 vision and shouldn't draw. You can always use meters to check for aliasing artifacts.
It's not like all of your samples and virtual instruments are 192khz or even 96k. Many are 48khz or even 44.1k.
I think there are many cases where people never need to go above 44.1khz unless you maybe have saturation on the master bus. I agree that good dithering is important though and think that there hasn't been enough research on that so far.
I try not to depend on these AI tools, not having them is inconvenient but I still write every line of code myself, so the speed I work at remains always the same.
I also never keep plans running for months on end. I pause them most of the time relying on free usage and resume them during busy hours when I run out of free usage. writing the code myself is also more fun tbh.
>I couldn't even move to real coding in 1 hour
That sounds... concerning? I would try to manage the context of the work you're doing yourself and only consult it for certain functions.
I don't think you need the very best from Anthropic if you follow these rules, you might also save quite a bit of money.
Sorry If this sounds like a lecture I just wanna give tips to continue your work. Best of Luck in getting your account back!
From what I gather the hatred for AI among musicians and artists is pretty universal. I can only speak for myself. but for me and the way that I draw and make music AI can only replace, never complement my creative process.
to be fair I wouldn't call people operating AI Image generators creative people. At best they're people curious about the technology itself, anybody willing to learn and do it for the sake of being creative does it themselves.
the demoscene is about putting in lots of technical effort into programs even if it would be completely unreasonable in any real software project.
This vibe coded mess is putting in so little technical effort even though it is completely unreasonable for any piece of software associated with the demoscene.
I'm suprised no one talks about this. AI Art isn't Art. AI Poetry isn't Art. And I'm tired of it. I know hacker news isn't the best place to complain about that but still... I'm not gonna read something somebody didn't put in the effort to write on their own. Especially not Poetry.
When you are hearing music, you are hearing the end Result of hundreds of intentional decisions made over a long time of deliberation, same can be said for Art. I simply do not hear or see that with AI Music or Art, even If I don't know it is AI generated.
A big part of listening to Music for me is relatability. I want to understand the tools and sounds used. And then I can make something similar with the tools I have.
None of that exists in AI. Music can only inspire others if it is the result of inspiration and real decisions that can be understood.
The slop sickens me. If deep down there still is a part of you that enjoys problem solving and creativity, then you should always do it yourself. The technology still isn't even that great.
I wanted to write a simple midi chord controller for my phone to make music, emphasis on simple. AI can't do it and couldn't even help me on small code fragments, because it doesn't look at the problem through the lens of my artistic creativity.
Vibe coding creates weak men because you reject the deeper meaning behind what you are creating. Vibe coding creates weak men because they can't code.
A single example being 14 cad a month, with the implication being that you have lots of monthly subscriptions for "small apps" sends shivers down my spine. I know YC has lots of wealthy people, but come on!
No Offense taken, but what's the point in using AI for anything unless you don't want to do it? I want live my life not consume information, is that really so bad?
The security advantage I see in mtotp is that you never reveal the password to the system you are authenticating with, but that there is also no electronic device that can be compromised
I've lost the joy in programming, the only thing I'm good at, I now make horrible music, but at least I don't exist as the means to an end that I don't control.
Step 1 in this situatoon is to try and see if this is a known mathematically unsolved problem, and if it is, giving up.
Isn't this just trying to find a hamiltonian cycle, isn't this NP hard? That's when I would give up, especially because you put so many constraints in it to make it human walkable.
Edit: Of course you don't have to give up, but it's good to know what you get yourself into
I remember asking myself this question years ago, and came to 162 bits. I was just a kid back then so the logic is probably wrong but I do wonder how simple the encoding could be under those constraints...
Edit: Here are the Notes
0 Empty
10 Pawn
1100 Knight
1101 Rook
1110 Bishop
1111 Queen
32 + 32 + 472
2 times 6 bits: position of the kings
30 bits: color mask
120 + 2*6 + 30 = 162 bits
We can store the rest using the methods from the blog post and add 18 bits for promotion, giving 180 bits.
I'm sure this isn't the most efficient way, and I think I had other methods and considered things like the bishops being able to occupy 32 squares, though special casing doesn't make sense because of promotions.
Technically if you got 8 bishops/queens/knights/rooks
You would occupy another 16 bits, giving 196 bits
I think the upper limit can be reduced at the cost of increasing the lower limit
EDIT2: I think I made the assumption at the time that to promote one piece you needed to capture at least one enemy pawn, giving the space for the two bits, which means the upper bound is actually 180 bits
Would love to see other people try in the comment section
It's not like all of your samples and virtual instruments are 192khz or even 96k. Many are 48khz or even 44.1k.
I think there are many cases where people never need to go above 44.1khz unless you maybe have saturation on the master bus. I agree that good dithering is important though and think that there hasn't been enough research on that so far.