Playonlinux error on start

When I was trying to run Playonlinux from an icon, nothing ever appeared. I started a terminal and ran it, and got the python error:

ImportError: cannot import name _remove_dead_weakref

I didn’t find much on this, but after a lot of searching found this site and the final answer that fixed it for me:

Edit this file:


And change the following from:

next_python "python"
next_python "python2.7"
next_python "python2.6"
next_python "python2"
next_python "none"


next_python "/usr/bin/python" #This line was added
next_python "python"
next_python "python2.7"
next_python "python2.6"
next_python "python2"
next_python "none"

That fixed it for me!


Zillion connections to Google, Amazon, Twitter and others when Firefox opened after deleting cached files

I noticed that when I opened my Firefox browser (58.0.2 64-bit Linux), the connection light on my router kept blinking for a long time. I did a netstat -t command to find out to what I was connecting. To my surprise, it was a LOT more than Google.

It apparently has something to do with deleting cached files or folders, as I show later.

Here is an approximate listing of what I should see (all of the “sea15” servers are Google):
tcp 0 0 JW-PC:46562 server-13-32-178-:https ESTABLISHED
tcp 0 0 JW-PC:54168 sea15s12-in-f195.:https ESTABLISHED
tcp 0 0 JW-PC:49378 sea15s07-in-f68.1:https ESTABLISHED

