Jump to content

Wiedergabe gestört nach Windows 10 Update auf 2004


FW43412

Recommended Posts

Hallo,

Habe das Problem durch hartnäckigen Wiederholen selbst lösen können. Ich habe den Treiber 5.2020.406.38260 vom 16.09.20 nochmals heruntergeladen, da ich die Mitteilung bei Hauppauge für diesen Treiber gelesen hatte, dass Fehlbelegung des Treiber unter Windows im Geräte Manger behoben sei, was bei mir immer der Fall war, nach den Neustart. Dieses mal kam auch der prompt Hardware erkannt, was die letzten Male nicht kam. Ich lies auch einen neuen Sendersuchlauf laufen, mit Erfolg.

Link to comment

I got same problem but even with IPTV streams, stutering sound or picture, using LAV and this works fine in any app except DVBViewer, happens only after 2004 update ..

Link to comment

I double click hvr930c 2020 driver setup, it extract in c program files 86/hauppauge/Win10 Drivers/5.2020.0406.38260/hvr900

 

I take only these files from that folder( emAudio64,emBDA64,emOEM64,emPRP,emPRP64) and paste them inside c program files 86/terratec/Cinergy HTC USB XS HD (64 Bit)/Cinergy_HTC_USB_XS

then open device manager, and install manually from there.

 

Or revert windows 10 version.

Link to comment
  • 1 month later...

Having a Cinergy HTC USB XS HD stick and using it for cable TV, I have succeeded to install and use it on Windows 10 20H2 (64bit) after some bit of trial and error, as follows.

 

The first notable attempt, but with partial success, was the Hauppauge method as mentioned earlier: I copied someplace the original Cinergy drivers from their default installed location (under Program Files (x86)\TERRATEC\), then uninstalled the driver via Control Panel / Programs and Features, then “installed” the 5.2020.0406.38260 driver from Hauppauge only to obtain its files, then copied the Hauppauge files emAudio64.sys, emBDA64.sys, emOEM64.sys, emPRP64.ax and emPRP.ax (this one is for SysWOW64 directory) over the previously saved Cinergy files (replacing them), then installed the Cinergy HTC device in Device Manager by pointing to these new combined drivers.

 

Result: the Cinergy HTC stick worked well, but only in TV/DVB-C mode; by switching to external composite or S-Video, the computer crashed with BSOD at each attempt. Later I replaced also the emMON.exe file with the one from Hauppauge (by renaming the hcwemmon.exe to emMON.exe), but there were no difference.

 

Because of the BSOD occurrences, I searched further for some other variants until I ended on this one that worked well for me: I took the eMPIA USB 2861 Device Driver 5.2015.521.0 for Windows 8.1, I copied all its files over the previous mixed driver files from above (although for 64bit system only the emBDA64.sys, emOEM64.sys, emPRP64.ax and emPRP.ax are useful) while keeping the emAudio64.sys and emMON.exe from Hauppauge version (these ones are not present in the eMPIA drivers), then installed the Cinergy HTC device in Device Manager by pointing to these new combined drivers.

 

Result: now the Cinergy HTC stick works well under all tested [1] circumstances.

 

Before each attempt I uninstalled the Cinergy HTC driversr (and restarted the system if/when requested). Except for the very first install of the Cinergy original drivers (Windows 10 1909 version at that time), I installed/uninstalled all tested drivers using the device properties under Device Manager.

 

For all tests I used either TerraTec Home Cinema Elgato 6.32.03 build or Geniatech 6.48.02 build, but also DVBViewer TerraTec Edition. As far as I guess (?) DVBViewer cannot switch to external inputs, this being something device dependent.

 

After all these tests I reinstalled the system clean (using MediaCreationTool20H2 tool) and installed the Cinergy HTC directly with my cocktail drivers, which worked well at first attempt.

 

