DP5.13: crossfade-crash ALWAYS!

[fsheinfeld]

I agree, this is something I do all the time as well, nothing wrong with that.

Like someone mentioned you could just select a few at the time instead of everything at one pass. Try also loading that chunk into a new sequence. That's usually the fix for most problems.

[James Steele]

Doing that type of cross fading is extremely common, I've made a living doing it for over a decade. I think it's better not to mock someone just because you don't understand what they're doing.

Not sure who was *mocking* him. But if you read the very first post the information given was far too inadequate of unclear for anyone to have any hope of offering a worthwhile suggestions.

The problem with the RESOLVED tag is when I was having a problem a couple weeks ago someone put RESOLVED in the title even though it wasn't, I couldn't figure out how to change it, and no one ever responded again.

Which thread. It wasn't SOMEONE... it had to be a moderator, possibly me. I'll look at the thread and see if I added RESOLVED to it and if so explain why. To change it back, you can edit your own post if you were the OP, and simply edit the subject header. The problem is we are getting a LOT of these threads where someone posts about a problem, sometimes with a rather alarming header (i.e. DP is TOTALLY BROKEN!!!!!, etc.), then they either find an answer on their own, or someone makes a suggestion, but then they disappear, sometimes without so much as a thank you. They often never come back to announce they found the answer on their own (sometimes it was operator error) or they tried a suggestion made here and that fixed it. That's unfortunately not very fair to MOTU, as a casual visitor to this site would browse this board and looking at the subject headers be completely freaked out. If they assumed every complaint/problem posted in this forum and SCREAMED in anguish by frustrated users was always valid, they'd run for the hills and certainly get an unfair opinion of DP.

