aspenleaf
Max Output Level: -88 dBFS
- Total Posts : 132
- Joined: 2011/08/09 05:18:12
- Status: offline
Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
I'm experimenting with an 500GB SDD for project files, separate from the 250GB SSD I use for my OS (Windows 10 x64). I copied a project, complete with all the audio, from an internal spinning hard drive to the SSD, then opened the project from the SSD. The audio files are still streaming from the internal spinning hard drive, not the SSD. I'd like to keep the files on both the SSD and the spinning drive as redundant backups. I also tried copying a video file from a spinning drive to the SSD, and Windows still accesses the spinning drive instead of the SSD, even though I open the file from the SSD. So it looks like a Windows issue, not a Sonar issue. Can anyone help me get the files to stream from the SSD? Thanks.
|
Zargg
Max Output Level: 0 dBFS
- Total Posts : 10666
- Joined: 2014/09/28 04:20:14
- Location: Norway
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 12:20:30
(permalink)
Hi. Do a save as, and select copy all files with it to the new SSD. Delete old files when done and sure all is well.
All the best.
Ken Nilsen ZarggBBZWin 10 Pro X64, Cakewalk by Bandlab, SPlat X64, AMD AM3+ fx-8320, 16Gb RAM, RME Ucx (+ ARC), Tascam FW 1884, M-Audio Keystation 61es, *AKAI MPK Pro 25, *Softube Console1, Alesis DM6 USB, Maschine MkII Laptop setup: Win 10 X64, i5 2.4ghz, 8gb RAM, 320gb 7200 RPM HD, Focusrite Solo, + *
|
rsinger
Max Output Level: -83 dBFS
- Total Posts : 387
- Joined: 2007/08/25 14:34:57
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 12:25:41
(permalink)
You need to change the folder location inside Sonar. Edit -> Preferences -> File -> Folder Locations -> Project Files.
Copy your Cakewalk Projects folder from your system drive to your secondary drive and then change the folder location inside Sonar.
Sonar Platinum, 64 bit, win 7 pro - 64 bit
Core i7 3770k 3.5 Ghz, 16 Gb Ram, 480Gb + 256Gb SSDs, 1 Tb Velociraptor, Echo AudioFire4
|
aspenleaf
Max Output Level: -88 dBFS
- Total Posts : 132
- Joined: 2011/08/09 05:18:12
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 12:35:52
(permalink)
I changed the folder locations in the preferences section of Sonar, and it is still streaming the audio files from the spinning drive. I was hoping to keep the files on the spinning drive as an easy backup without using an external backup drive, but as long as the files are present on the internal spinning drive, that's where they stream from instead of from the SSD. I did a "save as" of the entire project including audio to the SSD, but it still won't stream the audio from the SSD, even when I re-launch Sonar and make certain I am opening the project file from the SSD.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 12:57:13
(permalink)
Make sure you have 'Copy all audio with project' checked in the Save As dialog; otherwise the project will continue to refer to audio files from the original location.
That said, just copying all project folders to the new drive and launching projects from there should do the trick. I think either you're right that something is up with your Windows config, or you're mistaken that you're launching the projects from the new location. Try moving a test project instead of copying it so there's no chance for any part of it to run from the old location.
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
|
rsinger
Max Output Level: -83 dBFS
- Total Posts : 387
- Joined: 2007/08/25 14:34:57
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 13:00:19
(permalink)
I'm not on my daw, is there still an entry for Edit -> Preferences -> File -> Audio Data? Check the Global Audio Folder. There are different ways to store your audio data and it depends on how you do it. What version are you running? Platinum?
Sonar Platinum, 64 bit, win 7 pro - 64 bit
Core i7 3770k 3.5 Ghz, 16 Gb Ram, 480Gb + 256Gb SSDs, 1 Tb Velociraptor, Echo AudioFire4
|
aspenleaf
Max Output Level: -88 dBFS
- Total Posts : 132
- Joined: 2011/08/09 05:18:12
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 13:11:05
(permalink)
Yes, Sonar Platinum 2016.10. I thought I had it working. I deleted the original files from the spinning drive, then opened the file from the SSD and they streamed from the SSD. Then I did a "save-as" with the audio included back to the spinning drive and closed Sonar. I relaunched Sonar and opened the file from the spinning drive and the files streamed from the spinning drive. I closed Sonar, relaunched and opened the file from the SSD, and the audio then was streaming from the spinning drive again, not the SSD.
|
rsinger
Max Output Level: -83 dBFS
- Total Posts : 387
- Joined: 2007/08/25 14:34:57
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 13:19:36
(permalink)
I don't know what else to suggest. I have had my Cakewalk Projects folder on a secondary drive and that works fine, but I've never tried to have multiple folder locations ...
Sonar Platinum, 64 bit, win 7 pro - 64 bit
Core i7 3770k 3.5 Ghz, 16 Gb Ram, 480Gb + 256Gb SSDs, 1 Tb Velociraptor, Echo AudioFire4
|
dwardzala
Max Output Level: -61 dBFS
- Total Posts : 1470
- Joined: 2008/05/26 19:18:33
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 16:24:12
(permalink)
Delete the files from your spinning drive. Open from the SSD, but don't save as back to the spinning drive, just copy them (and copy them to a new directory not the original one.)
DaveMain Studio- Core i5 @2.67GHz, 16Gb Ram, (2) 500Gb HDs, (1) 360 Gb HD MotU Ultralite AVB, Axiom 49 Midi Controller, Akai MPD18 Midi Controller Win10 x64 Home Sonar 2017.06 Platinum (and X3e, X2c, X1d) Mobile Studio - Sager NP8677 (i7-6700HQ @2.67MHz, 16G Ram, 250G SSD, 1T HD) M-Box Mini v. 2 Win 10 x64 Home Sonar 2016.10 Platinum Check out my original music: https://soundcloud.com/d-wardzala/sets/d-wardzala-original-music
|
aspenleaf
Max Output Level: -88 dBFS
- Total Posts : 132
- Joined: 2011/08/09 05:18:12
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 18:29:28
(permalink)
Thanks for all of the suggestions. Unfortunately, I've tried them all and it still streams from the spinning drive unless I delete the files. I want to use the spinning drive as an internal backup drive, so I don't want to delete those files. As far as I know, there is no way to keep Windows from accessing that drive as long as it's connected to the motherboard. If anyone knows of a way to do that, please let me know.
I still don't understand why it won't use the files on the SSD. Sonar goes to that drive to open the project file, now that I've changed the folder locations, but even though the audio folder is in the project folder on the SSD, it still goes to the spinning drive for the audio files.
As I stated in my original post, it isn't just Sonar that accesses the spinning drive files instead of the SSD files. Windows Media Player does also, so I think it must be a Windows issue, but I don't know of any settings to control that. Can someone enlighten me?
|
aspenleaf
Max Output Level: -88 dBFS
- Total Posts : 132
- Joined: 2011/08/09 05:18:12
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 19:13:48
(permalink)
I came up with a partial, albeit cumbersome, solution.
I disabled the drive in Device Manager. Then when I launched Sonar and opened the project file, it said the audio files on the spinning drive were missing and where would I like to look for them. I navigated to the audio folder in the project folder on the SSD and Sonar is now using those files. So maybe it is something in the Sonar project file that is looking for the files on the spinning drive instead of the SSD.
I'll have to enable the spinning drive again and see if Sonar goes back to the spinning drive or if it will continue to use the SSD.
|
aspenleaf
Max Output Level: -88 dBFS
- Total Posts : 132
- Joined: 2011/08/09 05:18:12
- Status: offline
Re: Copied Sonar project to SSD, but Sonar is still accessing audio files on old drive
2016/12/11 19:24:11
(permalink)
I think that might have made Sonar change the project file to now look for the audio files in the audio folder on the SSD. I enabled the spinning drive and re-launched Sonar, opened the project and it went to the SSD instead of the spinning drive. I'll have to try a new project, starting it on the SSD, to see it Sonar will look for the audio files on the SSD for projects that were initially saved that way. Hopefully this will only be an issue on older projects I started on the spinning drive.
Can anyone tell me how to edit the project file so it looks for the audio files on the SSD? I checked the Cakewalk.ini and aud.ini files and didn't see any settings for individual project files.
|