I am experiencing the pad mode issues that other users have mentioned before when using the VCI 400 with Ipad.
My question is this… Why does the Algoriddim website say that the controller is fully supported, when it appears it is not.
Am I missing something, or are things being promised falsely? If I am right, I can only hope the website is updated so other users aren’t conned out of membership prices.
Device Model ( iPad Air 5th Gen):
Version of djay (most up to date):
Hardware/controllers used (VCI 400):
Hardware Firmware Version (21):
Hi @Alladthepungent, when creating new topics, please do not forget to answer the questions in our template with specific details about your setup not just “iPad” or “Latest Version”. This helps all of our community moderators to provide the most effective support to users with the utmost efficiency. Thanks!
Device Model (ex. 2020 iPad Air 4th Gen):
Version of operating system (ex. iOS 17.3.1):
Version of djay (ex. 5.1.3):
Hardware/controllers used (ex. Reloop Ready):
Hardware Firmware Version (ex. 2.7):
Can you please describe in more detail what isn’t working for you?
I have just updated my post, apologies.
The performance pad modes are not hardcoded, they set loop lengths instead of selecting which mode (ie cue, loop, roll)
After discovering the lack of automatic support, I presumed I could midi map the buttons, but you cannot map performance pad modes with DJay Pro
Thank you for the additional details @Alladthepungent. This is helpful. I’m afraid I still don’t fully understand the issue. Can you please try to capture a short video of the issue, upload it to your Google Drive/Dropbox, enable sharing permissions, then share a link to the video here? Then I can share this with our engineering team for further review and testing. Thanks!
I just want to repeat, that this is the original model. I have an adhesive overlay on my controller which says that it is limited edition, this isn’t true.
Thanks for the video @Alladthepungent. That explains it! Definitely doesn’t look like expected behavior. I’ve passed this onto the engineering team to see if they can replicate the issue and offer any suggestions.
- In the meantime, can you please confirm that you are using the built-in MIDI mapping and not a custom edit?
- I’m pretty sure there are still a few variations of the Vestax VCI-400 firmware out there. Can you please confirm the specific details and where you downloaded it from? Thanks!
Yeah of course, thanks.
It is the built in MIDI mapping. The firmware was downloaded from the Serato website. The only other firmware I’m aware of is the SE edition firmware which is incompatible with the original vci-400.
Thanks for the additional info @Alladthepungent.
So, did you install the standalone mixer firmware 2.0 or the second one in the list?
I’ve forwarded this to our hardware engineer, but unfortunately, he’s out sick today. I’ll report back here when I have more news though. Thanks!
I’m not using the standalone firmware, I’m using the Serato firmware.
Have you worked out what the problem is with this yet? whether it’s software or hardware based?
Hi @Alladthepungent, unfortunately our hardware team hasn’t been able to locate our VCI-400 from storage yet. We need this to try to replicate your issue and troubleshoot it further. I’ll report back when I have more news.
Is there any update on whether this has been looked into yet?
Hi @Alladthepungent, unfortunately our hardware team hasn’t been able to find our last remaining VCI-400 yet. As you can imagine, these controllers are hard to come by these days so getting a replacement could be challenging. I’ll push the team again though…
