hi,
i don't know if someone had asked for this before.
I use energy xt and muzys.
In muzys i like the way you can, with a right click and simple procedure, asign a knob, slider, button..., of my midi controller to any part of the sequencer, vst synth or vst fx.
In muzys you can move with the mouse a fader in the mixer section or any other part, then right click on it and asign it directly to a real fader in my midi controller, a kind of "midi learn" function. it's easy and real quick.
Would like to know if its posible to do this in energy xt in a quick way.
It would be nice feature to improve the work flow, also if you using it live.
thanks
yoss
FEATURE REQUEST list - what do you want from energyXT2 ?
-
- KVRist
- 44 posts since 16 Nov, 2005
Command line args, As posted here http://www.kvraudio.com/forum/viewtopic.php?t=244121
-
- KVRian
- 1372 posts since 21 May, 2004 from Serbia
It is possible and it's pretty straightforward.yoss wrote:hi,
i don't know if someone had asked for this before.
I use energy xt and muzys.
In muzys i like the way you can, with a right click and simple procedure, asign a knob, slider, button..., of my midi controller to any part of the sequencer, vst synth or vst fx.
In muzys you can move with the mouse a fader in the mixer section or any other part, then right click on it and asign it directly to a real fader in my midi controller, a kind of "midi learn" function. it's easy and real quick.
Would like to know if its posible to do this in energy xt in a quick way.
It would be nice feature to improve the work flow, also if you using it live.
thanks
yoss
First you need to click on the button marked with number 1 on the screenshot. This will call the "controller map" window.
Then you click on the button marked with number 2. This will activate the midi learn mode.
First move a control in XT2, then move a control on your midi controller. When you're done click again the button 2 to deactivate midi learn.
-
- KVRer
- 2 posts since 30 Aug, 2005 from Maple Ridge, BC, Canada
Hello,
Presently I use Cuabase SX3, Kontact 2 (for loading a very large sampled grand), a Roland XV-5080 and a Yamaha 01x.
I am in the market for a new DAW and I would like to find one that will replace Cubase SX3.
Will energyXT be able to do the things I presently do with my current setup:
1. Control surface support for the 01x?
2. Creation of patch maps/patch listings for external hardware devices.
3. Use of program and bank changs (MSB/LSB) to control external hardware?
4. Use of SysEX?
I do not mind doing any of the work for the above, but I just need to know if energyXT will do what I am asking.
Thank you.
mr_es335
Presently I use Cuabase SX3, Kontact 2 (for loading a very large sampled grand), a Roland XV-5080 and a Yamaha 01x.
I am in the market for a new DAW and I would like to find one that will replace Cubase SX3.
Will energyXT be able to do the things I presently do with my current setup:
1. Control surface support for the 01x?
2. Creation of patch maps/patch listings for external hardware devices.
3. Use of program and bank changs (MSB/LSB) to control external hardware?
4. Use of SysEX?
I do not mind doing any of the work for the above, but I just need to know if energyXT will do what I am asking.
Thank you.
mr_es335
-
- KVRian
- 1224 posts since 2 Dec, 2008 from Finland
My twenty cents:
1. LASH support under Linux. LASH is a system which eases audio projects: it starts programs related to a project and automagically connects them in Jack, the way I wanted them originally. It's getting better and more supported by other audio applications and really is essential. http://lash-audio.org/
2. New track&tab type: automation. It would be easier to have desired automation lanes in their own tracks, allowing them to be muted as wanted (comparing different mixes) and generally more easier to find the automation you want to edit.
3. A VST-plugin to route audio in and out of Jack-applications. There are several 'effect rack' programs in Linux that can't be used alongside eXT right now. Some of you talented programmers hanging around here could maybe do this? (please please) Like this: I would add this plugin as a send in eXT, it would create a Jack plug that I could connect to another program's input and then connect the audio-out of that program back again to input of this plugin, allowing me to control it's volume in eXT.
1. LASH support under Linux. LASH is a system which eases audio projects: it starts programs related to a project and automagically connects them in Jack, the way I wanted them originally. It's getting better and more supported by other audio applications and really is essential. http://lash-audio.org/
2. New track&tab type: automation. It would be easier to have desired automation lanes in their own tracks, allowing them to be muted as wanted (comparing different mixes) and generally more easier to find the automation you want to edit.
3. A VST-plugin to route audio in and out of Jack-applications. There are several 'effect rack' programs in Linux that can't be used alongside eXT right now. Some of you talented programmers hanging around here could maybe do this? (please please) Like this: I would add this plugin as a send in eXT, it would create a Jack plug that I could connect to another program's input and then connect the audio-out of that program back again to input of this plugin, allowing me to control it's volume in eXT.
-
- KVRist
- 490 posts since 9 Dec, 2008
I would love to see values in relation to the nodes for automation. It can be a pain when you get a mix just right and then want to add a volume automation and can't get the node value to exactly match what the channel volume was at. Or, have the nodes independant and relative to the overall volume - i.e. you have a channel's fader volume at -9.25 dB. Have the automation node center "zero" position be the -9.25 dB with the ability to move both below (-inf dB) and above (+xx dB). Perhaps nit-picking but it would be nice. 
-
- KVRian
- 644 posts since 6 Nov, 2006
coma977 wrote:fr- the sampler to let you choose the midi channels (differents) to each sample you load up,
thanks.
yes!-
- KVRist
- 77 posts since 8 Oct, 2008
+1ras.s wrote: 3. A VST-plugin to route audio in and out of Jack-applications. There are several 'effect rack' programs in Linux that can't be used alongside eXT right now. Some of you talented programmers hanging around here could maybe do this? (please please) Like this: I would add this plugin as a send in eXT, it would create a Jack plug that I could connect to another program's input and then connect the audio-out of that program back again to input of this plugin, allowing me to control it's volume in eXT.
and midi out working with software midi ins - to control other programs with xt2
-
- KVRer
- 4 posts since 9 Dec, 2008
It will be very usefull if you had the possibility to snap to zero or middle value for control like pan or pitch wheel and other negative and positive controller.
For pitch wheel it's very dificult to make the bar at 8191.5
For pitch wheel it's very dificult to make the bar at 8191.5
-
- KVRist
- 483 posts since 7 Aug, 2005 from Germany
once again some FRs ....
destructive and non-destructive midi processing:
a) destructive: typical functions to perform midi processing like delete doubles, split notes into 2,3,4,... parts, double tempo, half tempo, fade in / out, quantize length, position, start position, end position, and the like.
b) non-destructive: use of midi plugins (vst or mfx) in sequencer view. currently, if you want some midi processing between sequencer and instrument plugin, you have to drop a midi vst onto the modular view and rewire it. that causes he problem that in sequencer view the given track isn't showing the instrument plugin but the midi plugin. actually that applies to all modular plugin chains. however, support for external and eventually internal midi plugins within the sequencer would be terrific. there may be dedicated section within the mixer strip, called "Midi Inserts" whatsoever. that's the "easy" solution for simple effects chains. one might argue that there are midi plugins, like the ones from toby bear, that have midi AND audio I/Os and therefore could easily chained within the actual audio inserts. however, these plugins only pass through audio and only have audio I/Os for easier insertion into insert chains. when speaking about non-destructive midi processing, only track based midi data (that within midi clips for a given track) is supposed to be used. the logic / information flow is as followed:
Sequencer -> Midi FX / Processing -> Instrument -> Inserts -> Audio Out.
unfortunately this isn't represented in modular view
at this point, I have to elaborate more so bear with me for a moment:
inserts and sends are not displayed in modular view when inserted via the sequencer.
there is apparently a friction between modular and sequencer based working that needs to be overcome imho. it is not logical to put an instrument visible onto the modular view when inserted into the sequencer whilst insert effects are not. we sure have the manual routing of audio flow within the mixer and the mixer strip in the sequencer. but it is not logical to have two classes of insert effects that serve the same purpose.
there are two use cases:
- first: simple, unambiguous routing (as done when only using the sequencer)
- second: complex routing (of audio and midi flows)
these two use cases are not represented in an appriorate way by now. well, I wouldn't point this out if I hadn't a proposal.
you might display all inserts in modular view as a effect chain after the instrument, eg. Instrument1 -> Insert1 -> Insert2 -> Insert3 -> Audio Out for Audio Insert or respectivly for Midi Inserts (non-destructive midi processing) Sequencer (MidiOut1) -> MidiInsert1 -> MidiInsert2 -> Instrument.
Or: introduce "helper" components for both purposes, ie. Midi Inserts and Audio Inserts which are put between Sequencer and Instrument or Instrument and Audio Out respectivly. doing this, you can have either an option in modular view "Expand/Show Inserts" / "Collapse/Hide Inserts" (globally for all or context-sensitive via right-click + options above) or the Insert components can be opened and edited via double click into a new window (that might be docked as well as other windows).
check this:
http://img6.imageshack.us/img6/5239/newmodularview.png
technical hint here: plugins might further be distinguished using VST opcodes and the already implemented awareness of what is wired within the project.
finally some notions for people coming from modular-only DAWs. strictly speaking, you wire "everything with everything" which gives you most flexibility. however, EXT2 is supposed to be a hybrid DAW in which you can either work in modular or sequencer-based fashion. therefore, the paradigm of being able wire completely freely doesn't apply to that extent. but no worries, the solution is already there: busses aka group components.
essentially, groups a what I've already noted as dedicated Audio and Midi Inserts. from my point of view, EXT2 has to be more strict using groups for routing to bridge the gap between modular and sequencer based working.
here is my specification commandment:
you shall not be able to route more than one audio output to a effect that only has one audio input. use the group component instead. if you try anyway, EXT2 has to create a group and put the effect inside of it.
while the group component can be used to solve the above mentioned dilemma, it still as different scope than the proposed Audio and Midi Inserts (or components if you like the better).
I know if come a long way with my proposals and to some it might appeal irrational to some degree since you the ability to assign different audio out targets within the mixer. but the sole purpose is to achieve a stronger coherence between sequencer and modular workflow.
so feel free to comment, refine, second or abolish my thoughts on this topic
destructive and non-destructive midi processing:
a) destructive: typical functions to perform midi processing like delete doubles, split notes into 2,3,4,... parts, double tempo, half tempo, fade in / out, quantize length, position, start position, end position, and the like.
b) non-destructive: use of midi plugins (vst or mfx) in sequencer view. currently, if you want some midi processing between sequencer and instrument plugin, you have to drop a midi vst onto the modular view and rewire it. that causes he problem that in sequencer view the given track isn't showing the instrument plugin but the midi plugin. actually that applies to all modular plugin chains. however, support for external and eventually internal midi plugins within the sequencer would be terrific. there may be dedicated section within the mixer strip, called "Midi Inserts" whatsoever. that's the "easy" solution for simple effects chains. one might argue that there are midi plugins, like the ones from toby bear, that have midi AND audio I/Os and therefore could easily chained within the actual audio inserts. however, these plugins only pass through audio and only have audio I/Os for easier insertion into insert chains. when speaking about non-destructive midi processing, only track based midi data (that within midi clips for a given track) is supposed to be used. the logic / information flow is as followed:
Sequencer -> Midi FX / Processing -> Instrument -> Inserts -> Audio Out.
unfortunately this isn't represented in modular view
at this point, I have to elaborate more so bear with me for a moment:
inserts and sends are not displayed in modular view when inserted via the sequencer.
there is apparently a friction between modular and sequencer based working that needs to be overcome imho. it is not logical to put an instrument visible onto the modular view when inserted into the sequencer whilst insert effects are not. we sure have the manual routing of audio flow within the mixer and the mixer strip in the sequencer. but it is not logical to have two classes of insert effects that serve the same purpose.
there are two use cases:
- first: simple, unambiguous routing (as done when only using the sequencer)
- second: complex routing (of audio and midi flows)
these two use cases are not represented in an appriorate way by now. well, I wouldn't point this out if I hadn't a proposal.
you might display all inserts in modular view as a effect chain after the instrument, eg. Instrument1 -> Insert1 -> Insert2 -> Insert3 -> Audio Out for Audio Insert or respectivly for Midi Inserts (non-destructive midi processing) Sequencer (MidiOut1) -> MidiInsert1 -> MidiInsert2 -> Instrument.
Or: introduce "helper" components for both purposes, ie. Midi Inserts and Audio Inserts which are put between Sequencer and Instrument or Instrument and Audio Out respectivly. doing this, you can have either an option in modular view "Expand/Show Inserts" / "Collapse/Hide Inserts" (globally for all or context-sensitive via right-click + options above) or the Insert components can be opened and edited via double click into a new window (that might be docked as well as other windows).
check this:
http://img6.imageshack.us/img6/5239/newmodularview.png
technical hint here: plugins might further be distinguished using VST opcodes and the already implemented awareness of what is wired within the project.
finally some notions for people coming from modular-only DAWs. strictly speaking, you wire "everything with everything" which gives you most flexibility. however, EXT2 is supposed to be a hybrid DAW in which you can either work in modular or sequencer-based fashion. therefore, the paradigm of being able wire completely freely doesn't apply to that extent. but no worries, the solution is already there: busses aka group components.
essentially, groups a what I've already noted as dedicated Audio and Midi Inserts. from my point of view, EXT2 has to be more strict using groups for routing to bridge the gap between modular and sequencer based working.
here is my specification commandment:
you shall not be able to route more than one audio output to a effect that only has one audio input. use the group component instead. if you try anyway, EXT2 has to create a group and put the effect inside of it.
while the group component can be used to solve the above mentioned dilemma, it still as different scope than the proposed Audio and Midi Inserts (or components if you like the better).
I know if come a long way with my proposals and to some it might appeal irrational to some degree since you the ability to assign different audio out targets within the mixer. but the sole purpose is to achieve a stronger coherence between sequencer and modular workflow.
so feel free to comment, refine, second or abolish my thoughts on this topic
-
- KVRist
- 483 posts since 7 Aug, 2005 from Germany
one more - a small one 
it would be cool to have an option to create several tracks with several midi channels linking to one instrument. speeds up using multitimbral instruments
and jorgen: if you really consider to take my ideas posted above into consideration I'd be happy to send you the graphics (svg) I've created for the new comps
it would be cool to have an option to create several tracks with several midi channels linking to one instrument. speeds up using multitimbral instruments
and jorgen: if you really consider to take my ideas posted above into consideration I'd be happy to send you the graphics (svg) I've created for the new comps
-
- KVRian
- 1329 posts since 25 Dec, 2005 from Devon, England
I'm with you on clarifying the relationship between sequencer and modular, gamble. Your suggestions make good sense to me.
I'm with olicana with the vertical zoom too.
I'll say this again - Proper MIDI for drum tracks please.
I'm with olicana with the vertical zoom too.
I'll say this again - Proper MIDI for drum tracks please.
"are we there yet?"
-
deleted deleted https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=1
DELETED