Just read the online manual - am I right in thinking that the HC1000S is set to MIDI channel 1 by default but my HC4500 is already on that channel so the 1000S isn't doing anything to SSL.

So, I need to set the 1000S to channel 2, say, for it to work??

Hi bumbo08,

The Denon DN-HC1000S must be on MIDI channel 1 for you to use it in native control mode. Channels 2 to 4 are available for you to map as you please :)

The DN-HC1000S and the DN-HC4500 should work fine together :) If you delete the AUTO_SAVE.xml file from the Music -> ScratchLIVE -> MIDI folder it will not affect the DN-HC4500.

Also can you please give me the 5 digit build number of the version of Scratch Live that you are using? (this is found in the lower left hand corner of the setup screen)

Michael thanks for this. i'll try it now

it's build 19222

deleted auto_save but still doesnt work.,...

anyone..?

Hey bumbo08,

Just to double check - do you have the DN-HC1000S set to channel 1?

What happens if you connect the DN-HC1000S only and not the DN-HC4500 - does it work then?

Are you connecting both of these directly to a USB port on your computer or via a USB hub?

Hi Michael

As far as I know it is...

The HC4500 isn't connected when the HC1000S is and it is directly into a USB port. The SL3 is in one (the 'good' one), the ext HD is on FW800 and the HC1000 is on the second USB...

I know u guys must be busy with the public beta of 2.0 but just wanted to keep this alive...

I double checked and yes it is on MIDI channel 1. still the same problem though..connect, cue 1 buttons flash then nothing...

Hey bumbo08,

Don't worry, we're still here :)

Can you please download MIDI Monitor from here -> www.snoize.com and try using the DN-HC1000S with it - does MIDI Monitor show any MIDI data being received?

Also can you try renaming the MIDI folder (located in Music -> ScratchLIVE) and see if the DN-HC1000S works?

Finally do you have another computer you can try the DN-HC1000S on? Do you have the same problem on that machine?

Hi Michael

thanks for sticking with this!

Renaming the folder did nothing - no response. plugged into my older MBP and it runs fine (that's running SL2.0).

however, when running midi monitor on my old machine, it was receiving midi data fine and was listed as HC1000S but on my new MBP (my DJing one) it was just listed as USB MIDI source, not HC1000S - not sure if this is significant??

I've got almost the same problem. So I plugged my DN-HC1000S into my PC when I got it and everything worked like a charm. My buddy comes over with his MBP and we plug in the 1000S and can't get the thing to work. We give up troubleshooting forget about using it with the MBP.

I go back to plug it into my PC and Bam the 1000S completely useless. Every place on the internet keeps saying delete auto_save.xml delete auto_save.xml. But that file doesn't even exist on my PC.

When I plug in the 1000S into my system I get 3 flashing lights from the Cue-1 button.

Does anyone out there really know how this thing works? I figure the Mini config in Serato is not seeing it but I haven't found a place to help me figure it out. I'm running a HP laptop with Vista SP1, and SL 1.9.2. Any help would be appreciated.

Got the same prob as above just quit on me at a gig last night
running
ttm57sl
MB 4gb
1.9.2
had an issue with AUTO_SAVE .xml file but after deleting it it work fine for a while.

I tried using the 1000S on my work PC that has windows7 on it and it didn't work there either. For the heck of it I swapped out the USB cable of the 1000S with one from my phone and sure enough it was picked up by windows.

I wouldn't have thought a cable could go bad so fast. But it looks like that's all that was holding me back.

Ok so i updated the firmware vers on my TTM57sl and all is good again (for now)
will post again if anything goes wrong
fingers crossed.

i'm still having my problem as above..

any word on this yet?

not sure if the quoted is the issue here...?

Can you please go to: Applications > Utilities > Audio MIDI setup.
Plug the HC1000S in, then create a new MIDI configuration, change from a miscellaneous device to a recognized HC1000S MIDI controller.

Does that work?

Hey Matt

Tried that but I can't see anywhere that allows me create a new MIDI config or to change from a misc device to anything else...

I've taken a screenshot of my Audio MIDI set up screen...

Can you go up to Window then click the 'Show MIDI window' option?

Hi Matt

I see it now... :-)

I'll give it a proper go tonight - have to try using the HC1000 and HC4500 on a hub and see if it still functions OK as I don't have a spare USB at the moment.

I'll report back...

I had luck running a 4500 and the 1000 on a powered hub. I only tested for 15 minutes but there wasn't any conflicts that I saw.

Hey Chad

I tried the exact same thing and everything worked fine.

The only note I will make is that either the 4500 or 1000 has to be directly connected to a USB port, so the SL3 had to be jointly connected to the remaining unit - I'm guessing due to MIDI data being sent and conflicting with SSL.

I had mine
- SL3 & HC1000 > USB hub > 'good' USB port
- HC4500 > 2nd USB port