Instead, here is a listing of what I saw. I’ve bolded some of the text:
tcp 0 0 JW-PC:56480 a23-32-46-41.deplo:http ESTABLISHED
tcp 0 0 JW-PC:33474 server-13-33-147-:https ESTABLISHED
tcp 0 0 JW-PC:45466 ec2-54-213-234-15:https TIME_WAIT
tcp 0 0 JW-PC:56334 ESTABLISHED
tcp 0 0 JW-PC:34470 TIME_WAIT
tcp 0 0 JW-PC:34040 a104-126-1-33.depl:http ESTABLISHED
tcp 0 0 JW-PC:53200 ESTABLISHED
tcp 0 0 JW-PC:58400 ESTABLISHED
tcp 0 0 JW-PC:49226 sea15s01-in-f10.1e:http ESTABLISHED
tcp 0 0 JW-PC:51302 server-13-33-151-6:http ESTABLISHED
tcp 0 0 JW-PC:47918 sea15s11-in-f14.1e:http ESTABLISHED
tcp 0 0 JW-PC:60236 server-13-33-147-3:http ESTABLISHED
tcp 0 0 JW-PC:33614 a104-126-1-33.depl:http ESTABLISHED
tcp 0 0 JW-PC:53944 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:51256 ESTABLISHED
tcp 0 0 JW-PC:51990 ESTABLISHED
tcp 0 0 JW-PC:50912 server-13-33-146-6:http ESTABLISHED
tcp 0 0 JW-PC:51992 ESTABLISHED
tcp 0 0 JW-PC:34268 server-13-33-151-:https ESTABLISHED
tcp 0 0 JW-PC:37506 sea15s01-in-f130.:https ESTABLISHED
tcp 0 0 JW-PC:47854 server-13-33-147-1:http ESTABLISHED
tcp 0 0 JW-PC:55610 sea15s07-in-f68.1:https ESTABLISHED
tcp 0 0 JW-PC:34062 sea15s07-in-f14.1:https ESTABLISHED
tcp 0 0 JW-PC:53384 sea15s07-in-f14.1e:http ESTABLISHED
tcp 0 0 JW-PC:39098 a23-204-103-59.dep:http ESTABLISHED
tcp 0 0 JW-PC:58614 sea15s11-in-f162.1:http ESTABLISHED
tcp 0 0 JW-PC:47124 server-13-33-151-1:http ESTABLISHED
tcp 0 0 JW-PC:47538 a23-6-165-175.depl:http ESTABLISHED
tcp 0 0 JW-PC:32878 a23-45-230-178.dep:http ESTABLISHED
tcp 0 0 JW-PC:38836 a23-217-12-72.depl:http ESTABLISHED
tcp 0 0 JW-PC:37574 ESTABLISHED
tcp 0 0 JW-PC:37778 server-13-33-124-:https ESTABLISHED
tcp 0 0 JW-PC:48128 ESTABLISHED
tcp 0 0 JW-PC:54364 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:53278 ESTABLISHED
tcp 0 0 JW-PC:40764 ESTABLISHED
tcp 0 0 JW-PC:42124 ESTABLISHED
tcp 0 0 JW-PC:59364 ec2-54-225-214-20:https ESTABLISHED
tcp 0 0 JW-PC:54374 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:59902 server-13-33-151-:https ESTABLISHED
tcp 0 0 JW-PC:54736 ESTABLISHED
tcp 0 0 JW-PC:49646 sea15s01-in-f10.1e:http ESTABLISHED
tcp 0 0 JW-PC:38936 a104-109-200-201.d:http ESTABLISHED
tcp 0 0 JW-PC:51672 sea15s01-in-f142.:https ESTABLISHED
tcp 0 0 JW-PC:52276 ESTABLISHED
tcp 0 0 JW-PC:44270 ESTABLISHED
tcp 0 0 JW-PC:42024 ec2-35-162-179-12:https ESTABLISHED
tcp 0 0 JW-PC:59886 ESTABLISHED
tcp 0 0 JW-PC:45134 ESTABLISHED
tcp 0 0 JW-PC:50914 server-13-33-146-6:http ESTABLISHED
tcp 0 0 JW-PC:35590 sea15s01-in-f10.1:https ESTABLISHED
tcp 0 0 JW-PC:51330 ec2-52-52-244-13.u:http ESTABLISHED
tcp 0 0 JW-PC:53916 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:57792 ESTABLISHED
tcp 0 0 JW-PC:32934 ec2-54-164-46-184:https TIME_WAIT
tcp 0 0 JW-PC:54372 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:45136 ESTABLISHED
tcp 0 0 JW-PC:59458 xx-fbcdn-shv-01-s:https ESTABLISHED
tcp 0 0 JW-PC:38240 ESTABLISHED
tcp 0 0 JW-PC:37996 ESTABLISHED
tcp 0 0 JW-PC:42556 ESTABLISHED
tcp 0 0 JW-PC:58066 r-199-59-148-23.t:https ESTABLISHED
tcp 0 0 JW-PC:52060 ec2-54-213-128-13:https TIME_WAIT
tcp 0 0 JW-PC:53248 ec2-52-52-174-199:https TIME_WAIT
tcp 0 0 JW-PC:45300 sea15s07-in-f2.1e1:http ESTABLISHED
tcp 0 0 JW-PC:46038 ESTABLISHED
tcp 0 0 JW-PC:48748 ESTABLISHED
tcp 0 0 JW-PC:60442 server-13-33-151-:https ESTABLISHED
tcp 0 0 JW-PC:49114 server-13-33-147-8:http ESTABLISHED
tcp 0 0 JW-PC:43940 TIME_WAIT
tcp 0 0 JW-PC:55376 sea15s07-in-f67.1:https ESTABLISHED
tcp 0 0 JW-PC:54368 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:46308 ESTABLISHED
tcp 0 0 JW-PC:40772 ESTABLISHED
tcp 0 0 JW-PC:38888 a23-217-12-72.depl:http ESTABLISHED
tcp 0 0 JW-PC:43338 server-13-33-110-2:http ESTABLISHED
tcp 0 0 JW-PC:41848 server-13-33-151-1:http ESTABLISHED
tcp 0 0 JW-PC:60904 sea15s01-in-f3.1e:https ESTABLISHED
tcp 0 0 JW-PC:54116 ads16-fw-us-west.:https TIME_WAIT
tcp 0 0 JW-PC:38854 ESTABLISHED
tcp 0 0 JW-PC:50086 ec2-50-17-199-221.:http ESTABLISHED
tcp 0 0 JW-PC:51902 ESTABLISHED
tcp 0 0 JW-PC:32794 server-13-33-151-:https ESTABLISHED
tcp 0 0 JW-PC:41126 ec2-54-76-91-81.e:https TIME_WAIT
tcp 0 0 JW-PC:42880 ESTABLISHED
tcp 0 0 JW-PC:48318 sea15s11-in-f162.:https ESTABLISHED
tcp 0 1 JW-PC:37396 FIN_WAIT1
tcp 0 0 JW-PC:53922 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:46346 ESTABLISHED
tcp 0 0 JW-PC:59598 ESTABLISHED
tcp 0 0 JW-PC:60802 ESTABLISHED
tcp 0 0 JW-PC:33258 server-13-33-151-1:http ESTABLISHED
tcp 0 0 JW-PC:58754 sea15s11-in-f162.1:http ESTABLISHED
tcp 0 0 JW-PC:59376 ESTABLISHED
tcp 0 0 JW-PC:53920 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:42534 ESTABLISHED
tcp 0 0 JW-PC:39818 ESTABLISHED
tcp 0 0 JW-PC:53292 ESTABLISHED
tcp 0 0 JW-PC:51304 server-13-33-151-6:http ESTABLISHED
tcp 0 0 JW-PC:46356 ESTABLISHED
tcp 0 0 JW-PC:54370 a23-32-46-131.depl:http ESTABLISHED
tcp 0 0 JW-PC:38886 a23-217-12-72.depl:http ESTABLISHED
tcp 0 0 JW-PC:51448 TIME_WAIT
tcp 0 0 JW-PC:56056 xx-fbcdn-shv-01-s:https ESTABLISHED
tcp 0 0 JW-PC:59350 tags.expo9.exponen:http ESTABLISHED
tcp 0 0 JW-PC:40414 edge-star-mini-sh:https ESTABLISHED
tcp 0 0 JW-PC:45406 ESTABLISHED
tcp 0 0 JW-PC:52934 ESTABLISHED
tcp 0 0 JW-PC:55496 ec2-54-191-241-24:https ESTABLISHED
tcp 0 0 JW-PC:33036 a23-32-46-98.deplo:http ESTABLISHED
tcp 0 0 JW-PC:53028 ec2-52-72-47-138.c:http ESTABLISHED
tcp 0 0 JW-PC:39806 TIME_WAIT

