Hello again everyone! ... and a question, of course :)

[tyronehowe]

@MIDI Life Crisis: Hello Michael! Thanks for the welcome. I have had a look at your site – very interesting! That’s quite a catalogue you have there…

I have used some big-ish templates with Logic, so I’m hoping to try the same with DP. Once the dust has settled I will definitely go over to the composing and showcase area.

What’s a quaver?

I don’t use a separate notation program. I’ve used Logic’s editor for the few occasions when I’ve needed a score.

@bayswater: 7.24 on order!

@kgdrum: my thoughts exactly. I checked with MOTU before I ordered. I thought that this way I can be using and learning DP7 while waiting for DP8.

With Logic, I can say that moving to 64 bit made a HUGE difference to me. I know many vendors have come up various server techniques to allow more memory to be used for samples from a 32-bit application – but they all still use SOME memory and so that 32-bit app can still have memory problems. With 64-bit, I just didn’t need to ever think or worry about it. I’m guessing that the same will be true with DP8.

One thing I have noticed is that the DP8 announcement makes no mention of a 32-bit bridge for running 32-bit plug-ins. I wonder if MOTU have saved themselves a HUGE headache by just not supporting 32-bit plug-ins within DP8? If so, I think that decision will upset a few people.

@twistedtom: I have had a look through this forum recently, and people seem to be generally very happy with DP7.

Hello Nicky!
I am touched that you remember me so well! Yes, I had the avatar with the suit, and I know you liked it

Well, I know that one of the “selling points” of Logic was it huge array of bundled VIs, but I honestly never use them (EXS 24 very occasionally, but Kontakt can read those patches anyway). So whatever comes with DP will just be a bonus in my eyes.

I look forward to trying out a big-ish orchestral template when my DP7 arrives (which will be tomorrow). I expect it to be less efficient than Logic, but by how much is the question. You’re right again – DP efficiency was a big thing that bugged me.

There are some great videos by Mike Patti on YouTube. He is generally demonstrating CineSamples libraries (obviously), but also has several videos about scoring with DP. Absolutely fascinating, and you can see that he uses a huge DP template. All very interesting!

I hope I’m here to stay as well, MM. I always did love it here. And I always tell other people what a great place this was and is.

All the best

[Prime Mover]

Yeah, no word on a bridge. By this point (a week out), I'm really starting to worry. At first I was thinking, "no way they wouldn't have a bridge, that would be suicide", but the fact that there has been no more than one phrase dedicated to a 64bit feature, and that they advertise that DP8 can run in 32bit and 64bit mode makes me really dubieus. I'm starting to consider my options if this is the case. I only have 3 plugins that aren't 64bit capable, and probably one of them (Redline Headphone Monitor) will likely get updated. But B4-II and Korg Legacy VIs will never be 64bit. I can always run those standalone from outside, but it's a real pain.

Bah... someone needs to come out with a decent replacement for B4-II. Anything at NAMM look like a possibility? I have VB3, but I wasn't really happy with that one, and it doesn't like DP7.

Here's hoping that I'm wrong, and they come out with a bridge, but at this point, I'd bet against it.

[kgdrum]

Prime- I heard VB3 now worked with DP7.24,
Are you in SL or Lion?

[bayswater]

It would be inconvenient if DP never has a bridge for 32 bit plugins, but not a deal killer. A lot of people are using alternates like Bidule and seem to be successfully mixing 32 and 64 bit components. I'm using a G5 as a host to run UAD-1 which will never be usable on a iMac, and it won't be a big problem to add the remaining 32 bit plugs to that. It would make me very happy to be able to spread DP processing across multiple Macs a la Logic Node (but, unlike Logic, make it work properly).

[Prime Mover]

I'm pretty sure I was using 7.24 when VB3 crashed on me. Never-the-less, I really don't like VB3. Though it's realistic, I just don't like the timbre of the sound, it has less control than Vintage Organs, in some ways... the reversed drawbars always trips me up, and it DOES NOT interface well with Jambalaya AT ALL due to some inability to change MIDI routing per patch. I'd honestly rather use B4II standalone.

