Serious Problems With VMS4 and Traktor

please contact ADJ support on this - generally, you shouldnt have these problems!

Ok,thanks I´ll send the same message as a mail to EU Support. Really hope they can help me...

btw, what exact traktor version are you using?
while i'm re-reading your posting, i remembered that some of the early TP2 versions had issues with the vms which was solved by updating to a current version.

I have exact the same problem.

I have also a i7quadcore.

Have you already fixed it?

Please let me know:
vincent-cox@live.nl

And I have version 2.1.2 traktor scratch pro.

2.1.2 should not give you any headache.

please contact the support.

you can also post some screenshots meanwhile here in the forum, maybe we see sth interesting.

and dont cross/doublepost. deleted the other thread.

Perdon, no hablo ingles, este texto a sido traducido con google. Me preguntaba si han encontrado una solucion ya que tengo el mismo problema o muy parecido, he actualizado a traktor 2 con windows 7 y si selecciono mi vms4 como dispositivo de audio traktor se bloquea completamente.

He bajado los drivers para 64 bits y tengo el firmware actualizado.

Podrian ayudarme?



Sorry, do not speak English, this text has been translated with google. I was wondering if you have found a solution since I have the same or very similar problem, I upgraded to traktor 2 with windows 7 and if I select my audio device VMS4 as traktor is completely blocked.

I downloaded the drivers for 64 bit and I have the firmware updated.

Could help me?

what exact traktor version?

He ido actualizando desde su adquisicion, primero tuve la 2.0.1, despues la 2.1.2 y finalmente tengo instalada la version 2.0.3, mi vms4 no funciona en ninguna como dispositivo de audio, en cuanto es seleccionada bloquea el programa y a veces todo el sistema teniendo que reiniciar el equipo.

Esto sucede en modo 8out.

En modo 4out no bloquea el programa al iniciar y permite trabajar con 2decks, pero si selecciono canales de entrada para grabacion externa como en traktor1 aparece el mismo problema.


Google translation:

I have been updated since its acquisition, I first had the 2.0.1, 2.1.2 and finally after the version 2.0.3 I have installed my VMS4 not work on any device, audio is selected as the program crashes and sometimes all the system having to restart the computer.

This happens 8OUT mode.

4out mode does not block the program to start and can work with 2decks, but if I select input channels for recording foreign as traktor1 see the same issue.

Spanish;

HE ENCONTRADO LA SOLUCION AL PROBLEMA!!!

Analizando profundamente el funcionamiento de Windows 7 he dado con el origen del conflicto se llama "Configuracion de instalacion de dispositivos".

Es una nueva funcion de windows 7 que instala automaticamente los drivers mas adecuados para cualquier dispositivo que conectemos, no deberia causar problema pero lo hace.

Voy a intentar explicarlo claramente para ver si Google hace una buena traduccion y si no algun amigo del foro podria hacerlo.

Si hemos utilizado alguna vez un raton USB en windows 7 y la funcion de drivers automaticos estaba activa windows ha instalado unos drivers genericos para ese raton, ese es el problema.

No he conseguido averiguar porque pasa esto pero Windows reconoce la VMS4 como dos dispositivos midi, un controlador y un raton por su funcion touchpad, esto produce un conflicto de clonacion de drivers y hace que Traktor se congele, es sencillo pero dificil de encontrar.

Este es un problema que afecta mas claramente a los pc portatiles por ser los que suelen utilizar raton via usb.

No os apresureis, puede que si teneis un raton conectado y lo desconectais parezca el problema solucionado pero posiblemente al reiniciar o en otro momento volverá a aparecer asi que os recomiendo seguir esta pequeña guia para solucionarlo completamente:

Paso1:
Desinstalar todos los controladores de ASIO.
Desinstalar todos los controladores de Raton
Desinstalar Traktor
Borrar la carpeta Traktor de Mis Documentos.
Realizar una limpieza del registro con CCleaner o programa parecido.
Reiniciar


Paso2:
Asegurarse de que el sistema se inicia sin nada conectado a sus puertos USB
Desactivar la instalacion automatica de drivers.
Si no sabes hacerlo visita:
http://www.trucoswindows.net/f...ers-windows-7-a.html



Paso 3.
Instalar drivers asio 64 bits
Instalar traktor
Activar de nuevo la instalacion automatica de drivers y conectar la vms4

Paso 4

Ahora depende de tu situacion:

Si el problema fue un raton que ya no usas, problema resuelto.

Si usas un raton que tiene drivers o puedes descargar los de su compañia los tendras que instalar antes de conectar el raton.
Ahora seran diferentes los controladores de vms4 y tu raton, no habra conflicto. Problema resuelto.

Si tu raton es un generico sin drivers no debes hacer nada. Funcionara perfectamente con los mismos que usa el touchpad de la vms4, solo tienes que asegurarte de desconectar ese raton antes de conectar tu vms4 o volveran los problemas.

Si decides instalar otro raton o crees que la instalacion automatica de windows7 te vuelve a causar problemas puedes comprobarlo en la pantalla de "Dispositivos e impresoras". Si aparecen dos ratones y uno de ellos tiene un pequeño simbolo de advertencia amarillo es que existe conflicto.
Esto solo funciona si has seguido antes estas instrucciones y los drivers de la vms4 estan instalados en primer lugar. No se porque sucede pero es asi.



