Version of operating system Horizon OS latest as of July 25th 2025:
Version of djay 1.1.0:
Hardware/controllers used *Numark DJ2Go2 *:
The volume levels of the track don’t show visual update(no clipping etc shows) when turning the master level knob nor the track level knob on the Numark DJ2Go2 controller.
The headphone jack on the DJ2Go2 isn’t outputting any CUE volume of the selected track (cue level is on max and headphone cue button for the track is lit)
**How to reproduce the issue: play any track and see the green volume LED dots on the display.
Turning the hardware controllers knobs for master and/or level on the DJ2Go2 controller has no effect.
Ditto for headphone jack on the side of DJ2Go2 controller. No cue volume of any track is output
Hi @dirrogate, thanks for the details about your setup and the issue. I don’t have a DJ2GO2 to check for myself so I’ve passed this onto the hardware team. Are you experiencing issues like this with any other DJ hardware or only with the DJ2GO2?
It’s the only controller I have access to and was bought specifically to create a portable “deck in a bag” setup of quest+hardware controller with soundcard setup.
I’d have thought these scenarios were checked / vetted; though a search for ‘headphones’ on this forum is throwing up many similar issues with other controllers/platforms.
Further - even from the main popup menu that comes up on first connecting the midi controller (asking if you want sound output from Hmd or controller) —despite choosing controller for output, even the headphone socket on the MetaQuest 3 is outputting the master out.
P s. Also the issue of the LEDs not visually reflecting the proper sound levels when turning knobs on the DJ2Go2 controller
.
To eliminate the possibility of the headphone jack on the DJ2Go2 being faulty, I installed serato lite on a PC. Headphone jack works fine.
So, to recap: As of today, The MetaQuest3 cannot be used as a live DJing solution (for me) with DJay, because:
The Hardware controller; Numark DJ2Go2 does not output pre-cue over the dedicated headphone jack on the controller
grabbing user-folder content from the “air crate” will eventually show black records and then stop playing audio, forcing a restart of the app
even if using the Quest3 controllers, fingers accidently trigger critical buttons due to placement / locatio of these buttons (solution is to have the Quest3 controller trigger button pressed to signal intent on menu buttons)
This is all besides the nice to have frills like visually seeing the TT decks even when using a slim midi Dj controller like the Numark DJ2Go2
Hi @dirrogate, following from the DM you sent me. Our Quest Hardware team has receive a DJ2GO2 unit for testing the headphone issue and the artwork bug. They should be able to give a more detailed response by the end of the week. I hope that helps!
Hi again @dirrogate, our hardware team tested the DJ2GO2 controller today and the multi-channel output works (headphone output plays pre-cue, main output plays main output). Can you please confirm you are selecting “Controller” and not “Headset” on connecting the device when choosing which output to use?
Hi @Slak_Jaw I can confirm it’s not working for me.
I downgraded my MetaQuest3 to regular OS update. Currently running OS v79.1023 (I have now lost PTC OS beta privileges as a result)
Yes I select controller audio as output source and hear the “please position the passthru rectangle…etc”
what is happening is there is NO output from the headphone socket of the DJ2Go2 TOUCH controller (i use the DJ2Go2 TOUCH if that’s helpful info)
what I have noticed is, the pre-cue channel volume LEAKS into the main output volume no matter where the cross fader is.
also if playing say, platter 1 and moving the cross fader fully to side 1 and having master knob on the controller at full…but ALSO raising the pre-cue volume knob of side 1, this then raises the total volume output of side 1.
This should not happen. It means the pre-cue volume is leaking into the main output.
This leak of pre-cue volume into the main output is an indication of some bug/ error in audio handling of the software. Likewise this leak of pre-cue audio happens even for side 2. (If pre-cue button for side 2 is pressed and knob volume of side b is increased WHILE cross fader is fully to side 1)
note: when using the controller with my PC and serato lite, everything works as intended (no leaks of audio, pre-cue buttons and knobs work as does the headphone output on the controller )
Meanwhile , again confirming no pre-cue audio is coming out of the headphone socket on the DJ2Go2 TOUCH controller.
Can your team check:
what version of Metaquest3 OS they are using
are they indeed using a Metaquest3 or is it Metaquest S or Metaquest 2?
really disappointed it’s not working.
Hoping for a solution.
Hi again @dirrogate, while we wait for the hardware team to respond, let’s check some things:
Looking at the DJ2GO2 Touch user manual, I see this hardware has a Mini USB socket. How exactly are you connecting it to your Quest 3? Are you using a direct USB Mini to USB-C cable or some kind of adapter? Have you tried connecting with different cables and/or adapters? It’s possible this connection could be leading to the audio bleed.
Are you selecting the Headphone Cue buttons for each Deck on the DJ2GO2 to send the audio to the headphones?
a. For example, you should have the Crossfader set all the way to the Deck 1 side, and the Headphone Cue for Deck 2 turned On.
b. In this scenario only Deck 1 should be playing through the speakers and only Deck 2 should be playing in the headphones
Looking at the manual, it does not appear that this hardware has a Cue/Mix dial for the headphones. Are there any other controls on the side or bottom of the hardware?
1 - I’m using the original cable that comes with the DJ2GO2 Touch (mini usb to A). For the record it works perfect with a PC running serato lite. I’ve also tried multiple usb A to C adaptors that I know for sure are functioning with my MetaQuest3 both for PD and data.
2 - yes. Doing exactly as you ask in point 2 above .there is definate audio bleed going through the main output from the pre-cue level knob (on both side 1 and side 2 as is labelled on the DJ2Go2 touch)
3 - i understand there is no mix/cue fader or knob. And that the “level” knobs for 1 and 2 are the actual volume faders for the two channels. Yet, it’s the pre-cue level knob (marked cue level) that bleeds into the main output when turned up.
Meanwhile NO output is routed to the headphone socket located on the Right side of the hardware controller. there are no other sockets / knobs on the back, under, or side of this controller.
This might come as a bit left field…but hopefully the hardware team is more than a single gen z intern assigned
But bad / snide joke aside, I’m really hoping this can be sorted out.
I can’t tell you the real joy of Dj club culture , where as a guest Dj, you can literally whip out this cute controller (because hand tracking is jittery in low light club environ) —plug in good ear buds and your headset is the decks that can even ‘cast’ your performance to screens around where punters “see” themselves in-the-mix so to speak along with those "upcoming " old school style vinyls being displayed via the “air crate”
We know the MetaQuest3 also primarily runs under Android.
Can it be that hardware people at Algoriddim are not specifically testing for quirks in different controllers?
For instance, it’s concerning that the Numark DJ2Go2 Touch is clearly listed as supported for the MetaQuest 3, which made me go out and buy it… But now we learn that the hardware dept. Only just bought/got one of these controllers because of the bug I’ve reported ? @Slak_Jaw
Hi again @dirrogate, our hardware team did additional extensive testing today with the Quest 3, Quest 3S, on OS v78.0 and the “DJ2GO2 Touch” and the “DJ2GO2”. OS v79.xxxx is not yet available for download in our region so we are unable to test with it. They confirmed that the headphone and main outputs are performing as expected with none of the audio bleed or headphone output issues that you have described.
hi @Slak_Jaw I consider myself fairly advanced in troubleshooting matters and I have to give-up in this case. As i’d mentioned
to rule out the possibility of a faulty cable/physical headphone circuitry/jack on the DJ2Go2 TOUCH itself…I installed serato lite that comes with the controller and everything works as expected (pre-cue sound comes from the headphone socket)
I then tried multiple connecters and cables for the mini usb to usbC connector on the MetaQuest3 and NO it’s not routing pre-cue to the headphones.
Also it isn’t leaking pre-cue audio to the main output of the DJ2Go2 TOUCH hardware. It’s fully “routing” pre-cue audio to the main output
So unless the hardware team can upload a video proving it all works as intended , I’ll just have to chalk this down to a massive bad spend of money on my part
P.s. is the Quest dev team inhouse or an outsourced outfit? (A nagging feeling in me says they’re third party?)
Hi @dirrogate, thanks for the additional info and feedback. Our dev team is in house, however, our main Quest developer is currently on summer vacation. I should have more news to share when they return from vacation next week. Thanks again!
Hi again @dirrogate, as noted above, our engineer performed extensive testing on Meta OS v78 and could not replicate the issues you are experiencing with the DJ2GO2 Touch - everything is working as expected on our end. Meta OS v79.xxxx has not rolled out in our region yet so we have not been able to test the DJ2GO2 Touch on this OS yet. As soon as this version is available, we will do more testing. In the meantime, if possible, can you revert to Meta OS v78 on your Quest to see if your issues persist? I hope that helps!
Hi @Slak_Jaw ,
There isn’t a way afaik, to switch to a lower OS. A reset will simply load the most recent stable OS.
however, forgive me as I’m still skeptical about claims made by your MetaQuest engineer based on these assumptions:
we know Djay is having problems with routing pre-cue audio in Android. The myriad of complaints on threads in this forum refer to the same topic of no pre-cue audio on Controllers.
The Meta Quest is in part based on Android OS
The only sure fire way to prove that pre-cue audio is going to the DJ2Go2 headphone output is to have a video recording showing this.
What I can tell you is:
it does not happen for me. precue audio does not go to the headphone socket
what does happen is the pre-cue audio gets routed and merged through the main output socket.
The above can be experienced by louder audio signal and sound coming out the main output in the DJ2Go2 when turning up the knob of the Cue (pre-cue volume)
I guess I’ll have to resign to the fact that if there is no video proof from the engineer - it’s just their word over my experience
it’s not working.
