ALWAYS uninstall old drivers before installing new ones. This is a general Windows rule for EVERYTHING.
2.1 is the latest final release build. However, bugs are still there and they then begin working on beta versions, i.e. not yet ready for final release. These are labelles as 2.1a, 2.1b, 2.1c etc etc. When they reach a stage where they think it's ready for a final build release, they'll upload it as version 2.2 onto their site and the newest version.
Therefore, the beta version are simply the steps through bug fixes between 2.1 and 2.2.
Uninstall current driver, install the latest beta version and give it a try.
Ableton 9.7.5, Native Instruments Komplete Ultimate 11, MOTU 828 Mk2, Nektar Impact LX61+, Ableton Push, Native Instruments Kore 2, and a random selection of soft synths and sample libraries.
Windows 10 Pro 64 bit with Core i7 4960X Extreme Edition 12 core CPU, 64GB RAM, SanDisk Ultra Extreme SSDs and a GeForce GTX 970 G1 Gaming GPU.
Still no joy for me I'm affraid, just had complete laptop freeze when trying the latest mapping.
How was the book midi mapping for idiots?
MBP | TRAKTOR 2.6 | 4TRAK | ORBIT | LAUNCHPAD | KONTROL X1 | KONTROL F1 |KONTROL Z1| XONE XD53
Currently using driver 2.1b3.exe as far as I can see this is the latest beta driver available.
I was giging this past weekend and was in a booth with limited space. The USB connection was interfering with my X1(s). I use a 1ft straight USB to a 4 port hub connection opposed to the long cable that came with the Launchpad, for less clutter. So it has inspired me to re-map my entire launchpad so that the usb connector is at the top off the unit as opposed to the side. I have completed the bottom half and I'm incorporating new features to the layout. I am thinking of eliminating the following buttons and using their pad to assign other functions.
-Snap
-Quantize
-Cue
-Master
-Search
-Eq kills
Has anyone been using these functions soley from the launchpad?
Im hoping that an entire re-map will also fix this problem with users experiencing crashes due to LED feedback.
Last edited by jhyphinwill; 06-06-2011 at 02:41 PM.
MBP | TRAKTOR 2.6 | 4TRAK | ORBIT | LAUNCHPAD | KONTROL X1 | KONTROL F1 |KONTROL Z1| XONE XD53
I use the EQ kills on it. Everything else, I think the removal is justified but the EQ kills are handy and worth keeping I'd say.
Ableton 9.7.5, Native Instruments Komplete Ultimate 11, MOTU 828 Mk2, Nektar Impact LX61+, Ableton Push, Native Instruments Kore 2, and a random selection of soft synths and sample libraries.
Windows 10 Pro 64 bit with Core i7 4960X Extreme Edition 12 core CPU, 64GB RAM, SanDisk Ultra Extreme SSDs and a GeForce GTX 970 G1 Gaming GPU.
MBP | TRAKTOR 2.6 | 4TRAK | ORBIT | LAUNCHPAD | KONTROL X1 | KONTROL F1 |KONTROL Z1| XONE XD53
In order for this mapping to work the effects in the settings have to be in the correct order (see page 10 of this thread). But the mapping for the VCI-100 from DJTT has a different order of effects for its presets, meaning that you can't have this mapping and the standard djtt vci-100 mapping at the same time.
Does anybody know how to get around this issue?
|
Bookmarks