Issues transfering Sonar project between two computers

Author
BLUtunes
Max Output Level: -90 dBFS
  • Total Posts : 21
  • Joined: 2011/04/17 13:14:04
  • Status: offline
2011/04/25 14:33:29 (permalink)

Issues transfering Sonar project between two computers

I'm new to Sonar. In fact, I'm pretty inexperienced with DAWs in general, although I spent a LOT of time working in professional studios back in the pre-DAW days.
 
Anyway, I've run into some problems in transferring a Sonar project between two computers. I mostly chose Sonar because some of my other musician friends use it and like it, and I wanted to carry files back and forth between them. Last weekend, I went over to a friend's house to have him lay down some tracks for me. I brought the files over on a flash drive as "bundle files." He was able to open the files just fine, record his stuff, and then repack it all back up for me to take home to work on. However, my computer runs XP in 32 bit and his computer is a newer machine that runs Sonar as a 64 bit program.
 
As I've continued working on the project at home, I decided to use Session Drummer to add some drum parts. After I started messing around with the program, I realized that it had opened up SD in the 64 bit version, and I can't figure out how to make it do 32 bit. This caused it to be pretty unstable. When I've added SD to other projects (which had NOT been run through Gary's 64 bit machine), it opens as a 32 bit program and runs just fine. Is there anything I need to be aware of to keep this problem from popping up again in the future? I certainly hope to work with my friend some more on other recording projects.
 
Also, I will need to reconstruct this project, since I don't know what ELSE may be goofy about it. (Perhaps there are also some plugins that are now trying to open as 64 bit, for example.) So I need to reconstruct this project, but I'm not sure how to go about it exactly. I saved the original bundle and project files (i.e. BEFORE I took them over to his house for work) and just changed the file names. So, I still have them. I assume that I can just re-open that original bundle or project file, add the additional tracks that we recorded, and I should be good to go.
 
However, I don't really understand how Sonar handles file management. If I open the old bundle file (after changing the name back to the original name), will Sonar try to create ANOTHER folder with that song name, even though there is already a folder under that name? Or will it find the folder that it's looking for and install the files in there? For that matter, would there be any reason to even bother with a bundle file? Maybe it would be better just to open the original project file, since all of the audio files that it would be looking should already be there.
 
Thank you for your help!
Brad
#1

4 Replies Related Threads

    ChipAllen
    Max Output Level: -88 dBFS
    • Total Posts : 109
    • Joined: 2006/09/13 20:39:35
    • Location: eastern Massachusetts, USA
    • Status: offline
    Re:Issues transfering Sonar project between two computers 2011/04/25 14:49:11 (permalink)
    Welcome to Cakewalk and to the forums!!!
    I think you'll enjoy Cakewalk quite a lot.
    Most people do, although many of the posts in the forums are about problems because that's when we need each other.

    I can't address your 32/64 bit problem, I'm sorry to say.
    But the answer to your "is there any reason to even bother with a bundle file?" is No, you should be able to just open your original project file and continue working on your project.   You mentioned renaming some of the files.  If Cakewalk has any trouble finding files you might need to rename them back.
    The primary reason to use bundle files seems to be to get all the data in one file, for ease of transfer between machines, as you found.

    #2
    BLUtunes
    Max Output Level: -90 dBFS
    • Total Posts : 21
    • Joined: 2011/04/17 13:14:04
    • Status: offline
    Re:Issues transfering Sonar project between two computers 2011/04/25 18:46:42 (permalink)
    Thank you! I had heard that there were pretty friendly (and helpful) people hanging out here. That's what I'll do then. I'll change the name of the new files, and change the old file names back to the original filenames and then just open up the original project file. Then transfer the new tracks in. (I have some more tracks to import into the project anyway.)

    Would still like to figure out how to avoid having any of these problems in the future, as I hope to keep working with my friend on projects. We're both running Sonar, so there should be a way to do it, even though he's 64 bit and I'm 32.

    Brad
    #3
    ChipAllen
    Max Output Level: -88 dBFS
    • Total Posts : 109
    • Joined: 2006/09/13 20:39:35
    • Location: eastern Massachusetts, USA
    • Status: offline
    Re:Issues transfering Sonar project between two computers 2011/04/25 20:57:23 (permalink)
    You heard right, there are a lot of very, very helpful and knowledgeable people on the forum. You can learn a lot just by lurking and reading.

    I've pretty sure that there's a solution to the 64 bit/32 bit issue.
    It's probably just a save option.
    My guess is that before another day's end somebody who knows will chime in and you'll have your solution.
    #4
    BLUtunes
    Max Output Level: -90 dBFS
    • Total Posts : 21
    • Joined: 2011/04/17 13:14:04
    • Status: offline
    Re:Issues transfering Sonar project between two computers 2011/04/26 08:49:56 (permalink)
    Update: I was able to open the old project file, and import that added tracks that we did at my friend's house. That went fine. Thank you for your help!

    Still would like to know what caused the problem in moving files between computers running a 32 bit OS and a 64 bit OS.
    #5
    Jump to:
    © 2024 APG vNext Commercial Version 5.1