- #Moving fl studio projects to new computer archive#
- #Moving fl studio projects to new computer upgrade#
- #Moving fl studio projects to new computer full#
- #Moving fl studio projects to new computer plus#
As I said, it has worked for me, 100% of the time since I started filing that way. But I suspect the vast majority will eliminate the lost, crossed and confused filing if they just do as I suggested. So ok, what I said may not apply to every user, agreed. My reasoning is that it makes keeping organized and manageable files easier, reduces the odds of files getting scrambled, and besides, I dont want to spend a bunch of time figuring out where I was at in my work when I open it up later.
#Moving fl studio projects to new computer archive#
The reason the combination works consistently for me is probably tied in part to the fact that for the most part I only archive or move projects where the tracks have been rendered to stems. But even for them, its part of the solution, and further steps may be necessary. I can imagine a small number of scenarios where it isnt, and I acknowledge there are likely some I havent imagined.
#Moving fl studio projects to new computer full#
And I strongly suspect it is a full solution for the majority of users. Using the "copy project to folder" function is I think, a major part of the solution of a large part of the described problem. But its the way it is and what we have to work with for now.
And I have stated before that the minor changes made for V7 still werent really what was needed to make the process more obvious and transparent. In fact several of us have lobbied for some change in the way this works for quite some time. I am not saying the way things work, or the advice I tried to give is perfect. Most of my frustration is caused by the fact that this topic pops up so frequently, and it seems all to often the user seems hard set on refusing to try any of the advise given. Excuse, I'm old and it wasn't yesterday! Far easier to advise an upgrade. That changes things slightly, and to be honest, I dont remember the exact details. I also overlooked the fact that you were using V6. I think maybe I may have needed the reminder to get some sleep. In fact I not only apologize but thank you for pointing it out. I apologize for the lecturing tone, its quite unintended. It sounds like I should be clicking 'save as' instead, and naming every single revision of a song which might have 20 or even more stages before it is mixed down to wav - maybe that's one place I am slipping up?
In retrospect, what I think I'm doing is following the 'save it' rule - click 'save' every time you modify a project.
#Moving fl studio projects to new computer plus#
Goodness knows what I lost, mostly digital holiday photos on that one I thinkĪ plus is that every song I have recorded exists in name as mp3 and wav format, those are easy to archive Drives do fail though, I had one which turned to toast one day, for no particular reason, it just fried. When I remove the current drive I hope to also clone it so that I have a whole hard drive devoted to back-up. I will never allow any external entity to auto-backup for me again. What is to be done? I guess with the new DAW I need to identify these files from the word 'go' and name them, after listening back to them, I can't see any other way of stopping Mixcraft creating all these numbered files? It's not that easy to find them either, they come up under the File tab but not under the Recent Projects tab which is what I rely on to find previous projects.Īll my work was archived separately (hard drive) until I allowed Microsoft to use that drive for backup - it kept prompting me - it then wiped the entire drive and recorded a 'fail' for backup. Despite naming all my projects, I still end up with hundreds of numbered Mixcraft project files, they seem to be numbered by default? These files are ultimately useless because you don't know what they are after a while. That's comparatively easy for mp3s and wavs but not so easy for the Mixcraft project files.
#Moving fl studio projects to new computer upgrade#
Perhaps now is indeed a good point in time to upgrade my DAW and simplify my saved file names / folders. You have to understand, I sometimes make dozens to scores of a virtually identical audio file until I have it as I want it, that's when the fun begins, suddenly Mixcraft can't find the 25th run I made of a drum roll which I then (25.2) added some reverb to as an afterthought. If I'm lucky I remember exactly where the file was 'borrowed' from and manually direct Mixcraft to the folder and - yes! - the project loads. All my projects are named - otherwise my song production over the last 2 or 3 years or so would be something approaching '0' I should thinkĭon't know why there always seems to be a file missing from a project transfer - even when it's named, Mixcraft starts whizzing through multiple directories.
0 kommentar(er)
