There's jack, there's EQUIS (which i love, amazing project, thanks a bunch!)
Now, if i have a jack connected librecdj player, I may as well spawn another instance and connect that to equis instead of having one instance with 4 decks.
Hey carl, happy you like EQUIS!
I think it shouldn't be too hard to only show one deck (and not register the other jack ports). But what is your usecase of having 2 seperate librecdj processes over one?
separate computers running separate instances.
Imagine, if you will, someone who runs his own, much worse, player on two or more devices and these devices consume "control messages" (really a thin wrapper over midi) over nats. (it's low-latency enough for this)
Ah interesting. Running it on two computers would also provide some sort of redundancy. What do you mean with nats?
oh, it's not even redundancy, it's just "Deck 1", "Deck 2" as physical machines, this setup has it's own external mixer.
Nats is https://nats.io/
oh, it's not even redundancy, it's just "Deck 1", "Deck 2" as physical machines, this setup has it's own external mixer.
Nats is https://nats.io/
Ah okay.
Coming back to this feature request, I could imagine implementing this for the egui transition in obsoleszenz/librecdj#53 . But I think I would generalize the feature a bit and make it possible to select between 1 to 4 decks. Also only having 2 or 3 decks is a valid user wish :D
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?