Transmitter Software Capabilities and Issues (Jessie)
Re: Transmitter Software Capabilities and Issues
Hi All
There is a problem in the latest build that causes no transmission or streaming in MPEG-2 or streaming modes if you have no audio devices connected. I have a fix, but have run out of time to implement it properly. Rather than rush it out untested, I will publish it Tuesday evening.
So, if you haven't upgraded yet, I suggest you wait until I've published the fix.
Dave
There is a problem in the latest build that causes no transmission or streaming in MPEG-2 or streaming modes if you have no audio devices connected. I have a fix, but have run out of time to implement it properly. Rather than rush it out untested, I will publish it Tuesday evening.
So, if you haven't upgraded yet, I suggest you wait until I've published the fix.
Dave
Re: Transmitter Software Capabilities and Issues
Dave,
I did some quick tests on last version from today
Now caption is Ok in MPEG-2
Raspi cam is displayed "on the display" but depending on FEC settings (???) the cam display
takes one sixth of the screen with BATC logo displayed (for FEC 1/2, 2/3, 3/4) or the full size of the screen
(for FEC 5/6, 7/8)
Changing the parameters for the EasyCAP changes nothing
Even setting S-video mode (while entering in composite) and/or NTSC (while entering in PAL)
results on my side on a nice received picture (MiniTioune) so PAL/composite
Tested via menu and via console and even after a reboot with "wrong" parameters
73
Christian
I did some quick tests on last version from today
Now caption is Ok in MPEG-2
Raspi cam is displayed "on the display" but depending on FEC settings (???) the cam display
takes one sixth of the screen with BATC logo displayed (for FEC 1/2, 2/3, 3/4) or the full size of the screen
(for FEC 5/6, 7/8)
Changing the parameters for the EasyCAP changes nothing
Even setting S-video mode (while entering in composite) and/or NTSC (while entering in PAL)
results on my side on a nice received picture (MiniTioune) so PAL/composite
Tested via menu and via console and even after a reboot with "wrong" parameters
73
Christian
Re: Transmitter Software Capabilities and Issues
Hi Christian
Edited with a correct repsonse. Apologies, my previous response was incorrect.
The transmitted image size (in pixels) is reduced at lower video bitrates (= more FEC) to maintain acceptable performance. The image is thus smaller on the display. Details of the re-sizing here: https://wiki.batc.tv/Display_Resolutions
Dave
Edited with a correct repsonse. Apologies, my previous response was incorrect.
The transmitted image size (in pixels) is reduced at lower video bitrates (= more FEC) to maintain acceptable performance. The image is thus smaller on the display. Details of the re-sizing here: https://wiki.batc.tv/Display_Resolutions
Dave
Re: Transmitter Software Capabilities and Issues
New Software Release
I've just issued a new release 201707222. This is a minor update on 201707221 (issued 2 days ago) to correct the bugs that I had introduced with the audio source switching (reported by M0SKM and G0MJW - thanks guys!).
The behaviour of the audio switching is now explained here: https://wiki.batc.tv/Audio_Switching
I would suggest that all users upgrade to this release as soon as possible and report any problems here.
Dave, G8GKQ
I've just issued a new release 201707222. This is a minor update on 201707221 (issued 2 days ago) to correct the bugs that I had introduced with the audio source switching (reported by M0SKM and G0MJW - thanks guys!).
The behaviour of the audio switching is now explained here: https://wiki.batc.tv/Audio_Switching
I would suggest that all users upgrade to this release as soon as possible and report any problems here.
Dave, G8GKQ
Re: Transmitter Software Capabilities and Issues
Hi, just wondered if anyone has the same problem as I do regarding MPEG2 and MPEG4? Transmitting MPEG2 no sound or indication of MPEG2 on Minitoune unless I tick the low SR button, likewise when switching back to MPEG4 nothing unless I again tick Low SR?
Re: Transmitter Software Capabilities and Issues
Hi Richard
You should use the low SR button below 2MS.
I suspect if you selected autopid (top right) when switching from MPEG-2 to MPEG-4 you would not need to tick low SR. You have to prompt MiniTioune to rescan the PIDs when the incoming PIDs change (the audio PID changes between MPEG-2 and MPEG-4 on the Portsdown). Ticking/unticking Low SR also prompts a PID re-scan.
Neither set of software (Portsdown or MiniTioune) is perfect!!
Dave
You should use the low SR button below 2MS.
I suspect if you selected autopid (top right) when switching from MPEG-2 to MPEG-4 you would not need to tick low SR. You have to prompt MiniTioune to rescan the PIDs when the incoming PIDs change (the audio PID changes between MPEG-2 and MPEG-4 on the Portsdown). Ticking/unticking Low SR also prompts a PID re-scan.
Neither set of software (Portsdown or MiniTioune) is perfect!!
Dave
Re: Transmitter Software Capabilities and Issues
New Software Release
I've just issued a new release 201707311. It introduces 2 new features. You can select Menu 3 from Menu 2 of the touchscreen; the only new button on Menu 3 (so far) is an "Info" button, which puts up an information screen including the Portsdown software version, IP address and configuration. The other new feature is that on selection of "Vid Out" mode, the USB microphone audio is routed to the RPi audio output. This allows the use of the Portsdown to drive analogue transmitters with sound and video.
Other minor changes include the addition of the Grabby EasyCap to the sound switching logic, and a check to see that an RTL-SDR is connected before going into RX mode. This avoids the lock-up that would otherwise occur.
There is no urgent need to upgrade to this version unless you want to take advantage of the new features above.
Dave
I've just issued a new release 201707311. It introduces 2 new features. You can select Menu 3 from Menu 2 of the touchscreen; the only new button on Menu 3 (so far) is an "Info" button, which puts up an information screen including the Portsdown software version, IP address and configuration. The other new feature is that on selection of "Vid Out" mode, the USB microphone audio is routed to the RPi audio output. This allows the use of the Portsdown to drive analogue transmitters with sound and video.
Other minor changes include the addition of the Grabby EasyCap to the sound switching logic, and a check to see that an RTL-SDR is connected before going into RX mode. This avoids the lock-up that would otherwise occur.
There is no urgent need to upgrade to this version unless you want to take advantage of the new features above.
Dave
Re: Transmitter Software Capabilities and Issues
Thanks Dave,
Took me a while to see that little menu 3 in the bottom right. Is the touch screen source code available?
Mike
Edit - I have found it. Made a very subtle change to test I understood what I was doing.
Took me a while to see that little menu 3 in the bottom right. Is the touch screen source code available?
Mike
Edit - I have found it. Made a very subtle change to test I understood what I was doing.
Re: Transmitter Software Capabilities and Issues
Hi Mike
If you make a change to the touchscreen source, you'll need to recompile. I use this script to recompile and run the gui when I'm developing.
I would welcome any ideas or help with changes/improvements. I plan to restructure the Menu construction soon (as it is currently not scaleable) , but could really do with help with implementing my ideas list http://batc.org.uk/forum/viewtopic.php?f=103&t=5097 to fill in the blank buttons on Menu 3.
Dave
If you make a change to the touchscreen source, you'll need to recompile. I use this script to recompile and run the gui when I'm developing.
Code: Select all
# Compile rpidatv gui
cd /home/pi/rpidatv/src/gui
make clean
make
sudo make install
cd ../
cd /home/pi
reset
sudo killall fbcp >/dev/null 2>/dev/null
fbcp &
/home/pi/rpidatv/bin/rpidatvgui 1
Dave
Re: Transmitter Software Capabilities and Issues
Thanks Dave,
I will try to help but I have limited time and don't know a lot about gui programming in linux. As you can see, I worked out how to edit the buttons. More class based programming may help make it more scaleable but I think also it would help to split functions off into smaller chunks of code to make the project more managable.
I was thinking about adding a physical button functionality to overcome the problems some have been having with touch screens. A fairly simple two button interface, one to cycle through the items on the page, the other to select. Not as good as a touch screen but better than a broken one.
I will look at the to do list.
Mike
I will try to help but I have limited time and don't know a lot about gui programming in linux. As you can see, I worked out how to edit the buttons. More class based programming may help make it more scaleable but I think also it would help to split functions off into smaller chunks of code to make the project more managable.
I was thinking about adding a physical button functionality to overcome the problems some have been having with touch screens. A fairly simple two button interface, one to cycle through the items on the page, the other to select. Not as good as a touch screen but better than a broken one.
I will look at the to do list.
Mike