nobody seems to have resolved this issue yet. so, lets get the ball rolling please :¬)
in an older packager from last year, i believe its package 4 - these keys are present in the "hardware information"
*********************************************
** registry content under current user **
*********************************************
path: softwarehercules technologies
--->subkey: djconsoleseries
---------------------------------------------------------
"bootskin" <type:dword> : 0x00000003
"lastsymboliclink" <type:sz> : "?usb#vid_06f8&pid_b101&mi_07#6&b4269cf&0&0007#{2f712ab5-2cac-46d1-bad3-ce9b2f2d1b7f}"
--->subkey: djconsoleseries
mx
---------------------------------------------------------
--->subkey: djconsoleseries
mx6&1dfc1a74&0&0007
---------------------------------------------------------
"asiosamplerate" <type:dword> : 0x0000bb80
"asiosamplesize" <type:dword> : 0x00000018
--->subkey: djconsoleseries
mx6&3bf7984&0&0007
---------------------------------------------------------
"asiosamplerate" <type:dword> : 0x0000bb80
"asiosamplesize" <type:dword> : 0x00000018
however, in the latest package the subkey above is nonexistant. i dont know how large a role the registy plays with the hardware, but anything to do with the "samplerate" and "samplesize" is probably important i imagine.
can we work on getting this fixed!
thank you,
chris
Okay, I've been observing the interactions HDJSeriesCPL.exe has with the registy (using Process Monitor) on a machine where the problem is not present and I clearly see all the messages being successfully executed to change the sample rate, and bit rate.
However, as is expected, these messages do not appear on a machine where the sample rate is 'stuck'
Chris
Also noticed that on a machine where the problem is not present, the GUI is fairly smooth to operate and there's no visual blips. However, on a machine where the problem is present the interface exhibits a 'blinking' effect when moving between tabs or trying to change anything in the drop down menus.
As mentionned in the other thread on the subject, the problem has been recognized and fixed and will be included in the next driver release, along with other improvements, and support for the new DJControl Instinct.
Right, you're saying it's been fixed? What am I waiting on then?
a) I'm not bothered about new features, I just want the ones I had already to work correctly.
b) I don't need support for new hardware
Chris
Surely as a professional company you can release a quick-fix. Needless to say once this problem is resolved I won't be investing in anymore Hercules hardware. It's ridiculuos that you're bundling a 'fix' with drivers for new hardware I don't even have!
I'm not in the secrets of the gods, but given how drivers have been released in the past, 6 months between releases is not unusual.
However, since you know that problem wasn't present in the previous driver version, you could simply go back to using this one instead:
its for all hercules dj products........i have the trim and i have the same issue, just have to wait until the update is out....i even spoke to customer service and they want me to reutn it....not doing that again.....already did it once.
Hello Djdubc,
Why don't you use an older driver package?
Chris,
1) You start a discussion on a problem without describing the problem.
2) Even when one looks at your other posts, in the other discussion you don't post a clear description of your problem: you say you cannot switch to 24-bit without writing in which software.
If you cannot switch in 24-bit in VirtualDJ, it is not a bug, it is normal as VirtualDJ switches the Rmx in 16-bit (because VirtualDJ engine is in 16-bit).
i have, and i still have the same issue, just gotta wait thats all
fresh new drivers package :
http://ts.hercules.com/eng/index.php?pg=view_files&gid=17&fid=60&pid=240&cid=1
my issue has been fixed...........what happen to that other guy lmao
