AudioMasters
 
  User Info & Key Stats   
Welcome, Guest. Please login or register.

Login with username, password and session length
November 12, 2007, 08:41:45 AM
62097 Posts in 6146 Topics by 2111 Members
Latest Member: cereboso
News:   | Forum Rules
+  AudioMasters
|-+  Audio Software
| |-+  Adobe Audition Wish List
| | |-+  VSTi support
  « previous next »
Pages: [1] Print
Author
Topic: VSTi support  (Read 1191 times)
« on: January 27, 2007, 11:00:15 PM »
charles.monteiro Offline
Member
*****
Posts: 74

WWW

wow, I feel very lonely, to record a soft synth/sampler like SFZ without a hazzle seems to me to be a must. Apparently, not a biggie with anybody else i.e. according to the posts I see on the wish list.
Logged

Reply #1
« on: January 28, 2007, 06:48:53 AM »
ozpeter Offline
Member
*****
Posts: 2138



Most people using Audition are not into midi and VSTi and so forth - they'd presumably already be using a different program if they were.  So there's not that many people asking for it.  However, if Audition had such features it might attract people who currently don't look twice at it.  And, IMHO, if done correctly those who don't want such stuff would hardly know it was there.
Logged
Reply #2
« on: January 28, 2007, 11:22:41 AM »
SteveG Offline
Administrator
Member
*****
Posts: 8246



The argument against VSTi in Audition has always been that there isn't any point in supporting a plugin when you can't access all of its features. The line basically goes that because external MIDI direct MIDI input facilities don't exist within the prog, it's pointless running plugins that require it to work.

Personally I don't see why they couldn't be run though, with one relatively simple modification. It would, in fairness, not affect the operation or clutter the prog up at all, and if it was left at that, it would be fine. All that is required is that the MIDI stream that can be outputted from Audition if you import a MIDI file be directed to the input of the VSTi. That way you could 'play' your VSTi without requiring a massive (and quite unneccessary for most users) extension and cluttering of the multitrack screen. The one thing that the majority of current users absolutely don't want is all of those extra menus and screens involved with MIDI all over Audition - they would just get in the way.

If you added MIDI facilities to Audition, then they are either going to have to be as fully-developed and comprehensive from the outset as current MIDI software, or the prog is going to get crucified in comparative reviews. I don't believe that there is anywhere really for Adobe to go along this route that won't lead them into very murky waters, quite frankly - and I think that this is pretty much the way they see it too. Adding VSTi replay facilities from an imported file is one thing that they could do without any real penalties, but going any further than this would be starting to slide down a very slippery slope.
 
Logged

Reply #3
« on: January 29, 2007, 01:20:37 AM »
ozpeter Offline
Member
*****
Posts: 2138



I agree with part of what you say, SteveG - that adding full midi functionality to Audition would have to be done stunningly well to avoid adverse comparison with others further down the development track.  The developer of Reaper hit this problem early on, when its audio capabilities were very well developed but its midi side was very much an afterthought - the comments were pretty scathing.  It's since come on somewhat from there but it probably wouldn't be the first choice of someone much more midicentric than audiocentric.

However, the Reaper interface is a very good example of how you can have midi functionality without it showing.  And using it as an example, you could easily add better VSTi support than you are suggesting without ruffling anyone's feathers (IMHO).  Here's how it could be done -

The input button beside each track could have a "midi" option added - so it would read

None
Stereo >
Mono >
Midi >
etc

That would provide for linking your midi keyboard to the program and for recording midi data.

Then, you'd need a record mode selection, which maybe could be a right click on the track arm button (to cut down on interface clutter) - the options being

Record input
Record output

Recording input would record audio pre effects like at present, or midi data if the input was midi.

Recording output would record audio post effects (not usually a good idea) or the audio from a VSTi if one was among the effects on the track.

Of course you'd also have to allow for adding VSTi instruments to the effects rack.

This would allow you to insert an existing midi file onto a track and play it back through a VSTi - or to record a midi file in sync perhaps with other material on other tracks - or to record audio rather than midi from a VSTi, treating it much as if it were a real instrument being recorded with a mic, or an external sound module plugged into the line in socket of your soundcard.

What it would not do would be to provide for midi editing.  However, if they did want to go down the midi editing trail, then simply double-clicking on a midi file clip would bring up the midi editor - otherwise, you wouldn't see it.

Now how does that sound?  Wouldn't that add a lot of function without making it something un-Audition-like?

Logged
Reply #4
« on: January 29, 2007, 02:15:33 AM »
SteveG Offline
Administrator
Member
*****
Posts: 8246



The input button beside each track could have a "midi" option added - so it would read

None
Stereo >
Mono >
Midi >
etc

That would provide for linking your midi keyboard to the program and for recording midi data.

Then, you'd need a record mode selection, which maybe could be a right click on the track arm button (to cut down on interface clutter) - the options being

Record input
Record output

Recording input would record audio pre effects like at present, or midi data if the input was midi.

{et seq}

Now how does that sound?  Wouldn't that add a lot of function without making it something un-Audition-like?

Well at a first glance it would, but it would immediately run you into problems with existing functions - like SMPTE for instance, which my limited solution avoids compromising.* However you look at it, it's not going to be that simple to implement, even if it looks simple on the outside. And this has probably got as much as anything to do with why MIDI hasn't been offered in any than the most rudimentary form so far.

*It's okay to superimpose MTC onto an output stream, which is what happens at present I believe, but to have any sync slave operation running with a concurrent input from a keyboard isn't so easy at all. Mind you, this has to be sorted out anyway...  rolleyes
Logged

Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Valid XHTML 1.0! Valid CSS! Ig-Oh Theme by koni.