V-Rack question

For seeking technical help with Digital Performer and/or plug-ins on MacOS.

Moderator: James Steele

Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Post Reply
dpg4macman
Posts: 283
Joined: Mon Aug 20, 2007 12:59 pm
Primary DAW OS: MacOS
Location: Central PA USA
Contact:

V-Rack question

Post by dpg4macman »

I decided to try using a v-rack for the first time and loaded it with five VI's. (ST2,MX4x2,Independence & Rhino)I am running 32 bit and noticed my memory meter glowing bright RED. With only two MIDI tracks recorded. Is this normal? I have noticed DP8 using more memory than DP6. I also tried this in 64 bit and was still having memory issues. I have a Mac i5 2.5GHz with 16g ram installed. I would think I shouldn't be having any memory issues. Is there a preference I need to set?

Any help appreciated,

mvh
User avatar
bayswater
Posts: 12489
Joined: Fri Feb 16, 2007 9:06 pm
Primary DAW OS: MacOS
Location: Vancouver

Re: V-Rack question

Post by bayswater »

If the meter you are looking at is the one that exists in DP, compare it to the one in Activity Monitor, and rely on that instead. It's not clear what the DP meters are telling us.

Other thoughts: I usually put each VI in a separate V-Rack so I can turn them on and off in the Chunks window to minimize CPU load. Also, have a look at Magic Dave's suggestion to run multiple instances of VIs rather than multiple MIDI tracks on a single VI. This distributes processing across the processor cores.

And, there's something about repairing permissions before using in DP 8 ...
2018 Mini i7 32G macOS 12.7.6, DP 11.33, Mixbus 10, Logic 10.7.9, Scarlett 18i8, MB Air M2, macOS 14.7.6, DP 11.33, Logic 11
User avatar
MIDI Life Crisis
Posts: 26277
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: V-Rack question

Post by MIDI Life Crisis »

If that's a multicore machine, put each VI instrument in it's own V-Rack. MagicDave says that distributes the load among the cores (or in separate tracks if you;re not using VIs).

The repair permission thing was (I think) when you update to DP 8.01. It repairs many audio things.
2013 Mac Pro 2TB/32GB RAM

OSX 10.14.6; Track 16; DP 12; Finale 28

LinkTree (events & peformances)
Instagram
Facebook

MIDI LIFE CRISIS
dpg4macman
Posts: 283
Joined: Mon Aug 20, 2007 12:59 pm
Primary DAW OS: MacOS
Location: Central PA USA
Contact:

Re: V-Rack question

Post by dpg4macman »

Thanks guys, I did pull out the activity monitor and have my cpu meters displayed. (4 processors - 2 cores) According to the activity monitor and menu meters I am only using 5 to 6g of the 16g memory so I suppose the DP meter is showing a false reading? I have better luck when I create a VI in it's own track vs. V-rack. The only instrument I use more than one instrument in for one instance is SampleTank 2 and I never have an issue with it. (That is unless I try 64 bit - gave that up - I wasn't seeing any benefit far as memory was concerned so I switched back to 32 bit)

Thanks again,

mvh
dpg4macman
Posts: 283
Joined: Mon Aug 20, 2007 12:59 pm
Primary DAW OS: MacOS
Location: Central PA USA
Contact:

Re: V-Rack question

Post by dpg4macman »

I turned off the "Audio Performance" function in control panel preferences. The big RED line for memory was driving me crazy. I'm not having any performance issues.

mvh
b.g.
Posts: 262
Joined: Wed Sep 13, 2006 8:35 am
Primary DAW OS: MacOS

Re: V-Rack question

Post by b.g. »

MIDI Life Crisis wrote:If that's a multicore machine, put each VI instrument in it's own V-Rack. MagicDave says that distributes the load among the cores (or in separate tracks if you;re not using VIs).

