Инструменты пользователя

Инструменты сайта


hardware:audio

Различия

Показаны различия между двумя версиями страницы.

Ссылка на это сравнение

hardware:audio [11.01.2025 08:01] – создано viacheslavhardware:audio [11.01.2025 08:12] (текущий) viacheslav
Строка 2: Строка 2:
 Страничка на сайте производителя: https://www.behringer.com/product.html?modelCode=0805-AAG Страничка на сайте производителя: https://www.behringer.com/product.html?modelCode=0805-AAG
  
-ASIO driver:  {{ :hardware:behringer_2902_x64_2.8.40.zip |}} (на сайте производителя его нет, рекомендуют ASIO4ALL).+ASIO driver:  {{ :hardware:behringer_2902_x64_2.8.40.zip |}} (на сайте производителя его нет, тем рекомендуют стандартный драйвер + ASIO4ALL).
  
-Подходит он, однако, не для всех устройств U-Control UCA222:+Подходит драйвер, однако, не для всех устройств U-Control UCA222, как сообщают [[https://gearspace.com/board/music-computers/1316473-behringer-asio-driver-lower-end-interfaces.html|на форуме gearspace.com]]:
 > It seems that Behringer stopped using the original Texas Instruments PCM2902 and started using an cheaper equivalent from CoolAudio (v2902). My guess is that it changed the id that is used by the installer to recognize the connected device. The original Behringer ASIO driver only recognized the hardware ids ''USB\VID_08BB&PID_2900'' and ''USB\VID_08BB&PID_2902''. > It seems that Behringer stopped using the original Texas Instruments PCM2902 and started using an cheaper equivalent from CoolAudio (v2902). My guess is that it changed the id that is used by the installer to recognize the connected device. The original Behringer ASIO driver only recognized the hardware ids ''USB\VID_08BB&PID_2900'' and ''USB\VID_08BB&PID_2902''.
 > You can check the codes of the non-working UCA222 by connecting them to your computer, running dxDiag and going to the sound tab of the UCA222 and look for the hardware id. If it is not one of those two, then that is the reason. One alternative you have, then (besides ASIO4ALL) is the multi-brand ploytec driver. They have a free demo (which beeps every 30 seconds), but the commercial one costs 49€... > You can check the codes of the non-working UCA222 by connecting them to your computer, running dxDiag and going to the sound tab of the UCA222 and look for the hardware id. If it is not one of those two, then that is the reason. One alternative you have, then (besides ASIO4ALL) is the multi-brand ploytec driver. They have a free demo (which beeps every 30 seconds), but the commercial one costs 49€...
-> Another alternative would be adding the corresponding new hardware ids to the busb2902.inf file, although it most likely will not work. I tried with an unbranded chinese device with a PCM2704C and it failed, while with the ploytec driver it worked. +> Another alternative would be adding the corresponding new hardware ids to the ''busb2902.inf'' file, although it most likely will not work. I tried with an unbranded chinese device with a PCM2704C and it failed, while with the ploytec driver it worked. 
 + 
 +Панель управления драйвера\\ 
 +{{:hardware:pasted:20250111-080640.png}} {{:hardware:pasted:20250111-080700.png}}
  
-https://gearspace.com/board/music-computers/1316473-behringer-asio-driver-lower-end-interfaces.html 
  
  
hardware/audio.1736582515.txt.gz · Последнее изменение: 11.01.2025 08:01 — viacheslav

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki