seandodds
Hi all hope you can help i run a acer nitro 17" and recently purchased newer 18" predator virtual dj runs great on other but as soon I try to connect to my sc live 4 I get a blue spinning ring and if I click anything virtual dj crashes any help would be greatly appreciated
Mensajes 8 hours ago
DJJamieFox
@Seandodds...
Two things you can try since this is a Known issue with InMusic drivers and Windows 11...
First, I will paste this is post...
From Pete via Discord:
We have a preview fix/workaround for the inMusic (AKAI, RANE, m-audio, etc.) driver hang.
This preview includes everything in the previous Dyanmic Ports fix preview (loopMIDI, rtpMIDI, etc.) as well as the change in behavior to work around the inMusic driver bug.
This fix changes how we close **all** drivers, so needs broad testing with many different third-party MIDI drivers and devices, as well as with m-audio, AKAI, etc. drivers. We’ve tested with the ones we have, and so far, so good.
We’ve tested with the Akai and m-audio devices we have. We’d like folks with older m-audio drivers and devices to test this as well. If you are currently blocked by not being able to use a device from this brand, it’s worth giving this a try.
Instructions
Turn on, and leave on, developer mode in `Settings > System > Advanced > For developers`. **For this preview plugin to remain working, you must leave developer mode enabled.** That’s just because the preview is unsigned, and we check for developer mode before we allow loading of unsigned service plugins.
If you have the previous KSA preview installed, please uninstall it from `Settings > Apps > Installed Apps`.
Then install this KSA preview.
I recommend rebooting afterwards to be sure.
The Installer
Attached is the installer for x64. As none of these drivers were previously available for Arm64, I’m not planning to put out an Arm64 preview. As with other previews, this is unsigned and so may throw up warnings when you run the installer.
**IMPORTANT: During the fourth week of April, there will be another MIDI update. To retain these fixes, you will need to uninstall and then reinstall this preview fix after the KB comes through in the 4th week of April.** Why? Because the in-box update resets the registration to the non-preview components in System32.
Bugs Fixes
The previous fixes for loopMIDI, rtpMIDI, etc. are all still in place in this preview.
InMusic drivers hanging the service (AKAI, m-audio, RANE, and many others).
Issue 953 WinRT MIDI 1.0 messages from same driver packet have different timestamps (primarily for djay pro)
Tested With
So far, we have tested this fix with these drivers:
AKAI MPK mini with AKAI driver
Roland UM-ONE in vendor mode with Roland Driver
loopMIDI driver
BomeMIDI driver
Rane Four
Rane One
Rane Performer
Rane 72MKII
These devices work, but have bad note data coming through in addition to the normal note data, so we had to update the Bytestream translator (BS2UMP Transform) to ignore the extra invalid data. With that change to the transform in place, these all work.
M-Audio Uno with MIDISPORT Windows Driver v6.1.3
M-Audio MIDISPORT 2x2 (old yellow/green and blue one) with MIDISPORT Windows Driver v6.1.3
M-Audio MIDISPORT 4x4 Anniversary Edition with same driver as the others
M-Audio MIDISPORT 4x4 Old yellow/green and blue one) with same 6.1.3 driver
M-Audio MIDISPORT 4x4 Old Silver one with same 6.1.3 driver
M-Audio MIDISPORT 2x4 (black one with black and silver faceplate) with same 6.1.3 driver
Needs testing with other devices, especially combined audio/MIDI devices, and inMusic brand DJ equipment. If you test and find it to fix the issue for you with one of those devices, please feel free to reply below with the device name/model so that others will know.
Known Issues
Surprise removal (powering off or unplugging the device while in use) can hang the service for 30 seconds or more with these devices. Don’t have a workaround for that yet.
The preview is in the original link at Pete’s Discord Group. Post Link: https://discord.com/channels/980245825202552942/1488704319271206933/1488704319271206933
Second, in the latest VDJ build you will find a checkbox to disable MIDI 2.0 under the 'Missing Controllers' section in settings.
The problem is an incompatibility between the new MIDI 2.0 in windows and most InMusic drivers.
Two things you can try since this is a Known issue with InMusic drivers and Windows 11...
First, I will paste this is post...
From Pete via Discord:
We have a preview fix/workaround for the inMusic (AKAI, RANE, m-audio, etc.) driver hang.
This preview includes everything in the previous Dyanmic Ports fix preview (loopMIDI, rtpMIDI, etc.) as well as the change in behavior to work around the inMusic driver bug.
This fix changes how we close **all** drivers, so needs broad testing with many different third-party MIDI drivers and devices, as well as with m-audio, AKAI, etc. drivers. We’ve tested with the ones we have, and so far, so good.
We’ve tested with the Akai and m-audio devices we have. We’d like folks with older m-audio drivers and devices to test this as well. If you are currently blocked by not being able to use a device from this brand, it’s worth giving this a try.
Instructions
Turn on, and leave on, developer mode in `Settings > System > Advanced > For developers`. **For this preview plugin to remain working, you must leave developer mode enabled.** That’s just because the preview is unsigned, and we check for developer mode before we allow loading of unsigned service plugins.
If you have the previous KSA preview installed, please uninstall it from `Settings > Apps > Installed Apps`.
Then install this KSA preview.
I recommend rebooting afterwards to be sure.
The Installer
Attached is the installer for x64. As none of these drivers were previously available for Arm64, I’m not planning to put out an Arm64 preview. As with other previews, this is unsigned and so may throw up warnings when you run the installer.
**IMPORTANT: During the fourth week of April, there will be another MIDI update. To retain these fixes, you will need to uninstall and then reinstall this preview fix after the KB comes through in the 4th week of April.** Why? Because the in-box update resets the registration to the non-preview components in System32.
Bugs Fixes
The previous fixes for loopMIDI, rtpMIDI, etc. are all still in place in this preview.
InMusic drivers hanging the service (AKAI, m-audio, RANE, and many others).
Issue 953 WinRT MIDI 1.0 messages from same driver packet have different timestamps (primarily for djay pro)
Tested With
So far, we have tested this fix with these drivers:
AKAI MPK mini with AKAI driver
Roland UM-ONE in vendor mode with Roland Driver
loopMIDI driver
BomeMIDI driver
Rane Four
Rane One
Rane Performer
Rane 72MKII
These devices work, but have bad note data coming through in addition to the normal note data, so we had to update the Bytestream translator (BS2UMP Transform) to ignore the extra invalid data. With that change to the transform in place, these all work.
M-Audio Uno with MIDISPORT Windows Driver v6.1.3
M-Audio MIDISPORT 2x2 (old yellow/green and blue one) with MIDISPORT Windows Driver v6.1.3
M-Audio MIDISPORT 4x4 Anniversary Edition with same driver as the others
M-Audio MIDISPORT 4x4 Old yellow/green and blue one) with same 6.1.3 driver
M-Audio MIDISPORT 4x4 Old Silver one with same 6.1.3 driver
M-Audio MIDISPORT 2x4 (black one with black and silver faceplate) with same 6.1.3 driver
Needs testing with other devices, especially combined audio/MIDI devices, and inMusic brand DJ equipment. If you test and find it to fix the issue for you with one of those devices, please feel free to reply below with the device name/model so that others will know.
Known Issues
Surprise removal (powering off or unplugging the device while in use) can hang the service for 30 seconds or more with these devices. Don’t have a workaround for that yet.
The preview is in the original link at Pete’s Discord Group. Post Link: https://discord.com/channels/980245825202552942/1488704319271206933/1488704319271206933
Second, in the latest VDJ build you will find a checkbox to disable MIDI 2.0 under the 'Missing Controllers' section in settings.
The problem is an incompatibility between the new MIDI 2.0 in windows and most InMusic drivers.
Mensajes 5 hours ago