DP 8 "Memory" performance bar at 80%?

[wonder]

I have a tricked out mac thats powerful as heck.

DP8 is running a little slow and the Memory bar in the performance window is at 80% or so constantly.
DP 7 NEVER had any performance issues.

Any clues?

[Gravity Jim]

If you're seeing a "Memory" bar, then you are running DP8 in 32-bit mode. You'll get better performance in 64-bit mode.

[wonder]

Darn. Some of my VIs and plugs won't load in 64.

This normal?

[Radiogal]

Yes, it´s absolutely fully normal.
To run DP in 64 bit mode (or any DAW for that matter) you need to update the VI and plugins to the 64 bit version (if they exist in 64 bit)

Or use a 32 to 64 bit bridge like jBridge.
There are a few other wrappers around that I don´t use.
jBridge is working great on my system.

[hrw]

Yes, it´s absolutely fully normal.
To run DP in 64 bit mode (or any DAW for that matter) you need to update the VI and plugins to the 64 bit version (if they exist in 64 bit)

Or use a 32 to 64 bit bridge like jBridge.
There are a few other wrappers around that I don´t use.
jBridge is working great on my system.

I can't believe finally after all these years how many heavy VI's i've got running in DP 8 64 bit.
Gone are the days of VE Pro and a slave computer for me. I've got a big orchestral temp and it's doing pretty good. This is awesome!
If possible update everything to 64 or use the above suggestion and then never look back!
All my plugs are 64 bit now. Good luck.

[wonder]

I'll try the wrappers first )

[wonder]

is this for only VST plugs?

Most all my plugs are AU.

[Incogneato]

Yes; it is for VST only, I to have lost some plugins. I lost MX4 I liked that one for odd sounds, I do have M5-3 and a few others.

[kgdrum]

is this for only VST plugs?

Most all my plugs are AU.

Lots if not most plugs come as VST's & AU.
I was surprised when I started using jBridge how many of my plugs were available as VSTs.
Some companies even recommend if you have a choice of VST vs AU to go with VST,from my understanding many plugs are actually written as VST's and put into a AU wrapper to work as an AU plug.
Using DP8 64bit with jBridge works well and jBridges tech support & developer Joao is awesome!

[Gravity Jim]

I don't use a bridge, but it was pointed out in another thread that Plogue Bidule (the world's most mysteriously named software) is an excellent 32-bit bridge for AU plugs.

[tommymandel]

Despite 3 emails with Joao, I can't seem to get jBridge to work for me. It's too bad, as I too see the Memory Usage bar hit 80% when I revert to 32 bit mode in order to run my NI Pro-53, IK Sampletron, Young Compressor, and other favored plug-ins and VI's.
I've made VST my Primary Format in DP Prefs, run the jBridge App, moved the created bridge files into the root Library from my User Library, because that's where all my plug-ins are. . .
Has anyone had trouble with this, and then figured out what they were doing wrong, leading to successful 32-64bit bridging? I could use a useful hint I often get the message : bridging files couldn't be created because proper location couldn't be found. I then go and find the bridging files which actually *were* created, at the Root Level, and move them into my VST folder as I mentioned above, but jBridged files still don't show up in DP's Prefs/Audio-Plug-ins List.
Thanks.
Otherwise, I may seek Plogueness in my quest for 64 bit harmony with legacy plugs and vi's.

[Radiogal]

Wait. you do not need to "move" the bridged files anywhere. This is set automatically from what I can recall.
Also No need to have VST as your primary choice of plug in format. I have AU as primary.
I let jBridge do it´s thing and then I´ll go to the Audio Plugin preferences and activate the VSTs that where bridged.
Rescan. That should be it.

[tommymandel]

Much thanks, RG, I will try again, encouraged by your comments and success at it. Maybe it's because ages ago I renamed my Home folder to Homey I thought I was being cool. Perhaps jBridge wants it to be the same as my user name, and that's why I get "can't create folder in desired location" type of alerts from jBridge. I won't move the created files anywhere. I'll keep AU as my preferred plug-in format, and I'll try to rescan, although I don't know how to re-scan plug-ins that do not even appear in that Preferences/Audio plug-ins Window...

[tommymandel]

[tommymandel]

Joao was very willing to help, but after maybe 5 or 6 emails, we ran out of ideas. For some reason DP 8 on my OSX 10.6.8 system will not see the bridged plug-ins. I am looking for them when DP is launched, and I open Preferences/ Audio Plug-Ins. If their names do not appear on the list (under 64-bit operation) then there seems no way for me to check their boxes, let alone rescan them. ("Reexamine" I believe DP calls it there.) In the Finder, they are all there, in the 'bridged plug-ins' folder inside my root/lib/audio/plug-ins/vst folder. You can see them. I've repaired permissions. I've (at Joao's suggestion, which I'd already tried anyway) moved them from my User/Audio/etc... folder to the Root/Audio/etc... folder. Trashed everything (including the files in Application Support) and reran jBridger. Tried making an alias. . . and undid everything before I tried the next thing.
I can see that others here are successful in using jBridge to run their 32-bit only plug-ins in DP in 64-bit mode. but for the life'a'me, i can't arrive at where I'm messing up the process. I have VST chosen as the main format, even though RadioGal says that's not necessary, btw. Oh, also, I downloaded the demo of bidule, and running that in standalone, the bridged plug-ins are accessible. I also used Onyx to delete the AU cache, but since it's VST's not AU's that this is about, that was probably a waste of time.
Just once, I saw a glimmer of hope. I went back to 32 bit mode, and in launching itself, DP scanned a whole bunch of VST instruments and plug-in efx that it obviously hadn't scanned before. A similar thing may have happened when Logic/Mainstage became able to use 32-bit Audio Unit Bridge - I had given up and gone back to 32-bit mode; then one time I decided to give 64-bit a try again, and voila! the 32-bit plugs automatically called up that fabulous app.