Today I also saw a connection to “”

Not sure what is happening to cause this, or why I’m seeing so many connections to things that have no bearing to google (the home page), but it is concerning. I have not tried a different OS, but will do so at work. It doesn’t happen all the time with my own system, but is consistent if I remove the cached files from Firefox and then start the browser.

If I do not removed the cached files and folders, then it looks fairly normal:
tcp 0 0 JW-PC:41324 ESTABLISHED
tcp 0 0 JW-PC:59650 sea15s01-in-f3.1e:https ESTABLISHED
tcp 0 0 JW-PC:42008 ec2-54-191-46-28.:https ESTABLISHED
tcp 0 0 JW-PC:56694 sea15s01-in-f14.1e:http ESTABLISHED
tcp 0 0 JW-PC:46844 a23-204-103-74.dep:http ESTABLISHED
tcp 0 0 JW-PC:52824 server-13-32-178-:https ESTABLISHED
tcp 0 0 JW-PC:57186 ec2-54-148-143-13:https ESTABLISHED
tcp 0 0 JW-PC:54158 sea15s11-in-f164.:https ESTABLISHED
tcp 0 0 JW-PC:41318 ESTABLISHED

For some reason, Firefox generates a ton of connections to seemingly random (but probably not random) servers if the cache files are missing. It should simply create the folders without needing to connect to anything other than the home page, in this case

I don’t have any news feeds, and the “random” servers are different each time.

I will try asking in a forum about this.

I found someone had asked a similar question on Mozilla’s forum:

He links the issue to the webappstore.sqlite file, but even so, it is a mystery yet not answered by Mozilla as to WHY this file has all of these connections to odd servers, even if the file is delete and auto-recreated. The poster says:

“Why does Firefox connect to every single address while starting up, what is written to this sql db? I could say this is the solution at least solving the original question “where does this software get it’s 100-400 connection addresses”.

So this seems to be the source of some of the issue, but where does Firefox get the server names in the first place?

 I found that I could turn off my permissions to the file webappstore.sqlite, and that stopped the connections to odd servers, but then I was unable to do things like edit my WordPress website. So clearly it is needed for some things, and I need to be able to write to it.
