Controller troubleshooting - Revision history

Admin: /* The audio stutters or you can hear clicks, pops, noise */

2013-04-14T13:32:02Z

The audio stutters or you can hear clicks, pops, noise

← Older revision		Revision as of 13:32, 14 April 2013
Line 30:		Line 30:
	*make sure your laptop is not overheating (this will lead to the processor functions at much lower speed)		*make sure your laptop is not overheating (this will lead to the processor functions at much lower speed)
	*if none of these work for you it just means your computer is simply not powerful enough for real-time audio. Please check the system requirements for FutureDecks.		*if none of these work for you it just means your computer is simply not powerful enough for real-time audio. Please check the system requirements for FutureDecks.
	*for advanced users: you can use [http://www.thesycon.de/deu/latency_check.shtml DPC checker] or [http://www.microsoft.com/whdc/DevTools/tools/RATT.mspx RattV3] to check your system global latency		*for advanced users: you can use [http://www.thesycon.de/deu/latency_check.shtml DPC checker] or [http://www.microsoft.com/whdc/DevTools/tools/RATT.mspx RattV3] or [http://www.resplendence.com/latencymon LatencyMon] to check your system global latency

Admin: /* Controller doesn't work at all */

2013-04-14T09:04:40Z

Controller doesn't work at all

← Older revision		Revision as of 09:04, 14 April 2013
Line 13:		Line 13:
	#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.		#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.
	#*if you can see the device name in FutureDecks but the controller is still not working it means that the controller might either be defective or simply FutureDecks does not support it.		#*if you can see the device name in FutureDecks but the controller is still not working it means that the controller might either be defective or simply FutureDecks does not support it.
	#*make sure that the MIDI controller is set to work on it's default MIDI channel - read the controller's manual to see how to change that (if it has such a feature)		#**make sure that the MIDI controller is set to work on it's default MIDI channel - read the controller's manual to see how to change that (if it has such a feature)
			#**make sure that no other software is using the MIDI controller (on Windows only 1 software at a time can use a MIDI device)

	== Using controller's built-in audio ==		== Using controller's built-in audio ==

Admin: /* Controller doesn't work at all */

2013-04-14T09:01:46Z

Controller doesn't work at all

← Older revision		Revision as of 09:01, 14 April 2013
Line 9:		Line 9:
	== Controller doesn't work at all ==		== Controller doesn't work at all ==
	#make sure the controller is connected to the computer, that the cable is ok and the controller is powered on (if it has a power/on switch). Some controllers consume a bit more power than the USB port can provide and need an A/C adapter. Make sure this is working and it's connected to the controller.		#make sure the controller is connected to the computer, that the cable is ok and the controller is powered on (if it has a power/on switch). Some controllers consume a bit more power than the USB port can provide and need an A/C adapter. Make sure this is working and it's connected to the controller.
	#if the controller was made for USB2 make sure that it's connected to a USB2 port (usually black/grey) and not a USB3 port (these are blue ~~usually~~)		#if the controller was made for USB2 make sure that it's connected to a USB2 port (usually black/grey) and not a USB3 port (these are usually blue)
	#test if the controller appears in FutureDecks Preferences/Cfg Control section.		#test if the controller appears in FutureDecks Preferences/Cfg Control section.
	#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.		#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.
	#*if you can see the device name in FutureDecks but the controller is still not working it means that the controller might either be defective or simply FutureDecks does not support it.		#*if you can see the device name in FutureDecks but the controller is still not working it means that the controller might either be defective or simply FutureDecks does not support it.
	#*make sure that the MIDI controller is set work on it's default MIDI channel - read the controller's manual to see how to change that (if it has such a feature)		#*make sure that the MIDI controller is set to work on it's default MIDI channel - read the controller's manual to see how to change that (if it has such a feature)

	== Using controller's built-in audio ==		== Using controller's built-in audio ==

Admin: /* Controller doesn't work at all */

2013-04-14T09:00:16Z

Controller doesn't work at all

← Older revision		Revision as of 09:00, 14 April 2013
Line 9:		Line 9:
	== Controller doesn't work at all ==		== Controller doesn't work at all ==
	#make sure the controller is connected to the computer, that the cable is ok and the controller is powered on (if it has a power/on switch). Some controllers consume a bit more power than the USB port can provide and need an A/C adapter. Make sure this is working and it's connected to the controller.		#make sure the controller is connected to the computer, that the cable is ok and the controller is powered on (if it has a power/on switch). Some controllers consume a bit more power than the USB port can provide and need an A/C adapter. Make sure this is working and it's connected to the controller.
			#if the controller was made for USB2 make sure that it's connected to a USB2 port (usually black/grey) and not a USB3 port (these are blue usually)
	#test if the controller appears in FutureDecks Preferences/Cfg Control section.		#test if the controller appears in FutureDecks Preferences/Cfg Control section.
	#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.		#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.

Admin: /* Controller doesn't work at all */

2013-04-14T08:56:56Z

Controller doesn't work at all

← Older revision		Revision as of 08:56, 14 April 2013
Line 12:		Line 12:
	#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.		#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.
	#*if you can see the device name in FutureDecks but the controller is still not working it means that the controller might either be defective or simply FutureDecks does not support it.		#*if you can see the device name in FutureDecks but the controller is still not working it means that the controller might either be defective or simply FutureDecks does not support it.
			#*make sure that the MIDI controller is set work on it's default MIDI channel - read the controller's manual to see how to change that (if it has such a feature)

	== Using controller's built-in audio ==		== Using controller's built-in audio ==

Admin: /* Using controller's built-in audio */

2013-04-14T08:50:45Z

Using controller's built-in audio

← Older revision		Revision as of 08:50, 14 April 2013
Line 23:		Line 23:
	*'''never''' connect the controller to a USB hub/extender, connect it only directly to the computer		*'''never''' connect the controller to a USB hub/extender, connect it only directly to the computer
	*disconnect other devices that are connected to the USB ports		*disconnect other devices that are connected to the USB ports
	*disable WiFi		*stop all other software that are running (there may also be software running in the background installed by the laptop's manufacturer that's causing the problems)
			*disable WiFi (some cause a lot of problems for low-latency audio)
			*disable High-Quality Time Stretching (Master Tempo)
			*make sure your laptop is not overheating (this will lead to the processor functions at much lower speed)
	*if none of these work for you it just means your computer is simply not powerful enough for real-time audio. Please check the system requirements for FutureDecks.		*if none of these work for you it just means your computer is simply not powerful enough for real-time audio. Please check the system requirements for FutureDecks.
			*for advanced users: you can use [http://www.thesycon.de/deu/latency_check.shtml DPC checker] or [http://www.microsoft.com/whdc/DevTools/tools/RATT.mspx RattV3] to check your system global latency

Admin: /* Using controller's built-in audio */

2013-04-14T08:41:03Z

Using controller's built-in audio

← Older revision		Revision as of 08:41, 14 April 2013
Line 18:		Line 18:
	*make sure that the audio device (from the controller) is selected in FutureDecks' Preferences/Cfg. If you don't even see the device listed there it means that you should install the drivers for it.		*make sure that the audio device (from the controller) is selected in FutureDecks' Preferences/Cfg. If you don't even see the device listed there it means that you should install the drivers for it.
	*make sure that you are are actually playing something in both decks and that monitoring (headphone PFL) is activated. Also make sure that the volume on both the software and on the hardware controller is up.		*make sure that you are are actually playing something in both decks and that monitoring (headphone PFL) is activated. Also make sure that the volume on both the software and on the hardware controller is up.
			=== The audio stutters or you can hear clicks, pops, noise ===
			*try to increase the audio latency from Preferences/Cfg (try increasing it several times until the problem goes away)
			*change the USB port/socket that the controller is plugged into
			*'''never''' connect the controller to a USB hub/extender, connect it only directly to the computer
			*disconnect other devices that are connected to the USB ports
			*disable WiFi
			*if none of these work for you it just means your computer is simply not powerful enough for real-time audio. Please check the system requirements for FutureDecks.

Admin at 08:35, 14 April 2013

2013-04-14T08:35:25Z

← Older revision		Revision as of 08:35, 14 April 2013
Line 12:		Line 12:
	#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.		#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.
	#*if you can see the device name in FutureDecks but the controller is still not working it means that the controller might either be defective or simply FutureDecks does not support it.		#*if you can see the device name in FutureDecks but the controller is still not working it means that the controller might either be defective or simply FutureDecks does not support it.


			== Using controller's built-in audio ==
			=== There is no audio coming from the controller ===
			*make sure that the audio device (from the controller) is selected in FutureDecks' Preferences/Cfg. If you don't even see the device listed there it means that you should install the drivers for it.
			*make sure that you are are actually playing something in both decks and that monitoring (headphone PFL) is activated. Also make sure that the volume on both the software and on the hardware controller is up.

Admin at 08:29, 14 April 2013

2013-04-14T08:29:01Z

← Older revision		Revision as of 08:29, 14 April 2013
Line 5:		Line 5:
	*the ones that require drivers or other software to work ok		*the ones that require drivers or other software to work ok

	If a controller comes with drivers (either on a CD or downloadable from the manufacturer website) '''always''' install them '''before''' connecting the controller to the computer. This is true especially on Windows machines. If you first hook-up the controller before installing the driver then Windows will pre-install a default driver that it finds from Windows Update servers. This driver might work ok or it may not. Also, the controller name might be reported differently than it would've been with it's original driver installed. Because it's name will change than there is a chance that the script inside FutureDecks might not recognize the controller correctly. Again on Windows machines - try to always connect the controller to the same port. If you have an USB controller that was first ~~plug~~ in a USB port and you connect it to a different USB port (socket) ~~than~~ Windows will perceive this as a completely different device -- it will even install drivers for it. So, to avoid any problems try to always use the same USB port/socket.		If a controller comes with drivers (either on a CD or downloadable from the manufacturer website) '''always''' install them '''before''' connecting the controller to the computer. This is true especially on Windows machines. If you first hook-up the controller before installing the driver then Windows will pre-install a default driver that it finds from Windows Update servers. This driver might work ok or it may not. Also, the controller name might be reported differently than it would've been with it's original driver installed. Because it's name will change than there is a chance that the script inside FutureDecks might not recognize the controller correctly. Again on Windows machines - try to always connect the controller to the same port. If you have an USB controller that was first plugged in an USB port and you connect it to a different USB port (socket) then Windows will perceive this as a completely different device -- it will even install drivers for it. So, to avoid any problems try to always use the same USB port/socket.

			== Controller doesn't work at all ==
			#make sure the controller is connected to the computer, that the cable is ok and the controller is powered on (if it has a power/on switch). Some controllers consume a bit more power than the USB port can provide and need an A/C adapter. Make sure this is working and it's connected to the controller.
			#test if the controller appears in FutureDecks Preferences/Cfg Control section.
			#*if it's not there install a software a like MidiMonitor (on Macs) or MIDIOX (on Windows) and see if the device appears there. If it doesn't it means the controller is either defective, the USB port is or you simply have not installed the drivers/software that came with.
			#*if you can see the device name in FutureDecks but the controller is still not working it means that the controller might either be defective or simply FutureDecks does not support it.

Admin at 08:20, 14 April 2013

2013-04-14T08:20:45Z

← Older revision		Revision as of 08:20, 14 April 2013
Line 5:		Line 5:
	*the ones that require drivers or other software to work ok		*the ones that require drivers or other software to work ok

	If a controller comes with drivers (either on a CD or downloadable from the manufacturer website) '''always''' install them '''before''' connecting the controller to the computer. This is true especially on Windows machines. If you first hook-up the controller before installing the driver then Windows will pre-install a default driver that it finds from Windows Update servers. This driver might work ok or it ~~might~~ not. Also, the controller name might be reported differently than it would've been with it's original driver installed. Because it's name will change than there is a chance that the script inside FutureDecks might not recognize the controller correctly.		If a controller comes with drivers (either on a CD or downloadable from the manufacturer website) '''always''' install them '''before''' connecting the controller to the computer. This is true especially on Windows machines. If you first hook-up the controller before installing the driver then Windows will pre-install a default driver that it finds from Windows Update servers. This driver might work ok or it may not. Also, the controller name might be reported differently than it would've been with it's original driver installed. Because it's name will change than there is a chance that the script inside FutureDecks might not recognize the controller correctly. Again on Windows machines - try to always connect the controller to the same port. If you have an USB controller that was first plug in a USB port and you connect it to a different USB port (socket) than Windows will perceive this as a completely different device -- it will even install drivers for it. So, to avoid any problems try to always use the same USB port/socket.