Please use this thread to submit bugs and glitches and the status of the fixes.
GEOSATpro supports you! Thank you for supporting GEOSATpro!
GEOSATpro supports you! Thank you for supporting GEOSATpro!
Last edited by a moderator:
as from my other thread
I noticed when deleting files on the DVR you have to do them one at a time. So you find the file, hit yellow button to delete and it then kicks you back to the channel you were on.
Any way to have it where you can delete more than one file at a time?
bug...
Scanned in the religious audio only feeds on 87W C-Band
(4043 H 3910)
only logs one audio pid. Hit audio button and only shows one (should be about 25 different ones...each receiver shows different amounts due to software capacity)
good thing is it scans more than 4 PIDs so all the options are there
the bad is it may take 2 or 3 manual scans![]()
Wow. That kind of response is not something you'd get from your everyday designed-built-programmed-in-Korea generic box.We are analyzing the transponder to determine if the tables are configured following the DVB standards. The tables might be non-compliant to the DVB standards like the 139W audio services. We should be able to correct.
SO true....Wow. That kind of response is not something you'd get from your everyday designed-built-programmed-in-Korea generic box.
When time shift is enabled I can no longer view the detailed information on a channel.
We will look into a solution. For now set up the C and KU satellites using the separate satellite positions and program the inline switch.Set up the antenna tab with Universal LNB 5150/10750 as I have a DMX741. When I try to do a normal blind scan for C band the pop up menu asks for a Ku frequency span to scan.
Using DiSEqC 1.2 or USALS? If DiSEqC 1.2, did you aim the dish for each satellite then save each satellite in a motor position before starting the scan?On a side note when the "moving dish" indicator was active for the scan it did not move the dish from its prior position. I did it manually and restarted the scan.
I dont think that is a bug. I noted that in the review
http://www.satelliteguys.us/fta-mpeg2-equipment-reviews/286849-geosatpro-micro-hd.html#post2895155
primestar31 said:My microHD was set to the default video setting 1080p with the firmware that was shipped with it. My tv set handles 720p natively and 1080i with hdmi. I got a signal right away on my tv regardless, and was able to use it. I do though suggest the default to be set at say 480p, and then it'll even support OLD plasma's with component, if they use an HDMI to Component adapter.
Then again, IF this setting also controls the composite output, then it definitely would be best to set it to 480i natively. Otherwise people going composite with an OLD tv set won't get anything.
One last thing: when this setting is changed, PLEASE have a confirmation screen to click an "OK - this works" (ala Windows), OR have it time out in say 20 seconds and go back to the default! When I changed it to 1080i, it blanked out for so long, I though I was screwed. It then finally came back up. So, I'm not sure if my tv was just taking it's sweet time hand-shaking, or if that time-out feature already exists.