2020-05-25 (M) HouseRobotInterference

The RAND() function in Google Sheets worked well, but it required a lot of overhead from a browser, and I wanted to keep the power consumption down with this project. Not to mention, it was messy! The more I thought about it, the less sense it made to do things this way. It could have been an elegant solution to prandomly select a word, enunciate it via text-to-speech TTS, and repeat, but up against the hardware limitations of a Raspberry Pi, it was not going to be reliable. Plenty of other solutions have been turning around in my head since I started.
  • Prandomize the word list, and read sequentially
    • Pros:
      • One "start talking" command keeps things running for hours
      • Minimal delay
    • Cons:
      • A macro won't be smart enough to know when the reading is done
      • Dead time at the end of the list
      • I don't know if there is a clean solution
  • Find a collection of word sound files and shuffle them
    • Pros:
      • Easy as pie
    • Cons:
      • There may not be a collection out there
      • Copyright issues
      • Word list is static unless I find new sound files
  • Use TTS on all the words to make sound files
    • Pros:
      • Neat, once it's complete
      • Expandable via the same process
    • Cons:
      • Time to convert
      • Must write an Audacity macro to create files. Doable?
  • Record myself saying all the words
    • Cons:
      • Ugghhhhh, no thank you

The rest of the posts for this project have been arranged by date.
First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.