XT Software

lung · Post by **lung** » Tue Aug 15, 2006 9:39 pm

Hi Jorgen,

Is automap support on the table (still a possibility) for XT2?

I bought the Novation SL 37. Have Live Lite 5, and automap is quick VST tweaks with physical knobs/sliders. Makes the whole whole computer music thing much more like using an instrument for me.

eXT is the host with the right stuff for me, and I imagine soon XT2 will allow me to do the things I would have wanted Ableton for (well I have LiveSlice .. so there's not much I want Ableton for).. exception automap, as it's a serious workflow streamliner/optimizer. So much in fact that Ableton is calling me.. yet I don't want to complicate things with multiple hosts (sold T2 for that reason).

Automap saves one from switching templates, saving/reloading.. templates can be cumbersome when you use so many VSTs, and you just want to tweak random VSTs with your controller - you've got instant hardware access to parameters with automap.

I am going to try to get the SL's transport & MIDI clock generator to control eXT tonight.. anyone tried this.. possible? Works fine in Ableton.

BTW +1 for the metasurface/melohman/performance preset morphing idea in this snapshot/morphing thread.

Thx

disturb · Post by **disturb** » Tue Aug 15, 2006 10:00 pm

I've been holding back from buying one cause i wasn't sure how it would work with XT2...

Anyhow i believe it will be better than now since all plugins will be in the main, one will have directly access to plugin parameters from the seq (as opposed to cc mapping when loading multiple instances of eXT plugin).

It still seems like a proper implementation would be more difficult than for other hosts considering the modularity etc.

Wain and see...

jorgen · Post by **jorgen** » Wed Aug 16, 2006 4:50 pm

Is automap support on the table (still a possibility) for XT2?

Theres a possibility.

cheers
jorgen

djastroboy · Post by **djastroboy** » Wed Aug 16, 2006 4:52 pm

I plan to get an SL as well and would like to use it with eXT as well as Live.

soma · Post by **soma** » Wed Aug 16, 2006 8:45 pm

I'm in the same boat. I'm very interested to try out an Sl and if it works the way I hope, I'll get it.

lung · Post by **lung** » Wed Aug 16, 2006 9:10 pm

jorgen wrote:
Is automap support on the table (still a possibility) for XT2?
Theres a possibility.

cheers
jorgen

Thanks for your reply. Much appreciated.. I'll focus on creating SL templates for my synths (which I'll share when they're made), and we'll eventually see what secret technologies you weave into XT2.
cheers,
lung

lung · Post by **lung** » Wed Aug 16, 2006 9:21 pm

soma wrote:I'm in the same boat. I'm very interested to try out an Sl and if it works the way I hope, I'll get it.

Yes I initially bought the Remote LE 49 and the SL Zero so I could keep the keys separate from the knobs, idea was to have more flexibility (I like things modular), but I very much disliked the keys and knobs on the LE (very budget, quite heavy, despite being a Light Edition). The SL 37 (or 25/61) is a high quality instrument, and feels like it.. I exchanged the LE 49 & SL Zero for the SL 37, as they say, the difference was like night and day (a lot lighter to move around as well).

soma · Post by **soma** » Wed Aug 16, 2006 11:57 pm

How does the Sl function in XT?
Can you assign knobs 1-4 to parametrers in VST 1 and then switch the gui focus to VST 2 and have a whole new set of assignments.
Meaning the controller controls differnet things depending on what is in focus on the computer?
Sounds too good to be true...

lung · Post by **lung** » Thu Aug 17, 2006 3:02 am

soma wrote:How does the Sl function in XT?

Well, for now XT will only work with SL templates. Templates are the customizable setups that you have to manually change with an encoder like any traditional MIDI controller would. It's very easy to use. Having the encoders as well as knobs is great.. they are useful for different things, and coming from the analog world, I like the feel/direct control of analog pots for some things, whereas the encoder instant update (no jump) is also great. It updated the firmware to the latest OS automatically upon install of the software which was nice. You can import any Remote or X-Station template to create a quick SL template to work from. Lots of controller options:

Nicest thing is the LCD - can scroll through lists of parameters, can have each knob/slider work with 2 different setups (as far as I've learned in a few days anyways.. may be able to configure more) with the click of a button. Automap allows you to scroll up and down long lists of parameters for automap enabled hosts.

Automap is a different way of working. With an enabled host for example (like Live), if you click to focus on different areas of your host, all the sliders buttons etc. automatically configure to the host functions (e.g. volume, solo, mute, etc.).. then if you click on a VST, the buttons switch automatically to the parameters of the VST. You have to scroll through lines of parameters on the SL LCD display to get to the parameter you want sometimes, but they're all there. That's why you may want to create/use a custom template as well for your most used VSTs or a live setup.. whereas automap you just select the VST, scroll to the right line of the LCD, and tweak - better for everyday working - like trying-out VSTs in a song or tweaking some plugin - should never again have to use the mouse to turn a knob

.

I've owned a number of MIDI controllers over the years, and consolidated them all to the SL. It's by far the easiest interface I've used.. and the software works well, except the "Get names from VST plugin" feature in the editor to create a template (not automap) seems to crash the program on certain VSTs (MS-20.dll, reflex.dll, etc. - have yet to report to Ableton..).

Mind you, I just bought this thing and haven't had much time with it, so I'm sure my understanding of it is still limited. All I can say is that now that I've been using it a bit, I would not want to go back to a controller without the visual LCD strip the SL provides.. no more writing on strips of tape or dealing with those annoying template overlays, or guessing of what knob does what.

I think it would be very cool if XT2 was able to sync to the external MIDI clock this thing can generate, and be able to create tempo change automation from tweaking the tempo change knob on the SL.

Anyways, I'm obviously excited about this, I waited for years for something like this, and this exceeded my expectations which I deem good. Now maybe I'll run into more problems with time, but for now it's all good. =]

brendanw · Post by **brendanw** » Thu Aug 17, 2006 3:13 pm

+1 on automap support. I love my novation, and can only dribble at the thought of having automap implemented in xt2. Cheers, Brendan.

acid1 · Post by **acid1** » Thu Aug 17, 2006 4:30 pm

+1000 on automap, my novation SL is in hibernation atm

blakflag · Post by **blakflag** » Fri Aug 18, 2006 4:56 pm

Whatever capabilities Jorgen decides to include in XT2, I would hope he stays away from manufacturer-specific favoritism and go for more generic support. I'd love automap too, but Im on a Korg Kontrol49. Still havent forgiven Ableton for ignoring Korg for so long, then coding for Novation only, (when both technologies accomplish the same exact thing in the end)

When hosts program "new hotness" only for one line of controller it does nothing but alienate any customer who isnt on that controller.

jorgen · Post by **jorgen** » Fri Aug 18, 2006 7:09 pm

but Im on a Korg Kontrol49

can you control the function (text) displays with sysex?

btw, im all for generic support

jorgen

blakflag · Post by **blakflag** » Fri Aug 18, 2006 7:43 pm

Im not sure exactly how the displays get written but that would make sense. I can try to bug Korg for some documentation and get tell you what I learn though. I've been curious anyway.

But even without the displays, automapping would still be awesome. (even if the labels didnt show the parameters, as long as XT mapped each plug correctly.)

Oh here's an idea - you could have a big popup message on the *computer* screen as controllers got tweaked. For instance when I slide fader 1, on the computer screen it could say "OSC 1 (newval"). Thats what I really mean by generic support. Letting any controller that can send and receive midi CC reap the benefits, instead of only one particular proprietary SysEx protocol. (the unique controllers could have little extras for funtionality but everyone can have the base level)

Another random idea - let users make "image maps" of their hardware controller, like basically an image map of a bitmap picture of the controller, where they can define regions and say "oh yeah that region is CC #29, and its a endless rotary controller.". Then they could share this map with other users of that surface, and then everyone who owns that controller has it mapped for them and can just adjust the mapping for each plugin by clicking on bits of the image map and selecting from a option menu.

Sorry Im rambling.. just getting excited thats all.

soma · Post by **soma** » Fri Aug 18, 2006 9:14 pm

That is a great idea!

It doesn't have to be a pop-up. It would be nice if XT 2 had a small status field at the bottom of the window (like many applications have, IE, as an example).
This field could be context sensitve and display all sorts of good information, like parameter values, help, time, plugin cpu%, Ram usage, db output of a line, etc.
Making the field resizable to suit users' needs would be an even bigger bonus!

XT Software

KVR Audio

Dynamic MIDI Mapping (Sonar ACT) (..was Novation SL Automap)