But, like you say, no conflicts - which I'm VERY happy about.

I'm all good so you can close this thread if you like!

Thanks guys

I usually see problems when using the Scratch Live hardware on a hub, almost always.

I was using a Belkin powered hub for my test. It seems to be the one brand and type that works relatively well.

I'll keep an eye out but, like I say, having the 4500 and 1000 on the same hub resulted in one or the other not responding. It did feel like SSL was confused about where the MIDI was coming from and only allowed one to work,

Unplugging one of them fixed the problem...

I think the type of hub used is the key.

OK - thanks for that Chad. I'll investigate further...

Most USB hubs use poor switching architecture. Unfortunately the only cure is buying a good quality one (ie. expensive).

If anyone experiences issues with hubs most of the time it's because they will be using a poorly designed hub.

So try it out with a good hub, or if you are rolling fine now, then keep going. However I think what Chad was getting at was that you may experience issues in the future, and it may be a bad time (ie. at a club) which would be bad :-(

Hi everyone, I have the same problems as described above, using osx 10.6.4 + sl3 1.9.2

My DN-HC1000S is set to channel 3 but i switch it to channel 1 once it's booted up (holding SHIFT+FILES). It shows up under Audio & Midi devices in OSX as DN-HC1000S and MINI Monitor does show traffic on channel 1 with the good device name.

I deleted the .xml file and even the Midi folder from /Users/me/Documents/Music/...

So far no luck

Should I bring this device back ?
Is there a fix somewhere ?
Denon site shows no firmware upgrade :/

More informations, I tried the controller in Ableton, I can map Midi input there
So I guess it's really on the Serato side .. ?

Hoping to fix this issue, many thanks for your support !

rud, OSX 10.6.4 ?

hrr 10.6.2, typo

Note, I booted XP under bootcamp, and there the controller works fine
So it's definitely something with Serato + DN-HC1000S + MAC issue..

One more peace of info, I just tested on a MAC MIni 10.6.2, and I have the same issue.
The only non-regular settings I have are 5 IAC ports (used for Ableton, MAX, etc)

Could the existing AIC ports create the conflict ?

Sorry for this thread flood, but I'ld really like to solve this issue, as I'm probably not the only one .. ;)

Yes ! Found the bug

If custom IAC ports are enabled, the DN-HC1000S is not recognized by SL-1.9.x and 2.0-RC2

If you disable IAC ports (just bring the Audio + Midi window in OSX, deactivate the IAC driver), than start SL, it works !

There's a bug hidden here somewhere ;)

Feel free to contact me for further config infos

i had a similar problem with the HC1000S, where I had to uninstall my Logitech webcam driver in order for the Denon unit to work. Somehow that driver causes some MIDI devices to not be recognized or function properly. Do you have one of those installed to your knowledge?

DJMaytag: Neg, on my MBP I only have the SL3+HC1000S, and on the Mini, I unplugged all my gear first.

I could replicate the bug, so I'm somehow sure it is a "bug" either from Denon's either from Serato, either from OSX..

I suspect Serator looks for the first, and only, MIDI device that would be plugged on the computer, and thinks it's logically a controller for Serato.
Since I use IAC ports, I think the device order is somehow .. scrambled, resulting in Serato not knowing how to use the device (Remember Ableton and Midi Monitor did show some traffic ...)

So, right now this is not a "BIG" issue, but trust me, when Bridge will be released, a lot of Ableton users will get frustrated if they cannot use IAC ports + Serato !!! (monome, 4ever !)

Peace to all the community

And to Serato creators, please, keep spinning our world !

good findings, we'll put them to the test. Many thanks :)

Hey rud,


Scratch Live will look at all MIDI devices present, not just the first it finds :)

Hi Guys,

Im having the same issues as Bumbo08 above. I have a MBP, SL3 and HC 1000s I cant seem to get the MBP to see the hc1000s.. when I connect the 3 lights flash but thats it..

I see you say that you need to manually add the Midi device... but I dont know to do this.. can someone help... ....

im begging for resolution here....

Hey DJ_NEAL,

Which version of Scratch Live are you using? Which buttons light when you connect it to your computer?

Hi Michael R,

I am using Sertao SL 3, software version 1.9.2

The two cue 1 buttons flash 3 times..

Hey DJ_NEAL,

I see that you've taken your unit back and the new one works fine -> www.serato.com

:)

yeah.. thanks for all your help..

Well ladies and gents, MPB with ssl 2.0 and dnhc1000s.....worked fine the first day then nothing. I tried today and just the flashing cue 3 times. I decided to try a different usb cable than the one provided and voila....it worked. Tested by going back to the original and sure enough it stopped after the flashing cue buttons. Seems so silly that a USB cable is what's made the difference but imagine the returns if others are experiencing bad batches of cables like this.

Thanks for the follow up.

Hi all,

As everyones issues seem to be resolved I will close this thread for now :)