Sign In:     

Forum: VirtualDJ Technical Support

Topic: DDJ-GRV6 often not/partially recognized after Mac restart - only works after USB replug
Hi everyone,

I have a reproducible issue with an AlphaTheta DDJ-GRV6 on a Mac Studio running macOS Tahoe in combination with VirtualDJ.


Setup

Mac: Mac Studio (only USB-C ports used), macOS Tahoe

Software: VirtualDJ (latest version)

Controller: AlphaTheta DDJ-GRV6 (firmware up to date)

Connection: USB-C data cable from the GRV6 (USB PC/data port) directly into the Mac Studio

no hubs, no docks, no monitor USB hub or similar

the only other device connected to the Mac: a monitor via Thunderbolt 4

Audio: speakers connected to the GRV6, routing in VDJ is correct as soon as it is properly recognized

I tested both with and without USB POWER. Currently I am not using USB POWER.


Problem

After a restart/boot of the Mac, the controller is often:

not recognized by macOS at all (it does not show up in “System Information - USB”), or

only partially/half recognized.

In the “half recognized” state:

Audio sometimes works, sometimes not

In VirtualDJ I can sometimes only start the track (Play button) and possibly move volume/faders, but:

effects do not work

most LEDs do not light up

Play/Cue LEDs do not light up

jog LED feedback (e.g., rotating ring) is gone

It seems as if macOS enumerates only part of the device (e.g., audio), but not the full controller/MIDI/HID part.


Workaround

As soon as I briefly unplug and replug the USB-C data cable once, the GRV6 is immediately recognized correctly and afterwards:

full controller functionality is back

LEDs + FX work again

I want to avoid constantly unplugging it because I do not want to unnecessarily wear out the USB-C port.


Already tested

Different USB-C ports on the Mac Studio

USB POWER connected vs. not connected (does not reliably change the behavior)

Firmware up to date, VirtualDJ up to date

Checked Audio MIDI Setup / MIDI Studio (nothing suspicious, problem remains)

No hubs/docks in the chain


Questions

Is this a known issue on macOS Tahoe with the GRV6 (or VDJ + GRV6)?

Is there a workaround to “trigger” macOS to fully recognize the device after boot without physically replugging?

Is there anything on the VDJ side (reset/reinit, specific startup order, setting) that reliably prevents this?


Thanks - I can provide additional info/screenshots if needed.
 
Posted Mon 26 Jan 26 @ 10:53 am
oh, i just noticed i could have, or should have, logged into my vdj account, that’s why it says "no license", just to set the record straight, i do have a pro license :)
 
No one has an idea? 😌
 
Why does no one reply?!
 
Sounds most likely a failing port on the HW, you've seen problems at the o/s level so it's not vdj, it works a bit so there is comms, you've changed wire so it's not that.

Study input in mac midi monitor and wiggle the wire at the hardware point, see if that causes drop outs. Might be a case for return to manufacturer.
 
I would check with a third USB C cable too (yes I have lived with computers long enough to see a brand new "spare" cable being faulty as well)
 
Just to add some context: AlphaTheta support couldn’t help me either and kept insisting that this must be a VirtualDJ issue, even though I clearly communicated multiple times that the problem already occurs before VirtualDJ is even started.

By now I’ve tested more than three different USB-C cables (including brand-new ones). Wiggling the cable directly at the hardware does not cause any dropouts in macOS MIDI Monitor or MIDI Control Center - and once the connection is established, it stays stable. So this doesn’t behave like a classic loose cable or intermittent connection.

That’s exactly what makes this so frustrating: the issue shows up at the OS level, independently of VDJ, yet support keeps pointing back to software.

At this point I’m honestly considering returning the GRV6, even though I really like it a lot in terms of workflow and features, and switching to the FLX10 instead. I didn’t want to go that route, but after exhausting cables, ports, software checks, and support, I’m running out of options.

If anyone has seen something similar or has another idea, I’m still open.

Thanks for your replies so far guys :)
 
It seems it's easy to blame the software in order to get rid of an annoying issue that requires a serious deep dive from technical support to solve it..
Who would imagine that ?
 
You are using both USB connections, right ? One goes to your computer and the 2nd to a power-blick supply ?
I saw you said you tried both, but maybe the one you used is still not delivering enough power ?

Even though AlphaTheta says one USB (to computer) is good enough, i recommend to use both, so that all the necessary power is delivered to the controller.
 

.
 
I am currently using an ISY IWC 4065 (65W) power adapter, and I have also tested with the original iPad Pro power adapter as an alternative.
Whether the controller is powered via an external power supply or not does not change the behavior at all. The issue occurs in exactly the same way in all scenarios and is not resolved or improved by additional power.

My suspicion is rather that macOS Tahoe may not yet be fully supported, despite AlphaTheta stating that it is fully compatible. What makes this situation especially confusing to me is that I cannot find any reports online of users experiencing the same issue, which makes it hard to narrow down whether this is a broader compatibility problem or a very specific edge case.

Thank you for taking the time to look into this.
 
I would sugggest testing another DDJ-GRV6 to confirm that just Your unit is not faulty. Maybe You can still use (replacement) unit You wanted to use.
 
hey everyone - quick update on the whole controller situation.

unfortunately we never managed to pinpoint the actual cause of the issue. huge shoutout to the alphatheta support team though: we went back and forth through countless emails, videos, tests - they really tried everything to get to the bottom of it. in the end, they basically told me i’m running some kind of hardware/software combination where the problem can happen for reasons that aren’t realistically traceable or easily fixable. the weird part: on a friend’s windows 11 pc, the grv6 worked flawlessly.

i ended up switching to the ddj-flx10 and luckily i could still return the grv6. wasn’t exactly my plan to spend that much more money, but honestly - the flx10 worked perfectly right out of the box. even stuff like autogain and virtualdj actually remembering my settings after a reboot finally behaves the way it should, which never really worked right on the grv6 in my setup.

thanks a lot to everyone who took the time to help me troubleshoot - i really appreciate it! 🙏
 
I have been experiencing this issue now on windows PC with 2 different GRV6 controllers. Definitely a VDJ issue. Hopefully we can get a fix or we have to return my GRV6
 
This happens every time with the GRV6 and only in VDJ.

The controller does not have this issue when plugged in, with the same USB cable, with other DJ software Djay Pro or Serato.

It’s 100% a VDJ issue.

Good news? Just quit VDJ and restart it 2-3 times. That’s never failed.

Annoying, for sure - but solves it.