I think Mozilla should offer an explanation of what is happening and why the browser needs to connect to these hundred or so servers.

Mushroom logs

I’ve been experimenting with growing various kinds of mushrooms on hardwood logs. I started in September of 2016 when I inoculated a handful of logs with “plug spawn”, that is, short dowels that have specific mushroom mycelium growing on them. Mycelium is the part of the mushroom that is hidden inside the wood (or ground if it is the kind that grows in the ground). I chose the following kinds:

1. Turkey Tail on oak log
2. Lion’s Mane on oak log
3. Chicken of the Woods on oak log
4. Reishi on oak log
5. Shiitake on maple log
6. Nameko (or so I thought. More on that later…) on maple log. This plug spawn looked oddly blank, or just like plain damp wood.


I purchased spawn from,, and I also purchased beeswax to seal the holes and help retain moisture and keep out competing fungi.

The downside of using logs is that you often have to wait at least a year, maybe two or three before you see any visible mushrooms.


2016 gave us a particularly early, cold, and long frozen winter in the Vancouver, Washington area. I wasn’t sure if my mushrooms had survived or not. When June 2017 rolled around, I decided to double up and inoculate the same logs a 2nd time, just in case. I also had a couple of Douglas Fir stumps in which I put Phoenix Oyster plug spawn.

Through the hot summer, I kept watering the logs, and even gave them a soak in a small kiddie pool. Soaking all of them together turned out to be a mistake, which I’ll go into later.

By August I started seeing visible growth of mycelium happening on the Turkey Tail log, and a bit on a couple of others. By late September, the Turkey Tails mushrooms were about the width of a quarter-dollar. By mid-October I realized that all of the oak logs were growing Turkey Tail mushrooms. I knew I had purchased a variety, so chalked it up to soaking them all together, and Turkey Tail being a particularly aggressive mushroom.

Turkey Tail mycelium 8-9-2017 B
(First obvious mycelium growth on the Turkey Tail log)

(Turkey Tail mushrooms on an oak log. Snap them off and collect them, dice them up or use heavy scissors. Too tough to eat, these are used to make a broth and extract.)

I never did see any of the other kinds of mushrooms produce at all. The maple logs aren’t even growing Turkey Tails. I read that Nameko can take years to show up. I bought some more plug spawn from the same company, and was again wondering about it being so entirely free of obvious mycelium growth. This is the stuff that is supposed to carry the mushroom spawn into the log, and it if has no mushroom spawn, I am wasting time and money buying it. I took a picture of the package of damp dowels alongside a bag of another company’s bag of plug spawn and sent it to the vendor Mushroom Mountain asking what was up with the blank plugs.

no mycelium

No response at all from Mushroom Mountain. It has been months and still no response. I am certain they twice sold me blank wood with no mycelium. I gave them a bad review on Google and discontinued business with them. I hope the other spawn I ordered from them that had mycelium is actually the varieties I ordered. I even kept the little bag of dowels until this week, and no mycelium ever showed.

In October 2017 I was able to take several plum wood logs. This wood is very dense! The logs are 2 to 3 times as heavy as other logs I’ve used. I inoculated them with Blue oyster, Maitake, Shiitake, Reishi, and Lion’s Mane. Around Halloween, I ordered a bag of Nameko sawdust spawn (spawn grown on sawdust instead of dowels) from Field and Forest Products, along with the tools needed to do the inoculating. I inoculated 4 logs with Nameko and sealed the holes with wax. I also chose to put some into one of the Douglas Fir stumps I had. I also put some in the old log from 2016 in which I thought I had put Nameko previously. Sawdust spawn carries more mycelium into the log than plug spawn. The holes are larger, and the mycelium amount is greater.

few logs
(This out of focus shot shows the plum logs inoculated and waxed)

sawdust in holes
(This shows a plum log drilled and inoculated with Nameko sawdust spawn)

tool and bag
(This shows the bag of Nameko sawdust spawn white with mycelium, and the tool used to insert a measured amount of the sawdust into drilled holes in logs)

NOTE: I switched to using cheese wax instead of bee’s wax because I found that hornets and maybe bees have been stealing the wax and leaving my plug spawn exposed. I had never read that they do that, but I witnessed it, so made the change. So far, the cheese wax has been ignored.

