Skinny Posted May 23, 2017 Posted May 23, 2017 Hi, I have: Win 10 64 bit after last update Windows 10 Creators Update http://www.DVBViewer.com stopped to show any programs (dvb-c) (elier worked fine). My dvb-c stick is: http://www.gearbest.com/tv-box-mini-pc/pp_188368.html I took drivers from: http://www.astrometa.com.tw/integrated_en.html?rnd=0.8584378458326747 I tried drivers : https://www.dropbox.com/s/ffckhetzp3vmjio/AMDVBT2_Setup_170427.exe?dl=0 and https://www.dropbox.com/s/g7ckkst7gib86sc/AMDVBC_Setup_170427.exe?dl=0 and still can't find any programs on program from producer https://www.dropbox.com/s/cy823cnthstyg8e/TVR_DVBC_Setup_V4.7.9.exe?dl=0 works fine Where is the problem ? support.zip Quote
Tony Posted May 24, 2017 Posted May 24, 2017 (edited) Are you sure? Creators Update has blocked many previously functional programs, but in this case, it is probably wrong...According to my experience, DVBViewer detects the Astrometa usb stick only as a DVB-T/T2 receiver (or I can not). The driver of this patch is written in a strange way, the cable driver and the terrestrial driver vary very little, but DVBViewer does not know it. Only software delivered by the manufacturer can receive DVB-C. Edited May 24, 2017 by Tony Quote
Skinny Posted May 26, 2017 Author Posted May 26, 2017 Before Windows update DVBViewer & Astrometa worked fine with DVB-C, I still have no idea what to do Quote
Griga Posted May 26, 2017 Posted May 26, 2017 Maybe this helps: http://www.dvbviewer.tv/forum/topic/59399-no-playback/?do=findComment&comment=462963 Quote
cismondo Posted May 31, 2017 Posted May 31, 2017 (edited) Try these drivers: 160614 The new ones are faulty and don't install. They only seem to do so when using the *.exe. Edited May 31, 2017 by cismondo Quote
Skinny Posted June 3, 2017 Author Posted June 3, 2017 cismondo, installing old drivers doesn't help Quote
Skinny Posted July 18, 2017 Author Posted July 18, 2017 after update DVBViewer 6.0.3 still doesn't work Is there any help here ? Quote
Tjod Posted July 18, 2017 Posted July 18, 2017 After every driver related change, you should run "Scan Device" (Options > Hardware). Try the DVBViewer without RS. Stop the RS disable the RTSP device in Options > Hardware an set the TV card to normal. Start the DVBViewer vis Start Menu > DVBViewer Pro (Debug Mode) And then try a channel scan and post a new support.zip But I assume if "Scan Device" doesn't help only other driver can help. If the driver doesn't work with the Windows version it can't be fixed inside the DVBViewer. Quote
Skinny Posted July 18, 2017 Author Posted July 18, 2017 still doesn't work, I see proper drivers Options > Hardware, but I can't find any dvb-c programs support.zip Quote
Tjod Posted July 18, 2017 Posted July 18, 2017 From the settings everything looks OK. And in the log are no errors. The driver from the stick simply doesn't return any data. As if the antenna cable is not attached. So nothing which can be changed by the DVBViewer. If antenna cable and DVB-C stick are OK the driver/Windows Version combination is the problem. So only a new/changed driver for the DVB-C stick (or a other Windows version) can change the situation. Quote
mitsu Posted October 27, 2017 Posted October 27, 2017 Skinny, have you found a solution to this? I just changed to cable network and I have two of these devices. Quote
mitsu Posted October 29, 2017 Posted October 29, 2017 I got cable channels working with Astrometa. I first uninstalled all Astrometa SW and cleaned the installation directories. Then I installed the older cable driver version AMDVBC_Setup_160614. For some reason the new driver does not want to install correctly in Windows 10. Quote
ShK Posted February 19, 2018 Posted February 19, 2018 I bought this Astrometa USB DVB-T/T2/C + FM + DAB/DAB+ (VID_15F4_PID_0131) cheaply from eBay and faced the same issue. I find out that the latest driver works on Win10x64, but you need to modify Astrometa driver's AMDVBT2BDA.inf -file: HKR,"Parameters",DVBCMode,0x10001,0 <----- DVB-T (default) HKR,"Parameters",DVBCMode,0x10001,1 <----- DVB-C Because driver is now modified you need to disable Win10 Driver Signature Verification. Otherwise it will give the error code, and does not work. Quote
rvs Posted March 25, 2018 Posted March 25, 2018 (edited) I did a program a few years ago. You can find some information and links here. I do a new version here. Change : - Reset the device in an another thread - Can stay in systray - Target the .net framework 4.0, which is now the most common. Requires to start in Administrator because it read and write the registry and reset the device. It's provided as is. Only test in my PCs. Edited March 25, 2018 by rvs Add images 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.