Espero que se entienda todo y que si lo haceis me conteis el resultado.

Un saludo


English

Sorry for my English, translated automatically by Google.

I FOUND THE SOLUTION TO THE PROBLEM!

Deeply analyzing the performance of Windows 7 I have traced the origin of the conflict is called "Device Installation Settings".

It is a new feature of Windows 7 that automatically installs the appropriate drivers for any device more we connect, it should not cause problems but it does.

I'll try to explain clearly to see if Google makes a good translation and if any friend of the forum could do.

If you've ever used a USB mouse in Windows 7 and the automatic function was active drivers windows installed a generic driver for that mouse, that's the problem.

I have not managed to figure out why this happens but Windows recognizes the midi VMS4 as two devices, a controller and a mouse touchpad for its function, this causes a conflict of cloning of drivers and makes Traktor freezes, is simple but hard to find.

This is a problem that affects more clearly to the notebook PC because I usually use the mouse via usb.

Do not hurry, maybe if you have a mouse connected and log off the problem seems solved but possibly to restart or reappear later so I recommend you follow this little guide to solve it completely:

Step 1:
Uninstall all ASIO drivers.
Uninstall all Mouse drivers
Traktor uninstall
Delete the folder My Documents Traktor.
Perform a registry clean with CCleaner or similar program.
reboot

Step2:
Ensure that the system starts with nothing connected to its USB ports
Disable automatic installation of drivers.
If you can not do this visit:

http://www.worldstart.com/disa...-install-win7-vista/

Step 3.
Install 64-bit drivers asio
Install traktoR

Reactivate the automatic installation of drivers and connect the VMS4

step 4

Now it depends on your situation:

If the problem was a mouse that you no longer use, problem solved.

If you are using a mouse that has drivers or you can download your company's will have to install before connecting the mouse.
Now drivers will be different VMS4 and your mouse, there will be conflict. Problem solved.

If your mouse is a generic without drivers should not do anything. Work perfectly with them using the touchpad VMS4, just make sure to unplug the mouse before connecting your VMS4 or problems will return.

If you decide to install another mouse or do you think the automatic installation of windows 7 you again cause you can check on the screen of "Devices and Printers". If two mice and one of them has a little yellow warning symbol is that there is conflict.
This only works if you followed these instructions before drivers are installed the VMS4 first. Not because it happens but it is so.



I hope you understand everything and if you do it may tell me the result.

a greeting

quote:

I have not managed to figure out why this happens but Windows recognizes the midi VMS4 as two devices, a controller and a mouse touchpad for its function, this causes a conflict of cloning of drivers and makes Traktor freezes, is simple but hard to find.

wow. you learn something new every day!!!

windows recognizes the vms4 as mouse touchpad as well, since the little field in the middle is exactly that - a mouse.

but very interesting that this can conflict with other mouse drivers...

thank you for sharing this!

Hola, he leido casi todo el post de los foros alemanes con la traduccion de Google y he de decir para los que aun tengan problemas que les recomiendo prueben mi pequeña guia puesto que yo tuve los mismos problemas.
Hice todos los cambios en Windows que en el foro se mencionan, tambien todos los que recomienda Native Instruments. No funcionó ninguno.
Me volvi loco buscando una solucion y finalmente encontre el conflicto de controladores de raton.

Tengo Intel core I5, 8gb de memoria RAm, windows 7 home premium x64.

Y ahora Traktor version 2.0.3, VMS4 con firmware 3.11 y controladores x64

Tras solucionar el conflicto que ya he explicado mi Vms4 funciona perfectamente, todos sus canales en modo 4 y 8 out, con latencia de 6 mls.

Probada en sesion de hasta 8 horas horas seguidas, sin chasquidos, sin mala calidad de sonido y grabando la sesion continuamente. Utilizando la vms4 al maximo.

Si que estoy con ustedes en que American audio deberia tener en cuenta estos problemas y actualizar sus drivers, yo personalmente animo a que incluyan en elllos una seccion de drivers propios para el raton incorporado en la Vms4 y solucionar el conflicto con windows a la vez que quiza unos calculos mas apropiados para los procesadores y sistemas actuales.

Un saludo



Hello, I've read almost all of the forum post with the German translation of Google and have to say to those who still have trouble proving that I recommend my little guide since I had the same problems.
I made all the changes in Windows mentioned in the forum, also recommending that all Native Instruments. It did not work either.
I went crazy looking for a solution and finally found the mouse driver conflict.

I have Intel Core i5, 8GB of RAM, windows 7 home premium x64.

And now Traktor version 2.0.3, VMS4 with firmware 3.11 and x64 drivers

After resolving the conflict that I have explained my VMS4 works perfectly, all channels in 4 and 8 out, with a latency of 6 mls.

Tested in session up to 8 hours hours without clicking, no poor sound quality and continuously recording the session. Using the maximum VMS4.

If I'm with you that American audio should consider these issues and update your drivers, I personally encourage you to include in a section of elllos own drivers for the mouse built into the VMS4 and resolve the conflict with windows while perhaps a more appropriate load for the processors and systems.

a greeting

Same mouse problems here on vms4.1 you have to do something to correct the conflicts!