joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Clean Audio Tool - Does it REALLY have to go through everything on C:?
When all my audio is in a dedicated folder on D: which is what I have selected as the Audio Path?
|
jpetersen
Max Output Level: -61 dBFS
- Total Posts : 1499
- Joined: 2015/07/11 20:22:53
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/19 16:58:37
(permalink)
☄ Helpfulby joden 2016/03/20 14:28:25
Clean Audio Folder is something everybody tries once and then gives up on.
It was designed in the Win3.1 days when there was no recycling bin yet.
It had a bugfix in Newburyport, but the concept has never been updated.
The generally accepted workaround - GAW(R) - is to use "Save As", ensure you have "Copy All Audio with Project" selected, then save to a new directory.
You now have a new directory containing only those audio files you really use.
Unfortunately you now need to delete (or better rename) your original directory, then name your new directory to the original name.
|
annifarkle
Max Output Level: -88 dBFS
- Total Posts : 136
- Joined: 2007/01/06 22:47:05
- Location: The Seattle area
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/19 19:45:32
(permalink)
I 100% agree. I haven't tried using that in years for those reasons. I like your work around.
Boredom is the enemy, So says the child in me. AGF  Sonar Platinum SubscriptionWin 10 Pro AMD A10-7850 Radeon R7, 12 Computer Cores 4C+8G 3.70 GHzRam- 16 GB64-bit OS x64 processor
|
vanceen
Max Output Level: -74 dBFS
- Total Posts : 814
- Joined: 2003/11/08 08:55:56
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 12:33:30
(permalink)
The last time I attempted to use Clean Audio, it deleted literally all my audio files. Fortunately I had backups.
Mind you, it was probably my mistake. But then I've been using Cakewalk / SONAR for 26 years, so it's not a rookie error.
Don't use Clean Audio Files. The described workaround works well.
SONAR Platinum Windows 10 ASUS X99E WE Core i7 5960X 32 GB Corsair DDR4 2133 C13 Fireface UFX USB driver 1.098 GeForce GTX 950
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 13:00:32
(permalink)
☄ Helpfulby bapu 2016/03/20 18:37:32
But to be fair, it's invaluable for those still running Windows 3.1
|
joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 13:24:41
(permalink)
Yeah I have never used it before (after about 15 years of CW use) but I am wanting to use projects on a laptop and thought I could reduce size a bit. I use the Per Project audio folders, but when I look at those, some have up to 15 different wav files when all the project has is three tracks. This makes the size of the folder huge. It was these files I was hoping could be cleared but using the Clean Audio Tool...but going by the derisory comments (not much constructive!!) here, it is something CW should probably write OUT of the software!!
|
Johnataxia
Max Output Level: -90 dBFS
- Total Posts : 12
- Joined: 2013/10/31 14:10:43
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 13:50:33
(permalink)
I use "Clean Audio Folder". And to be honest I never have a problem. As the post says I never understand why it explores all my drive! And the time it takes, as the years pass it takes more time because we have more capacity drives ! Bue well, meanwhile Sonar looks all my files I go to prepare another round of "Mate" ;) Very Interesting method " jpetersen" I never realized of that option!
|
joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 14:17:29
(permalink)
jpetersen
Clean Audio Folder is something everybody tries once and then gives up on.
It was designed in the Win3.1 days when there was no recycling bin yet.
It had a bugfix in Newburyport, but the concept has never been updated.
The generally accepted workaround - GAW(R) - is to use "Save As", ensure you have "Copy All Audio with Project" selected, then save to a new directory.
You now have a new directory containing only those audio files you really use.
Unfortunately you now need to delete (or better rename) your original directory, then name your new directory to the original name.
Just tried that, but it does not really work all that well. Yes it reduces a little bit (in the example one I tried it reduced from 132MB to 101MB) but there are still multiple wav files for the same part.
|
bvideo
Max Output Level: -58 dBFS
- Total Posts : 1707
- Joined: 2006/09/02 22:20:02
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 14:40:51
(permalink)
FYI when it searches all your drives it is not looking for audio files, it is looking for all possible project files so it doesn't delete audio that is in some project somewhere else.
W10 pro, Sonar Platinum, Alesis Multimix 16 FW, MOTU Express 128, Gigabyte Z370 HD3P, i7 8700K, 16 Gigs, ssd + 2 X 2T disks, D50-MEX, JV80, A90EX, M1REX
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 14:52:59
(permalink)
jpetersen
The generally accepted workaround - GAW(R) - is to use "Save As", ensure you have "Copy All Audio with Project" selected, then save to a new directory.
You now have a new directory containing only those audio files you really use.
You can slim things down even further if you also check "Create One File Per Clip." This trims any audio not explicitly referenced by the clips in your project. Also check out my "Friday's Tip of the Week" for Week 70 about "The Third Way to Back Up Your Files." This splits the difference between minimum size and retaining portions of files not explicitly referenced by the clips themselves. Finally, remember that one track may reference more than one file unless you bounce all your clips and flatten any processing. Additional files are generated for undo as well.
|
joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 15:01:16
(permalink)
Thanks Craig, but how does one determine, what are, say, the files created for undo? Although I must admit to being confused by this as when I re-open a project (for example I come back to it the next day after a shutdown) and go to the Undo section it always has zero undo options?
I will check your tip of the week...had not noticed that one.
|
joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 15:08:22
(permalink)
Okay just tried the Create One File Per Clip, and it showed LESS reduction than Clean Audio Folder...COFPC reduced to 121mb from 132mb (CAF reduced to 101) so neither is really reducing it much at all.
I think the only (pita) method is to export each part down to a wav file and then reimport and THEN save the project.
|
jpetersen
Max Output Level: -61 dBFS
- Total Posts : 1499
- Joined: 2015/07/11 20:22:53
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 17:31:26
(permalink)
The method strips out unused wav flies quicker and safer than the CAF utility.
If you are still working on your project and just want to clear unused clips, don't bounce
to single tracks yet. If you are still left with many files, be aware your project is using them.
You may like to delete tracks and clips you do not need (are you sure?) manually in your
Sonar project before using Save As.
But if the object is to reduce size to a minimum (perhaps the project is complete and ready to archive?),
then it is valid to bounce down all open Audiosnapped clips, etc., to tracks.
Also check the bit depth and sample rate of your audio clips. If it is higher than 44k1Hz (or 48kHz)
then consider reducing to one of the two bit rates and use 24 bit depth.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 18:08:16
(permalink)
☄ Helpfulby joden 2016/03/20 19:42:38
joden
Okay just tried the Create One File Per Clip, and it showed LESS reduction than Clean Audio Folder...COFPC reduced to 121mb from 132mb (CAF reduced to 101) so neither is really reducing it much at all.
I think the only (pita) method is to export each part down to a wav file and then reimport and THEN save the project.
If you "Save As..." into a new folder with "Copy all audio with project" and "Create one file per clip" checked, that should give a minimal audio file size. There will be as many audio files as there are clips. However, you mentioned three tracks. At 44.1 kHz/24 bit, each minute of one track of continuous audio is about 15 MB. If you're recording at a higher sample rate or bit depth, the size will be larger. But assuming 44.1/24, three stereo tracks that lasts three minutes will require around 135 MB. The only way you're going to get it smaller is to go 16 bit, or use data-compressed files like FLAC or MP3. Even with a laptop, it's worth getting an external drive for data (which will also improve operational efficiency). I bought a 500 GB USB 3.0 drive for $18 on closeout at Office Max; it's 4.5" x 3.25" x 0.5" and needs no external power supply. Granted that was a super-low price, but it's well worth spending a few extra bucks instead of nickle and diming yourself on the megabytes.
|
joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 19:31:35
(permalink)
Yeah, point taken Craig The ultimate goal, as these are backing tracks, was to be able to turn them of and on whenever, wherever when playing live, for EG if a guitarist sits in, I can simply mute out the guitar parts. Instead of "fixed" MP3 files which require a whole process to remove parts. This is why I want to also experiment with Sonar Playlist, I am currently using Cantabile to run the MP3 backing tracks and live softsynths (pianos, EPs organs etc). The tracks are mostly just drums and the odd guitar part or two. Anyhoo maybe I AM trying to "nickle and dime" myself too much, so I will think on your comment seriously. Cheers Dennis
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 20:42:19
(permalink)
Why not just convert the individual tracks to MP3? Or Ogg Vorbis, since SONAR supports it natively and a lot of people think it sounds better for a given bit rate? SONAR isn't a snob, it'll play whatever you throw at it.
|
joden
Max Output Level: -65 dBFS
- Total Posts : 1263
- Joined: 2007/09/22 17:03:46
- Status: offline
Re: Clean Audio Tool - Does it REALLY have to go through everything on C:?
2016/03/20 22:52:05
(permalink)
Yeah, good suggestion. That might do it, although Sonar's MP3 converter is not the quickest around so that may take a while...Maybe export the tracks to wav and then convert in, say, Audacity...which takes about three seconds...whatever, your suggestion is sensible and does get around the size issue. Although I am still sussing out using the USB drive idea as well 
|