The weather has become freezing as it is almost Christmas, but the logs have had two months of mild temperatures for the mycelium to become established, so if the mycelium likes plum wood, I should start seeing some obvious mycelium growth around Fall of 2018. I figure that Japanese varieties should do well in plum.

The Turkey Tails are still growing on the oak logs I have from before. I harvested some of them and made a tasty broth (hot water extraction) by chopping them up finely and boiling in a pot of water for about 4 hours. I also did an alcohol extraction of them by placing them in a mason jar and filling it with vodka and sealing it for 2 months, shaking it daily. The broth and the extract are said to contain substances helpful for fighting diseases and boosting the immune system. I figure they can’t hurt, so I’ll try them. At least the broth is tasty! I also bought a large Maitake mushroom from an organic store and am doing the same broth and alcohol process with it.


Sounding Good Despite Incompetent Sound Techs And Well-Meaning Band Members

I sing as a hobby, and usually get to tweak the sound board to make my voice sound good for whatever venue I play. However, occasionally there are actual sound techs for the house and that person will set up the board and adjust it during the concert (if I’m lucky). However, I’ve had a couple that simply did a simple sound check at the beginning with a fancy iPad out in the audience seats, and then sat there the rest of the show listening to tunes on an iPhone. SMITE!!

If you are going to do the job, do the damn job. Know what the knobs are for and what effect they have when changed. Then pay attention to the band during the performance. When the crowd shows up, the audio dynamic changes due to sound absorption. I’m not sure why, but I almost invariably am given way too much bass and my voice sounds muddy compared with my band mates who have higher registers. A good sound tech is such a wonderful asset!

Even on gigs where I set up my own sound board, I’ve had to argue with one person who had a one-size-fits-all EQ form for the sliders, the classic “smile” shape. No, it really doesn’t fit all, and you have no business changing the settings if you don’t know what you are doing. I don’t care if “you’ve done it that way for years because it’s the right way and everyone knows that”. You’re wrong, and get away from my mixer. At one gig, an expert set us up, and within minutes a band member was over there changing things. There is only so much you can do if you want to stay together as a band. Choose your battles.

At my last gig, I set up my mic did a few singing tests to make sure I sounded good for the venue, and walked away for a few minutes while the instrumentalists set up. I came back and did another test just to have confidence, and I sounded MUDDY AS HELL. I looked at the board and someone had turned the mid range down to 0, the treble to negative 10, and the bass up! @#$%@#$!!! I set it back to how I had it and tested my mic again, and sounded good again. I had to assume that one of them thought he or she was adjusting their own levels and changed mine. Glad I caught it before the show.

Start the EQ flat with everything at middle. If you can move out to where the audience will be for your vocal test, do it. Or if the sound tech is adjusting things, he/she/other should be experienced enough to set your vocals to be crisp and clear with good warmth. My mic has a larger diaphragm than most, so it picks up sound (and bass) more easily than other mics. That typically means I need to boost my treble and slightly lower the bass. I sometimes use a high-pass filter to cut mic handling noise, and use the much hated “clown nose” foam cover to mitigate sibilance. Some singers have a cow over that setup because it isn’t the mic they prefer, the EQ is different, and the foam cover they assume always makes the sound muddy. It does not. All of that can be tweaked at the EQ.

I did an article months ago on Mic Shaming that describes how to try out and select a microphone at a store, assuming they will let you. If they won’t, go somewhere else. Sometimes musicians will have a selection and will let you try some if you know them. Some will try to sell you on the kind they use, but you really should try out a few without a preconceived notion hanging over you. But remember, when using someone else’s microphones, PLEASE BE CAREFUL! Don’t drop it ever. Don’t swing it by the cord. Don’t pull it off the cord while the mic is live, unless you push in the release button gently and remove gently. If it is a mic that uses Phantom Power, turn the speakers down before removing the mic from the cord or you will cause a loud POP which is bad for the speakers and the ears of those around you. Treat the speakers with great care also, they tend to cost a lot of money.