THAT is why I go around wasting MY time adding "[RESOLVED]" to some of these threads, because it's just doesn't help anything to have erroneous reports adding to the legit problem reports. One of the reasons I resisted starting this board years ago as opposed to MOTU-MAC, is that the vast majority of requests I got to start the board were from people who want to get in, TAKE from the community and never come back. You'll see those posts often here. Someone who joined the day before, has ONE or TWO posts tops, and it's a post about how DP is total garbabe and he can't get XYZ to work right. Someone gives him an answer, he posts no follow up or thank you, and disappears never to be heard from again, never to participate or contribute to the discussion. Well, that is until the next time he has a problem. Lately, it's been my impression (and I'm not pointing fingers at anyone in particular) that the "get-in-get-what-I-want-get-out" types are popping in here more frequently because they're unhappy about DP6 or whatever and bringing the whole place down. I may actually start a different forum altogether for "DP Problems, Help Requests" or whatever to leave the "Digital Performer" forum as a place for more constructive sharing/discourse about work methods, trips/tricks, plug-ins, etc.

So, if I jump the gun on the "[RESOLVED]" tag, my apologies but I'd rather err in that direction.

As for the crossfade problem of the OP, something very important to consider is if the project were loaded into DP 6.02 and the same operation attempted, would it STILL crash? If not, MOTU may have fixed that in DP 6. It does bear pointing out that DP 5.13 is an end of life version and I'm not even sure if MOTU is still doing tech support for it. And even if "DP5.13: crossfade-crash ALWAYS!" is true... it's somewhat irrelevent as it's a dead version and no fix is forthcoming from MOTU. It's sort of like going to a Logic Forum and posting "Logic 7: crossfade-crash ALWAYS!" Granted it's a bummer, but ummm... what can anybody do about it? MOTU's moved on and probably a majority of DP users as well. I'm not saying there's not a strong contingent laying back on DP5 waiting for the day that they read enough postive things about the latest DP 6 that they venture out, but we all have to realize there's nothing that can be done about problems in DP 5.13.

[bongo_x]

... To change it back, you can edit your own post if you were the OP, and simply edit the subject header. The problem is we are getting a LOT of these threads where someone posts about a problem, sometimes with a rather alarming header (i.e. DP is TOTALLY BROKEN!!!!!, etc.), then they either find an answer on their own, or someone makes a suggestion, but then they disappear, sometimes without so much as a thank you. ...

I understand why you're doing it, I just couldn't figure out how to change it. I think it's because I wasn't the original poster.

bb

[waterstrum]

As for the crossfade problem of the OP, something very important to consider is if the project were loaded into DP 6.02 and the same operation attempted, would it STILL crash? If not, MOTU may have fixed that in DP 6. It does bear pointing out that DP 5.13 is an end of life version and I'm not even sure if MOTU is still doing tech support for it. And even if "DP5.13: crossfade-crash ALWAYS!" is true... it's somewhat irrelevent as it's a dead version and no fix is forthcoming from MOTU. It's sort of like going to a Logic Forum and posting "Logic 7: crossfade-crash ALWAYS!" Granted it's a bummer, but ummm... what can anybody do about it? MOTU's moved on and probably a majority of DP users as well. I'm not saying there's not a strong contingent laying back on DP5 waiting for the day that they read enough postive things about the latest DP 6 that they venture out, but we all have to realize there's nothing that can be done about problems in DP 5.13.

Good point James.

We shouldn't be looking for bug fixes on versions that aren't current.

[Anders Peev]

I believe there are still a lot of 5.13 users. I don't intend to move over to 6 until there is a version that truly works. If a Dp 4 user ask for help on this forum should we just tell her/him that we wont help him/her because DP 4 isn't a current version?

/

Anders

[James Steele]

I believe there are still a lot of 5.13 users. I don't intend to move over to 6 until there is a version that truly works. If a Dp 4 user ask for help on this forum should we just tell her/him that we wont help him/her because DP 4 isn't a current version?

Read my post again, Anders. What I'm saying is that if there is indeed a bug in DP 5.13 that accounts for this, THERE IS NOTHING WE OR MOTU CAN DO ABOUT IT. There will be no more updates or bug fixes for DP 5.13, so it's not that we WON'T help him, but that we CAN'T. Certainly you understand that, right?

[Anders Peev]

Aah! Sorry James, my mistake!

/

Anders

[waterstrum]

Letting go of 5.13.....

Has the multiple crossfade-crash been fixed in DP 6.02?

[James Steele]

Letting go of 5.13.....

Has the multiple crossfade-crash been fixed in DP 6.02?

I can't tell you that. I've done multiple crossfades all the time with DP 6.02 and haven't had that crash. I've also never done so many at once. If I had his project I could try it and see if it happens in DP6. For all I know maybe there's just ONE problem soundbite that's corrupted and causing the crash, or once you try to crossfade more than ____ soundbites it happens?

[jnunally]

I have had plenty of issues with crossfades crashing DP5.13.

I have a couple suggestions.

First try crossfading one track, Let's say track one. If you can, watch the background processing window wait till all the crossfades are done before you do anything else. If this works, save the file.

Then try the next track the same way. If it works save it.

If all goes well, continue until you either complete all the fades, or a track crashes DP. Be sure to save between each of the tasks. If it does crash on one track in particular, go back and try to fade the first half of the track. If that works, then go to the second have and fade that. The idea is to try and isolate where the heck the particular fade issue is.

I once had a very strange problem with trying to crossfade a track that had been auto-tuned. I didn't actually tune the whole track, just one word. For some reason, every time I tried to cross fade that particular spot it would crash, every time. The way I fixed it was to solo the track, make sure there were no clicks or pops at the edit points, then merged it. Bingo, it worked. I was able to save the file and do other crossfades with no problems.

I have had crossfades crash DP many times. I think it is related to file name problems, either the soundbite file, or the crossfade file. When you clear up those issues it works pretty well.

Another issue I have had is giving the machine, or DP, to much information to process all at once. This is why I suggest watching the background processing window to see if it behaves better when you let it finish a task before moving on. If you are crossfading hundreds of edit points, then go to do another simple task, like scrolling the window, you might just be sending the machine, or DP, over the top. Who knows, but in my experience it seems to help now and then to let the machine process for a while before I send it any more tasks to tackle.

Good luck,
Jim

@James

Concerning the threat title: I don't wanna panic people from using DP, but, unfortunately, in my case, i have this 100% error rate.
Below i will post my (surprising) solution.

But first here again, that's the deal:

I have 15 Drum Tracks (not 18 ), and i create soundbits at every snare / base / tom hit etc. i am doing this for 16 bars in total, quantize it, and then i have to Crossfade it of course!

please find a screenshot below:








view it big:
http://img139.imageshack.us/img139/4874/dp1.jpg

http://img151.imageshack.us/img151/6951/dp2.jpg

When i start the crossfading, DP crashes after a few Minutes, like i described in the first post. end of story.

If you might point your view to this post here
http://www.motunation.com/forum/viewtop ... =1&t=35002
this is a threat from me in which i asked a while ago about which DP version to use.

So, 5.13 with Leopard does not work for me like you can read here.

SOLUTION (for me:)
5.11 with Leopard (right, even that 5.11/Leopard is not officially supported by Motu) W O R K S like a charm for me. I can crossfade 16 bars the way i described above on iMac and on PowerMac., works perfecly and stabil.
So i am wondering, why only i am experiencing this. It's fresh 10.5.6 installation.
My friend is experiencing excactly the same, but with Leopard on PowerPC.
5.11 does only work here, too.

Looking forward reading from you.

Thanks.

[djc]

The problem is we are getting a LOT of these threads where someone posts about a problem, sometimes with a rather alarming header (i.e. DP is TOTALLY BROKEN!!!!!, etc.), then they either find an answer on their own, or someone makes a suggestion, but then they disappear, sometimes without so much as a thank you. They often never come back to announce they found the answer on their own (sometimes it was operator error) or they tried a suggestion made here and that fixed it. That's unfortunately not very fair to MOTU, as a casual visitor to this site would browse this board and looking at the subject headers be completely freaked out. If they assumed every complaint/problem posted in this forum and SCREAMED in anguish by frustrated users was always valid, they'd run for the hills and certainly get an unfair opinion of DP.

THAT is why I go around wasting MY time adding "[RESOLVED]" to some of these threads, because it's just doesn't help anything to have erroneous reports adding to the legit problem reports. One of the reasons I resisted starting this board years ago as opposed to MOTU-MAC, is that the vast majority of requests I got to start the board were from people who want to get in, TAKE from the community and never come back. You'll see those posts often here. Someone who joined the day before, has ONE or TWO posts tops, and it's a post about how DP is total garbabe and he can't get XYZ to work right. Someone gives him an answer, he posts no follow up or thank you, and disappears never to be heard from again, never to participate or contribute to the discussion. Well, that is until the next time he has a problem. Lately, it's been my impression (and I'm not pointing fingers at anyone in particular) that the "get-in-get-what-I-want-get-out" types are popping in here more frequently because they're unhappy about DP6 or whatever and bringing the whole place down. I may actually start a different forum altogether for "DP Problems, Help Requests" or whatever to leave the "Digital Performer" forum as a place for more constructive sharing/discourse about work methods, trips/tricks, plug-ins, etc.

James, First, a word of appreciation for all your hard work on this board. Perhaps more work and stress than many are aware of or appreciate. One comment-I am a person who reads the DP board from time to time (when I HAVE time) and replies very little. The main reason I kept my yap shut is that I am humbled by the depth of knowledge the regulars have regarding DP and the recording process in general and don't see much use in adding to the din with less informed comments or opinions. Unfortunately, I take much more than I give but feel that is the lesser of two evils. However, the "take" is very much appreciated! I also agree that there is way too much hyperbole on this and other boards. DP isn't perfect but neither are its users so rages are sure to happen. It seems to me every board on programs and/or gear has its fair share of doomsayers so, regarding the causal reader, things will probably even out in the end.

So relax and take some time off. Let Shooshie run things for a while!

djc

[James Steele]

So relax and take some time off. Let Shooshie run things for a while!

I fixed your previous post to show the first part was a quote from me. I appreciate the sentiment, but I can't really take time off. With much respect to Shooshie, it takes a lot of time to keep things going smoothly and that's a responsibility that I can't delegate away.