"MIDI mapper"...erm, help?

[haydxn]

CC#6 is the 'data entry' controller; it's traditionally used with RPN and NRPN data.. you set the RPN/NRPN parameter number with the appropriate pair (98 & 99 or 100 & 101), and then you send the value via CC#6. that's what it means, i guess T is ignoring the fact that it has a number aswell

[braj]

I've tried it in Live 4 (excellent MIDI learn there, and the controller makes a power of difference)

I really wish T2's mapping worked like Live's, which is the best I've seen in a host. Everything can be mapped. It's outstanding.

What would be nice for T2.1 would be patch memory for the controller, available in a global menu. You could create presets for all of your different synths and effects, and for the mixer. Allow you to change presets via a key command as well, so you could change them quickly. You could use the same controller but change presets for different synths, mixing, everything very easily. I could live with just my Oxygen8 if T2 had this sort of feature.

[piaz]

Gottverdom, haydxn, is there still SOMETHING you don't know how to respond in less than 5 minutes ?

[haydxn]

erm... sorry i don't know the answer to that one

[IIRs]

My Oxygen8 controllers work fine..

You can create a mapped template by exporting a suitable edit as an archive: just import this and rename instead of clicking the "new edit" button.

And of course, don't forget the "Automation Options" page:

[braj]

My Oxygen8 controllers work fine..

You can create a mapped template by exporting a suitable edit as an archive: just import this and rename instead of clicking the "new edit" button.

And of course, don't forget the "Automation Options" page:

But what would work much better would be to be able to save and call up mapping 'patches' as needed, so within the same edit you could use your knobs for mixing and synth programming on multiple plugs. Say, I could have patches called Pro53, Synth1, Mixer, Master verb, etc and use a key command to scroll through them while I mix. Right now, you'd have to go remap the controller every time you wanted to use it for something else in your edit. Not too convenient IMO.

[ModuLR]

yes, VST based automapping would rock.. I s'pose if you've got a C4 or MackieControl you can do that already... unfortunately, I don't have one!

[IIRs]

I could see that being useful, but some synths offer integral controller mapping in which case you might be better off using that in the normal way..

Failing that, the "add all parameters" option at the top of the list may speed you up a bit.

[SaviorNeeded]

My Remote 25 has room for something like 40 set-ups; even my UC-16 has a bunch. This is not helpful to the conversation here, but I thought I'd throw it in because I am HAPPY that almost all of the software and hardware I've bought since starting this hobby a couple years ago have been better than I expected. This is not normally the case when I buy a couch or a restaurant meal or a magazine for example.

I make my buying decisions largely based on what I see here at KvR, so thanks much.

Tom

[braj]

Actually, I'm kind of excited about the idea. The thing is, if I have to rely on each synth's way of mapping controllers, or rely on doing it from my midi controller, I get confused as to what is affecting what and I just end up not using it as much. But if you could have one central place to be able to program everything, it would rock. It is 90% there already, all we really need is the ability to create presets in controller mapping view, and the ability to select them from the Automation menu.

This would be a killer feature that would make T even more powerful and flexible. Besides eliminating the need to set up mapping for every edit.

[ModuLR]

It would also be schweet.. if there was a recent params area on the Midi Mapper that keeps a list of the last 10-20 params adjusted. That way, one could just move the param you wish to automate on the VST, press [shift+ctrl+m], then map the parameter from the "recent params area" instead of fishing thru those parameter lists. Some VSTs have a sickening number of parameters to sift thru.

[SaviorNeeded]

Man, I'll say! Have you seen Cameleon 5000?

Tom

[headquest]

Good morning all!

Thanks for the help yesterday.

I half hoped that coming back this morning - after a PC powerdown, etc - this might just solve itself, but no such luck.

Still not working

[headquest]

secondly, does your controller simply send CC messages, or does it send sysex? I'm not sure that the control mapper will work with sysex.

looking at the ozonic webpage ... the controllers can apparently be programmed to do either ... so that MIGHT well be a possible issue ???

slainte rob

Can you clarify how this would be an issue? (In Live 4 it "worked straight out of the box" without changing any Ozonic settings)?

I'm gonna read the Ozonic manual over my morning coffee now. Wold have read it sooner, but its a freakin' PDF.

[headquest]

PS - Could my problem simply be that the Ozonic is so new out, and it's somehow slipped under Tracktion's net?

Having said that, it was instantly recognised as the MIDI and Audio in/out on the settings page.