DP8 is on it's way now.

[FMiguelez]

VE Pro is way off my radar, for instance.

best, perhaps, to leave it there (off your radar, that is...) VEPro5 has some *serious* issues with DP (7.42) http://community.vsl.co.at/forums/34.aspx

Your link takes me to the general forum instead of the thread you mention.

Coud you describe what the problems are? VE Pro 5 and DP7 work perfectly on my system.

[williemyers]

Your link takes me to the general forum instead of the thread you mention. Coud you describe what the problems are? VE Pro 5 and DP7 work perfectly on my system.

Yes, FM, it is VSL's (only) forum re: VEPro. However, right at the top, you'll find a 3-page sticky, "VE Pro 5 Audio/Event Input in DP " detailing the inability to bounce MIDI tracks in DP when using VEPro5. In the middle of that sticky, you'll find VSL's take on it...
"Unfortunately it seems that this issue is unlikely to be solved due to the way DP handles bouncing, so when using Audio/Event Input plugins in DP, freezing first is the only option at this point. I'll have a look at the viability of a MAS version of the VE Pro 5 Server Interface, which will at least circumvent the single MIDI input port limitation of AU without breaking bounce to disk functionality.
Karel Bassez
Software Engineer, Vienna Symphonic Library GmbH"
let me repeat the operative line in his response; "this issue is unlikely to be solved due to the way DP handles bouncing"

beyond this, if you do a search for "Digital Performer" in the forum, you'll find a handful of posts re: problems with DP.
Glad it's working well for you, just noting that it's not working well for everyone...

[stubbsonic]

Add my name to the list of folks who would love to see even minor advancements to the notation (quickscribe) window. It is still my main notation program and it does pretty well, but I'd like to use it for percussion, and not have to write in articulations by hand.

[MIDI Life Crisis]

I'm not talking about the QS window. There is a separate notation window and it is super cool but undeveloped.

[stoecklem]

The bouncing issue with DP and VE pro is unfortunate but doesn't affect me at all since I don't use that feature. The more serious issue is that DP 7 does not support VE pro delay compensation, something that should be fixed in DP 8.

[stubbsonic]

I'm not talking about the QS window. There is a separate notation window and it is super cool but undeveloped.

In previous DP versions, there was a notation view that scrolled some sloppy notation, but that view is gone. Now QuickScribe is the only notation window there is in DP.

[MIDI Life Crisis]

I'm not talking about the QS window. There is a separate notation window and it is super cool but undeveloped.

In previous DP versions, there was a notation view that scrolled some sloppy notation, but that view is gone. Now QuickScribe is the only notation window there is in DP.

Wrong.

You can get to the notation window by either ctl clicking on the track name in TO or by the dropdown on the right side of the GE window. The notation is only "sloppy" if you're not playing to a click and/or playing sloppy.

Just because you can't find it in the menu doesn't mean it's not there. That's why there's a manual.



You might want to check out the DP 7 manual INDEX, or even the TABLE OF CONTENTS as both have dedicated references to the Notation Editor. An awesome tool that still needs development.

[zed]

That's why there's a manual.

You mean that really awkward manual that is heavy as hell and hurts my fingers to even pick up? That same manual that I can't keep near my workstation because it is so big and bulky? That same manual where you have search the index or table of contents and then carefully flip through hundreds of pages to numerous locations instead of quickly typing in a search term and being able to instantly click through to the vital information which can stay open on the screen?

I hardly ever look in the manual anymore, even when I *want* to look up something. You already know what I think they should do about it.

[MIDI Life Crisis]

Yes, that's the one.

[FMiguelez]

Your link takes me to the general forum instead of the thread you mention. Coud you describe what the problems are? VE Pro 5 and DP7 work perfectly on my system.

