Microphone Position Calculator
Music and sound makers might find this input/output utility useful. https://www.shure.com/en-US/support/tools/pag-nag-calculator
Including experiments with styles and scripts for your edification and enjoyment.
Music and sound makers might find this input/output utility useful. https://www.shure.com/en-US/support/tools/pag-nag-calculator
https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Audio_concepts
So, even the Invidious instances are being thwarted. I'll just link the videos to whatever instance was working at the time.
For anyone who's been psychologically damaged by youtube ads, like me, I'll be changing the links to the 'Listening to' videos to an Invidio.us instance. I tried to give youtube a fair shake by turning off uBlock for the site, but the ads are just off the chain.
I think I got them all.
You might be interested in the History of Recording. All those cool records from the psychedelic era had to be made somewhere. It really makes you appreciate how comparatively easy it is to record sounds and make music in 2023.
I'm building my first SoundFont in Polyphone.
Sometimes I like everything centered. Sometimes I don't.
Music and sound makers, H.G. Fortune (RIP) left some legacy in the form of free VST2 audio plugins for all to enjoy. Thanks, H.G.
I was using horizontal rules to create space between posts by padding them, but replaced them by wrapping each post in an article element and padding that instead. I'm not sure if the page sounds any better.
I also noticed that the sun/moon button (top right) didn't scale when using the browser zoom level. It made it into a square with rounded corners — not the intended effect. But there's a way to make a circle with CSS that scales to any size.
clip-path:circle(50%);
That all happened because I reset the font-size to 1em instead of 2. That should default to the user settings in the browser. I like the text a little larger so I just use the browser zoom.
I'm pretty sure I've never used an <h6>
element in my life. Imagine being so detailed that you used them all the time, and found yourself requiring <h7>
's and possibly <h8>
's?
Man, I'd freak out if I had to be that detailed.
I found some Psychedelic Radio stream to listen to at the Psychedelic Jukebox. If you like listening through VLC or whatever, the location is https://cast5.asurahosting.com/proxy/psyched3/stream
Cap'n Crunch was actually born in 1963 in the midwest, but the better story is him being born on Crunch Island. Either way, Cap'n Crunch is a child of the 60's. Except he was already a sea captain.
I recently discovered that Orca is a free screen reader for Linux. Just now I installed it on my Debian laptop, so I'm going to read the docs and play around with it. See how my page sounds. Listening to documents. Hearing markup. Walking off muttering.
Right I'll let you know.
Update: that is one robust piece of software. For casual use (me) the Read Aloud plugin for Firefox gives me enough audio feedback to hear what I'm doing.
Use headings to navigate the sections of the page. Then reduce the font-size of the headings to zero with CSS if they don't work with your visual design. This will effectively hide the heading from view, but they will still work for screen readers and other technology.
h1,h2,h3{color:transparent;font-size:0px;line-height:0px;}
I'm doing that until I find a reason not to. Most of my posts are so short it seems a needless visual redundancy. But it's important that the headings are there in the source code.
I wanted to see the difference that swapping the higher and lower values on the blue channel made.
Black #000000
Blue #00000F
Blue #0000F0
Blue #0000FF
Wow, AI Help on Mozilla Developer Network.
Could be rad.
Did you really think there wouldn't be bubbles?
"If a website is optimised already for use with a keyboard only, it will also work in many respects with a screen reader. Still, some close attention needs to be paid, especially regarding semantics and custom interactivity."
— Accessibility Developer Guide
I got the Read Aloud plugin for Firefox and listened to my web page. It's not as hard as Meshuggah, but it sounds pretty good.
This article on landmark roles helped me see some ways to create better sounding pages. One thing is to structure your page with the right elements and attributes for screen readers. That kind of machine munches out on your code and tells you exactly what it thinks out loud.
I don't use a screen reader, but it doesn't matter because I can use the browser Developer Tools (usually F12) to see roughly the same thing in the Accessibility tab. The article linked above explains it in detail. In short, it's about roles and semantic elements, so you know our success is assured.
I 💖 ELEMENTS
Today I learned there's a new code playground on MDN, and that there's a new <search>
element in the HTML Standard.
I also found out that the big search engines don't use the <meta keywords="">
for page ranking, and haven't for years. I'm not sure if that means they don't use the keywords at all, or just not for page ranking. [Update: Not at all]. Since I'm not vying for top placement in search results, I'm going to continue to operate as if the keywords are still useful in helping the pages flow like an endless river into the heart of the cosmos.
Mine is: 1366 x 634.
Nice to meet you. I'm glad we could share screen dimensions.
Wherever you are it's
Creating continuity.
I like space.
Added a Go to Top button down there. ➘
Reading H.P. Lovecraft: The Complete Fiction.
<html lang="en">
Don't forget the lang attribute, or the page won't validate.
Added a night mode switch up there. ➚
<hr>
Define thematic changes with the horizontal rule.
<hr>
Animate.
Transition.
A single thought or phrase.
•
Justified.
Or centered.
Your favorite song today.
•
Upended.
Then regained.
The process is the way.