INTERACT FORUM
More => Old Versions => JRiver Media Center 26 for Windows => Topic started by: dominique-tanguy on December 29, 2019, 09:27:44 am
-
Hi to all,
I was using WDM driver with MC25. I have the same parameters in MC26 (Options/General/ Features WDM ticked)...
I have just uninstalled MC25 to keep only MC26, but the WDM driver is not available anymore in my list of Audio optiosn...
Any idea?
Cheers,
Dominique
-
Make sure you are using MC26.0.14
-
Remove the WDM driver from the General --> Features list and then close JRiver and then run it again.
Then add the WDM driver from the JRiver General --> Features list and then close JRiver and then run it again.
-
Make sure you are using MC26.0.14
I was running 012. I have installed 014. Same issue. No WDM driver visible despite ticked in "Features"
My setup:
Library
Total files: 10.142
Audio files: 9.123
Image files: 1.018
Video files: 1
Other files: 0
Processing
Thumbnails built: 35% (3574 of 10142)
Audio analyzed: 3% (276 of 9124)
Background Tools Running
No tools currently running
Power
Mode change (disable screensaver, keep monitor on) [expires in 3 seconds]
Media Center
Version: 26.0.14 registered
Install path: C:\Program Files\J River\Media Center 26\
Interface plug-ins: Interface Plugins: TiVo Server (not running)
JRMark: never run
Program run time: 56 seconds
Memory used: 41,4 MB memory
Handles used: 618 handles
Advanced System Info
Memory & CPU
CPU features: MMX, SSE2, SSE3, SSSE3, SSE4.1, AVX
Free Physical Memory: 11,8 GB
Total Logical Cores: 8
Total Memory: 15,9 GB
Operating System
Microsoft Windows 10 64-bit
Audio inputs and outputs
Haut-parleurs (SMSL USB DAC) (driver 10.0.18362.1)
Microphone (High Definition Audio Device) (driver 10.0.18362.1)
Microphone (High Definition Audio Device) (driver 10.0.18362.1)
Bluetooth
Bluetooth Device (RFCOMM Protocol TDI) (driver 10.0.18362.1)
Énumérateur Microsoft Bluetooth (driver 10.0.18362.449)
Énumérateur Microsoft Bluetooth LE (driver 10.0.18362.1)
Intel(R) Wireless Bluetooth(R) (driver 20.100.0.4)
Redmi (driver 10.0.18362.1)
Redmi (driver 10.0.18362.449)
Service d’accès à l’annuaire téléphonique (PSE) (driver 10.0.18362.449)
Service d’accès Sim (driver 10.0.18362.449)
Service d’objet poussé (driver 10.0.18362.449)
Service de passerelle audio pour casque (driver 10.0.18362.449)
Service de réseau personnel (driver 10.0.18362.449)
Service de source audio (driver 10.0.18362.449)
Service NAP de réseau personnel (driver 10.0.18362.449)
Transport Avrcp Redmi (driver 10.0.18362.1)
Transport Avrcp Redmi (driver 10.0.18362.1)
CDROM
Optiarc BD ROM BC-5500S USB Device (driver 10.0.18362.1)
Computer
PC ACPI avec processeur x64 (driver 10.0.18362.1)
Disk drives
Samsung SSD 970 EVO 500GB (driver 10.0.18362.1)
Display adapters
Intel(R) HD Graphics 630 (driver 26.20.100.7263)
Radeon RX Vega M GH Graphics (driver 24.20.11016.4)
Firmware
Microprogramme système (driver 10.0.18362.1)
HIDClass
Contrôleur système HID (driver 10.0.18362.175)
Contrôleur système HID (driver 10.0.18362.175)
ITECIR Infrared Receiver (EC) (driver 5.3.3.1)
Périphérique d’entrée USB (driver 10.0.18362.175)
Périphérique d’entrée USB (driver 10.0.18362.175)
Périphérique d’entrée USB (driver 10.0.18362.175)
Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID) (driver 10.0.18362.1)
Périphérique de contrôle consommateur conforme aux Périphériques d'interface utilisateur (HID) (driver 10.0.18362.1)
Périphérique fournisseur HID (driver 10.0.18362.175)
Périphérique fournisseur HID (driver 10.0.18362.175)
Transmetteur infrarouge Microsoft eHome (driver 10.0.18362.1)
Keyboard
Clavier 109 MCIR Microsoft eHome (driver 10.0.18362.1)
Clavier MCIR Microsoft eHome (driver 10.0.18362.1)
Périphérique clavier PIH (driver 10.0.18362.1)
Touches de clavier de contrôle à distance Microsoft eHome (driver 10.0.18362.1)
Monitors
Moniteur Plug-and-Play générique (driver 10.0.18362.207)
Mouse
Souris HID (driver 10.0.18362.1)
Souris HID (driver 10.0.18362.1)
Net
Bluetooth Device (Personal Area Network) (driver 10.0.18362.1)
Intel(R) Dual Band Wireless-AC 8265 (driver 20.50.0.5)
Intel(R) Ethernet Connection (2) I219-LM (driver 12.17.10.8)
Intel(R) I210 Gigabit Network Connection (driver 12.17.10.8)
Print queues
EPSON Stylus Pro 3800 (Copie 1) (driver 10.0.18362.1)
EPSON Stylus Pro 3800 (driver 10.0.18362.1)
Fax (driver 10.0.18362.1)
File d’attente d’impression racine (driver 10.0.18362.1)
Microsoft Print to PDF (driver 10.0.18362.1)
Microsoft XPS Document Writer (driver 10.0.18362.1)
OneNote (driver 10.0.18362.1)
Samsung ML-1640 Series (USB003) (driver 10.0.18362.1)
Send To OneNote 2016 (driver 10.0.18362.1)
Printer
EPSON Stylus Pro 3800 (driver 6.63.0.0)
Samsung Universal Print Driver 3 (driver 3.0.13.0)
Processors
Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz (driver 10.0.18362.387)
Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz (driver 10.0.18362.387)
Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz (driver 10.0.18362.387)
Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz (driver 10.0.18362.387)
Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz (driver 10.0.18362.387)
Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz (driver 10.0.18362.387)
Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz (driver 10.0.18362.387)
Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz (driver 10.0.18362.387)
SCSIAdapter
Contrôleur des espaces de stockage Microsoft (driver 10.0.18362.449)
Contrôleur NVM Express standard (driver 10.0.18362.1)
SDHost
Contrôleur hôte numérique sécurisé compatible SDA (driver 10.0.18362.207)
SecurityDevices
Module de plateforme sécurisée 2.0 (driver 10.0.18362.267)
Software devices
Bluetooth (driver 10.0.18362.1)
Microsoft Device Association Root Enumerator (driver 10.0.18362.1)
Microsoft Radio Device Enumeration Bus (driver 10.0.18362.1)
Microsoft RRAS Root Enumerator (driver 10.0.18362.1)
Synthé. de table de sons Microsoft GS (driver 10.0.18362.1)
Wi-Fi (driver 10.0.18362.1)
Sound, video and game controllers
AMD High Definition Audio Device (driver 10.0.1.6)
Périphérique High Definition Audio (driver 10.0.18362.356)
Redmi Hands-Free HF Audio (driver 10.0.18362.1)
SMSL USB DAC (driver 4.67.0.36759)
Son Intel(R) pour écrans (driver 10.27.0.5)
System
Agrégation de processeurs ACPI (driver 10.0.18362.1)
Bouton d'alimentation ACPI (driver 10.0.18362.267)
Bouton de fonctionnalité définie ACPI (driver 10.0.18362.267)
Bouton veille ACPI (driver 10.0.18362.267)
Bus de caméra de bureau à distance (driver 10.0.18362.329)
Bus redirecteur de périphérique du Bureau à distance (driver 10.0.18362.1)
Compteur d'événement de haute précision (driver 10.0.18362.267)
Contrôleur d'interruptions programmable (driver 10.0.18362.267)
Contrôleur embarqué compatible ACPI Microsoft (driver 10.0.18362.267)
Contrôleur High Definition Audio (driver 10.0.18362.1)
Contrôleur High Definition Audio (driver 10.0.18362.1)
Contrôleur hôte GPIO d’E/S série Intel(R) - INT345D (driver 30.100.1816.3)
Contrôleur hôte I2C d’E/S série Intel(R) - A160 (driver 30.100.1816.3)
Contrôleur hôte I2C d’E/S série Intel(R) - A161 (driver 30.100.1816.3)
Contrôleur hôte I2C d’E/S série Intel(R) - A162 (driver 30.100.1816.3)
Coprocesseur arithmétique (driver 10.0.18362.267)
Énumérateur de bus composite (driver 10.0.18362.329)
Énumérateur de bus racine UMBus (driver 10.0.18362.329)
Énumérateur de cartes réseau virtuelles NDIS (driver 10.0.18362.1)
Énumérateur de lecteur virtuel Microsoft (driver 10.0.18362.1)
Énumérateur de périphérique logiciel Plug-and-Play (driver 10.0.18362.329)
Énumérateur UMBus (driver 10.0.18362.329)
Énumérateur UMBus (driver 10.0.18362.329)
Énumérateur UMBus (driver 10.0.18362.329)
Gestionnaire de volumes (driver 10.0.18362.1)
Horloge système (driver 10.0.18362.267)
Horloge système CMOS/en temps réel (driver 10.0.18362.267)
Intel(R) 100 Series/C230 Series Chipset Family LPC Controller (HM175) - A152 (driver 10.1.1.38)
Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #1 - A110 (driver 10.1.1.38)
Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #2 - A111 (driver 10.1.1.38)
Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #3 - A112 (driver 10.1.1.38)
Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #5 - A114 (driver 10.1.1.38)
Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #9 - A118 (driver 10.1.1.38)
Intel(R) 100 Series/C230 Series Chipset Family PMC - A121 (driver 10.1.1.38)
Intel(R) 100 Series/C230 Series Chipset Family SMBus - A123 (driver 10.1.1.38)
Intel(R) 100 Series/C230 Series Chipset Family Thermal subsystem - A131 (driver 10.1.1.42)
Intel(R) Management Engine Interface (driver 1815.12.0.2021)
Intel(R) Serial IO UART Host Controller - A127 (driver 30.100.1725.1)
Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) Gaussian Mixture Model - 1911 (driver 10.1.1.42)
Interface de gestion Microsoft Windows pour ACPI (driver 10.0.18362.1)
Interface de gestion Microsoft Windows pour ACPI (driver 10.0.18362.1)
Microsoft System Management BIOS Driver (driver 10.0.18362.1)
Périphérique d'ancienne génération (driver 10.0.18362.267)
Périphériques IR grand public (driver 10.0.18362.1)
Pilote d’affichage de base Microsoft (driver 10.0.18362.329)
Pilote d’infrastructure de virtualisation Microsoft Hyper-V (driver 10.0.18362.476)
Pilote de rendu de base Microsoft (driver 10.0.18362.329)
Plug-in du moteur d’alimentation Intel(R) (driver 10.0.18362.387)
Pont PCI vers PCI (driver 10.0.18362.418)
Pont PCI vers PCI (driver 10.0.18362.418)
Pont PCI vers PCI (driver 10.0.18362.418)
Pont PCI vers PCI (driver 10.0.18362.418)
Pont PCI vers PCI (driver 10.0.18362.418)
Pont PCI vers PCI (driver 10.0.18362.418)
Pont PCI vers PCI (driver 10.0.18362.418)
Pont PCI vers PCI (driver 10.0.18362.418)
Pont processeur hôte standard PCI (driver 10.0.18362.267)
Racine complexe PCI Express (driver 10.0.18362.418)
Redmi Hands-Free HF (driver 10.0.18362.1)
Remote Desktop USB Hub (driver 10.0.18362.356)
Ressources de la carte mère (driver 10.0.18362.267)
Ressources de la carte mère (driver 10.0.18362.267)
Ressources de la carte mère (driver 10.0.18362.267)
Ressources de la carte mère (driver 10.0.18362.267)
Ressources de la carte mère (driver 10.0.18362.267)
Ressources de la carte mère (driver 10.0.18362.267)
Ressources de la carte mère (driver 10.0.18362.267)
Ressources de la carte mère (driver 10.0.18362.267)
Ressources de la carte mère (driver 10.0.18362.267)
Ressources de la carte mère (driver 10.0.18362.267)
Système compatible ACPI Microsoft (driver 10.0.18362.329)
Système compatible UEFI Microsoft (driver 10.0.18362.329)
TPS65988 Device (driver 1.0.2.6)
Ventilateur ACPI (driver 10.0.18362.267)
Ventilateur ACPI (driver 10.0.18362.267)
Ventilateur ACPI (driver 10.0.18362.267)
Ventilateur ACPI (driver 10.0.18362.267)
Ventilateur ACPI (driver 10.0.18362.267)
Zone thermique ACPI (driver 10.0.18362.267)
Zone thermique ACPI (driver 10.0.18362.267)
USB
Concentrateur USB générique (driver 10.0.18362.1)
Contrôleur hôte ASMedia USB 3.1 eXtensible - 1.10 (Microsoft) (driver 10.0.18362.207)
Contrôleur hôte Intel(R) USB 3.0 eXtensible - 1.0 (Microsoft) (driver 10.0.18362.207)
Contrôleur hôte Intel(R) USB 3.1 eXtensible - 1.10 (Microsoft) (driver 10.0.18362.207)
Dispositif de stockage de masse USB (driver 10.0.18362.1)
Hub USB racine (USB 3.0) (driver 10.0.18362.1)
Hub USB racine (USB 3.0) (driver 10.0.18362.1)
Hub USB racine (USB 3.0) (driver 10.0.18362.1)
Périphérique USB composite (driver 10.0.18362.1)
Périphérique USB inconnu (échec de demande de descripteur de périphérique) (driver 10.0.18362.1)
Prise en charge d’impression USB (driver 10.0.18362.1)
Prise en charge d’impression USB (driver 10.0.18362.1)
USB DAC Devices
SMSL USB DAC (driver 4.67.0.36759)
VolumeSnapshot
Cliché instantané de volume générique (driver 10.0.18362.1)
Cliché instantané de volume générique (driver 10.0.18362.1)
-
It works!
I have disconnected my DAC, unticked and ticked again WDM, and the driver is back!
But it is labelled "JRiver Media Center 25" despite I am using MC26.
Dominique
-
Thank you, Dominique! Mine works too. As mentioned in the other current thread (the one I started): "Disconnected my DAC, ticked WDM, and MC 25 shows up in 'Select Playback Device'. Then reconnected the DAC. The trick seemed to have been disconnecting the DAC whilst ticking/unticking WDM in Tools>Options>General>Features". Yes, it's JRMC25 (I'm running 26), but that doesn't seem to matter...
-
But it is labelled "JRiver Media Center 25" despite I am using MC26.
If it is labelled "JRiver Media Center 25 (JRiver Media Center 26)" in the Windows 10 Sound Settings, you can rename that first portion in the Windows 10 "Sound > Device Properties" settings.
Apparently MC can't rename an Audio Device if Windows already knows about it, or something like that. Maybe if you completely removed the WDM using Windows Device Manager, MC might be able to get the name correct when the WDM is set up again, but I haven't tried that. I just rename, as above.
BTW, the need to disconnect the DAC to get the WDM to install again is a weird one. Maybe if you had changed the Default Audio Device in Windows to say the PC speakers, that would have had the same effect, if the DAC has its own drivers. Or maybe even if it just used the Windows drivers. It sounds like the DAC driver/hardware didn't want to release the Default Audio Device setting.
-
I've had the same problem on 26.14, with the WDM driver. Yes, you can rename it at the sound properties level, but not (that I can find) in the device manager. The only option there is to delete it known as MC 25. The rename will work until you uninstall the real MC25. Then there is nothing that the system sees resembling the WDM driver for 26, even after a re-install of 26.
Any other suggestions? This problem has been with us for many versions, and the renaming the sound properties device always took care of it, unless you eventually wanted to delete the previous installation.
There must be a better fix for this that doesn't involve any minor surgery after the update. ??
--Bill
26.14 seems really solid, though, for everything else. Kudos!
-
The name is purely visual, it is of no consequence. You don't have to rename it.
-
The name is purely visual, it is of no consequence. You don't have to rename it.
Of course. But as soon as you uninstall the previous version (25), the Windows system no longer sees anything.
So what's the best way to force the current new version (26 in this case) to regenerate a correctly named driver?
--Bill
-
Worst case just disable the WDM feature in MC, save, and re-enable it, that'll force a driver re-install at any time.
I'll look if we can make the installer re-install the driver if its no longer present in the system for some reason, if it doesn't do that already.
-
The name is purely visual, it is of no consequence. You don't have to rename it.
The name is consequential. It looks to users that they have an old version. Many people have reported this problem. You should keep the name in sync with the version number or remove the number from the name. Otherwise people think there is a problem.
-
The name is consequential. It looks to users that they have an old version. Many people have reported this problem. You should keep the name in sync with the version number or remove the number from the name. Otherwise people think there is a problem.
As we've said before, Windows doesn't like renaming devices you already have. We can't force it to rename when you upgrade MC.
I might remove the version from the display name in the next driver update, but that still won't affect people that already have it installed right now.
-
As we've said before, Windows doesn't like renaming devices you already have. We can't force it to rename when you upgrade MC.
I might remove the version from the display name in the next driver update, but that still won't affect people that already have it installed right now.
Rather than trying to rename it, since MC created the WDM driver in the first place, just delete the old one and create a new one with the correct name. ?
-
Rather than trying to rename it, since MC created the WDM driver in the first place, just delete the old one and create a new one with the correct name. ?
Thats the same thing, Windows caches device information and just reuses the old name. Also, people are not particularly happy when we do that, since it messes with the default output device etc.
-
Thats the same thing, Windows caches device information and just reuses the old name. Also, people are not particularly happy when we do that, since it messes with the default output device etc.
While it may require some work for those changes to take effect, have you considered renaming the device as a one-time thing so that it's called "JRiver Media Center" instead of being version-specific?