- Freestreamcoder.png (216.88 KiB) Viewed 265 times
portsdown 4
Re: portsdown 4
Hi Dave C (G8DKQ)
Can you offer any more suggestions for Joe? he has a PD4 with a pluto.
Ignoring all that has gone on before re OBS, it is taking 30 seconds before a transmission to start AND stop after pressing the TX button on the PD4.
The SD card on the PD4 was from BATC and the pluto has the correct firmware for the PD4 installed.
I asked Joe to check for updates and ensure the PD4 is the latest version, also that the pluto is plugged into a blue USB3 port on Pi.4
He still has the 30 second lag which is fundamentally wrong.
My ONLY thoughts after all of this was for Joe to build a new SD card for PD4 and try again.
Once the PD4 is working his freezing issues can be readressed.
Just wondered if you might have any further thoughts on what might cause a 30 Second delay between going into and coming out of transmit to help Joe 9H1GT?
Thanks and 73
Nick
Can you offer any more suggestions for Joe? he has a PD4 with a pluto.
Ignoring all that has gone on before re OBS, it is taking 30 seconds before a transmission to start AND stop after pressing the TX button on the PD4.
The SD card on the PD4 was from BATC and the pluto has the correct firmware for the PD4 installed.
I asked Joe to check for updates and ensure the PD4 is the latest version, also that the pluto is plugged into a blue USB3 port on Pi.4
He still has the 30 second lag which is fundamentally wrong.
My ONLY thoughts after all of this was for Joe to build a new SD card for PD4 and try again.
Once the PD4 is working his freezing issues can be readressed.
Just wondered if you might have any further thoughts on what might cause a 30 Second delay between going into and coming out of transmit to help Joe 9H1GT?
Thanks and 73
Nick
Re: portsdown 4
Not sure, there should be a few seconds of delay, but not 30 seconds. I assume the correct firmware in the Pluto etc. Perhaps the PD4 is being asked to do too much? If you stick to the recommended hardware and firmware, it should just work. Back to basics. C920, audio dongle, 333ks 2/3FED what happens?
I was wondering about the image in the picture above. Clearly this is not for a PD4 but controlling the Pluto directly from the PC. I assume Joe is using only the PD4 and doesn't have a PC in the mix. If he is using the IPTS and still having issues, I suspect the data rate is too high. So for 2/3 it should be less than 440kb/s. Secondly, if he is able to generate a transport stream directly, and has a Pluto, why is there a PD4 there at all? It is not required. Evariste's 0303 firmware, when set to DATV mode, can do all the work already.
Mike
Re: portsdown 4
Hi
IPTS IN mode is only supported for H264 (not H265) the Pluto. H265 IPTS IN only works with the LimeSDR.
Long TX selection/deselection delays when using H264 IPTS IN and the Pluto generally suggest that the actual input bitrate is too high. Many encoders do not stick to the bitrate that you set.
There is no satisfactory way to get HDMI input into a Portsdown 4 for transmission; it works on the monitor screen, but that is because it does not need video encoding/compression.
If you have a PC running, why not use DATV Easy to directly drive the Pluto? Portsdown 4 was designed as a get-you-started and portable capability for terrestrial DATV operation. If you are working from a fixed location (particularly for QO-100) I would recommend a PC-based solution for transmit.
Dave, G8GKQ
IPTS IN mode is only supported for H264 (not H265) the Pluto. H265 IPTS IN only works with the LimeSDR.
Long TX selection/deselection delays when using H264 IPTS IN and the Pluto generally suggest that the actual input bitrate is too high. Many encoders do not stick to the bitrate that you set.
There is no satisfactory way to get HDMI input into a Portsdown 4 for transmission; it works on the monitor screen, but that is because it does not need video encoding/compression.
If you have a PC running, why not use DATV Easy to directly drive the Pluto? Portsdown 4 was designed as a get-you-started and portable capability for terrestrial DATV operation. If you are working from a fixed location (particularly for QO-100) I would recommend a PC-based solution for transmit.
Dave, G8GKQ
Re: portsdown 4
Sorry for the confusion I use a Lime and was trying to help joe initially with his freezing.
Talking to him it transpired that a long delay to transmit I assumed was 2 or 3 seconds (normal) but was actually 30 seconds to transmit AND to revert to receive.
I then tried to direct Joe to focus on that issue which is clearly not right as it might also be masking many other things.
Clearly there is a fault somewhere.
My first thoughts were pluto Firmware and I got Joe to confirm this was correct.
If a fresh SD card still produces the same 30 second delay, my only thoughts were hardware.
Just trying to help Joe in Malta get his PD4 working properly BEFORE re addressing any other issues that may go away if the 30 second TX?RX fault is resolved.
73
Nick
Talking to him it transpired that a long delay to transmit I assumed was 2 or 3 seconds (normal) but was actually 30 seconds to transmit AND to revert to receive.
I then tried to direct Joe to focus on that issue which is clearly not right as it might also be masking many other things.
Clearly there is a fault somewhere.
My first thoughts were pluto Firmware and I got Joe to confirm this was correct.
If a fresh SD card still produces the same 30 second delay, my only thoughts were hardware.
Just trying to help Joe in Malta get his PD4 working properly BEFORE re addressing any other issues that may go away if the 30 second TX?RX fault is resolved.
73
Nick