Which Host is Best for this..?

[gdog]

Hi everyone,

I've been using these hosts: Orion Pro v7.0, FLStudio7, Phrazor and energyXT1 on my AMD 64bit dual-core WinXP HomeSP2 PC, and while I like many aspects of them, none let me work the way I want to. Hopefully you experienced KVR folk can help me choose the best host (that I don't own) after I tell you how I work/would like to work and what I like about the hosts I've used so far.

Okay, the most important thing for me is to be able to quickly map my midi controller rotaries, faders and buttons to VST synths and effects AND to SAVE these maps, so I can quickly load them in future projects. Phrazor lets me do this (this is my favourite thing about Phrazor!), but this brings me on to my next point.

To record high resolution/smooth CC data sent to multiple VSTs (Synths and effects) ideally in separate midi tracks, but most importantly at the same time. Phrazor lets me do this (not in separate tracks), but at the expense of a major bug that stops me from being able to use it live/realtime, namely there are loud pops in audio while recording automation.

Be able to create automation envelopes quickly for any VST parameter and which can be exported as midi files containing CC data.

The above 3 paragraphs contain the most important things for me, but if the host has these I would be very, very happy :

Have PDC, preferably automatically set up.

Be able to freeze and unfreeze tracks.

Have a mixer that's easy to link to my controller, a la FLStudio.

Mute and unmute tracks by pressing a button on my controller.

Must be able to drag n drop audio files into an audio track - 16,24,32bit WAVs are necessary, but more format support welcome.

Preferably, I'd like a host that is modular like energy XT, but without the midi-sync problems when using the main view. However, if the host has racks a la Phrazor, then I can live without it.

A proper sequencer a la eXT (and NOT like FLStudio's playlist) with a piano roll that has good shortcuts a la eXT.

Be Stable, and not contain bugs. FLStudio7 is stable for me, whereas eXT and Phrazor aren't (both contain big bugs especially when trying to record midi).

That's all I can think of for now. I tried Sonar6 when I took my keyboard to a mate's house, but had trouble setting up ACT, so would like to avoid that (and Project 5). Also, if I can't find a host that let's me do I what I want, I will very reluctantly buy Native Instruments Kore and load it into FLStudio. I really would not like to do this though, as it is quite expensive for me and also, I've heard there are quite a few bugs with the current verison of Kore.

Thanks for reading, I look forward to hearing any advice that you can give me on this matter

[fandango]

Okay, the most important thing for me is to be able to quickly map my midi controller rotaries, faders and buttons to VST synths and effects AND to SAVE these maps, so I can quickly load them in future projects. Phrazor lets me do this (this is my favourite thing about Phrazor!), but this brings me on to my next point.

To record high resolution/smooth CC data sent to multiple VSTs (Synths and effects) ideally in separate midi tracks, but most importantly at the same time. Phrazor lets me do this (not in separate tracks), but at the expense of a major bug that stops me from being able to use it live/realtime, namely there are loud pops in audio while recording automation.

Well, I'm damn drunk, but I shall attempt to suggest that ACT mapping in Sonar would be perfect for this.

Basically, ACT takes your MIDI controller and then allows you to assign your MIDI rotaries etc. to customized mappings for whatever object is in focus. So, If I have the Audio Track selected, rotaries 1 and 2 might control volume and pan, however, when I move the focus to a synth (say, Synth1) then rotaries 1 and 2 are mapped to the Cutoff and Resonance. It kinda foxed me at first, but now I find it indispencable. It's wonderfully customisable. You can switch from synth to track to EQ etc. and the rotaries/faders will point to your personalised choice of parameter.

[fandango]

I tried Sonar6 when I took my keyboard to a mate's house, but had trouble setting up ACT, so would like to avoid that (and Project 5).

Oops. Okay, so what was the problem you had with ACT?

[Dewaine]

Hate to sound like a fan boy but... P5. I do not use ACT and understand you had problems with it in Sonar.... but many use it in P5 without problems..... P5 is a $99 download and a steal. I have FL from '01 and XT as well and they are never used since I got P5....

Yes I read that you want to avoid P5 but gee.... what you describe fits it so well :]

And yes I am a "little" drunk, I guess Sonar and P5 users hit the juice on Saturday nights!

I am sure others will be on soon with other options for you, but I just have to give my $.02

[alby75]

For live Usine (www.sensomusic.com) is exactly for you.
Except for PDC which has no sens in live situation?!

[gdog]

Thanks for all the replies so far

Fandango, I agree ACT sounds perfect for this. The problem I had was I was using an old 2nd hand Evolution MK449 keyboard and it's not supported by the ACT presets (unlike the Edirol keyboards, which seem to be supported very well in Sonar). Parameters weren't automatically linking and I could only link Sonar objects not VST parameters, eg Sonar volume faders, and I'd have to do this manually with right click - it would not automap.

Dewaine, thanks for your reply, I will try the demo and see how it goes, but to be honest I don't think I'll like it, as it is by the same people who made Sonar and I can't get Sonar's ACT to work with my Evolution keyboard.

Alby75, thanks for telling me about Usine, I'm downloading it now and see how it is for me Also, I work both live and in my makeshift studio, but I think PDC would be useful for both situations.

Thanks again for all the replies so far, further suggestions welcome I will report back after testing Project5 and Usine (maybe a few days, and I'm fully aware of the deadline regarding Project5's sale )

[fandango]

Fandango, I agree ACT sounds perfect for this. The problem I had was I was using an old 2nd hand Evolution MK449 keyboard and it's not supported by the ACT presets (unlike the Edirol keyboards, which seem to be supported very well in Sonar). Parameters weren't automatically linking and I could only link Sonar objects not VST parameters, eg Sonar volume faders, and I'd have to do this manually with right click - it would not automap.

Ah, I think I know what's happening here (possibly!). I have an M-Audio Ozone and an EMU Xboard61 and I don't like the ACT presets that come with the Ozone (and I don't think the xboard has ACT presets at all). So basically scrap the presets, they're only meant as a handy guide for a few well-known controllers, and not a limitation!

1. Go to Options->Controllers/Surfaces...
2. Add a controller surface ("ACT MIDI Controller", <your input device>)
3. Go to Tools-> [Your new ACT Surface should appear as a menu item here]

You'll get this dialog:-


4. Assign your controllers manually. (i.e., left click along the top row one at a time assigning each rotary in turn, and again for the next row. you only need to do this once, you can save your MK449 as a custom preset)
5. Make sure that "Active Controller Technology" is Enabled. (it's off by default sometimes)

<you should be setup correctly for future projects now>



6. Open a synth/effect, press the ACT Learn button.
7. e.g., touch the GUI "cutoff" and "resonance" button
8. e.g., twist rotary 1 and rotary 2 on the MIDI keyboard
9. Press ACT Learn again and accept the mappings.
10. Synth will be assigned correctly whenever it's in focus. Use the ACT device dialog to see how things are set up. (that last screenshot is just to demonstrate, you don't need the ACT device dialog sitting there constantly, just close it once you're happy your device is working okay)

NOTE - something else that might trick you into thinking that a fader/rotary isn't working. By default, ACT uses "Match" capture mode. If you have your cutoff at, say, the halfway point, then it won't move the parameter until you've turned your rotary(or pushed your fader) up or down past that point. This is to stop parameters "jumping" when you switch between instruments. You can set it to "Jump" in the ACT dialogue Options page if you prefer that method.