124ds
Hello
I experienced problems when using more than on midi controller on Virtual DJ 2021(mac build 6242.1746).
One major problem is when using a Reloop 8000MK2 in combination with a Numark Scratch for the timecode and in addition a Numark MixTrack 3.
The midi buttons of the Reloop sometimes have a significant delay or do not working at all. When resetting the midi connector (cable on/off) the problem is mostly solved for a while. It seems that there is a cue for midi commands that is running full.
Also the timecode signal is sometimes not properly received/processed. In that case the deck plays while the needle is lifted up or sometimes even without the motor is on when pressing a midi button (mapped to a hot cue). This might be resolved when playing around with timecode signal on/off or pressing play/stop button on the Mixtrack.
Is this a problem with the setup at all or are there some tipps and hints for the problem described above?
Thank you and regards
Daniel.
I experienced problems when using more than on midi controller on Virtual DJ 2021(mac build 6242.1746).
One major problem is when using a Reloop 8000MK2 in combination with a Numark Scratch for the timecode and in addition a Numark MixTrack 3.
The midi buttons of the Reloop sometimes have a significant delay or do not working at all. When resetting the midi connector (cable on/off) the problem is mostly solved for a while. It seems that there is a cue for midi commands that is running full.
Also the timecode signal is sometimes not properly received/processed. In that case the deck plays while the needle is lifted up or sometimes even without the motor is on when pressing a midi button (mapped to a hot cue). This might be resolved when playing around with timecode signal on/off or pressing play/stop button on the Mixtrack.
Is this a problem with the setup at all or are there some tipps and hints for the problem described above?
Thank you and regards
Daniel.
Posted Fri 08 Jan 21 @ 11:14 am
PhantomDeejay
I believe that it's a limitation of recent versions of MAC OS X.
Which version are you using ?
Which version are you using ?
Posted Fri 08 Jan 21 @ 3:51 pm
124ds
Hello thank you
I am using 10.13.6. The problem seems specific for vdj.
I am using 10.13.6. The problem seems specific for vdj.
Posted Sat 09 Jan 21 @ 11:02 am
124ds
Hello
There might be a relation to the order of connecting the different controllers after the (re)start of vdj. When the Reloop is connected last, the issue occurs more likely as when it was connected first. Does anybody know if midi message handling is processed via queues and if there are different queues (for each controller)?
Thank you
There might be a relation to the order of connecting the different controllers after the (re)start of vdj. When the Reloop is connected last, the issue occurs more likely as when it was connected first. Does anybody know if midi message handling is processed via queues and if there are different queues (for each controller)?
Thank you
Posted Wed 13 Jan 21 @ 9:40 am
124ds
There are some more issues related to controller/audio setup. Sometimes audio settings (e.g. Headphone, Timecode) are lost. This as well as the MIDI problems discussed above is depending on the order of the various controller are connected /switched on. Reconnecting the controller solves the problems seriously. Is there a way to safe the order of the controllers in a setup?
thank you
Regards
thank you
Regards
Posted Mon 08 Feb 21 @ 3:14 pm
PhantomDeejay
It may be a longshot, but can you open MIDI Studio on your MAC (without any device connected) and DELETE all MIDI devices from there ?
Does that improve / solve your issue ?
Does that improve / solve your issue ?
Posted Mon 08 Feb 21 @ 7:04 pm
124ds
Hello, thank you.
No, it does not help. The problem occurs more likely (>90%) when starting (switch on) the controllers before vdj is started. When vdj is started while the controllers are already connected it works most of the time (>90%) regarding the audio problem and (>70%) regarding the midi communication.
Regards
No, it does not help. The problem occurs more likely (>90%) when starting (switch on) the controllers before vdj is started. When vdj is started while the controllers are already connected it works most of the time (>90%) regarding the audio problem and (>70%) regarding the midi communication.
Regards
Posted Tue 09 Feb 21 @ 4:11 pm
124ds
user20189735 wrote :
The problem occurs more likely (>90%) when starting (switch on) the controllers before vdj is started. When vdj is started while the controllers are already connected it works most of the time (>90%) regarding the audio problem and (>70%) regarding the midi communication.
Regards
The problem occurs more likely (>90%) when starting (switch on) the controllers before vdj is started. When vdj is started while the controllers are already connected it works most of the time (>90%) regarding the audio problem and (>70%) regarding the midi communication.
Regards
Sorry that was wrong. The problem occurs more likely (>90%) when starting (switch on) the controllers while vdj is already running. Switching the order is much better regarding the issue.
Posted Thu 11 Feb 21 @ 7:54 am