Timeking
Max Output Level: -87 dBFS
- Total Posts : 158
- Joined: 2010/09/12 20:00:08
- Location: fort pierce, fl, usa
- Status: offline
cannot identify unreadable filename after CleanAudioDisk command
Any idea how to determine what the actual filename is when the dialog box is too narrow to actually see the path to the file?
Greg Graves, Ohmegga Audio Studio Fort Pierce FL timeking {[at]} fflynet.net
|
Timeking
Max Output Level: -87 dBFS
- Total Posts : 158
- Joined: 2010/09/12 20:00:08
- Location: fort pierce, fl, usa
- Status: offline
Re: cannot identify unreadable filename after CleanAudioDisk command
2013/12/02 19:41:20
(permalink)
Greg Graves, Ohmegga Audio Studio Fort Pierce FL timeking {[at]} fflynet.net
|
Timeking
Max Output Level: -87 dBFS
- Total Posts : 158
- Joined: 2010/09/12 20:00:08
- Location: fort pierce, fl, usa
- Status: offline
Re: cannot identify unreadable filename after CleanAudioDisk command
2013/12/04 01:43:05
(permalink)
This is not a serious problem (yet), but without the ability to CleanDisk, all those bad takes are going to pile up and eventually fill my harddrive. Am I not being clear as to what my question is? Is the only 'fix' to open all my project files one by one and see which one is corrupt? that would take days....
Greg Graves, Ohmegga Audio Studio Fort Pierce FL timeking {[at]} fflynet.net
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: cannot identify unreadable filename after CleanAudioDisk command
2013/12/04 02:03:22
(permalink)
I wish I had an answer for you. I have not used anything other than the "Save As" function to clean projects since the introduction of per-project audio folders.
|
Timeking
Max Output Level: -87 dBFS
- Total Posts : 158
- Joined: 2010/09/12 20:00:08
- Location: fort pierce, fl, usa
- Status: offline
Re: cannot identify unreadable filename after CleanAudioDisk command
2013/12/04 09:50:37
(permalink)
Yes, you ~could~ clean a project by SaveAs to a new ProjectFolder, and then delete the old folder. That would work IF you knew which Project was had the corrupt wrk file, which in my case I don't. I only know that some wrk file somewhere has taken a crap, but not which one. I guess the only way to resolve this is the brute force method of going through every one of my wrk's (or whatever the extension is). As Sonar is currently coded, the CleanAudioDisk is only useful as long as you don't have a corrupt file, in which case you don't know what it is unless you are keeping all your projects near the C:\ root of your harddrive. Bummer.
Greg Graves, Ohmegga Audio Studio Fort Pierce FL timeking {[at]} fflynet.net
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re: cannot identify unreadable filename after CleanAudioDisk command
2013/12/04 10:41:42
(permalink)
The text of many dialogs may be captured in the Windows clipboard by pressing CTL-C. I have no idea if that'll work for this particular dialog, but the trick works with all Windows messageboxes and with programs that utilize Windows messageboxes for their own dialogs. Once in the clipboard, open Notepad and press CTL-V.
 All else is in doubt, so this is the truth I cling to. My Stuff
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: cannot identify unreadable filename after CleanAudioDisk command
2013/12/04 11:38:17
(permalink)
My guess is the unreadable file is not even a SONAR file, but a file from some other app that uses the same extension (.TPL for Template is quite common). If Dave's tip doesn't get you the full path, you can search whatever part of the path is visible for that extension, and I wager you will find a non-Cakewalk file.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
arachnaut
Max Output Level: -67 dBFS
- Total Posts : 1168
- Joined: 2007/05/05 17:24:33
- Location: Sunnyvale, CA USA
- Status: offline
Re: cannot identify unreadable filename after CleanAudioDisk command
2013/12/04 13:00:23
(permalink)
- Jim Hurley - SONAR Platinum - x64 - Windows 10 Pro ASUS P8P67 PRO Rev 3.0; Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X; GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61 64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither
|
Timeking
Max Output Level: -87 dBFS
- Total Posts : 158
- Joined: 2010/09/12 20:00:08
- Location: fort pierce, fl, usa
- Status: offline
Re: cannot identify unreadable filename after CleanAudioDisk command
2013/12/09 07:10:15
(permalink)
Well I "knew" that the Crl-C Ctrl-V wouldn't work, but I tried it anyway, and sure enough, no worky. HOWEVER, the sysexp.exe program did capture the contents of that window, and it turned out to be a truncated .cwp file of a previous version of one of my projects (I name projects Song v01, song v02, etc., periodically saving to same project folder ... that way I can always go back a level and retrieve something I screwed up [a procedure I learned the hard way in Microsoft Word]). SO MUCH THANKS!!
PS: You can tell I"ve been a long-time Cakewalk user since I referred to my .cwp files as .wrk. Silly me.
Greg Graves, Ohmegga Audio Studio Fort Pierce FL timeking {[at]} fflynet.net
|