MOTUnation.com

Prime Mover wrote:

kgdrum wrote:Rethinking about it,I do think your correct about the pan law,that would certainly be a mess. Yes selectable settings for this would be cool.
You don't think if they rewrote DP they might have tweaked a bit given the opportunity to improve on DP under the hood?

Well, DP8 is a complete re-write so it's kind of a given that they "tweaked" things, but not in any way that would change the sound, that's pretty much a no-no in any kind of production software. The only time I've ever heard this happening, and I was pretty shocked, was when NI announced that Kontakt 5 was updating its existing filters. All the Kontakt fanboys at the NI forums tried to argue that this was an objective improvement that will not negatively impact anybody, but I find that impossible to believe. You just don't mess with what's there, you add new things. That's why we still have the old "Reverb" and ParaEQ plugins, even though newer plugins have made those almost completely obsolete.

MOTU seems to be pretty solid on this concept, which is why we've got so much old stuff kicking around. But I think that's the mark of a mature manufacturer, not just changing things on a whim, but making absolutely sure that users' old work remains unchanged.

Yeah but Kontakt 5 to me clearly sounds better than the previous versions, no contest!

bralston wrote:But you can still just open those files in DP8 in 32-bit mode with one click. (Right click DP...get info...check open in 32-bit mode). All your older plugs will be there. Save your settings with those older plugs. Delete the plugs you don't need. All those things you mentioned. Then close...and reopen in 64-bit mode and be on your way. I don't see what the issue is really. I much prefer stable and optimized in 64-bit than less stable (or not stable) in 64-bit with a 32-bit bridge.

This is true. The issue is that it's not always going to be that easy, and doing this for hundreds of projects amounts to a lot of time watching DP load projects, taking notes, and spending many hours of assessing the strategies of how to best continue working versus just continuing to work on the music. There are many VI tracks that I am not ready yet to commit to audio tracks, so it isn't as easy as just doing that either.

But yes. This beats having to go back to versions of the song on another computer or having to open them in a previous version of DP. It is workable, just more of a nuisance than I wanted it to be. That's what I get for having a world of projects still in progress, I suppose. This won't be the first time I have had to jump through hoops to continue working on my library of songs.

It was probably inevitable, anyway. I have a serious apprehension that SampleTank 3 will not automatically open SampleTank 2 instances anyway... which means that I will be required to open up every project in 32-bit mode anyway, just to save presets and prepare the project for 64-bit.

I guess I will just have to consider what I am working on, on a particular day, and launch the version of DP8 which is suitable for the project at hand, and create some way to indicate which version of DP needs to be used for which project. I think I'm going to have to have a policy of only working on projects in 64-bit mode when I have to. Not all, but *many* of my projects are at a stand still in desperate need of breaking free from the 32-bit limitations. These days I actually work on parts of the song in different projects (i.e. build the drum track in one DP project, deleting a whole bunch of tracks and VIs, so that I can then bounce the drum track and bring it back into the other version of the project). It is a lot of extra thinking and considering.

zed wrote:This is true. The issue is that it's not always going to be that easy, and doing this for hundreds of projects amounts to a lot of time watching DP load projects, taking notes, and spending many hours of assessing the strategies of how to best continue working versus just continuing to work on the music. There are many VI tracks that I am not ready yet to commit to audio tracks, so it isn't as easy as just doing that either.

But yes. This beats having to go back to versions of the song on another computer or having to open them in a previous version of DP. It is workable, just more of a nuisance than I wanted it to be. That's what I get for having a world of projects still in progress, I suppose. This won't be the first time I have had to jump through hoops to continue working on my library of songs.

I feel your frustration. When you started those projects did you think you wouldn't be able to finish them without a 64-bit version of DP? I mean you can still work on the projects at least.

Developers who are out of business or for other reasons won't keep up with the times really aren't MOTU's fault. I've heard from MOTU the whole bridge thing is kludgy and just adds more potential for problems.

James Steele wrote: When you started those projects did you think you wouldn't be able to finish them without a 64-bit version of DP? I mean you can still work on the projects at least.

To honestly answer that question, when I bought this Intel Mac I totally believed I was going to have plenty of headroom. But almost immediately I found that this wasn't true, and I've been waiting for the 64-bit version to alleviate those problems ever since.

But I'll make it work. I have spent 10 years in a tangle of workarounds since losing StudioVision Pro. I will manage to find a way to make this work too. I just know that there is a mountain of unwelcome work ahead.

