u/spatula

The schedule is listing at 8:00 PM what's actually being shown at 9:00 PM for example. So the guide data is an hour early (or the station is showing everything an hour late).

This is for RetroTV, virtual channel 30.4, KMMC-LD physical channel 14, hosted by KDTS-LD in the San Francisco Bay market. Tuner ID 10A53FC5.

Kind of strange. It seems like they're following the Mountain time schedule, but doing it in Pacific time.

Edit: see my comment below; I think what's actually happening is the station is showing the east coast feed of RetroTV, so everything is actually 3 hours ahead, and what I thought I was seeing yesterday was an artifact of the program I was watching being shown twice a day, four hours apart, and I mistook one for the other.

Update to a post from about 9 months ago: https://www.reddit.com/r/Citrus/comments/1ohjufe/sudden_leaf_chlorosis_leaves_falling_off_branches/

Thank you again to everyone who gave me advice about my Dekopon. It was indeed a "bathtub of doom" situation, in which the lower roots were constantly being soaked with water/mud (partly from someone "helping" to water it) from poorly draining clay soil underneath well-draining citrus soil.

Because it hadn't been too long since it was originally planted, I was able to extract it back from its location and transplant it into a big pot with some fresh citrus soil into which I blended some extra perlite to help it drain really well. I also took the kind advice here about Dynomyco Spark, fish/kelp fertilizer, and Southern AG citrus fertilizer.

Now I have a super-happy Dekopon. It lost one of its big branches due to the root rot, but I'm "aiming" the opposite side south to try to encourage it to branch out in the other direction to balance it out some, with some success so far. It even has some blossoms coming now!

I also picked up a sad-looking, Shiranui from a local nursery that had suffered from some leaf miners and also needed a bigger pot and some fresh soil. That one has also turned around rapidly this summer and already has some tiny fruit growing on it. It gave us about 3 big, delicious fruit in February already.

It's much too late to try putting these in the ground for this year, and next year before I try to plant them, I'll have to figure out the whole drainage situation to avoid getting another "bathtub of doom" again.

https://preview.redd.it/fpzhi42d7geh1.jpg?width=4284&format=pjpg&auto=webp&s=5e21f1515acc50f610345ed462a80485e530ab0f

https://preview.redd.it/qx8hchqc8geh1.jpg?width=3024&format=pjpg&auto=webp&s=146e190387b7104b8607288c324d5b18ea1ea4a2

Example Tuner ID 10A53FC5. New channels on virtual channel 30 have popped up and have no guide data:

30.3 Heartland
30.4 Retro
30.5 Hasbro Legends

These are on physical channel 14, hosted by KDTS-LD.

I've posted occasionally about my years-long struggle to get our electrical utility to address their power-line QRM in my area, and I think I've mentioned the custom monitoring code I wrote to keep tabs on the problem. The code started out life as a pretty egregious hack by my own standards, held together with chewing gum and duct tape, and always intended as a throwaway script that basically worked.

After two years and hearing some interest from others, I sat down with Claude Code and did some significant refactoring to make it less of a code embarrassment.

This isn't for the technologically faint-of-heart: you'll have to be comfortable setting up a Python venv, installing requirements, editing a text configuration file, etc., but if you can follow instructions in a README there's a good chance of success.

So if you have a use for a power-line noise monitor, I invite you to check out the project at https://github.com/spatula75/n6ol-powerline-qrm-monitor . It wakes up once a minute, samples audio off your receiver, performs time-domain analysis and produces CSV data logs and PNG charts, optionally correlated with the weather at your QTH, optionally uploaded to your web server via ssh. If you want to see the kind of output it generates, you can see the live results at https://n6ol.us/noise/ .

Be sure to read through the README and follow the instructions especially regarding audio device selection, receiver settings, and level calibration.

I'm the only one who has used this so far, so it has been extensively tested only in my own environment. I'm happy to take PRs if you need to make tweaks to get it working for you, and I'm open to suggestions about improvements, especially around setup, which is admittedly fiddly at the moment. It's known to work in a Windows 11 64-bit environment on an inexpensive, outdated PC, with a Python 3.14 venv and an Elecraft KX3 feeding audio to the on-board sound card, monitoring 60 Hz power-lines. (It should work with 50 Hz if you edit the configuration and change the '120' to a '100'.)

(Note: Claude was mainly used to follow my instructions on how I wanted the existing hacky code restructured; the only thing I let it generate on its own was a test suite and the README.md. Thus if you were chomping at the bit to burp "hurr durr AI slop" at me, your comment is valid only regarding the parts of the code that other people aren't going to use.)

today's PG&E noise chart so far