Hiya!
I have installed a new system, build latest QTractor (playing with it now, man!) and copied some projects. Well, guess what - he opens them but posibly because the path is different to the projects folder, does not load audio files and I don't know how to reload them into the project so that QTractor would re-associate them again. M?
Okay, I've fixed the issue
Okay, I've fixed the issue but I am still happy I created this thread so everybody and Rui would know that such a problem may exist.
My sound files were in one folder and the projects was in another. Both folders were in a QTractorSessions folder where I save everything, so all relative paths were correct.
On the old system, where the project was created, it was loading okay although the project file was in one folder and samples in the other. On the new system, however, QTractor seemed to search for samples in the folder where the project was in and could not find audio files.
What I did was edit the paths to the audio of every clip, that partially helped but the clips sort of reloaded and so all my editing of clips' lengths were gone - the audio maximized all clips.
So then I just took the project file and put it into the same folder with the sound files. Then it worked.
I think the way session project is created - the dialogue - has a potential to screw locations like this, because when you save midi clips and audio files, you are asked to save them in a location and so you create a folder for them, but saving a project file is not synced with that and you save it, not realizing that saving a session project is not saving it into the dir you have specified before for midi clips. You know what I mean?
Re: Reloading old projects
Hi, Lougi,
Oh well, you may find that existing .qtr session files just points to external media content files.
Qtractor doesn't own nor aggregate any of the files under one single directory as, for example, Ardour does. Speaking of which, all Qtractor content are file-paths/references as what may be considered as links in Ardour realm.
Anyway,
There's (my own) hidden agenda to make all media files bundled in a, ... erm, "bundle" file. Think of it as an ODF file, zipped for compression sake, suitable for extra-inter-web exchange, got that? Well, that is not in the horizon yet. But is feasible. If someone has the nerve to step in, I'm all green-lights to embrace the effort. Outsourcing, eh?
Cheers.
Post new comment