Here's a really stupid idea...

Is it possible to run DP7 and DP8 and have them sync to each other? Keep your incompatible stuff in DP7 using it as a host and send it to DP8 via IAC?

I said it was stupid!

MIDI Life Crisis wrote:Here's a really stupid idea...

Is it possible to run DP7 and DP8 and have them sync to each other? Keep your incompatible stuff in DP7 using it as a host and send it to DP8 via IAC?

I said it was stupid!

not stupid brutha! We do that kinda stuff alot. Except we use two rigs synced. Even have an older G5 that syncs to run the stuff not compatible today.

now the idea that motu would allow us to boot two versions of DP which both have to access the same drivers, that would be wild.

So I am calling your idea 'innovative'

DP7. It's the new VE Pro. LOL!

MIDI Life Crisis wrote:DP7. It's the new VE Pro. LOL!

I like the idea a lot!

Let DP be a bridge unto itself...

... and all the children were set free.

It works on two Macs -- I do it now with an iMac and G5, but has anyone tried it with one Mac and two instances of DP?

It probably wouldn't be too hard to trick DP8 into being able to load two instances of the same app. In fact, it might just be as easy as copying one, call it "Digital Performer 8 - 32bit", and toggle the 32bit option. Heh heh, even if it doesn't work, I guarentee that it will once they release 8.01, just use DP8.01 for your main, and DP8 for your 32bit V-Rack.

Unfortunately, I can only imagine just how much of a RAM hit having two instances of DP open would cause. Not to mention, how do you plan on passing audio back and forth? Soundflower?

Honestly, if it comes down to this, you'd probably be better off just running one instance of DP8 in 32bit mode.

EDIT: Okay, I just realized what ReWire is and I'm feeling really stupid right now, disregard some of this.

Thanks SixStringGeek. I checked out jbridge and it is so worth the $13. I won't go into details, but more info on "why" can be found here:

http://www.motunation.com/forum/viewtop ... 64#p434064

My hope is that once the paid version arrives, patches from the DP projects will be saved. That's a minor annoyance but it appears that the SAVEC function had been disabled for the demo. No doubt I'll be back posting here once the full version arrives - but so far it looks like this is what the Dr. ordered for running DP8 in 64 bit boot mode.

Awesome!

Bennie Sims wrote: I have been using the JBridgeM for a couple days now and it works great until you have to bounce. At that time the bounce may crash or will finish bouncing but after or during the process my MOTU audio system crashes along with DP8 and the JBridge. After that happens it is impossible to start DP8 and the MOTU audio system again without restarting the computer.

I am able to freeze VIs and bounce w/o a problem so can I assume you are using a processing plug-in? If so, which one?

Thanks.

frankf wrote:A few months ago I bought VEP to run LASS in Komtakt5 in 64 bit for a large film project. Now it looks like Ill be running 32 bit VIs and plugs in VEP and let DP8 handle the 64bit plugs/VIs. A welcome switch. It looks like so far VEP will be hosting only my Korg VIs on an as needed basis.
Frank

I would suggest some serious testing to see if DP beats VE Pro in 64 bit VI handling as far as efficiency and crash resistance.
I haven;t gotten DP 8 but that is the 1st thing I will do.
Give it some truly evil cpu hits and see which crashes 1st, what problems occur etc,
I have been pretty impressed with VE Pro and consider it bullet proof.
I have never seen DP as stable when maxed out in cpu hit and ram hit, and I have seen VE Pro very stable. The fact that DP8 has handled DP’s flawed latency reporting to VE Pro is a great development too, allowing for VE Pro to work even more efficiently.
So now it is "let the best VI handling program win".
I still haven’t seen head to head testing between DP 8 and VE Pro yet, I would truly love to see this.
Obviously, if it is even close in DPs favor I will stay in DP for VIs as the less programs needed to make a “master” daw file, the better,

MIDI Life Crisis wrote:

Bennie Sims wrote: I have been using the JBridgeM for a couple days now and it works great until you have to bounce. At that time the bounce may crash or will finish bouncing but after or during the process my MOTU audio system crashes along with DP8 and the JBridge. After that happens it is impossible to start DP8 and the MOTU audio system again without restarting the computer.

I am able to freeze VIs and bounce w/o a problem so can I assume you are using a processing plug-in? If so, which one?

Thanks.

I am using my Lexicon Reverb. Do you get rid of the bridges after you freeze the tracks before bouncing? Secondly I am guessing you can't freeze the reverb track?