The repair permission thing was (I think) when you update to DP 8.01. It repairs many audio things.
Just a point of clarification I hope: A single V-rack may contain one or many strips. Magicd’s advice is to run one VI instrument per strip, not necessarily one VI instrument per V-rack.
MacBook Pro retina 2015, i7, 16GB, DP 10, M4
User avatar
MIDI Life Crisis
Posts: 26277
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: V-Rack question

Post by MIDI Life Crisis »

His response to me (on this board) seemed to indicate that it is essentially a 'per fader' issue. I understood it to mean one core for each fader so that would mean one VI per Vrack. I've not had time to evaluate that empirically.
2013 Mac Pro 2TB/32GB RAM

OSX 10.14.6; Track 16; DP 12; Finale 28

LinkTree (events & peformances)
Instagram
Facebook

MIDI LIFE CRISIS
b.g.
Posts: 262
Joined: Wed Sep 13, 2006 8:35 am
Primary DAW OS: MacOS

Re: V-Rack question

Post by b.g. »

MIDI Life Crisis wrote:His response to me (on this board) seemed to indicate that it is essentially a 'per fader' issue.
Agreed.
I understood it to mean one core for each fader
Agreed.
so that would mean one VI per Vrack.
I'm open to correction, but I don't follow here. As a single Vrack may contain one or more faders--like the Mixer--if a single Vrack has, say, four faders then each fader would address a separate core, no?
MacBook Pro retina 2015, i7, 16GB, DP 10, M4
User avatar
Booter
Posts: 39
Joined: Sat Jan 23, 2010 3:28 pm
Primary DAW OS: Unspecified

Re: V-Rack question

Post by Booter »

From what I understand the memory meter is showing how much of DP's available memory is used. In 32 bit mode DP can't access most of your mac's memory. Any 32 bit app can only access 4 gig of memory. The v-rack has nothing to do with your problem. You just loaded too much stuff into your synths for 32 bit mode. When I got DP 8 I switched everything to 64 bit and I'm never going back.
Digital Performer 2.7 - 8.0, Logic 9, PT 8, MacBook Pro Core i7 16 gig, Quad Mac Pro 6 gig, Mac Mini 2 gig, Roland XP-50, Kurzweil K2000, MOTU 2408 MK3, MOTU Mach 5 II, Ethno
User avatar
Shooshie
Posts: 19820
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Dallas
Contact:

Re: V-Rack question

Post by Shooshie »

b.g. wrote:
MIDI Life Crisis wrote:His response to me (on this board) seemed to indicate that it is essentially a 'per fader' issue.
Agreed.
I understood it to mean one core for each fader
Agreed.
so that would mean one VI per Vrack.
I'm open to correction, but I don't follow here. As a single Vrack may contain one or more faders--like the Mixer--if a single Vrack has, say, four faders then each fader would address a separate core, no?
One core per fader. Many faders per V-Rack. Many cores per V-Rack.

Shoosh
|l| OS X 10.12.6 |l| DP 10.0 |l| 2.4 GHz 12-Core MacPro Mid-2012 |l| 40GB RAM |l| Mach5.3 |l| Waves 9.x |l| Altiverb |l| Ivory 2 New York Steinway |l| Wallander WIVI 2.30 Winds, Brass, Saxes |l| Garritan Aria |l| VSL 5.3.1 and VSL Pro 2.3.1 |l| Yamaha WX-5 MIDI Wind Controller |l| Roland FC-300 |l|
User avatar
MIDI Life Crisis
Posts: 26277
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: V-Rack question

Post by MIDI Life Crisis »

Thanks for the clarification guys.
2013 Mac Pro 2TB/32GB RAM

OSX 10.14.6; Track 16; DP 12; Finale 28

LinkTree (events & peformances)
Instagram
Facebook

MIDI LIFE CRISIS
b.g.
Posts: 262
Joined: Wed Sep 13, 2006 8:35 am
Primary DAW OS: MacOS

Re: V-Rack question

Post by b.g. »

All is right with the world.
MacBook Pro retina 2015, i7, 16GB, DP 10, M4
Post Reply