Copy link to clipboard
Copied
So I'm having two separate issues with my Audition Project;
I am working on a radio drama and the files are fairly long -- 15-30 minutes long. The issue i'm having is every so often (Usually when I open the project) random tracks will be muted. not on the track bar, but the actual clips, which makes it incredibly difficult to track down and unmute.
Second thing is; I cannot render out master to adobe encoder. just won't work.
Third; when I do a mixdown the file's time tracker is over 2 hours long. which, as i've said before, is not anywhere near how long my actual files are.
Copy link to clipboard
Copied
Which version of Audition are you using and on which computer platform?
Are you not rendering the mixed down audio within Audition?
Usually if the session time is showing as much longer than it should be there may be a random very short clip hidden away up at the far end of the timeline. If so you need to search it out and remove it. The session shouldn't be any longer than your included clips.
Copy link to clipboard
Copied
For the AME (Adobe Media Encoder) problem, what version of Audition and what exact version of AME are you using?
Copy link to clipboard
Copied
The issue isn't a clip at the end -- the file plays exactly as long as it should but ti shows as being multiple hours long (Actually, the timer changes from time to time; 1:27:30 to 2:57:30 or anything in between).
I'm using the latest version of CC (I'll double check that everything is updated, but last time i check it was the latest version)
Copy link to clipboard
Copied
patrickp29961343 wrote:
The issue isn't a clip at the end -- the file plays exactly as long as it should but ti shows as being multiple hours long (Actually, the timer changes from time to time; 1:27:30 to 2:57:30 or anything in between).
The timer can only show timelines of that length in the Multitrack view if there is something on a track somewhere to extend it. It doesn't matter how long a file plays for there can still be an unwanted minute clip somewhere up the timeline to cause this behaviour.
Copy link to clipboard
Copied
ryclark wrote:
patrickp29961343 wrote:
The issue isn't a clip at the end -- the file plays exactly as long as it should but ti shows as being multiple hours long (Actually, the timer changes from time to time; 1:27:30 to 2:57:30 or anything in between).
The timer can only show timelines of that length in the Multitrack view if there is something on a track somewhere to extend it. It doesn't matter how long a file plays for there can still be an unwanted minute clip somewhere up the timeline to cause this behaviour.
There is of course another solution to this, and that's just to highlight the part of the timeline that you want to mix down, rather than the entire session. Make the time selection, and right-click on it. Select Mixdown Session To A New File>Time Selection. That will give you a mixdown of just what you want. But I agree with ryclark about the extra mini-clip being there somewhere, I'm afraid - never seen anything other than this causing this problem.
Copy link to clipboard
Copied
Allow me to be more vivid with my problem by showing you it.
Attach in that link is a short gif of the timer from my VLC player timer of the exported mixdown. It does 'wind down' in terms of length -- getting down about to 39~ minutes before continuing to run back up to the before mentioned times. The only solution I've found for this is to not export anything through Audition or Premier (which has the same issue).
Copy link to clipboard
Copied
Does it do the same if you output the mix from Audition as a standard .wav file? Is it just an .mp3 mix from Audition that does it? Also does the bad file open and play and show the correct length if you open back up into Audition?
Copy link to clipboard
Copied
It plays the correct lenght on the computer -- on my phone (Where I listen to the mixdown during my commute) it will act as though the super long length is right and just loop the audio.
I didn't notice the dialog to change the format type for the mixdown, but It happens in .mp3 and .wma (exported to this instead of .wav by accident) but not .wav. So i'm assuming it's a codec issue now.