Help with Audition- Files not found- Link media

[John25293753dd87]

Hello,

   I recorded a few voice tracks on my laptop and want to edit them on my pc. I found the file via the cloud on my PC and when I clicked it, I get the '1of1 files reference by the Session could not be found. I then tried to copy the file over directly to my pc, but I get the same error when I try to open it up on my PC.

It gives me an option to click 'link media' at the bottom but when I do, I don't know what I need to look for. It just says Host_005 in the file name. 

I included a few screen shots. Any help would be greatly appreciated. Thanks! 

[SteveG_AudioMasters_]

We'll get this bit out of the way first: Rule one of working with cloud-based media - don't. You shouldn't ever save work you're wanting to preserve, only on cloud-based media. At the best of times it's flaky, and if you don't understand the implications it will go wrong. And I'm pretty sure you haven't understood what you've done.

What you appear to have done is saved the session file remotely. Trouble is, that file doesn't contain any of the audio, so just copying it and trying to open it is inevitably not going to find your audio, because it isn't on the machine you are now trying to open the session file on. All the session file contains is information about how the session is laid out, etc - but no audio.

If you want to edit your podcast on a different machine, you don't just need the sesssion file, but the audio files as well - and they will be on the machine they were recorded on originally. What you need to do is put them in a folder that isn't your desktop, and transfer transfer the audio, and the original session file to the machine you want to edit on. You may still need to relink the files, but now you'll be able to locate them, because they'll be in the same folder that the session file is in. You should keep a copy of all of this on your original machine, because that's your safety fall-back for when the cloud's bit of wet string fails.

Whilst we're about it, the other thing you should never do (for the same reason) is attempt to save actual audio remotely to a cloud-based storage 'solution'. Always save it locally, and then transfer the completed files. That way, when it screws up, you can have another go.

Sorry if this seems a little harsh, but I'm afraid that this is the reality of cloud-based working. If you don't understand exactly what is (or just as likely isn't) going on, it's going to bite you!

[John25293753dd87]

Thanks for the help and advice. Your point about the cloud makes sense.

So what you are saying sis I saved the session, but not the audio. Where would I find the audio porition? Sorry for the newb question, but I am not seeing it. 

[SteveG_AudioMasters_]

That I can't tell you - the only path indicated is the one to the session file that's on your desktop. When you first recorded the files, Audition would have asked you where to store the audio, and that's where it will be. Possibly on your desktop, but I really can't tell, I'm afraid. It will be wav files you're looking for, and they will almost certainly be there somewhere, because the one thing Audition is very good at, if recording in Multitrack view, is not losing files.

[John25293753dd87]

Thanks for the help. Found everything I needed to find and moved it over. 

[shorewalker]

As a newcomer/returnee to Adobe Audition (I last used it under the Syntrillium CoolEdit label) I am frequently surprised by the program's absolutely unituitive use of media assets in all sorts of places. I am still forming a mental model of how this works. But I can barely believe that the same company that gives us Adobe Indesign, with its clear and understandable use of media assets, has also given us the current state of Audition..

[SteveG_AudioMasters_]

Adobe is a huge company, and it has many disparate development teams. They are not obliged all to do the same thing with assets, and especially in Audition's case there's a good reason for that - and it's to do with user use continuity. A lot of the asset handling hasn't changed, simply because corporate users have requested that it doesn't - they don't want their users either having unworkable upgrades, or having to alter their working practices. I'm not sure exactly how you get around that, but it's very much part of the reason for not altering things without a lot of consultation and careful thought.

On top of that, of course, is that Audition is 'different' in Adobe terms anyway, because of its roots - as you've noted.