Onno (VK6FLAB)

Anything and everything Amateur Radio and beyond. Heavily into Open Source and SDR, working on a multi band monitor and transmitter.

#geek #nerd #hamradio VK6FLAB #podcaster #australia #ITProfessional #voiceover #opentowork

  • 0 Posts
  • 61 Comments
Joined 7 months ago
cake
Cake day: March 4th, 2024

help-circle

  • There are at least three legal ways to do this. CB radio, ISM frequencies and amateur radio. I say legal because the radio spectrum is heavily regulated because every transmitter affects everyone else to more or lesser extent.

    You can buy CB or ISM band radios and get started.

    Amateur radio is a better option in my opinion. There are many more frequencies to experiment with, people who can help and people to talk to.

    Amateur licensing is different in each country, but an introductory licence is often no more than a weekend course and exam. I know of nine year olds who have done this. It’s not hard. No Morse code required either.

    With such a licence in hand you can use things like JS8Call, CODEC2, Olivia, WSPR and hundreds of other protocols to communicate using just a radio and a computer.

    Disclaimer: I’m a licensed amateur in Australia and have been since 2010. I hold an introductory licence, here it’s called a Foundation licence, and have been having an absolute blast with all that I can do.

    If you have specific questions, don’t hesitate to ask.








  • Multiple camera angles are used for two reasons:

    1. Added visual interest. People tend to want variety and colour and movement offered by different views can provide that. This is the obvious reason it’s being used.
    2. Ability to edit without it being obvious. Often a presenter will require multiple takes to “get it right”. If you edit in the take, the picture “jumps” because humans move around. If you have multiple cameras you can edit and switch cameras without it looking like an edit. If you then also look at a different camera when you make a mistake, you can keep recording and fix it when you edit it together.


  • Sadly not. Form an audio frequency perspective, noise is many different frequencies. The human voice pretty much matches human hearing.

    A voice is not one frequency, that’s a tone. We’ve constructed systems that throw away much of the voice frequencies whilst still being understandable. Telephone calls, digital radio communication, etc.

    That’s not to reduce noise, it’s to cram more calls across the same link. There’s a side effect that does reduce noise to some extent, but not significant enough to remove construction noise.


  • I suspect that your success rate will be very low. Bone conduction microphones might be your best bet.

    Fundamentally a microphone doesn’t know the difference between “good” sound and “bad” sound.

    Most noise cancelling solutions are based around the idea that nearby sound is good and distant sound is bad.

    It differentiate between the two by using the fact that it takes time for sound to travel.

    If you have two identical microphones, you can set them up so that you talk directly into one, but not the other.

    Any environmental sounds are picked up by both and used to cancel it - sometimes in software, other times just by reversing the microphone polarity.

    Bone conduction microphones get their signal from physical contact with the audio source, your body.

    Source: I’ve done a little bit of audio recording over the years in and outside of studios. My information might be incomplete and out of date. YMMV.



  • Generally laziness helps.

    If you host a system, then you have to dedicate resources to maintaining it, which quickly escalates to lack of interest.

    If you pay someone to host it, you get to spend your energy on things that you’re interested in.

    If you can find people to pay you for things that you’re interested in, but they just want fixed, you have a business.

    So, be conservative in what you host and frivolous in what you outsource.

    Note that this says nothing about FOSS. since that’s about a related but different concepts.

    From a FOSS perspective, be frivolous (as in, do lots) in your bug reports and patches, be conservative in which projects you own.