Looks very fun :-) Does anyone notice issues with the sound quality? In many of the examples I hear clicking: sometimes as if the attack is too high, or as if there is some kind of aliasing or sample rate issue, or just clipping. Probably noticeable with headphones. For instance in the announcement video at 3:11 or in the "J.S. Bach, Prelude in C Major (BWV 846)" video between 4.4s and 7.2s. It's somewhat visible if I load that audio in Audacity and turn on the spectrogram view with these settings: Logarithmic, 200 to 6000 Hz. Algorithm: Reassignment, 1024, Blackman-Harris, 1. Colors: 50, 40, 50.
What's odd is that I hear the glitches in in Firefox and in the file downloaded with yt-dlp, but not in Chromium. Is Google serving me bad audio on purpose?
Correction: some videos also do have glitchs on Chromium.
Once I realized that Flash .swf files could be compressed to half the size using gz, so I sent an e-mail to Macromedia suggesting that they zip their files. The next version had that feature enabled by default, which made me happy :-)
Also, at the time when interactive maps had 4 arrows to click and move North, South, East and West I developed a map using Flash and MapServer where you could drag the map around with the mouse. I sent a message to Google to show my work and they replied saying it was cool. Later Google maps came out with such an interface. I'll never know if my messages had any impact but I can still dream they were my inventions :-)
For years I've thought that dating sites could benefit from such post limits. If one could write 3 posts per day I think one would be more careful about what is posted and success might be shifted a bit from quantity of posts to their quality instead.
I like the idea. I think it would be nice to read in SlowSocial how will posts be treated. Will the company's algorithms read them? parse them? Put users into categories? I assume not, but it might be nice to display this in the front page.
I know what you mean. I still think Processing and p5.js might be the best way to start, but what's missing is a bridge to move to the next level: showing other ways of doing things, comparing languages, IDEs, how to avoid the spaghetti, what are the strengths and weaknesses of different tools, etc.
When I started using it 3 years ago I was concerned about using Kotlin (a language developed mostly by one company) or choosing a framework with a small community. After writing hundreds of audiovisual programs in Java, Kotlin, C++, JavaScript and some other languages I can say OPENRNDR provides the most frictionless creative experience for me. I enjoy it every day. Still, to appreciate what it has to offer I think it's better to start with Processing or p5.js and write growing programs until they become hard to follow. Then it makes sense to have a good IDE and a beautiful API.
If I look at [1] and [2] I see that in 2019 Finland's energy use was 55% fossil based. Sweden's was 31%. Coal was 5.10% for Finland, 0.20% for Sweden.
ps. I see there's worse... Germany 77.42% fossils, coal 17.53%. Still, I never had an impression Finland is a green energy hub (no waterfalls, no sun in winter). It is a green hub though.
To me the sound of those big bikes is a form of terrorism. They rise my blood pressure, increase stress levels and make me hate. Try living somewhere where every 20 minutes such bikes make the windows of your flat shake and you can't hear your TV or your partner talking until the bike is gone. Why do I have to suffer this every day of my life? I can't wait until the ICE is part of our primitive past.
What's odd is that I hear the glitches in in Firefox and in the file downloaded with yt-dlp, but not in Chromium. Is Google serving me bad audio on purpose?
Correction: some videos also do have glitchs on Chromium.