I currently use a Heil PR35 handheld mic, a Mackie ProFX8v2 mixer board, and a QSC KW122 powered speaker. I also have a Heil Fin stand mic, but rarely use it. I’m fine using other equipment as well. I chose my setup by comparing what other singers in my area use, and then balancing those choices with my own voice and budget. I am the one most responsible for how I sound at a show, so as much as possible, I want the components to be under my control. Unless there is a known competent sound tech at the board, adjust the settings to where you sound good, NOT just where you think they should be. Test it, if at all possible, or you are setting yourself up for problems.

The first two gigs I did with a band, my voice was muddy (way too much bass). The sound equipment in some venues is genuinely lousy, has been there for 40 years, and should have been retired a long time ago. But venues don’t make money by paying for new equipment and they are in it for the money. If possible, bring your own stuff and use it instead of the venue equipment. Do a real mic test after you set up and SING a song so You Know That You Know That You Know you sound good in that venue. A venue with lots of cloth on the walls, carpet, and people in the audience wearing clothing, will absorb sound. Try singing in a closet full of clothing and your voice almost disappears. Conversely, a venue with little cloth and a lot of hard surfaces will bounce the sound a LOT, perhaps too much to be viable. Tweak the volume and EQ to make your voice sound good in that particular venue.

Read about other people’s experiences online and then try it over and over again. You can learn a lot from other’s mistakes and tips, but in the end you have to actually go do it repeatedly to learn your equipment (and learn to recognize when it is failing). I had a sound board start losing a channel right before a gig, so had to switch. Happily I had an open channel left of the mixer. One gig I tried three mixers before one actually worked normally. That was a nervous set-up.

All in all, get yourself gear that you have tested and like, and get used to how it works. Learn what all the knobs and sliders do. Talk with other singers and instrumentalists. Then go do your best. Some days it just won’t go your way and you have to make the best of it. Some days, you don’t get to change the mixer because a control freak is in charge. Some days an incompetent tech will ignore your band through the show. Some days you have to use 3rd hand ancient crap equipment and end up sounding awful. Which is why, as much as you can, be in charge of how you sound and know how to sound good.

FFMPEG to NTSC-DVD, odd pulsing…

I’ve been using FFMPEG for years to create DVD compatible video. Recently, I made a change on my Sony Handicam from 60i to 60p video, and suddenly I’m getting an odd pulsing in the resulting video, but only when I convert to MPEG2. Converting to MP4 still works fine or I’d be sunk. By pulsing, I mean that the light seems to pulse every 1 second like someone is turning up the color contrast knob and then back down. Very brief, but continuous.

[EDIT: I just did a recording in 60i and it still pulses when I try to encode using “-target ntsc-dvd”, so either FFMPEG changed something, or there is a deeper issue happening on my computer, but I doubt that since all other encodings work fine, and encoding in DVD quality via Corel Visual Studio works fine on the same PC in Windows.]

Here is the code I normally use:

ffmpeg -i part1.m2ts -target ntsc-dvd part1.mpg

Pretty straightforward code, and it has always worked up until I made this change to recording in 60p. I must say that 60p has a more professional appearance to my eyes. I’m not sure what I’m seeing differently, but it does create a good impression.

I suspect that if I took apart the mechanics of what -target ntsc-dvd does that I may find a setting that I might be able to tweak.

I found one entry about the macro creating progressive output, so it should (I would think) preserve the progressive input. He said that he tried this code to get his to work, though I admit I don’t understand what it is doing yet. (It didn’t work for me at all. I still got the pulsing video.)

ffmpeg -y -i 00000.MTS -pass 1 -target ntsc-dvd -b:v 4000K -flags ildct+ilme -top 1 /dev/null && ffmpeg -y -i 00000.MTS -pass 2 -target ntsc-dvd -b:v 4000K -flags ildct+ilme -top 1 test.mpg

(ilme means interlaced motion estimation)
(ildct means use interlaced dct)

Another described what I’m seeing from a post back in 2006, and said his solution was “I’ve found the solution to my own question. I simply needed to set motion estimation to full (-me full) and the problem went away.”

