Page 1 of 1
Portsdown No H264 Operation - Filter Modulator Board
Posted: Mon Feb 25, 2019 3:03 pm
by M0SKM
In conversation with Arthur G4CPE he mentioned there was no H264 operation since a recent update. He thought the card may be corrupted and fitted a spare; this restored H264 working. When he subsequently updated the spare that also failed to transmit H264. Arthur said on an analyser it looks like no modulation is happening.
In order to confirm hardware wasn't to blame I located and blew the dust off mine; it worked great on the old software on Portsdown and Ugly modes. Since I have other means of generating the signals I updated mine to the latest software and now that doesn't produce H264 either.
Is anyone else able to confirm whether they have a problem?
73 Steve
Re: Portsdown No H264 Operation - Filter Modulator Board
Posted: Mon Feb 25, 2019 10:28 pm
by G8GKQ
Steve, Arthur
I have just tested H264 on my Portsdown (with filter-modulator board) and can't find anything wrong. I also forced an update and it still worked. I will try building a new card tomorrow to see if I can find anything that might be causing your problems.
In the meantime, please could you list all the settings on Menu 1 of your Portsdown (or post a photo) so that I can try to reproduce your exact problem. Also please tell me what software version you are running (from Menu 2, Info)
Thanks
Dave
Re: Portsdown No H264 Operation - Filter Modulator Board
Posted: Mon Feb 25, 2019 11:02 pm
by M0SKM
Hi Dave,
These from mine; Arthur might post in the morning.
Steve

- 20190225_223517.jpg (578.75 KiB) Viewed 4035 times

- 20190225_223543.jpg (490.33 KiB) Viewed 4035 times

- 20190225_224216.jpg (215 KiB) Viewed 4035 times
Re: Portsdown No H264 Operation - Filter Modulator Board
Posted: Tue Feb 26, 2019 9:06 am
by M0DHP
Hi Steve
Does changing Audio from "Auto" to "EasyCap" or "None" make a difference?
73
Ray M0DHP
Re: Portsdown No H264 Operation - Filter Modulator Board
Posted: Tue Feb 26, 2019 9:23 am
by M0SKM
Hi Ray,
Changes in audio settings make no difference.
73
Re: Portsdown No H264 Operation - Filter Modulator Board
Posted: Tue Feb 26, 2019 12:56 pm
by G8GKQ
Hi Arthur and Steve
I can't work out what might have gone wrong here, but think that the safest thing would be for you to reinstall the H264 encoder. To do this, you will need to go to the command line through the console, delete some files, then reboot and then force an update.
So, log on to the console (by SSH), select "Shutdown" and then "Exit to Linux". The copy and paste these 4 lines in, one at a time (right click in the terminal window to paste):
Code: Select all
rm -rf /home/pi/avc2ts/libmpegts
rm -rf /home/pi/avc2ts/fdk-aac
rm -rf /home/pi/avc2ts/libyuv
sudo reboot now
After the reboot, go to Menu 3 on the touchscreen, "Check for Update" and "Force Update".
Hopefully that should sort it. Please let me know.
Dave
Re: Portsdown No H264 Operation - Filter Modulator Board
Posted: Tue Feb 26, 2019 2:43 pm
by M0SKM
Hi Dave,
Just had a text from Arthur to say no change; which is exactly what I found.
Both these systems produced perfect H264 with the earlier software; no other parameters are changed.
73 Steve
Re: Portsdown No H264 Operation - Filter Modulator Board
Posted: Tue Feb 26, 2019 4:14 pm
by G8GKQ
Hi Steve
I don't know what else to suggest. Could one of you put one of the offending cards in the post to me and I will take a look at what has happened and send it back to you?
Thanks
Dave
Re: Portsdown No H264 Operation - Filter Modulator Board
Posted: Tue Feb 26, 2019 4:52 pm
by M0SKM
Dave,
There was a newly written card in the Pi which I use for my DTX1 TS Dock. I fitted that one to my Portsdown and H264 operation was restored.
Since then I formatted the card removed from the Portdown and rewrote it; it also works now.
All I can conclude is that our cards didn't like the update process on this occasion.
Arthur hasn't finished a rewrite yet but I'm guessing it will also work.
Thanks for your help.
Steve
Re: Portsdown No H264 Operation - Filter Modulator Board
Posted: Tue Feb 26, 2019 9:58 pm
by G8GKQ
Hi Steve
It sounds like one of the GitHub servers must have been down during the update. Unfortunately, the script is not failsafe.
Thanks for letting me know
Dave