This is my cocktail if anyone else is interested (but it can also be built relatively easy following the above suggestions). Included are also the x86 files, but with no particular reason (I don't have any Windows 10 20H2 32bit version to check the patch and I also have no idea if the 32bit version of the 2004/20H2 has the same problems with DVB as the 64bit one).

 

Of course, the system will protest at driver install time because of the unsigned drivers, but in this particular case it can be easily ignored.

 

[1] However, I did not tried its analog TV and DVB-T modes.

Link to comment
  • 2 weeks later...

Super, vielen Dank euch allen!

 

Habe das selbe Problem mit meiner Terratec Cinergy HTC XS HD, und war zunächst sehr verunsichert wo die Ursache zu suchen ist (hatte den Stick ewig nicht mehr benutzt, ebenso DVBViewer, zusätzlich völlig neue Windows Version und dazu auch noch eine neue Wohnung mit neuem DVB-C Anschluss).

 

Die Lösung hier im Thread hat dann aber auf anhieb funktioniert! Danke auch an @secaricafür das Zusammenpacken eines funktionierenden Treibers, hat mir nochmal einiges an Aufwand erspart.

 

Schade, dass einwandfrei funktionierende Hardware so schnell durch ein Softwareupdate beinhahe in Elektronikschrott verwandelt wird...

Link to comment
  • 1 month later...

Ich habe für meinen PCTV 292e nach längerem Probieren unter Windows 10 Version 2004 Erfolg gehabt, indem ich vom USB-2-Port den Stick auf einen USB-3-Port gesteckt habe und den Treiber

 

Dateiname: driver_hcwembda_5_2017_0911_35255_win7_win8.zip  Version: 5.2017.0911.35255

 

installiert habe. Mir fehlt jetzt als einziger Sender der BR-München, alle anderen Sender funktionieren damit sogar z. Teil mit neuerdings 100%-Anzeige anstelle von 71%.

Also es besteht noch Hoffnung, dass mein 292e-triple-stick doch noch nicht entsorgt werden muss!

Link to comment
  • 3 months later...
Am 23.9.2020 um 13:59 schrieb einmorgen:

Ich hatte ebenfalls die beschriebenen Probleme. Ich habe hier und ein einem anderen Forum gelesen, dass ein aktuelle Treiber von Hauppauge Abhilfe schaffen konnte.  

Mein Elgato eyetv hybrid TV Stick von Januar 2011 läuft jetzt mit einem Treiber aus der ZIP Datei von Hauppauge. So bin ich vorgegangen:

Datei herunterladen und alle Dateien extrahieren.
http://www.hauppauge.de/files/drivers/hcwembda/driver_hcwembda_5_2019_0221_37057_win10.zip

Im Gerätemanager:
1) Treiber von Eyetv Hybrid im Gerätemanager deinstallieren,
   Treiber vom Datenträger löschen lassen
2) Nicht booten
3) Treiber aktualisieren:
   Navigieren zu c:\Users\<user>\Downloads\driver_hcwembda_5_2019_0221_37057_win10\64
   "Weiter" wählen
   Treiber für PCTV460 auswählen
   Installieren lassen
   Im Gerätemanager erscheint das Symbol "PCTV460e"
   
Eyetv hybrid TV Stick ausstecken und wieder einstecken

Eyetv4 Windows Anwendung starten:
1) Hardware "PCTV 290e/460e BDA 2875 TV Tuner C" auswählen
2) Fernsehprogramm wählen -> Funktioniert (SD und HD)

Hi Einmorgen,

 

ich habe das gleiche Problem wie so viele hier im Forum, auch den eyetv hybrid TV Stick wie du, nur leider hat deine Anleitung bei mir bisher nicht geholfen weil ich sie nicht wirklich nachvollziehen kann. Könntest du es nochmal Schritt für Schritt erklären?

Vor allem 2 Fragen zu deiner Anleitung:
1) Wo Klicke ich auf "Treiber aktualisieren" - nachdem ich das Gerät im Gerätemanager deinstalliert habe, erscheint es hier ja nicht mehr?

2) Wo/wie kannst du den Treiber für PCTV460 auswählen?

Wenn ich den Pfad wie beschrieben auswähle, findet Windows nichts und ich kann auch nichts auswählen.

 

Wäre super, wenn du mir hierbai helfen könntest!

 

Danke im Voraus

Link to comment
  • 2 years later...
On 11/29/2020 at 10:12 PM, secarica said:

Having a Cinergy HTC USB XS HD stick and using it for cable TV, I have succeeded to install and use it on Windows 10 20H2 (64bit) after some bit of trial and error, as follows.

 

