VI outputs question

Discussion of Digital Performer use, optimization, tips and techniques on MacOS.

Moderator: James Steele

Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
Post Reply
edledbury
Posts: 15
Joined: Wed Apr 19, 2006 4:03 pm
Primary DAW OS: Unspecified

VI outputs question

Post by edledbury »

O.K. this may be a dumb question but......

Why does DP not publish the first pair of audio outputs from a VI in the instruments bundle list? I'm remaking my orchestral template and have decided to use multiple instances of VE PRO rather than using the (buggy) Event Input plug. As a result, I now have 26 or so instances of VE PRO spread over 2 auxiliary pcs. In the interest of efficiency, I'm trying to keep my outputs prefs to a minimum. In practice, that means 6 outputs per instance. The trouble is that only outputs 3+4 and 5+6 appear in the instruments bundle. Outputs 1+2 are obviously still available via the Plug-In output, but it makes organizing the template and routing tracks to Auxes (for monitoring) and Audio tracks (for printing) more complicated than it needs to be.

Is there anyway to have DP publish those outputs alongside all the others

Thanks,

Ed
User avatar
FMiguelez
Posts: 8266
Joined: Sun Oct 24, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Body: Narco-México Soul/Heart: NYC

Re: VI outputs question

Post by FMiguelez »

Because 1-2 are assigned to the actual VI instrument.

What I did was to leave those alone in a V-Rack and start my return audio track assignments on 3-4 on a normal chunk.

The ones in the rack are just there to enable/disable the VE Pro connection and to privide sound for newly assigned instruments (in VE Pro) that have not been routed yet. No big deal.

If you need to not "waste" bundles, you'll be surprised by how many you save if you route mono instruments to mono bundles.
Mac Mini Server i7 2.66 GHs/16 GB RAM / OSX 10.14 / DP 9.52
Tascam DM-24, MOTU Track 16, all Spectrasonics' stuff,
Vienna Instruments SUPER PACKAGE, Waves Mercury, slaved iMac and Mac Minis running VEP 7, etc.

---------------------------

"In physics the truth is rarely perfectly clear, and that is certainly universally the case in human affairs. Hence, what is not surrounded by uncertainty cannot be the truth." ― Richard Feynman
edledbury
Posts: 15
Joined: Wed Apr 19, 2006 4:03 pm
Primary DAW OS: Unspecified

Re: VI outputs question

Post by edledbury »

Here's the problem - if I only use the additional outputs (3+4 and upwards) I need to to add an extra stereo pair to my VE PRO prefs, thus adding upwards of 24 unused additional stereo pairs that have to be buffered.

I don't see why outputs 1+2 can't appear alongside their neighbors, allowing me to name them properly and select them as an input for an aux or audio track. Right now, for example, I have an instance that is hosting a variety of pianos. Ivory, a Wurli, an Upright and some accordions.
Ivory and the Upright are routed to outputs 1+2, the Wurli to 3+4 and the accordians to 5+6.
In the instruments bundle list, the Wurli and the accordions are listed and are available as audio inputs whenever I add a new audio track, but the pianos have to be specially routed via a bus or their own aux. It's cumbersome and unnecessary.
frankf
Posts: 1133
Joined: Tue Oct 19, 2004 10:01 pm
Primary DAW OS: MacOS
Location: NYC
Contact:

Re: VI outputs question

Post by frankf »

Create (and name as VIx 1-2) a bus in the Bundles>busses. Assign the VI instrument track output 1-2 to VIx 1-2 bus. Create an Aux Track with bus VIx 1-2 as input. Place it next to the other VIx Tracks (3-4, etc) and there you go
Frank


Frank Ferrucci
DP 8
Mac Pro 3,1 OS 10.6.8, 24gb RAM
Metric Halo 2882, ULN-2
Frank Ferrucci
http://www.ferruccimusic.com
Mac Pro 6,1 64gb RAM DP9.52 OSX 10.12.6 MIO 2882d & ULN2d Firewire Audio Interfaces, MOTU MTP-AV USB
edledbury
Posts: 15
Joined: Wed Apr 19, 2006 4:03 pm
Primary DAW OS: Unspecified

Re: VI outputs question

Post by edledbury »

As I said, given that all other outputs from a VI are automatically published as potential audio inputs, having to assign the first pair to a specially created bus is cumbersome. I know perfectly well how to do it, I just wish I didn't have to.....
frankf
Posts: 1133
Joined: Tue Oct 19, 2004 10:01 pm
Primary DAW OS: MacOS
Location: NYC
Contact:

Re: VI outputs question

Post by frankf »

edledbury wrote:As I said, given that all other outputs from a VI are automatically published as potential audio inputs, having to assign the first pair to a specially created bus is cumbersome. I know perfectly well how to do it, I just wish I didn't have to.....
I didn't read where you knew how to do it, just trying to be helpful.


Frank Ferrucci
DP 8
Mac Pro 3,1 OS 10.6.8, 24gb RAM
Metric Halo 2882, ULN-2
Frank Ferrucci
http://www.ferruccimusic.com
Mac Pro 6,1 64gb RAM DP9.52 OSX 10.12.6 MIO 2882d & ULN2d Firewire Audio Interfaces, MOTU MTP-AV USB
User avatar
charlesparente
Posts: 144
Joined: Fri Jan 07, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: VI outputs question

Post by charlesparente »

edledbury wrote:Here's the problem - if I only use the additional outputs (3+4 and upwards) I need to to add an extra stereo pair to my VE PRO prefs, thus adding upwards of 24 unused additional stereo pairs that have to be buffered.
Another factor in this decision about outputs/bundle routing is exactly how do you want to do your VI mixing?

Inside VE Pro??

inside DP's MIDI or audio 'return' tracks??

Depending on your decisions, it's feasible to have a single audio out for a single VEP instance and not worry about the bundle routing, but if you want to do all mixing inside DP
then there's little choice but to manually configure the bundles, deal with Auxs, etc.

I like Fernando's idea about placing the VI default output (1-2) in a v-rack!
Charles
http://www.dptips.net [...my very humble tribute to DP]

DP 8-latest version, Mac OS 10.9.4, MacMini 2012, 16GB RAM, Metric Halo ULN-2d, MOTU Micro-Lite usb MIDI interface, Vienna SE, VE Pro, Kontakt latest version, many Kontakt VIs and libraries.
Post Reply