I like your changes, especially the ability to save to memory and use a new offset value when changing frequency.
The Oscar frequency pages are really handy as well!
May I suggest the ability to save the memory data to either disk or to one or more of the preset buttons?
Thanks for all the hard work you put in to this software, I'm sure it is appreciated by many people.
The Oscar 100 button will help a lot of newbies I'm sure and is very convenient.
I'm getting an reading MER of 7.2 compared with 6 on version 0.8 - is their a different calibration or is the performance enhanced in some way?
73 Nigel G8AYC.
With V0.9 the received MER is much lower than with V0.8s and signals are much harder to lock.
Is this release supposed to work with the V1 board?
There are a number of stations reporting the same problem on the BATC Facebook group.
73s thanks for all the hard work put into this software.
The beacon is 8.9dB MER on a 1.0m dish. I've never seen it that strong - it's usually 8.5dB. The lack of an LNA in the 4335 doesn't seem to matter. They all give 8dB MER on the beacon with 08s.
Readings are also all the same with all boards on broadcast, receiving 12073H, SR27500, DVB-S2 at 11.0dB MER. I do notice that DVB-S broadcast signals give an MER about 1.5dB lower with 09b89 compared to 08s. I haven't seen enough DVB-S signals on QO-100 to check.
This old laptop frequently goes slow, so I'll reserve judgement on lock times.
Unable to see D number but ok on expert page
Probably need a wider monitor.
Tried v9 beta 8-9 no good
I need a new computer and monitor.
I think the attached pictures may have come out in wrong order.
- 20190507_154447.jpg (509.73 KiB) Viewed 814 times
- 20190507_153615.jpg (686.09 KiB) Viewed 814 times
It worked superbly on Sunday for my first ever DATV QSO.
I must have had bad reception conditions when first trying it.
73s Keep up the good work, thanks for the software.
I have been testing Minitioune v0.9beta8_9 with a Serit NIM. All good, except one minor issue:
When receiving H265 720p (1280x720 pixels) is displays that the received image is 1280x960 and sizes it for 4:3 in the viewing window. If I send the stream to VLC it correctly detects 1280x720 and displays at 16:9.
The transmitted signal comes from GStreamer piped through ffmpeg (to add service metadata), and ffmpeg reports that it is sending 1280x720.
It may be that some vital metadata is missing on this H265 stream, or it may be the MiniTioune/Windows 10 combination. Has anyone else seen this behaviour? It happens that same at 720x406 (detects as 720x540), but 1920x1080 is detected and displayed correctly.