Hi @dirrogate, I’m really sorry to hear that you don’t want to believe what our engineer is saying. I can assure you they are not lying and making claims that it works when it doesn’t. In my years of experience helping in this Community, I’ve seen many cases where users had isolated issues that we could not replicate on our in-house, seemingly identical, setups. There are many reasons why this can occur. Our engineers are very busy with multiple projects across several platforms, so I’m not going to bother them with a request for video proof that they are not lying. I hope you understand.
Perhaps if this doesn’t meet your satisfaction and you don’t want to wait until they receive the latest v79 for further testing, we could pursue a refund of your djay purchase. Additionally or alternatively, as I fully understand your frustration with the issue you’re experiencing on Quest, I could look into offering you an extended free trial of djay on one of our other platforms. Please let me know what you think and how you’d like to proceed. Thanks!
Thanks @Slak_Jaw ,
I’ll wait it out. The big damper and disappointment comes because I went out and bought the DJ2Go2 touch expressly believing it would make for a portable, compact VR only setup at clubs for guest Dj gigs with coolness factor (chromecast would send the passthru Metacast view to screens in venues)
This is only because the controller is listed as supported. But I’ll have to wait.
Thank you for the 7 day workaround trial of Djay Pro for PC. Again, it was only to see workflow between Djay Pro PC and the MetaQuest for playlist and crate building.
As it stands, there’s no compatibility for songs meticulously “hot cued” and looped in the PC version to carry over when the same songs are loaded to the MetaQuest.
By itself, I do not intend to DJ with a PC (I’m exclusively Evangelizing VR DJing to clubs and Djs too)
Hello again @dirrogate, I have some news for you. Our Quest hardware testing team finally received the Horizon OS v79 update. They are now experiencing the same audio issues as you’ve described.
So, something has changed in this OS update that has broken the audio routing for the DJ2GO2 Touch. This probably isn’t the news you were looking for, but at least we can replicate this issue now. Our engineering team will investigate this further to determine what changed and caused this issue. I’ll report back here when I have more news. Thanks!
Yeah definately not what I was hoping for, but still…this gives hope. fwiw, the pre-cue audio is being routed to the main output.
As a side note, I’ve been constantly tweeting to @RealityLabs at Meta to support and work with devs in the Music industry (ive mentioned Algoriddim and the developer of the excellent Synthspace VR)
Perhaps a direct reach out to Reality Labs from you guys is recommended. So they can’t go breaking things with each successive release, willy nilly
On the other two issues:
You’d mentioned that the team had found out what the cause for black records in the local library was. can we have a hot fix for this? it’s getting impossible to use local songs stored on the quest (unless one remembers to NOT pull the records from the ‘air crate’)
also the inclusion of the virtual decks when using the DJ2Go2 Touch controller.
P.s. you might now want to re-check if the same audio routing issue messes up with the other controller(s) you have working with DJay for MetaQuest
Thanks for the additional feedback and suggestions @dirrogate. Regarding the points above, we will not be releasing a hot fix for this. The team is working on a larger update for Quest which should include this fix. We are already testing if this audio issue affects other DJ controllers as well. Thanks again!
