Long Recording Bug

[AncientMariner]

I can't seem to find a "summary" on this one, so I'll take a chance and start it. Just recently, finally, upgraded to version 8. My gig is FOH at a mid-sized (2000 seat) busy (330 shows/year) venue. My recording needs mostly are for "internal use only", recording the whole show, all tracks (50+). Used DP for many years before this gig, for things that didn't depend on long reliable recording.

Until V8, Digital Performer was not a candidate ... the long recording bug was a deal-breaker. It stung me enough times to just quit trying. Did the demo on V8, ran it really hard, no problems, so I bought it. Still working fine.

So ... is the bug finally gone, for real? Has anyone from MOTU admitted the bug existed, and stated that they actually found the cause and fixed it?

[bayswater]

I did soundscape project recording with DP, 36 hours, 3 tracks. Just in case of project length problems, I set it up to loop with one hour takes. I don't recall whether it was DP 7 or 8. If it matters, I can probably find the files and figure out which it was. Anyway, it worked.

[AncientMariner]

Up to and including the final version of DP7, the bug bit me too often, even recording a simple stereo track @ 48k from the built in input. Sometimes would crash after as little as 8 minutes.

[mikehalloran]

The bug was acknowledged and fixed. I don't remember which version of 8. There are old threads on this if you want to search.

[MIDI Life Crisis]

It also has to do with the recoding format, drive speed and available space, how you have your computer setup, what else is running, what demands the network is making, etc. it's all interdependent and not just a DP issue, per se. There WAS a bug at one time. There is not now, but again, that doesn't mean something else isn't to blame if you're seeing an issue.

[AncientMariner]

You know this how? You work for MOTU? Same system would work fine with ProTools or Audition ... only DP had this problem.

[MIDI Life Crisis]

30 years of computing. That's how. Some might call that "experience." You asked. I answered.

YOU'RE WELCOME.

[AncientMariner]

I'll see your 30 & add 10. About 20 of them coding & designing hardware.

[MIDI Life Crisis]

Let's not turn it into a pissing contest. I'm not interested. HD I realized you wanted to do that I wouldn't have bothered and given your responses I'm sorry I did. Maybe someone else is interested in your pushback. I'm not. Good luck. Blocking.

[Shooshie]

Up to and including the final version of DP7, the bug bit me too often, even recording a simple stereo track @ 48k from the built in input. Sometimes would crash after as little as 8 minutes.

Bizarre. I've recorded 2 hour projects without break at 24bits/48K on location with laptops many times with many versions of DP. Never had a problem. In fact, other than an occasional thread here, I wouldn't have known there was a bug. It never affected my recording.

I DO remember MOTU saying that the bug is fixed. I don't remember the version, but it seems like it wasn't that long ago. Probably 8.01 or something. But if you were crashing after 8 minutes, I suspect you've got other problems and may have to dig deeper. The bug absolutely did not affect 8 minute recordings. If it had, I'd have lost many, many live location recording projects. The typical continuous recording time for a location recording for me is about 30 to 45 minutes, then a break, then another of slightly less time. Occasionally they go for 2 hours without break, as mentioned before. Never a problem. Sometimes I record at 88K, which theoretically would nearly double the odds of a crash happening with such a bug rampant. It never did, not even with 6 mics.

I'm just saying, there may be another problem. Are you using plenty of RAM?

Shooshie

[Shooshie]

In fact, other than an occasional thread here, I wouldn't have known there was a bug. It never affected my recording.

Come to think of it, in 28 or 29 years of recording or playing live performances with Performer and Digital Performer, I've not had a crash — ever — while in front of an audience. I've had a few in the studio where it was possible to do it over, but I've never lost a track during a performance. I'm not alone in that; many people use DP for precisely that reason, including a large percentage of the top touring shows in the industry. That includes Madonna, Beyoncé, many 1st tier rock bands, jazz aficionado groups, and the like.

I toured nationally as MD for live shows in top performing arts venues for many years; DP never dropped a note or cue. There were versions I would not install until things were fixed. The years of version 4 to version 5 were particularly troublesome, but I found stable configurations and ran with them. Seems like 4.11 was the first OS X version I was able to use for work.

DP has been amazing for me. And it made me look like I actually knew what I was doing!

Shooshie

[AncientMariner]

Well, 8 minutes was the minimum time I got a crash, and that was some time ago. Normally took closer to a half hour. No doubt there were factors that interacted with the bugged code. I did search the forum, but didn't find a clear answer, nor the clear admission of the bug. Not doubting it's here, I just didn't run across it.

I really like DP, for a lot of reasons ... mainly the chunk thing, and the superior MIDI handling, compared to ProTools ... and Audition has zilch in that world.

Anyway, thanks! V8 is working fine for me ... in fact, just got back from my mat wherein I grabbed 40 tracks, no issues. Nice to know they put this one to bed ... the only reason I kept my other platforms current.

BTW, it works very well with the Dante Virtual Soundcard, which is how I capture tracks. Our stageboxes are RIO3224s.

Off to the night show. Thanks again!

[mikehalloran]

You know this how? You work for MOTU? Same system would work fine with ProTools or Audition ... only DP had this problem.

We've been paying attention for a long time. As I mentioned, there are other threads on this former issue. Do an Advanced Search and you will find them. Or don't.

The DP issue is fixed. As MLC mentions, there are other possible system causes that have nothing to do with DP.