It could be a whole host of things from network issues to not detecting the stream. I assume these connections are all wired and not via WiFi.
Use wireshark to check the network traffic
Run a port scanner to check the ports are open
Make sure OBS is really sending UDP by receiving it with VLC
John, your 250 and 333 OBS scripts work fine, could you also share your 500ks script (basic.ini) in case you have that ?
I use OBS with yr scripts, ffmpeg with your settings in the .bat file, and tested it on th eportsdown using the IPTS viewer.
Btw, there is a 4 second delay between what I see on the OBS window on the PC and what the portsdown display shows
Thanks for your excellent explainations here !!
My comment is about 250K s/s but with 1/2 error correction. 3/4 worked fine from the start.
Using that on line table gives me a bitrate of 24750 but this was not working very well with ffmpeg.
I noticed that in the ffmpeg command window the actual bitrate was more like 27500 and so I tried that.
Success. I kept the FFVBitrate=149.
That took me days to find out so perhaps it would help someone else trying to send 250 K with 1/2?
I am seeking guidance with OBS streaming to ffmpeg and then to Portsdown2020.
My setup is as per Dave's sample ffmpeg scripts (and OBS profiles). I have one configuration for 250K s/s + 1/2, one with 250K + 3/4, and one with 333K + 3/4 (as supplied, unchanged).
I am using the pthreads ffmpeg as instructed. My PC is an i5 4 core (about 50% CPU load maximum, all video applications running).
The test setup involved checking the stream with the stream viewer in Portadown2020. All was fine - video looked good.
My problem came when I up-link to Eshail2 and view the down-link on my Minitiouner Pro. The video is mostly black and does not refresh. It stutters and can work for about 5s maximum.
I suspected that MT may not be showing my video so I also (as yet another test) streamed UDP to VLC. Again, no video in VLC.
I thought I would check my up-link and down-link so I switched OSB streaming and ffmpeg off, and went back to the simple Pi Cam (V2) input to Portsdown. H264.
That all works fine at 250K and 333K for both 1/2 and 3/4 FEC via Eshail2. So the RF up-link/down-link is OK.
Please can a) someone suggest a next course of action - I am unsure what to look at next, or b) is there a good stream checking application I may use (is this is the problem).
It may well be the way I set up OBS, of course. I am combining a web cam, a series of picture stills in a slide show, and a text scroll.
Please, any guidance where to look next? Could the PC be to slow to encode at the required frame rate for example?
ta, 73, Mike
Many thanks for replying. No that had occurred to me too - why do I not check the 'actual' modulated RF up-link low power output from Portsdown with MT Pro?
I will try that. I also have a Pluto here too, should I need to check the spectrum, but it looked nice and narrow on the Live Tune App I use.
I don't see any ffmpeg errors apart from at 250K s/s where I had to increase the bit rate from 24750 in order to remove these lines. See above...
I think I must have made a mistake yesterday.
Today, it does work with both the up-link RF from Portsdown and also via Eshail2.
My only concern is I may have not changed the FEC over on Portsdown from 250 to 333 perhaps?
Or the PA was getting over-heated?
I have to use about 60-90W here, approximately. Dish is 1.1m with POTY.
I can reduce that a bit if I strip out the extra coax to the POTY, the directional coupler and the RG402 onto the POTY as that wastes over 2dB. Its still on-going this project. As they tend to be.
So all is well, but a bit hot. PA shuts-down at 46C at present (I can adjust that).