That would imply that changing my code to
ffmpeg -i part1.m2ts -target ntsc-dvd -me_method epzs part1.mpg
should fix it. But it didn’t, I get the same pulsing as I did without that additional code. [method full is not available, only zero or epzs]

So I’m open to suggestions. Right now, the only solution I have is to go back to 60i, or use Corel Video Studio x9 in Windows. Video Studio is able to create the DVD video without any pulsing (though I have to create an MP4 file for it to use, since it seems to choke badly on MTS or m2ts files, each click takes a few minutes to process).

Loud Garage Door Opener – Fix it!

(Please note: I’m not a structural engineer or even a licensed contractor. If you decide to do this modification, it is at your own risk.)

Our garage door opener motor was LOUD! The whole room above it vibrated far more loudly than being in the garage with the motor. This is due to the mechanical connection of the motor to rigid metal straps which are then bolted to the ceiling beam.


I spent a few weeks studying how other people and companies try to solve this issue. Some methods would probably work but appeared kind of dangerous (such as hanging the motor housing from rubber straps). The point of vibration isolation is to have an insert of some kind that will absorb the energy of the vibration without transmitting it to the beams and walls of the house. Most solutions seem to use rubber or Sorbothane pads to sandwich the metal frame, with the idea that the two pads will jiggle and absorb the energy of the vibrating metal.

KEY IDEA: A rigid structure will always transmit the vibrational energy; a flexible insert before the ceiling will absorb the vibrational energy and transmit far less.

I looked at using rubber or Sorbothane washers between the metal and the ceiling, but in order to seat the lag bolts properly, I would have to squish the washers which would drastically reduce the vibration-absorbing ability of the material (it needs to be able to jiggle to absorb the energy). I thought about bolting rubber pads above and below the metal straping to help absorb the vibrations. But the stiffness of the pads which would directly touch the ceiling and the bolting seemed counter-intuitive to me (it just didn’t seem like it would work).

I looked at all kinds of vibration absorbing pads and other vibration isolators, but finally settled on a hanging neoprene isolator (Mason 2LVR8). They do make spring versions, but those are really made for large heavy motors instead of a lightweight garage door opener. I needed something that would easily jiggle, and these neoprene isolators were rated at 0-30 pounds, which sounded perfect. I also chose to add neoprene washers as an additional damper on 2 spots where loose metal was going to touch. I bought the Mason isolators online from a vendor named Grainger for $9 each. Amazon actually wanted $6 more per unit! I used three isolators to hold the motor. That may be overkill for the light weight, but I wanted three anchor points on the ceiling like the original installation.


NOTE: The center track for the garage door is fairly level to begin with. This means that after I installed the isolators, the motor had to move up a few holes in the metal strap. That was easier than cutting the strap metal.

To mount the isolators, I used “hanger bolts” to replace the lag bolts that originally held the metal straps to the ceiling. Hanger bolts don’t have a head. Instead, they have a wood screw side for anchoring to wood beams, and a machine screw side to accept nuts. In order to drive them into the ceiling (into the existing holes from the current lag bolts), I used the two-nut method (a jam nut and a regular nut tightened together). I used 5/16 inch bolts because that is what was currently installed in the ceiling beam. The current lag bolts were 2 inches long, so I used 3 inch long hanger bolts to leave some bolt hanging down from the ceiling. See the pic below.


They do make a special driver made just for the purpose of installing hanger bolts, but such a driver only works to install, not to remove, so it has a very limited purpose. It is difficult to remove a hanger bolt but the two-nut method is usually used for that also. The next picture shows the whole thing installed. I used a nylon locking nut on the top of the isolator housing (shown on the bolt pic above), and another nylon locking nut and washer to hold the housing rigidly tight to the ceiling. The purpose of the top nut was the regulate how much of the hanger bolt was allowed inside the housing. As you can see below, there isn’t much room for the top and bottom bolts to coexist without touching, but they must not touch. I ended up with about a 1/4 inch gap between the two bolts. You can see the gap between the ceiling and the two other units in the pic below.

Installed iso hang

KEY IDEA: The concept of the hanging isolator is to put vibrations from a hanging device into the jiggly and squishy neoprene. The jiggling action uses up the energy and keeps it from being directly transmitted to the rigid metal above it. If the bottom bolt were tight against the bottom of the unit, a lot more energy would be transferred to the housing and then to the ceiling beam and that would defeat the purpose of the isolator.

