SHOULD I DUMP DP???
Moderator: James Steele
Forum rules
The forum for petitions, theoretical discussion, gripes, or other matters outside deemed outside the scope of helping users make optimal use of MOTU hardware and software. Posts in other forums may be moved here at the moderators discretion. No politics or religion!!
The forum for petitions, theoretical discussion, gripes, or other matters outside deemed outside the scope of helping users make optimal use of MOTU hardware and software. Posts in other forums may be moved here at the moderators discretion. No politics or religion!!
SHOULD I DUMP DP???
I am one of the many users suffering from the constant crashing of dp 5.1 . I've tried everything listed on the site, and I still get crashes 10 times a day.
I am running a mac pro, with an 828.
I am so fed up with the uselessness of Dp right now, I seems that nothing can be done other than wait for an update to come in who knows how long. Unless I can find a cure for this, I think I will switch to logic.
Ive been using dp for years know, and I'm just fed up. How can I try to run a business with a program won't even run.
Thoughts?
I am running a mac pro, with an 828.
I am so fed up with the uselessness of Dp right now, I seems that nothing can be done other than wait for an update to come in who knows how long. Unless I can find a cure for this, I think I will switch to logic.
Ive been using dp for years know, and I'm just fed up. How can I try to run a business with a program won't even run.
Thoughts?
- mhschmieder
- Posts: 11415
- Joined: Wed Jul 06, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: Annandale VA
If you're having DP 5.1 specific problems, back out to 5.0.
If your problems are due to the recent update of Mac OS X 10.4, see if you can back that out.
Any time you do a system or application program, you are creating risk. Computers are all-purpose, unlike a hardware synth or hardware recorder. It is not realistic to expect that a vendor can check every possible combination of hardware, OS, software, peripherals, drivers, etc.
That said, DAW vendors have a particular burden on their shoulders as they are at the centre of most of what we do. I'm not making excuses for MOTU if they made a major booboo (I'm one of the lucky ones who is whizzing along on DP 5.1, but I recognise that it might have been the luck of the draw), but I also don't see why you'd dump it after years of use when anything you would use in its place would likely have similar problems, or other problems that might be worse, and involve a huge learning curve.
I understand that you're venting, but validation won't help your REAL dilemma, which is in your final rhetorical statement. As you are trying to run a business and are now in deep doodoo over the instability of DP 5.1 on your particular platform, your quickest path to productivity is to see what you can do to backout to the last known stable combination of OS and DP on your system.
Although I mostly do pro bono work and thus can't afford to have two computers, I urge anyone who depends on DP for a major source of their income to always have a stable computer, no matter how old, that they don't retire and/or upgrade until their OTHER computer (which may get updated more frequently) has passed every test they can think of.
This may seem obvious and not very helpful at this stage of your frustration, but giving up won't help much either. Take a deep breath and then take an inventory of the progression of events, and you are probably in better shape than you think at the moment.
If your problems are due to the recent update of Mac OS X 10.4, see if you can back that out.
Any time you do a system or application program, you are creating risk. Computers are all-purpose, unlike a hardware synth or hardware recorder. It is not realistic to expect that a vendor can check every possible combination of hardware, OS, software, peripherals, drivers, etc.
That said, DAW vendors have a particular burden on their shoulders as they are at the centre of most of what we do. I'm not making excuses for MOTU if they made a major booboo (I'm one of the lucky ones who is whizzing along on DP 5.1, but I recognise that it might have been the luck of the draw), but I also don't see why you'd dump it after years of use when anything you would use in its place would likely have similar problems, or other problems that might be worse, and involve a huge learning curve.
I understand that you're venting, but validation won't help your REAL dilemma, which is in your final rhetorical statement. As you are trying to run a business and are now in deep doodoo over the instability of DP 5.1 on your particular platform, your quickest path to productivity is to see what you can do to backout to the last known stable combination of OS and DP on your system.
Although I mostly do pro bono work and thus can't afford to have two computers, I urge anyone who depends on DP for a major source of their income to always have a stable computer, no matter how old, that they don't retire and/or upgrade until their OTHER computer (which may get updated more frequently) has passed every test they can think of.
This may seem obvious and not very helpful at this stage of your frustration, but giving up won't help much either. Take a deep breath and then take an inventory of the progression of events, and you are probably in better shape than you think at the moment.
cchord:
Most of the complaints I've heard have been from those using firewire interfaces-- particularly those using FW400 interfaces and FW HDs. There still seems to be the FW bus logjam-- not saying that this is exactly what's causing your problem-- but it's not difficult to shove more stuff down one FW bus than it can handle, even on the Intels.
Forgive me for not researching your setup, but do you have a Book Pro or a Tower Pro?
Depending on the issue, I would sooner consider changing the interface before changing DAWs, but I don't want to speak too soon.
Most of the complaints I've heard have been from those using firewire interfaces-- particularly those using FW400 interfaces and FW HDs. There still seems to be the FW bus logjam-- not saying that this is exactly what's causing your problem-- but it's not difficult to shove more stuff down one FW bus than it can handle, even on the Intels.
Forgive me for not researching your setup, but do you have a Book Pro or a Tower Pro?
Depending on the issue, I would sooner consider changing the interface before changing DAWs, but I don't want to speak too soon.
6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33
- Michael Canavan
- Posts: 3856
- Joined: Fri Jul 15, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: seattle
My Fireface will simply freak out sometimes if I start the two external FW HD's up, it really does not like sharing the bus with HD's.Frodo wrote:cchord:
Most of the complaints I've heard have been from those using firewire interfaces-- particularly those using FW400 interfaces and FW HDs. There still seems to be the FW bus logjam-- not saying that this is exactly what's causing your problem-- but it's not difficult to shove more stuff down one FW bus than it can handle, even on the Intels.
RME even strongly recommend getting a FW PCI card so that the bandwidth is increased.

