cparmerlee
Max Output Level: -67 dBFS
- Total Posts : 1153
- Joined: 2013/06/25 22:14:42
- Status: offline
Instrument track vs. separate MIDI + Audio tracks
I don't use any external hardware synths. Everything is a software synth. I'm trying to get a handle on best practices for that set-up. I am really struggling to understand why anybody would ever use what seems to be the more popular method, creating separate MIDI and audio tracks and then routing the MIDI into a synth, then the output of the synth into the audio track. It seems about 1000 times easier to simply insert an instrument track. As far as I can tell, this achieves the same result with much less clutter. You can put all the same audio effects on that track and do all the same automation. Where is there any benefit in doing it the long way around? I have been doing some arrangements with as many as 9 or 10 instrument tracks and this has been working great. Almost no drop-outs and the latency is not a big problem. I have not seen any need to freeze tracks. I tried it the other way this afternoon (splitting into separate MIDI and audio tracks). Not only was this far more cumbersome, it seemed to consume twice as much CPU power for the same exact voices, and this causes frequent drop-outs with most of the different synth modules. All the posts I have read seem to imply that the "proper" way to do this is with split tracks. My guess is that is the old way of doing things, and old habits die hard. I can't see a single advantage to that method -- and am at the point of concluding it isn't even viable on my computer hardware. Is there any advantage that I am missing? Why would anybody ever split tracks when they can simply insert an Instrument Track?
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 21:48:00
(permalink)
The Simple Instrument Track works fine if you have a single non-multi-timbral synthesizer being driven by a single MIDI track. And you don't mind losing a few of the controls. But if you're seriously into software synthesizers it's only a matter of time before you'll run into the limitations of the SIT. You may want to overlay two patches, slaving a second synth off the same MIDI track as the first. Can't do that with a SIT. You may want to use a multi-timbral sampler such as Kontakt for convenience and better CPU efficiency. Can't do that with a SIT.
 All else is in doubt, so this is the truth I cling to. My Stuff