I set a ladder and a box underneath the motor to keep it from sagging very far while I worked on the straps. The weight of the opener motor and track was apx 20-25lbs. I used another ladder to move around and work. This picture shows the installed isolators with the ladder under the motor unit. I had to have an additional box to keep the track from sagging and possibly bending.


The next picture shows the order of assembly of the top pieces:
(DO NOT assemble this way prior to install. It all has to be installed piece by piece on the ceiling. This is just to show how it is all assembled.)
1. hanger bolt
2. nylon locking nut (need pliers to hold wood screw part while installing nut)
3. isolator housing
4. metal washer (optional)
5. nylon locking nut
6. lower bolt
7. nylon locking nut
8. neoprene washer
9. 5/16 metal “fender” washer
10. the neoprene isolator (built into the housing)
11. neoprene washer at head of lower bolt


Any place where I was going to have loose metal touching metal, I put in a neoprene washer to absorb energy that would otherwise become a rattling sound.There is about a 1/4 inch gap between the ends of the bolts. Plenty for the amount of jiggling of this motor.

Mason 2LVR8 from $9 x7 ($63)
Hanger bolts x3
Machine bolts x3 (I chose 2 1/2 inch)
standard 5/16 metal washers x3
5/16 fender washers x3
3/8 (fit better) neoprene washers x6
5/16 nylon locking nuts x9
(I estimate the various little parts cost around $12)


adjustable wrench, ratcheting crescent wrench, vise grips or pliers, impact driver and impact sockets, ear protection when using impact driver

The impact driver is handy for installing the hanger bolts. It is very quick, but does make a racket. The nice part is that there is no torque on the handle like there is with a standard drill motor. But a wrench or a socket driver can insert the hanger bolts also, it just takes longer.

I remounted the motor to the metal straps and used a level on the center track to verify that I had it pretty close to level.

strap diff

I measured the sound before and after the install using both a Realistic brand sound pressure meter, and an Android app called Spectrum Analyzer. Unfortunately, I forgot to squish the range of the Spectrum Analyzer to show the range of human hearing (~1KH to 4KHz), so I only got the default low end.



Overall it shows about a 20dB drop. The other sound meter before registered about 66dB in the room above the opener. After the isolator install there wasn’t enough noise to even move the meter (range was about 60-80). There is an odd constant peak at about 130 Hz. Not sure what that is.

In human reaction terms that is “WOW! The noise is almost totally gone!” Originally, I was going to install these on the door tracks also, and install pads where the tracks attach to the garage wall. But after the decrease in noise, that became unnecessary.

This project is likely beyond the ability of many homeowners, but could be installed by a contractor easily. It did take several hours because I was still working out the details as I was going.

I don’t think that there will be any issue with the motor not having a rigid mount. It seems to operate normally and with very little visible jiggling except when it first starts or when it is about to finish.

I also did this fix at another house, but felt that it would also benefit from having the door raceways muffled a bit more. Sadly, I didn’t take any sound readings on this before starting the project.

I used Sorbothane bushings and washers, since I already had some. The object here is to float the perforated metal between the jiggly material. The top part is like a washer, but has a middle insert. I had to drill out the hole in the metal to 1/2 inch first so that the insert would fit. Then I used a lag bolt that is 1/2 inch longer than was originally installed, so that I could get the same grip while leaving a bit of slack so the metal could vibrate without being tightly pressed against the beam (the white area at the top of the picture). This should help absorb a bit more of the vibration without transferring it directly through the metal parts to the beam. I may leave a bit more slack than is shown in the picture. If the material is too squished, then it loses its ability to jiggle and becomes pointless. I used a washer under the material to help hold it in place. Sorbothane is easily torn by metal edges or screws.

sorbothane at 909

But now that we are selling the house, I’m going to remove the isolators and reinstall the lag screws. If anything were to go wrong with the unit, the blame would be on me regardless of whether or not that blame were real, and I can’t afford that. But that gives me more isolators to use in my other house where we have two garage door openers.