M2 Studio Ultra, RME Babyface FS, Slate Raven Mti2, NI SL88 MKII, Linnstrument, MPC Live II, Launchpad MK3. Hundreds of plug ins.
cchord59 is using a Mac Pro, so rolling back to 5.0 on that machine isn't an option.mhschmieder wrote:If you're having DP 5.1 specific problems, back out to 5.0.
I haven't used a Mac Pro, so I don't have any direct experience, but I do have a MacBook Pro. I agree with Frodo, a good start would be to remove the external Firewire hardware and see if stability improves. I would also suspect any drivers or third party kernel extensions that load at startup. Also, try removing all third party plug-ins and see if things improve. Unfortunately, much is still in its first generation on the Intel platform.
As others have noted in this board, a bad stick of memory can also be the cause of frequent crashes. Apps like DP can reveal bad memory where other less memory intesive apps may never exhibit a problem.
Are all of these crashes happening with all projects or just one or two? I have seen corrupt project files, damaged audiio files - even a corrupt sample library cause crashes. Some have had success by simply rebuilding a project's bundles.
This might be a long shot, but do you use Widgets? After being instantiated for the first time, they remain in memory until you either reboot or remove them (you can also quit them in Activity Monitor). If so, I would try removing all Dashboard Widgets in case there is a conflict.
Good luck.
Mike
- Dwetmaster
- Posts: 3491
- Joined: Tue Aug 15, 2006 9:59 am
- Primary DAW OS: MacOS
- Location: Montreal Canada
I also have a MBP and I don't want to go back to G5 but I seriously thought about it. I really can't get a lot done without the constant fear of crashing. I know that if I save often I won't lose much but it still looks unprofessionnal in front of clients when your software crashes constantly like that.
Anyways cchord59, I still think DP is a great software to use when it's working and I believe that, hopefully soon, all will be good. I just can't wait because IT IS frustrating sometimes.
But I work sometimes without any FW plugged in and I'm still getting these crashes? I would love to have someone post here saying his or her system is working well with intel...Frodo wrote:
Most of the complaints I've heard have been from those using firewire interfaces-- particularly those using FW400 interfaces and FW HDs.
Anyways cchord59, I still think DP is a great software to use when it's working and I believe that, hopefully soon, all will be good. I just can't wait because IT IS frustrating sometimes.
MacPro 8Core 2.8GHZ 16GB RAM OSX10.8.3
MacBook Pro 17" Unibody 2011 OSX10.8.3
896mk3, BLA Modded 896HD, BLA Microclock, MTP-AV, Yamaha KX-8, CME VX-7 Mackie Ctrl, megadrum, Presonus C-S,
DP8.04, Bidule, M5 3, Ethno 2, BPM 1.5 Kontakt4, BFD2, SD2, Omnisphere, Wave Arts P-S5, Altiverb7, PSP VW & OldTimer, VB3, Ivory 2 Grand, True Pianos, Ozone 5, Reason 4, AmpliTube3, Bla bla bla...
A few El & Ac basses & Guitars, Hammond A-100.
MacBook Pro 17" Unibody 2011 OSX10.8.3
896mk3, BLA Modded 896HD, BLA Microclock, MTP-AV, Yamaha KX-8, CME VX-7 Mackie Ctrl, megadrum, Presonus C-S,
DP8.04, Bidule, M5 3, Ethno 2, BPM 1.5 Kontakt4, BFD2, SD2, Omnisphere, Wave Arts P-S5, Altiverb7, PSP VW & OldTimer, VB3, Ivory 2 Grand, True Pianos, Ozone 5, Reason 4, AmpliTube3, Bla bla bla...
A few El & Ac basses & Guitars, Hammond A-100.
FWIW, there was an updated driver released about two weeks ago. Don't know if that will help, but just in case, here's the link:
http://www.motu.com/download/download_m ... duct_id=14
http://www.motu.com/download/download_m ... duct_id=14
MacPro5,1 2012, six core 2 x 3.06, 10.12.5, Digital Performer 9.13, 40 gb ram, 828mkIII, 2408 mkII, MTP AV, Logic Pro X 10.3.1, Studio One v 3.2, Pro Tools 12.7.1
- Michael Canavan
- Posts: 3856
- Joined: Fri Jul 15, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: seattle
I recently installed DP on the macbook, and at first it was buggy as hell. I was running 10.4.6. upgraded to 10.4.8 and it's running. Haven't used it enough to say it's running as well as the PPC version though.
If you are having problems it would be a good idea if you give basic system information, RAM, internal and external HD's, OS version, DP version, soundcard.....
If you are having problems it would be a good idea if you give basic system information, RAM, internal and external HD's, OS version, DP version, soundcard.....
M2 Studio Ultra, RME Babyface FS, Slate Raven Mti2, NI SL88 MKII, Linnstrument, MPC Live II, Launchpad MK3. Hundreds of plug ins.
- Timeline
- Posts: 4910
- Joined: Tue Nov 09, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Fort Atkinson Hebron, Wisconsin...
- Contact:
I look at posts like this with disdain. The complainer gives no specs, location or offers anything but negativity to see what is said.
This is a mole pure and simple.
I use FW interfaces with NO issues 5.1 and anyone combining hard drives and IO's on a FW buss is a fool.
Get a life!
This is a mole pure and simple.
I use FW interfaces with NO issues 5.1 and anyone combining hard drives and IO's on a FW buss is a fool.
Get a life!
2009 Intel 12 core 3.46, 64GB, OSX.10.14.6, Mojave, DP11, MTPAV, Key-station 49,(2) RME FF800,
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2
- Dwetmaster
- Posts: 3491
- Joined: Tue Aug 15, 2006 9:59 am
- Primary DAW OS: MacOS
- Location: Montreal Canada
Well TimeLine, there's no reason to get disdained like this.
The only reason I didn't give any specs is because I have te exact same system I've seen over and over again on this board.
I don't know about cchord's problem but it's hell on my brand new macbook pro with 896HD, and the latest drivers. And this, with or without my FW drive plugged in.
I also didn't know about putting everything on my one and only FW being foolish.
On a more constructive tip, I just saw a post by a guy named Yaking taking about SuperDuper being a good way to backup your system before wiping everything and reformat. I'll give it a try tonight and I'll try to report tomorrow.
thanks
The only reason I didn't give any specs is because I have te exact same system I've seen over and over again on this board.
I don't know about cchord's problem but it's hell on my brand new macbook pro with 896HD, and the latest drivers. And this, with or without my FW drive plugged in.
I also didn't know about putting everything on my one and only FW being foolish.
On a more constructive tip, I just saw a post by a guy named Yaking taking about SuperDuper being a good way to backup your system before wiping everything and reformat. I'll give it a try tonight and I'll try to report tomorrow.
thanks
MacPro 8Core 2.8GHZ 16GB RAM OSX10.8.3
MacBook Pro 17" Unibody 2011 OSX10.8.3
896mk3, BLA Modded 896HD, BLA Microclock, MTP-AV, Yamaha KX-8, CME VX-7 Mackie Ctrl, megadrum, Presonus C-S,
DP8.04, Bidule, M5 3, Ethno 2, BPM 1.5 Kontakt4, BFD2, SD2, Omnisphere, Wave Arts P-S5, Altiverb7, PSP VW & OldTimer, VB3, Ivory 2 Grand, True Pianos, Ozone 5, Reason 4, AmpliTube3, Bla bla bla...
A few El & Ac basses & Guitars, Hammond A-100.
MacBook Pro 17" Unibody 2011 OSX10.8.3
896mk3, BLA Modded 896HD, BLA Microclock, MTP-AV, Yamaha KX-8, CME VX-7 Mackie Ctrl, megadrum, Presonus C-S,
DP8.04, Bidule, M5 3, Ethno 2, BPM 1.5 Kontakt4, BFD2, SD2, Omnisphere, Wave Arts P-S5, Altiverb7, PSP VW & OldTimer, VB3, Ivory 2 Grand, True Pianos, Ozone 5, Reason 4, AmpliTube3, Bla bla bla...
A few El & Ac basses & Guitars, Hammond A-100.
I have a mac pro tower 2.66 quad.Frodo wrote:cchord:
Most of the complaints I've heard have been from those using firewire interfaces-- particularly those using FW400 interfaces and FW HDs. There still seems to be the FW bus logjam-- not saying that this is exactly what's causing your problem-- but it's not difficult to shove more stuff down one FW bus than it can handle, even on the Intels.
Forgive me for not researching your setup, but do you have a Book Pro or a Tower Pro?
Depending on the issue, I would sooner consider changing the interface before changing DAWs, but I don't want to speak too soon.
I am using an 828 with the latest drivers, and i've tried running dp without an external fw hd and without the 828 and it still crashed.
I'm not running any 3rd party plugs.
- Timeline
- Posts: 4910
- Joined: Tue Nov 09, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Fort Atkinson Hebron, Wisconsin...
- Contact:
Reloading everything rarely fixes these issues but who knows.
Sorry to unload there but there are so many of us with none of the issues you have. Your post stated " so many others" which isn't true.
You will be able to get your system working I'm sure and I would start with a call to MOTU. I use SCSI still internal on my desktop but I have a MB 1.75 with 5.1 also and it works fine. In fact I have done many sessions on it with FW IO's and No clicks failures or bad audio has ever darkened my door.
It's true, I use RME FF 800's but so what. FW is FW. I use the 800 buss though as the 400 buss is way too slow.
A single 10 channel IO takes up an entire FW 800 buss BTW when monitoring through the same interface on a laptop. On a desktop you can get up to three RME's online if only the analogs are in use, (10 channels max each).
NEVER use FW IO and and FW HD at the same time or your dead!!!! That also includes USB drives at the same time. For a laptop you must upgrade your internal drive to a faster drive or one with more room and just live with it or get an accessories plug but either way you are testing buss speeds internally in a Laptop which is not intended to be a base for a studio system but rather an adjunct to a desktop due to power. The new machines are much the same although the specs say otherwise and you have the added issues of software incompatibilities which have not been resolved.
Still could be your IO is messed up. Maybe get a hold of a few others to try.
Good luck
Sorry to unload there but there are so many of us with none of the issues you have. Your post stated " so many others" which isn't true.
You will be able to get your system working I'm sure and I would start with a call to MOTU. I use SCSI still internal on my desktop but I have a MB 1.75 with 5.1 also and it works fine. In fact I have done many sessions on it with FW IO's and No clicks failures or bad audio has ever darkened my door.
It's true, I use RME FF 800's but so what. FW is FW. I use the 800 buss though as the 400 buss is way too slow.
A single 10 channel IO takes up an entire FW 800 buss BTW when monitoring through the same interface on a laptop. On a desktop you can get up to three RME's online if only the analogs are in use, (10 channels max each).
NEVER use FW IO and and FW HD at the same time or your dead!!!! That also includes USB drives at the same time. For a laptop you must upgrade your internal drive to a faster drive or one with more room and just live with it or get an accessories plug but either way you are testing buss speeds internally in a Laptop which is not intended to be a base for a studio system but rather an adjunct to a desktop due to power. The new machines are much the same although the specs say otherwise and you have the added issues of software incompatibilities which have not been resolved.
Still could be your IO is messed up. Maybe get a hold of a few others to try.
Good luck
If you think I am a mole, your sadly mistaken. Sounds like fun though.Timeline wrote:I look at posts like this with disdain. The complainer gives no specs, location or offers anything but negativity to see what is said.
This is a mole pure and simple.
I use FW interfaces with NO issues 5.1 and anyone combining hard drives and IO's on a FW buss is a fool.
Get a life!
Are you running an intel Mac? if not you probably won't be having the same issues that Many Many other on this forum are.
If you read other posts on this issue, you'll see all the info you need. thats why I didn't include it here.
- Timeline
- Posts: 4910
- Joined: Tue Nov 09, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Fort Atkinson Hebron, Wisconsin...
- Contact:
I appologize and retract the mole comment. Yes I see NOW your speaking of the Intel Mac. Please post your specs in the future. See how important profile info is on first post? I've been harping on this for months.
Yes, If MOTU can't get the Intel machines working smoothly I see your point but I would go back to a non-intel with a lease for a while befor you jump ship on DP.
Yes, If MOTU can't get the Intel machines working smoothly I see your point but I would go back to a non-intel with a lease for a while befor you jump ship on DP.