The first notable attempt, but with partial success, was the Hauppauge method as mentioned earlier: I copied someplace the original Cinergy drivers from their default installed location (under Program Files (x86)\TERRATEC\), then uninstalled the driver via Control Panel / Programs and Features, then “installed” the 5.2020.0406.38260 driver from Hauppauge only to obtain its files, then copied the Hauppauge files emAudio64.sys, emBDA64.sys, emOEM64.sys, emPRP64.ax and emPRP.ax (this one is for SysWOW64 directory) over the previously saved Cinergy files (replacing them), then installed the Cinergy HTC device in Device Manager by pointing to these new combined drivers.

 

Result: the Cinergy HTC stick worked well, but only in TV/DVB-C mode; by switching to external composite or S-Video, the computer crashed with BSOD at each attempt. Later I replaced also the emMON.exe file with the one from Hauppauge (by renaming the hcwemmon.exe to emMON.exe), but there were no difference.

 

Because of the BSOD occurrences, I searched further for some other variants until I ended on this one that worked well for me: I took the eMPIA USB 2861 Device Driver 5.2015.521.0 for Windows 8.1, I copied all its files over the previous mixed driver files from above (although for 64bit system only the emBDA64.sys, emOEM64.sys, emPRP64.ax and emPRP.ax are useful) while keeping the emAudio64.sys and emMON.exe from Hauppauge version (these ones are not present in the eMPIA drivers), then installed the Cinergy HTC device in Device Manager by pointing to these new combined drivers.

 

Result: now the Cinergy HTC stick works well under all tested [1] circumstances.

 

Before each attempt I uninstalled the Cinergy HTC driversr (and restarted the system if/when requested). Except for the very first install of the Cinergy original drivers (Windows 10 1909 version at that time), I installed/uninstalled all tested drivers using the device properties under Device Manager.

 

For all tests I used either TerraTec Home Cinema Elgato 6.32.03 build or Geniatech 6.48.02 build, but also DVBViewer TerraTec Edition. As far as I guess (?) DVBViewer cannot switch to external inputs, this being something device dependent.

 

After all these tests I reinstalled the system clean (using MediaCreationTool20H2 tool) and installed the Cinergy HTC directly with my cocktail drivers, which worked well at first attempt.

 

This is my cocktail if anyone else is interested (but it can also be built relatively easy following the above suggestions). Included are also the x86 files, but with no particular reason (I don't have any Windows 10 20H2 32bit version to check the patch and I also have no idea if the 32bit version of the 2004/20H2 has the same problems with DVB as the 64bit one).

 

Of course, the system will protest at driver install time because of the unsigned drivers, but in this particular case it can be easily ignored.

 

[1] However, I did not tried its analog TV and DVB-T modes.

 

I am reviving a quite old thread, but I wanted to use my Terratec Cinergy HTC USB XS HD stick with Windows 10 22H2. I used these instructions with the "cocktail" drivers and DVB-T works great, DVB-C also great, Analog TV also great. Thanks secarica!!

 

The only problem is with Analogue Capture. Used multiple pieces of software (OBS, ChrisTV, Terratec Home Cinema), yet no matter what I do I get no sound from the Line-in. I open Windows 10 sound devices, I see on record tab the Cinergy Line device, it is enabled and set as default, box "listen to this device" is also checked, yet no sound comes and the level scale does not change. Also its permissions (microphone and camera) are enabled on environment variables menu. Any help would be much appreciated.

Link to comment
vor 10 Stunden schrieb Thanosjb:

The only problem is with Analogue Capture. Used multiple pieces of software (OBS, ChrisTV, Terratec Home Cinema), yet no matter what I do I get no sound from the Line-in.

 

Under Windows 10 Cortana likes to occupy analogue audio in, assuming that a microphone is connected to it, thus disabling the usage in other software. There are known cases where Cortana disabled a whole DVB card in this way - see this German post.

Link to comment
1 hour ago, Griga said:

 

Under Windows 10 Cortana likes to occupy analogue audio in, assuming that a microphone is connected to it, thus disabling the usage in other software. There are known cases where Cortana disabled a whole DVB card in this way - see this German post.

 

Thanks for the prompt reply. Unfortunately it did not solve my issue :( disabled cortana, rebooted, still the same..

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...