-
1. Re: Render Required Audio Files Insanity!
Kevin-Monahan Jan 30, 2014 3:17 PM (in response to jmottle)Hi jmottle,
Adobe phone support staff have to be some of the most incompetant and useless people I've ever dealt with professionally, so I'm sending my plea here.
Did you happen to get a case number? If so, PM it to me and I'll escalate your case. Sorry for all your issues.
Thanks,
Kevin
-
2. Re: Render Required Audio Files Insanity!
jmottle Jan 30, 2014 3:51 PM (in response to Kevin-Monahan)After the headache with the Mackie control surface and support I was VERY hesitant to even bother calling support again, however this afternoon I decided to spend 3 hours (1 on hold) calling again. I had somone who at least this time who at lest had used the software before. (case #185130639)
Becuase we have very large projects (8 that are each 8 hours long) and around 4TB of video and audio, all of this data is on a networked Gigabit Synology NAS. I've been editing from Synology NAS devices on much shorter projects (usually around 30-60 min) and have never had this above issue. THe support person however has told me they will not help me as using Premiere from a network is not supported. A bit questionable as I've never had any issues for the last 6 years doing just this.
Before I run out and purchase a very expensive RAID array that can be attached locally, I want to know why the issue is happening first. Of course as is always the case I'm under a massive deadline. I'm supposed to deliver all of this rendered footage by Wednesday next week.
If you are able to esacale this and allow me to speak with someone who can look into this, I woudl be most appreciative. I have a lot of people who are going to be pretty pissed when I tell them we're going to blow this deadline.
Jeff
-
3. Re: Render Required Audio Files Insanity!
jmottle Mar 1, 2014 9:45 AM (in response to jmottle)Ok, so I moved all of the data for one project to an external SSD connected to my new Mac Pro via Thunderbolt. I STILL have the same problem. I need to speak with someone at Adobe about how to fix this ASAP. I'm fed up with this BS! While I was away for the last few weeks, I would have hoped someone from Adobe would chime in here to assist. However I guess that was wishfull thinking!
-
4. Re: Render Required Audio Files Insanity!
Peru Bob Mar 1, 2014 10:55 AM (in response to jmottle)Did you PM Kevin?
-
5. Re: Render Required Audio Files Insanity!
jmottle Mar 1, 2014 11:00 AM (in response to Peru Bob)I just did now. I had assumed he would read the thread he posted to.
-
6. Re: Render Required Audio Files Insanity!
Kevin-Monahan Mar 1, 2014 1:38 PM (in response to jmottle)Hi jmottle,
I just answered your PM. The issue is the way the Audio Sequence Settings are chosen in setting up a Multicamera Source Sequence. If you choose Switch Audio when setting it up, all tracks will need to be rendered. See my response is this thread: http://forums.adobe.com/message/6145770#6145770
Sorry again for the inconvenience.
Thanks,
Kevin
-
7. Re: Render Required Audio Files Insanity!
jmottle Mar 1, 2014 2:45 PM (in response to Kevin-Monahan)Hi Kevin,
I sent a PM, but for the benefit of others I'm posting here too. None of my projects were set up with a multii camera sequence. The one I am working on currently only has one camera and the others, though they have multiple video tracks, were created manually. As you can see in the sequence settings I don't have that option for the audio settings. Unless I'm missing something, I don't think this is my problem.
Weeks ago I also tried an experiment and deleted every audio track except for one, which also rules out flattening the sequences. While it reduced the number of audio tracks it had to render, it still took forever to perform and is somethign that previously never had to be done.
-
8. Re: Render Required Audio Files Insanity!
jmottle Mar 5, 2014 3:39 PM (in response to jmottle)For the benefit of anyone else who runs into this issue, I was finally able to get resolution on this. I'll spare the details of how frustrating this process was, but it's fixed now.
In our case our audio clips were 96000 Hz, however the Sequence settings were at 48000 Hz. Every time we tried to export this was forcing the audio to be downsampled first. Once the sequence settings were set to 96000, the rendering of audio stopped and immediately exported. One month of frustration fixed in 10 min by a level 2 enterprise support tech who actually knew what they were doing and were quite knowledgeble. Which is a lot more than I can say for al of their other techs.
-
9. Re: Render Required Audio Files Insanity!
shooternz Mar 5, 2014 4:14 PM (in response to jmottle)Mentioning audio source info like this in your first post
In our case our audio clips were 96000 Hz, however the Sequence settings were at 48000 Hz.
...may have lead to a quicker resolution.
You did mention wavs but you also knew the issue was about audio rendering.
I am sure someone would have picked up on it.
From the User Reference File.
Create a 24p sequence
1. Select File > New > Sequence.
2. From the Available Presets list on the Sequence Presets tab, choose the 24p preset that matches the frame aspect ratio and audio sampling
rate of most of your footage. 24p presets are located in the DV-24p, DVCPRO50 > 480i, DVCPROHD > 1080i, and DVCPROHD > 720p
folders.
3. Select a location, type a name for your sequence, and click OK.
-
10. Re: Render Required Audio Files Insanity!
jmottle Mar 5, 2014 4:16 PM (in response to shooternz)If I thought to mention it, I probably would have been able to solve it myself. I did not mention it as I did not know this was the issue.
-
11. Re: Render Required Audio Files Insanity!
Kevin-Monahan Mar 5, 2014 4:38 PM (in response to jmottle)Jeff,
Very glad this was solved. I apologize that it took so long to get a solution to this problem. This case shows how crucial it is to set up your sequence to precisely to match clip settings.
Thanks,
Kevin -
12. Re: Render Required Audio Files Insanity!
shooternz Mar 5, 2014 4:52 PM (in response to Kevin-Monahan)If I am correct...a video clip that does not match gets a "warning message".
Why not the same for audio? (as it does in Audition)
Maybe a FR