Yes, FM, it is VSL's (only) forum re: VEPro. However, right at the top, you'll find a 3-page sticky, "VE Pro 5 Audio/Event Input in DP " detailing the inability to bounce MIDI tracks in DP when using VEPro5. In the middle of that sticky, you'll find VSL's take on it...
"Unfortunately it seems that this issue is unlikely to be solved due to the way DP handles bouncing, so when using Audio/Event Input plugins in DP, freezing first is the only option at this point. I'll have a look at the viability of a MAS version of the VE Pro 5 Server Interface, which will at least circumvent the single MIDI input port limitation of AU without breaking bounce to disk functionality.
Karel Bassez
Software Engineer, Vienna Symphonic Library GmbH"
let me repeat the operative line in his response; "this issue is unlikely to be solved due to the way DP handles bouncing"

beyond this, if you do a search for "Digital Performer" in the forum, you'll find a handful of posts re: problems with DP.
Glad it's working well for you, just noting that it's not working well for everyone...

I see. I expected your link to take us straight into the thread you meant. Sorry it didn't occur to me to look for it.

MIDI Bounce is not working?? I honestly didn't realize until now, since I never bounce anything these days.
Either way, that hardly qualifies as a "serious issue", especially since one can opt to record in real time instead.

If you search THIS board for "DP problems", you will find more threads than you can read. It would make a new user think DP is a unusable POS with tons of problems. But you and I know this is not true. Why would VSL's forum be any different?

[Prime Mover]

I honestly don't understand why everyone stresses real-time recording over bouncing. I don't trust real-time recording. You never know when the CPU is going to spike you're going to get a glitch. That doesn't happen in bouncing, since the computer can slow down to accommodate lag. But it can (and undoubtedly does, even in small doses) when real-time recording. I've even seen Magic Dave advocate bouncing over real-time. He once said that he ALWAYS bounces, at least when mastering. I just think it's infinitely safer. Real-time recording seems like playing with fire to me.

[dix]

I honestly don't understand why everyone stresses real-time recording over bouncing. I don't trust real-time recording. You never know when the CPU is going to spike you're going to get a glitch. That doesn't happen in bouncing, since the computer can slow down to accommodate lag. But it can (and undoubtedly does, even in small doses) when real-time recording. I've even seen Magic Dave advocate bouncing over real-time. He once said that he ALWAYS bounces, at least when mastering. I just think it's infinitely safer. Real-time recording seems like playing with fire to me.

I do it mainly for QC. If something glitches while recording at least I can hear it. I've bounced things where a fader, plugin or something was set wrong and got unanticipated results (most memorably when an AutoTune scale was set to the wrong key and it went to the client like that! D'oh!). Therefore I always listen to the bounced track in its entirety anyway, so recording is actually a time-saver.

…although I'm not sure I knew that you could bounce things that could not be played in real-time. That's really good to know. Apart from avoiding possible cpu spike glitches are there any other advantages to bouncing?

[FMiguelez]

I honestly don't understand why everyone stresses real-time recording over bouncing. I don't trust real-time recording. You never know when the CPU is going to spike you're going to get a glitch. That doesn't happen in bouncing, since the computer can slow down to accommodate lag. But it can (and undoubtedly does, even in small doses) when real-time recording. I've even seen Magic Dave advocate bouncing over real-time. He once said that he ALWAYS bounces, at least when mastering. I just think it's infinitely safer. Real-time recording seems like playing with fire to me.

It may seem so to you, but in my experience it has been 100% reliable, every time. BTD, on the other hand, seems to diminish its reliability proportionately to the session's complexity.

Also, how many BTD problem-related threads have you read on this board?
How many real-time recording problem threads have you seen?

That should give you a clue about this...

[MIDI Life Crisis]

I routinely BTD on every project w/o incident. MIDI gets recorded in real time most often, and freezing VIs is how I pull those tracks in. Then I bounce the whole sequence and it's sample accurate and sounds fine. No color wheels or anything unless a HD is clogging things.

I could see where a complex seq with a brazillion (or 10,000) audio tracks could be problematic. I'll leave those recordings for others to make.

[Prime Mover]

Actually, I've never once had a problem with BTD. Real-time, on the other hand...