MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
On a hunch, I exported the soundbite as a deinterleaved AIFF file to the desktop. I opened another template and it popped right in showing its "true colors".
I then dragged the new AIFF back into the track-vocal project and the waveform is visible and functioning.
Still Clueless in Houston.
Buzzy
Early 2009 Mac Pro 4,1>5,1 3.33 GHz Hex Core Intel Xeon OS X 10.8.5 SSD (32 gigs RAM) DP 9.51 PCI-424e / original 2408, 2408mkII, 24I/O, MTP-AV
Tritonemusic wrote:I think I fixed this for myself once by trashing the files in the Analysis Files folder and letting DP reanalyze after restarting DP.
Makes sense, TTM.
I may try this on a backup copy just for my own edification.
Buzzy
Sent from my iPhone using Tapatalk
Early 2009 Mac Pro 4,1>5,1 3.33 GHz Hex Core Intel Xeon OS X 10.8.5 SSD (32 gigs RAM) DP 9.51 PCI-424e / original 2408, 2408mkII, 24I/O, MTP-AV
Oh? It's rare that I see anything BUT the black bar, since upgrading to DP9.
I've been assuming all along that it is Operator Error and that some defaulting of a new feature is causing this to happen. Nothing showed up in Preferences, but I haven't dived deeply enough into the local menus and how the parallels feature (or whatever it's called) works. Assuming it's to blame.
Hmm, I wonder if trashing the analysis files will help, as suggested? For me though, it happens also on brand-new fresh tracks just added to the project. Maybe that doesn't matter though.
I'll try to remember to login to post again later tonight, as this is likely the first thing I'll do when I start a session after dinner.
I should have mentioned that this happened to me in a version of DP7, Buzz. No harm can come from reanalyzing the files, so I'd give it a try. I think your idea of trying it on a backup is wise, however.
DP 10.13, OS 13.6, iMac Pro (2017) 3.2 GHz 8-Core, 32 GB RAM, MOTU M4
Curiouser and curiouser. I didn't get around to re-analyzing files as I was so busy using every minute of my day to get massive amounts of work done on a jazz project this weekend. I definitely want to do a backup before I try that!
I'm trying to think whether this ever happened to me before DP9, and I think it did, but rarely. Maybe we can narrow it down to specific actions or workflow order. At any rate, if re-analyzing straightens it out, it's just a matter of doing backups first for safety.
This happened to me often in DP8, especially with long takes >20,30,60mins. It had been talked about on here before and was assumed to be some bug with long files and trashing analysis folder did seem to fix it sometimes. That said, have NOT seen it yet in DP9.