|
sharke
Max Output Level: 0 dBFS
- Total Posts : 13933
- Joined: 2012/08/03 00:13:00
- Location: NYC
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 21:49:00
(permalink)
There are some problems/oddities with instrument tracks, like one I discovered the other day in which cloning an instrument track results in a track whose mix controls are all linked with the original track.
But other than this, if you're having no problems with them them just keep using them. I also feel that a lot of the people who swear by split tracks just do so because old habits due hard. For 95% of cases of using VSTi's I think there's no reason why having split tracks would be better than a simple instrument track. You're right, they're so much neater and more convenient. Can't say I've noticed any difference in performance though.
One day however, you might find the need to do something different like process the left and right sides of a synth's stereo output differently, and for this it's worth knowing how to set up audio tracks with synths by the more conventional method.
JamesWindows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
|
...wicked
Max Output Level: -1.5 dBFS
- Total Posts : 7360
- Joined: 2003/12/18 01:00:56
- Location: Seattle
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 22:02:07
(permalink)
All of the above, plus I'll add I like the organization of having them separate. I put all the synth audio tracks into a folder at the bottom of the project. This way I can MSR them as a whole. Then I put the MIDI tracks into folders grouped by instrument type (DRUMS, BASS, GTR...) Often times I'll have separate parts of the same synth that I'll keep on separate MIDI tracks for ease of workflow when arranging which helps tremendously. In music like electronica, where you tend to write by building up huge arrangements and then trimming down this is great. That said, inserting a synth is a pain becuase you have to do a bit of organizing, and bouncing down is a pain because you have to select both the MIDI AND the audio track (srsly, I wish they'd fix that).
=========== The Fog People =========== Intel i7-4790 16GB RAM ASUS Z97 Roland OctaCapture Win10/64 SONAR Platinum 64-bit billions VSTs, some of which work
|
SuperG
Max Output Level: -63 dBFS
- Total Posts : 1371
- Joined: 2012/10/19 16:09:18
- Location: Edgewood, NM
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 22:09:55
(permalink)
Drums - can never get them just right in a single stereo track. That's plenty of reason to split them out into multiple audio tracks.
|
cparmerlee
Max Output Level: -67 dBFS
- Total Posts : 1153
- Joined: 2013/06/25 22:14:42
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 23:11:03
(permalink)
bitflipper slaving a second synth off the same MIDI track as the first.
Aha. I didn't think of that. Thanks.
|
Jeff M.
Max Output Level: -80 dBFS
- Total Posts : 541
- Joined: 2012/09/22 03:02:04
- Location: RI, USA
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 23:11:23
(permalink)
I don't use SIT for all the reasons given above - multi-timbral synths, multi-out drums, organization, etc.
Platinum 64 RME UCX | Studio Cat Platinum: i7 2700k @ 4.5Ghz | 16Gb DDR3 | Win 7 64Komplete Kontrol S61 Gibson, Jackson, Parker, Suhr, Breedlove, Taylor, Lakland, Peavey, Marshall, Kemper
|
cparmerlee
Max Output Level: -67 dBFS
- Total Posts : 1153
- Joined: 2013/06/25 22:14:42
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 23:12:59
(permalink)
sharke process the left and right sides of a synth's stereo output differently,
That's way beyond my skill level at this point, but I can see that could make a difference.
|
cparmerlee
Max Output Level: -67 dBFS
- Total Posts : 1153
- Joined: 2013/06/25 22:14:42
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 23:15:58
(permalink)
SuperG Drums - can never get them just right in a single stereo track. That's plenty of reason to split them out into multiple audio tracks.
Can you please explain a little more about that? Do you send them to two different synths?
|
Jeff M.
Max Output Level: -80 dBFS
- Total Posts : 541
- Joined: 2012/09/22 03:02:04
- Location: RI, USA
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 23:40:30
(permalink)
Many drum VSTs have multi outs - separate outs for kick, snare (top & bottom), overheads, room, toms, etc. Each will typically have different fx added to them - comps, eq, verb "wetness".
Platinum 64 RME UCX | Studio Cat Platinum: i7 2700k @ 4.5Ghz | 16Gb DDR3 | Win 7 64Komplete Kontrol S61 Gibson, Jackson, Parker, Suhr, Breedlove, Taylor, Lakland, Peavey, Marshall, Kemper
|
SuperG
Max Output Level: -63 dBFS
- Total Posts : 1371
- Joined: 2012/10/19 16:09:18
- Location: Edgewood, NM
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 23:47:34
(permalink)
Jeff M. Many drum VSTs have multi outs - separate outs for kick, snare (top & bottom), overheads, room, toms, etc. Each will typically have different fx added to them - comps, eq, verb "wetness".
Exac-a-lackly!
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 23:53:51
(permalink)
cparmerlee
SuperG Drums - can never get them just right in a single stereo track. That's plenty of reason to split them out into multiple audio tracks.
Can you please explain a little more about that? Do you send them to two different synths?
One or more MIDI tracks go to a single synth that has many audio outputs.
|
cparmerlee
Max Output Level: -67 dBFS
- Total Posts : 1153
- Joined: 2013/06/25 22:14:42
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/12 23:55:45
(permalink)
Jeff M. Many drum VSTs have multi outs - Each will typically have different fx added to them
OK. Makes sense. Thanks. This gets me wondering, maybe an imponderable. Before all this DAW sophistication, it would have been possible, but really complicated, to do that level of processing all using hardware and miles of patch cords. And in the analog world, there is the issue of accumulating noise at every connection poiont. Is the level of fine tuning mentioned in this thread essentially the DAW equivalent of what always went on in the biggest studios? Or do DAWs enable levels of processing that were rarely attempted in the analog studios of the past? And another question along those lines. It has always been a truism that the best studios were distinguished by using the most expensive, exotic microphones. While I don't question that the most expensive mics can capture subtleties that other mics might miss, I wonder if a closet full of really expensive mics is as important today as it used to be.
post edited by cparmerlee - 2013/07/13 00:09:52
|
SuperG
Max Output Level: -63 dBFS
- Total Posts : 1371
- Joined: 2012/10/19 16:09:18
- Location: Edgewood, NM
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/13 00:14:36
(permalink)
Jeff M. Many drum VSTs have multi outs - Each will typically have different fx added to them
OK. Makes sense. Thanks. And another question along those lines. It has always been a truism that the best studies were distinguished by using the most expensive, exotic microphones. While I don't question that the most expensive mics can capture subtleties that other mics might miss, I wonder if a closet full of really expensive mics is as important today as it used to be.
It might make sense for a studio owner or big-time producer, but for Joe Homeslice, probably not. I'd bet a wooden nickel you could trip up a few folks using A-B blind comparos against Chinese and east European knock-offs. Of course, there are mic modeling plug-ins, such as the one Antares produces. Then again, those exotics are quite nice, and vanity has never been a sin in the music world...
|
jsg
Max Output Level: -69 dBFS
- Total Posts : 1079
- Joined: 2003/11/20 04:54:18
- Location: San Francisco, California
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/13 00:31:48
(permalink)
☄ Helpfulby rsinger 2013/07/14 14:19:29
cparmerlee I don't use any external hardware synths. Everything is a software synth. I'm trying to get a handle on best practices for that set-up. I am really struggling to understand why anybody would ever use what seems to be the more popular method, creating separate MIDI and audio tracks and then routing the MIDI into a synth, then the output of the synth into the audio track. It seems about 1000 times easier to simply insert an instrument track. As far as I can tell, this achieves the same result with much less clutter. You can put all the same audio effects on that track and do all the same automation. Where is there any benefit in doing it the long way around? I have been doing some arrangements with as many as 9 or 10 instrument tracks and this has been working great. Almost no drop-outs and the latency is not a big problem. I have not seen any need to freeze tracks. I tried it the other way this afternoon (splitting into separate MIDI and audio tracks). Not only was this far more cumbersome, it seemed to consume twice as much CPU power for the same exact voices, and this causes frequent drop-outs with most of the different synth modules. All the posts I have read seem to imply that the "proper" way to do this is with split tracks. My guess is that is the old way of doing things, and old habits die hard. I can't see a single advantage to that method -- and am at the point of concluding it isn't even viable on my computer hardware. Is there any advantage that I am missing? Why would anybody ever split tracks when they can simply insert an Instrument Track?
Let's say you're using a VST like Kontakt. And let's say you create a single instrument track. Now suppose you need 4 different instruments loaded into Kontakt, each on a separate MIDI channel. So now you create 3 additional MIDI tracks and route them to Kontakt. It works. The problem is that now when you trigger the active track and play back that instrument on MIDI channel 1, all the other tracks are receiving MIDI data as their tracks will "light up". You won't hear the other tracks, only the active track, but it's still not good monitoring practice to see signal where there is none. This is the situation where you want to create a separate MIDI and audio track--because when you add more tracks, the signals will be discreet. Since every software synth handles issues differently (some allow for multiple, simultaneous instruments, some don't, some allow for patch changes, some don't) it's best to decide on a case by case basis. For those synths that are only triggering one instrument at a time, then it makes sense to use a single instrument track. JG www.jerrygerber.com
|
jsg
Max Output Level: -69 dBFS
- Total Posts : 1079
- Joined: 2003/11/20 04:54:18
- Location: San Francisco, California
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/13 00:39:49
(permalink)
bitflipper The Simple Instrument Track works fine if you have a single non-multi-timbral synthesizer being driven by a single MIDI track. And you don't mind losing a few of the controls. But if you're seriously into software synthesizers it's only a matter of time before you'll run into the limitations of the SIT. You may want to overlay two patches, slaving a second synth off the same MIDI track as the first. Can't do that with a SIT. You may want to use a multi-timbral sampler such as Kontakt for convenience and better CPU efficiency. Can't do that with a SIT.
Actually, you can (I know it works, I've done it), but you shouldn't. Reason explained in my other post preceding this one. JG www.jerrygerber.com
|
icontakt
Max Output Level: -32.5 dBFS
- Total Posts : 4266
- Joined: 2012/03/04 08:18:02
- Location: Tokyo
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/13 00:59:17
(permalink)
There's a bug in grouping SITs. For example, load one instance of SI-Drum Kit, one instance of SI-Bass, two instances of SI-Electric Piano and record a take on each track. Then group the Solo buttons of the two electric piano tracks, solo them and start playback. Do you hear anything? In my case, no I don't.
Tak T. Primary Laptop: Core i7-4710MQ CPU, 16GB RAM, 7200RPM HDD, Windows 7 Home Premium OS (Japanese) x64 SP1Secondary Laptop: Core2 Duo CPU, 8GB RAM, 7200RPM HDD, Windows 7 Professional OS (Japanese) x64 SP1Audio Interface: iD14 (ASIO)Keyboard Controller/MIDI Interface: A-800PRODAW: SONAR Platinum x64 (latest update installed)
|
Glyn Barnes
Max Output Level: -0.3 dBFS
- Total Posts : 7564
- Joined: 2009/06/10 05:12:31
- Location: A Stone's Throw from the Line
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/13 01:04:59
(permalink)
I always use separate audio and midi tracks. - I find it more logical. Audio is audio and MIDI is MIDI, my simple brain finds the simple instrument track harder to comprehend.
For example I never quite get what the volume and pan faders do on an SIT, do they turn down or pan synth using MIDI or alter the volume and pan on the audio track. I suppose i could easily find out but it just seems easier to use a method where its all clearly layed out. - A lot of the time I use multi out and/or multi-timber synths. For example an instance of Kontakt may contain eight instruments, with 8 stereo outs, driven by eight midi tracks, An Instance of an hammond Organ VSTi (B4 II) with one audio track and three midi tracks (upper & lower manuals and pedels) or Superior drummer with one midi track and a multitude of audio outs.
- Track templates make the setting up of these scenarios easy.
- The "clutter" can be managed, X2's auto track zoom is a great feature. Track folders are another big help One solution is to hide the MIDI tracks in consul view and hide the audio
|
lowdown
Max Output Level: -85 dBFS
- Total Posts : 300
- Joined: 2004/04/14 16:07:38
- Location: Essex - UK
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/13 05:26:30
(permalink)
I have had a couple of problems with SIT's, regarding the staff view. When I try to do some edits, X2A crashes - and not on any on particular Synth. If I do the same thing the 'old' way, no crashes. Garry
|
lawajava
Max Output Level: -55 dBFS
- Total Posts : 2040
- Joined: 2012/05/31 23:23:55
- Location: Seattle
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/13 13:39:29
(permalink)
charmerlee - I don't know about your skill level playing your material, but my skill level on keys needs extra help - which is why I never use simple instrument tracks.
With separate midi / audio tracks I clone the midi track as often as I want, so that I have multiple take tracks. They all route to the same audio track. So I can do bits and pieces of my performance and get clean parts, but they sound seamless to the audio track.
You could do the same thing with Take Lanes I suppose, but I'm not an adopter of those yet. If not using Take Lanes, the approach I've mentioned above only requires one instance of the synth say for five take tracks. If you had five alternate take tracks with SITs you'd have five synths loaded, which takes up unnecessary CPU.
Two internal 2TB SSDs laptop stuffed with Larry's deals and awesome tools. Studio One is the cat's meow as a DAW now that I've migrated off of Sonar. Using BandLab Cakewalk just to grab old files when migrating songs.
|
rsinger
Max Output Level: -83 dBFS
- Total Posts : 387
- Joined: 2007/08/25 14:34:57
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/14 14:17:53
(permalink)
jsg Let's say you're using a VST like Kontakt. And let's say you create a single instrument track. Now suppose you need 4 different instruments loaded into Kontakt, each on a separate MIDI channel. So now you create 3 additional MIDI tracks and route them to Kontakt. It works. The problem is that now when you trigger the active track and play back that instrument on MIDI channel 1, all the other tracks are receiving MIDI data as their tracks will "light up". You won't hear the other tracks, only the active track, but it's still not good monitoring practice to see signal where there is none. This is the situation where you want to create a separate MIDI and audio track--because when you add more tracks, the signals will be discreet. Since every software synth handles issues differently (some allow for multiple, simultaneous instruments, some don't, some allow for patch changes, some don't) it's best to decide on a case by case basis. For those synths that are only triggering one instrument at a time, then it makes sense to use a single instrument track. JG www.jerrygerber.com
Thanks for the explanation. I was reading the thread thinking that I've done that, added additional midi tracks to a SIT, with Omnisphere and it seemed to work fine. I can see that when I decide to develop that particular idea/project further I'll want to reorganize it first.
Sonar Platinum, 64 bit, win 7 pro - 64 bit Core i7 3770k 3.5 Ghz, 16 Gb Ram, 480Gb + 256Gb SSDs, 1 Tb Velociraptor, Echo AudioFire4
|
cparmerlee
Max Output Level: -67 dBFS
- Total Posts : 1153
- Joined: 2013/06/25 22:14:42
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/14 20:17:03
(permalink)
Today I decided to experiment a little more in this area. Before ramping up on SONAR, I had purchased the Garritan Jazz and Big Band library for use with Finale. The latest version of that library comes with the Aria player. I added Aria to the VSTs synths available in SONAR. And this has the side-benefit of including the basic orchestra voices that Garritan bundles with Finale 2012. When I added Aria to my project, I had a choice of "regular" Aria or "multi" Aria. I think this means that the regular one has a single stereo output, and you can only select "0/1" as the output for each Aria channel. I presume this means that Aria mixed based on the MIDI channel inputs. That all makes sense to me, as it should be a pretty efficient way to run a lot of similar instruments, and they will all dump to the same audio track. In other words, that would be a pretty clean solution if you wanted the same effects (collectively) on all the instruments running through Aria. But when I selected "Aria multiple" (and further selected the option for mono outputs), I ended up with 32 audio tracks in SONAR. I can see that this would certainly be flexible because each of those 32 outputs could theoretically have its own effects chain. But what a mess visually! And it seems to me, so far at least, that lots of effects can be the enemy of a glean mix. So at least I think I understand what is possible, but I an not so sure this will lead me to a better result as the master bus hits the eardrums. I do have a 25" monitor (plus a smaller second monitor), but that doesn't seem nearly large enough to make these really complicated routing scenarios coherent.
|
robert_e_bone
Moderator
- Total Posts : 8968
- Joined: 2007/12/26 22:09:28
- Location: Palatine, IL
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/14 22:09:16
(permalink)
I never have the Insert Soft Synth dialog box insert my tracks for me, for that very reason. The synth I most often use for multiple instruments is Kontakt 5, and I only happen to prefer checking the box for opening the synth properties page (the Kontakt UI). I then load up whatever instruments I am including in that particular instance of Kontakt, redo the Output Section routing assignments (including renaming the outputs to better match the instrument, such as Piano, Bass, etc.), and then I add only the number of audio and midi tracks needed for each instrument. The whole process is quite speedy, and works flawlessly. Note - I choose to limit each instance of Kontakt 5 to load 5-6 instruments) I did the same thing with Battery 3, and have several projects set up with different custom kits loaded, with each kit piece routed to its own output channels, and I already have a Drums track folder with a midi track and all of the needed audio tracks already set and pre-leveled (as a starting point for any new project). That approach REALLY saves me a bunch of time and gives me complete control over each and every kit piece, which is a dream come true over using a couple of hanging mics to capture the whole kit - from years past. Anyways, hope that helps. Bob Bone
Wisdom is a giant accumulation of "DOH!" Sonar: Platinum (x64), X3 (x64) Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22 Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64 Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms
|
joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/14 22:41:47
(permalink)
Bob, if I may ask, what do you tick in the Insert Soft Synth options box and why? I have always used the Simple Instrument Track option (as well as the Synth Property), but a lot of what is being said on this thread makes sense. So much so that I am considering changing my methods to suit. Dennis
|
cparmerlee
Max Output Level: -67 dBFS
- Total Posts : 1153
- Joined: 2013/06/25 22:14:42
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/14 23:23:52
(permalink)
robert_e_bone The synth I most often use for multiple instruments is Kontakt 5, and I only happen to prefer checking the box for opening the synth properties page (the Kontakt UI). I then load up whatever instruments I am including in that particular instance of Kontakt, redo the Output Section routing assignments (including renaming the outputs to better match the instrument, such as Piano, Bass, etc.), and then I add only the number of audio and midi tracks needed for each instrument. If I understand things correctly, you can further simplify by selecting the same output channels for similar instruments -- for example, 4 separate trombone voices might be put to the same output channel, and therefore end up in a single audio track. This would save a lot of clutter, and would be essentially the same thing as sending 4 audio channels to their own sub-mix bus. Is that a reasonable scenario?
|
robert_e_bone
Moderator
- Total Posts : 8968
- Joined: 2007/12/26 22:09:28
- Location: Palatine, IL
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/15 00:17:25
(permalink)
Well, I wouldn't normally choose to do that, as I would want the ability to control each trombone voice completely separately in Sonar, rather than within Kontakt. For instance, you could not apply automation to individual trombone voices if you had them all combined within Kontakt to one output channel, nor could you apply any Sonar audio effects to individual trombone voices - reverb, EQ, delay, phase, etc. (you would only get to use what was in Kontakt). If I had a bunch of brass instruments to deal with, I would likely load them all into a unique instance of Kontakt 5, route each instrument to its own audio output, and to corresponding audio tracks in Sonar, along with individual midi tracks, all grouped under a track folder for Brass. That keeps everything grouped, where you could expand/collapse as needed, AND preserve complete control over all aspects of each brass instrument's sound. Bob Bone
Wisdom is a giant accumulation of "DOH!" Sonar: Platinum (x64), X3 (x64) Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22 Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64 Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms
|
joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/15 01:54:02
(permalink)
Bob, did you miss my question to you prior to cpalmerlees post?
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/15 02:04:25
(permalink)
While waiting for Bob, try this for the equivalent of a SIT check "MIDI Source", "Synth Track Folder" and "First Synth Audio Output" For multi-out synth check "MIDI Source", "Synth Track Folder" and "All Synth Outputs: Stereo" For multi-out synths with mono outputs you could also use "All Synth Outputs: Mono" instead of "All Synths Outputs: Stereo"
|
joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/15 02:44:08
(permalink)
Thanks Scook
|
robert_e_bone
Moderator
- Total Posts : 8968
- Joined: 2007/12/26 22:09:28
- Location: Palatine, IL
- Status: offline
Re: Instrument track vs. separate MIDI + Audio tracks
2013/07/15 05:44:01
(permalink)
I did miss your question, joden - sorry. The options in the Insert Soft Synth dialog box are there to do some of the work for you, and which ones you use are entirely up to you. As Scook posted above, to auto-generate midi/audio tracks per the scenarios he describes would work, and there is nothing wrong with setting them that way. My own personal preference is to simply leave all boxes un-checked, except for the one to open the synth properties page, because for me and my brain, inserting a single midi and one or two audio tracks for a synth that I am only using 1 set of outputs for is super fast, and I would NEVER myself choose to use the ALL outputs choices, because I would invariably end up with a whole bunch of extra tracks I would have to go back and delete. Also, the synth I MOST often load multiple instruments with multiple midi channels and multiple outputs is NOT properly handled anyways by any of the options - for how I use tracks. I am referring to Kontakt 5, which is usually the synth I use that supports multiple instruments and multiple outputs. (Battery 3 is my other one, but I already have a bunch of custom kits and customized routing assignments for that set up as project templates). So, for Kontakt 5, if I have loaded up multiple instruments for a given instance of it, then NONE of the check boxes would have it generate multiple midi tracks (I would want a separate midi track generated for each loaded instrument, and the check box choices do not support that), and NONE of the check box options would generate the precise number of audio tracks I would need, as I personally choose to limit the number of loaded instruments into a single instance of Kontakt 5 to either 5 or 6, because of some quirks in Kontakt's audio Output Section and how it displays tracks for Input assignment for audio tracks in Sonar. So, since I limit myself to 10-12 outputs, there is no check box combination that would auto-generate that precise number of audio tracks, and I would end up with manual work anyways, either adding or deleting tracks. And, lastly, I don't feel like checking and removing checks each time I am inserting a synth (depending on the synth containing multiple instruments or not), I just prefer to do the track insertions manually. I also, in ANY case, have to go manually rename each track, set panning, and for midi set channels for synths with multiple loaded instruments going to multiple midi channels, so I just do the whole thing manually, and I rarely, if ever, miss doing something, where I might if a lot of that was auto-generated. Again, this is all my own preferences, and the reasons behind them. Other folks use or do not use particular checked boxes for their approach. My approach works for me, and is always the same - set up needed midi and audio tracks manually, to exactly match what is needed for each instance of an inserted soft synth. I hope any of that helps, it is really just personal choice - the above are the choices I made, and the rationale behind them. Bob Bone
Wisdom is a giant accumulation of "DOH!" Sonar: Platinum (x64), X3 (x64) Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22 Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64 Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms
|