I don't have Bidule or anything like that, and I really haven't found a need for it because I rarely work with REALLY LARGE VI setups, not sure what advantage it would be in my workflow. So I don't think there's much reason for me to get it as a 64bit bridge, I'll just likely go standalone.

[mikehalloran]

I just heard from Magic Dave. He confirmed that anyone upgrading to DP 7 now will get 8 at no additional charge when it ships.

[tyronehowe]

I’m guessing that there will not be a bridge. I have some plug-ins that won’t ever be updated to 64-bit (like Virtual Guitarist 2). I’d have to run them under VE Pro.

[monkey man]

Hello Nicky!
I am touched that you remember me so well! Yes, I had the avatar with the suit, and I know you liked it

Well, I know that one of the “selling points” of Logic was it huge array of bundled VIs, but I honestly never use them (EXS 24 very occasionally, but Kontakt can read those patches anyway). So whatever comes with DP will just be a bonus in my eyes.

I look forward to trying out a big-ish orchestral template when my DP7 arrives (which will be tomorrow). I expect it to be less efficient than Logic, but by how much is the question. You’re right again – DP efficiency was a big thing that bugged me.

There are some great videos by Mike Patti on YouTube. He is generally demonstrating CineSamples libraries (obviously), but also has several videos about scoring with DP. Absolutely fascinating, and you can see that he uses a huge DP template. All very interesting!

I hope I’m here to stay as well, MM. I always did love it here. And I always tell other people what a great place this was and is.

All the best

Well, the efficiency can only matter less as our rigs get quicker; even a 50% difference could easily get lost in the noise of a machine upgrade, along with efficiency gains of DP tweaks over time. MOTU would have been aware of grumblings of said efficiency or lack thereof, and from what I've read, users have reported progress where this is concerned. I reckon you have cause to be optimistic, Tyrone.

Hey man, thank you for the forum compliments; you're indeed a worthy "Unicorn", and IMHO fit this place like a glove. Not OJ's glove, but a glove nevertheless.

[Armageddon]

But B4-II and Korg Legacy VIs will never be 64bit. I can always run those standalone from outside, but it's a real pain.

Boy, I had to dig deep for this thread! During my monthly check-in to see which of my plugs/VIs have been upgraded, I recently saw that Korg had updated all their VIs and the MDE-X suite. So I downloaded all the installers and started by installing my analog VI updates (MonoPoly, PolySix, MS-20 and Legacy Cell) After installing the newest MS-20 update, I fired it up standalone, just to make sure it was copacetic. Now, previous to this, I've had problems in the past loading up my M1 and WAVESTATION standalone -- the VI would open, I'd get a warning stating "Device State has changed" and my Audio/MIDI prefs would then pop up with some bizarre sample rate my audio interface wasn't even close to actually using. The only solution to this was to trash the prefs and restart the VI, where I could then enter the proper sample rate and MIDI device ... then, it would be fine. However, with all my Korg analog VIs, the above-listed discrepancies happened, then, suddenly, I'd get the dreaded "You Must Restart Your Computer" transparency laid over my entire screen. This had never happened before, and while I first chalked it up to the new upgrade, I checked the three VIs I hadn't upgraded yet and it did the exact same thing. However, I could load them up in my spiffy new "Audio Plugin Player" app with no problem, so it was apparently an issue limited only to the standalone versions. I finished upgrading all my Korg VIs and then trashed all their prefs, after which they opened fine and allowed me to set the proper sample rates and keyboard controls.

It had been a while since I used the Legacy Analog VIs, so I can't say for sure whether it was system upgrades, audio device upgrades or a lack of programming skills on Korg's part (since I've always had issues with Korg's VIs working with my interface, I'll assume the latter), but the fact that just simply opening a VI would cause my entire system to crash that spectacularly is a bit alarming. I guess I'll stop praying for a virtual Triton now ...