General
merging two projects
Started by UniFly on .
Sign in or create an account to join the conversation.
Hi,
How can I merge two projects into different interfaces and avoid variable conflict? Maybe by using different Lemur Input/Output? What is the fastest way? - I know that I can change all the parameters if there is no good option.
It's required for Traktor+Ableton project.
How can I merge two projects into different interfaces and avoid variable conflict? Maybe by using different Lemur Input/Output? What is the fastest way? - I know that I can change all the parameters if there is no good option.
It's required for Traktor+Ableton project.
Hi
Couple of options of the top of my head...
Use different MIDI channels for the different interfaces - good if you will be running through a single port hardware io
Or use separate MIDI Targets - good direct to computer or via a multi port MIDI io
Hope that helps
MM
Couple of options of the top of my head...
Use different MIDI channels for the different interfaces - good if you will be running through a single port hardware io
Or use separate MIDI Targets - good direct to computer or via a multi port MIDI io
Hope that helps
MM
About channels:
There are ~2000 parameters in Traktor .tsi file (1-16 channel). It's very huge number:] Unfortunately, in Traktor it's not possible to replace .tsi channel automatically and in Lemur I can't do mass change, I guess.
So I have one option.
How to use different MIDI port/target for Traktor interface in Lemur?
There are ~2000 parameters in Traktor .tsi file (1-16 channel). It's very huge number:] Unfortunately, in Traktor it's not possible to replace .tsi channel automatically and in Lemur I can't do mass change, I guess.
So I have one option.
How to use different MIDI port/target for Traktor interface in Lemur?
Think of the Lemur daemon as a multi port MIDI interface
You can have some partsof your project communicating on MIDI target 0
And other parts communicating on MIDI target 1 - think another set of cables...
Each target has 16 midi channels . . . .
Traktor would need to reference each port as needed..
What exactly are you trying to do?
You can have some partsof your project communicating on MIDI target 0
And other parts communicating on MIDI target 1 - think another set of cables...
Each target has 16 midi channels . . . .
Traktor would need to reference each port as needed..
What exactly are you trying to do?
Thanks for your support. I was not configured MIDI1 in Lemur Daemon tool. Now it works perfect.
First interface with MIDI0 objects dedicated for Traktor
Second interface with MIDI1 objects dedicated for Ableton
First interface with MIDI0 objects dedicated for Traktor
Second interface with MIDI1 objects dedicated for Ableton
No worries, glad you got it sorted...
The multiple options possible with multiple targets is a powerful feature
Lots of different ways of approaching things here
Maybe use targets 1 & 2, and keep 0 as a generic one, most projects default to 0
Also you can set other targets for any hardware you have as well
The multiple options possible with multiple targets is a powerful feature
Lots of different ways of approaching things here
Maybe use targets 1 & 2, and keep 0 as a generic one, most projects default to 0
Also you can set other targets for any hardware you have as well