You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the codebase of mark's initial implementation of external control ther was the possibility to run several xwax instances at the same time.
advantage: different builds or feautures can be tested within one dj-session as its limited to a specific deck(instance). in case there is any problem with xwax, the specific deck-instance can be restarted without taking knowledge of the crowd/listeners.
but that would require more as the IP-argument when executing xwax-client...
The text was updated successfully, but these errors were encountered:
Currently OSC server bind to a ip:port, it would be hard to start
multiple server on 127.0.0.1 at the same port. It would need to modify
xwax-client and add port argument so we can control multiple xwax instances.
On 28/03/14 06:11 AM, othmar52 wrote:
In the codebase of mark's initial implementation of external control
ther was the possibility to run several xwax instances at the same time.
advantage: different builds or feautures can be tested within one
dj-session as its limited to a specific deck(instance). in case there is
any problem with xwax, the specific deck-instance can be restarted
without taking knowledge of the crowd/listeners.
but that would require more as the IP-argument when executing xwax-client...
—
Reply to this email directly or view it on GitHub #2.
Hi Olivier,
do you have plans to implement this feature in your xwax-client?
since a few weeks i have a pair of CDJ-1000 (additional to my 3 turntables)
As i am limited to 3 simultaneously decks with my Audio8DJ it would be handy to restart a specific deck (instance) with a different timecode without stopping xwax at all...
In the codebase of mark's initial implementation of external control ther was the possibility to run several xwax instances at the same time.
advantage: different builds or feautures can be tested within one dj-session as its limited to a specific deck(instance). in case there is any problem with xwax, the specific deck-instance can be restarted without taking knowledge of the crowd/listeners.
but that would require more as the IP-argument when executing xwax-client...
The text was updated successfully, but these errors were encountered: