Skip navigation
jornbhor
Currently Being Moderated

problem with audio export blocked at 8000 hz since AE CC 12.2.0.52

Dec 17, 2013 2:42 AM

Hi,

 

Today it's a mess, I don't know if it's my iMac which is dying or what, but several problems.

 

I try to export a comp, it has worked well and today, the frequency of the audio in the render parameter is blocked at 8000 hz, when I try to use another frequency and confirm, the frequency is back at 8000 hz !!! I try with other audio files, but it's the same problem...

 

solution ?

Branched to a new discussion.
 
Replies 1 2 Previous Next
  • Currently Being Moderated
    Dec 17, 2013 4:00 AM   in reply to jornbhor

    Hi there, I've the exact same problem since the update.

    It's set to 8,000 Khz and it can't be changed (at least it's not taken into account) :-/

    Sad... Hope they will fix it really soon...

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 17, 2013 4:05 AM   in reply to jornbhor

    Same thing happened here. Since this morning. One of our three computers has this problem... The other two seen fine, with the same update,

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 17, 2013 4:08 AM   in reply to snjezhi

    Actually i found a temporary fix, when you change to the resolution you want, it works, even if it's not set in the dropdown menu.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 17, 2013 4:17 AM   in reply to southarena

    That seems to work. Even though it looks like it keeps on skipping back to 8000. When I rendered something after putting it on 48000, it worked fine. Weird. Hope they get it fixed soon. Tanks for the tip!

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 17, 2013 8:42 AM   in reply to jornbhor

    What are your system specs? This would be helpful to others incase this will be an issue to them as well.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 17, 2013 4:35 PM   in reply to TDRonline

    This is a bug in After Effects CC (12.2). My apologies for this. We've already identified the problem code and our developer knows how to fix it.

     

    You can avoid the bug by double-checking the audio sample rate value, and changing it if necessary, as your last action before you click OK in the Output Module Settings dialog.

     

    The bug is that the audio sample rate value is being changed when it should not be when you do one of the following:

    1. Open the Output Module Settings dialog
    2. Change the Format in the Output Module Settings
    3. Open and OK the Format Settings dialog

     

    When this happens, the audio sample rate is changed to the lowest value acceptable for the format and the codec you have selected. For example, with QuickTime the lowest value is 8kHz, and for MXF OP1a the only acceptable value is 48kHz.

     

    Here's the important part: when you OK the Output Module Settings dialog, as normal it will save and use the current value (ie., whatever you set it to) for the audio sample rate. This bug is only a user interface problem that causes the audio sample rate control to be reset when the actions listed above happen.

     

    That means that as long as you keep an eye on the audio sample rate setting and change it as your last action before OK'ing the Output Module Settings dialog, you'll get the result you want. You can verify what setting will be used by twirling open the Output Module settings summary in the Render Queue panel.

     

    You can also define an Output Module template (Edit > Templates) with the settings you want to use, and the audio sample rate will be applied as expected when you use this template. However, be aware that this bug will also occur when you open the Output Module Settings dialog to create the Output Module template, so make sure that you double-check the audio sample rate before OK'ing the dialog for the template.

     

    (Under the hood, what is happening is the 3 actions above occur cause the Output Module dialog to initialize all of its parameter controls. Normally during this initialization the values for all of these parameters are set to their stored values. The bug is that the audio sample rate parameter is failing to initialize, so the value resets to index zero, the lowest acceptable value for the given format. The bug is due to some re-wiring we did in this dialog.)

     

    Again, apologies that this bug exists. The fix will be in our next release, though I don't have a schedule to give you on that at this moment. Until then please use the workaround of double-checking the audio sample rate value before OK'ing, or to create and apply Output Module templates

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 17, 2013 4:22 PM   in reply to Tim Kurkoski

    I lost my job because of this bug

     

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 17, 2013 4:39 PM   in reply to iDJIGIT

    Do you not use AME to encode instead of AE itself? I've never used AE to finish up, just AME.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 20, 2013 7:33 PM   in reply to Tim Kurkoski

    We've already identified the problem code and our developer knows how to fix it.

    The fix will be in our next release, though I don't have a schedule to give you on that at this moment.

     

    You know the problem and how to fix it. Release it now. Dont make us wait for your schedule, we have our own. By the time most of us remember that there is a problem and workaround, it will be once the render is complete. And that will be too late for some.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 3, 2014 8:32 AM   in reply to Tim Kurkoski

    Any update? Any date of when it will be release?

     

    Thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 3, 2014 11:36 AM   in reply to blobinabottle

    No release date to share for the fix right now. We are evaluating options for this and other bug fixes. We'll share more information after we have a plan in place.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 3, 2014 12:28 PM   in reply to Tim Kurkoski

    Hurry up please, this is continously biting me in the ***. I would use AME, but it crashes on open.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 7, 2014 2:29 PM   in reply to Tim Kurkoski

    This really has to be fixed now, with an emergency update release not on some update calendar in the future, I'm (and a lot of others) losing many precious hours in production because of this bug. I keep rendering, and it ends up at a horrible sound quality, only to have to go back in an re-render it yet again...and again.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 7, 2014 4:39 PM   in reply to StratoArt

    We're working on it.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 12, 2014 11:27 AM   in reply to jornbhor

    I've been doing render like crazy for the last 3 weeks and no problem... This afternon, after 4 or 5 render, the bug appeared!!! Why? Nothing as changed except updating InDesign CC, which should not influence After Effect... Please a release like tomorrow!!!

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 12, 2014 11:50 AM   in reply to frank_omni

    Our current target is to release a bug-fix update by the end of January, if all goes well. This update will include more than just this single fix.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 12, 2014 1:21 PM   in reply to frank_omni

    frank_omni wrote:

     

    I've been doing render like crazy for the last 3 weeks and no problem... This afternon, after 4 or 5 render, the bug appeared!!! Why?

    This bug only appears when you open the Output Module Settings dialog. If you have been using Output Module templates and not opening the settings to change them, you would not encounter this bug.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 14, 2014 10:07 AM   in reply to Todd_Kopriva

    This kind of stuff needs to be fixed RIGHT AWAY.  We should NOT have to wait for some other updates to fix something that is part of a cruicial feature of the interface.

    It is unnecceptable that this is still an issue a month since discovery!

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 14, 2014 10:14 AM   in reply to KGBMike

    Even if we were to just do an update with a single fix, it would take time. We need to test the fix, make sure that it doesn't break something else, test the patch mechanism, etc.

     

    We are releasing this update as quickly as is feasible without rushing and then introducing the risk of breaking something else.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 23, 2014 1:01 PM   in reply to Todd_Kopriva

    Another issue and a work around. If you are going from After Effects.... to Premiere... then to Pro-Tools, You have to make sure it is set to 48k (48k is the only one i needed), and you have to render each composition separately using the fix above.

     

    It sucks... and it takes way more time then just rendering everything at once, but hey, it works.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2014 9:23 AM   in reply to KGBMike

    This is horrendous Adobe!  AE used to be the most stable app until you switched over to CC on subscription base.  Now I have lost all confience and trust in you.  I have been using AE since version 3.1 withj no complaints until CC came.  Things are supposted to get better, not worse.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2014 9:34 AM   in reply to Todd_Kopriva

    Todd,

     

    I know these things take time.  I know of your dedication as I remember you helping people out since the mograph.net days.

    All of the things you mention for the process of a patch are valid and should not be skipped.

     

    Where I'm coming from is that, for a patch that addresses something that effects A LARGE PORTION of renders that your customers are outputing from After Effects, this is taking too long.  Adobe, the company, needs to put forth the necessary resources to fix this in less than a months time and/or have the organization in such a way, that a fix to something like this does not have to wait to be bundled in other patches.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2014 9:33 AM   in reply to MavisMedia

    It used to take us much longer to get a fix out... many months in some cases. In this case, the fix will be coming out in the month after the bug was found.

     

    So, why does this diminish your confidence in us? We have made mistakes in the past, too.

     

    We are sorry for this mistake, and we are working to fix it. I just don't understand why you think that this is somehow worse than the past.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2014 10:52 AM   in reply to Todd_Kopriva

    I agree with Todd on this one - fixes and updates are coming out at a much faster rate now. Also especially since the subscription model, they seem to be focusing on workflow improvements more and less on flashy and nearly pointless new features.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 31, 2014 4:40 PM   in reply to Szalam

    FYI: We found a problem with the bug-fix update, so we needed to build a new patch and redo some testing. We're still working on this and hope to have a bug-fix update out within a week or two.

     

    Here's a post about some known issues and their workarounds:

    http://adobe.ly/Lyq9D8

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 5, 2014 8:10 AM   in reply to Todd_Kopriva

    When is this going to be fixed?

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 5, 2014 8:34 AM   in reply to David Blast

    See the last sentence of my first paragraph in the previous message.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 5, 2014 2:33 PM   in reply to Todd_Kopriva

    To have to export to another program (or sorry, they're now called 'apps') such as Media Encoder, just to output a file, which is something After Effects does by itself anyway, is a waste of time.  I'm currently outputting around 60 clips for use on a stadium screen and I had set up an output module with the correct render & audio settings etc.

     

    After outputting 15 files, I thought I should just check them and I'm glad I did as the audio was output at 8.000Khz, even though I set up 44.100 in the output module.  Take a look in the output module to check and it's set at 8.000.

     

    I've now gone through your workaround and have updated the output module and double checked it, so I'm now ok to proceed.  I just wonder how many people have been affected by this, working for clients, wasting time and maybe even being made to look stupid because of it.  Many people here are freelancers and rely on their reputation for doing good work to get the next job.  This is something that could jeopardize that for those people.

     

    The first post here is 17th December, you said "the fix will be coming out in the month after the bug was found."  It's now 5th February. That's now only a week off 2 months from the first post, where you responded with "We've already identified the problem code and our developer knows how to fix it."  So it appears you already knew the problem existed before 17th December.  Come on guys, get your finger out.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 6, 2014 1:53 PM   in reply to Todd_Kopriva

    Todd,

     

    LeeHarper is a much more elegant writer than I am, but I think our point may be one and the same.

     

    I am a business owner. Time is money to me. Your amateur bug (which wasn't even there before!) is costing me money. Just like your amateur handling of our credit card credentials also cost me money. I am quite baffled that you have the audacity to be so rude seeing as your company was recently involved in such a scandal.

     

    I really hope you're a student help, in which case I'd argue that you should find another job. Alternatively you're some aspergian programmer, in which case I'd suggest that you'd leave the social media stuff to someone who understands the social aspect better than you do. If you used to be in charge of internet security for Adobe please don't do anything on the Internet ever again.

     

    Not that I in any way owe this to you, Todd, but notice how a lazy response on your part escalated matters. Social media 1o1.

     

    Question remains: WHEN is this bug fixed?

     

    Thanks.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 6, 2014 2:09 PM   in reply to David Blast

    David,

    I know attitude is hard to convey in a text-based medium, but I haven't even seen Todd being rude in general. He's one of the most patient people I've encountered. The fact that he volunteers his spare time in these user-to-user forums in order to help speaks a lot about his character.

     

    In this specific instance, I don't see him being rude either. He said quite clearly that they had a fix, but in testing they found that their update broke some other things so, instead of pushing it out with issues (like what happened with drag-and-drop importing in the 12.2.0 update), they've decided to make a less flawed update available and he gave us a timeline of one to two weeks.

    Less than a week later, he got asked when it was coming out, so he pointed the poster to the information.

    It didn't seem rude to me. I've seen lots of people posting in forums without reading what's come before, so pointing to a post that had the information that was being sought (as well as further info in case the poster was interested) seems like the appropriate thing to do.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 6, 2014 2:24 PM   in reply to Szalam

    Szalam,

     

    Well, isn't that the kind of reply to make me feel shameful of my rude musings.

     

    I'm not a forumnite, and I don't know the lingo. I'm just this guy working for a living, you know?

     

    If it is true, like you said, that Todd volunteers spare time to answer us, then I sincerely apologize to Todd. Honest.

     

    Todd, dude, it's the bug, it's Adobe the last couple of month, it's not you personally. It was never you personally to begin with. Apologies.

     

    Sorry if I've mistepped boundaries here, but again, I think LeeHarper had a fair point, no?

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 6, 2014 2:37 PM   in reply to David Blast

    I'm not going to get back into the bug issue as I've already said my point above.  What I think is a pain in the arm is that we have to find these bugs ourselves, through being bitten by them, then doing a web search or a search through these forums to find out the issue.

     

    If I'd already known the bug existed and there was a workaround already worked out, it would've been useful to have that information before I'd found it the hard way.  I'm not on this forum much and I don't regularly get on the Adobe site, much less often do a search for "bug of the day".  Is there some way users could be informed of a known bug when it's discovered?  Kinda like a press release but sent to people who are using the affected software?

     

    Surely this information could be fed to the Creative Cloud app?  So it pops up with a message one morning, a little like a news feed?  Or even just an email with the information would be useful.  A quick read and we wouldn't all be moaning that we've wasted working time and we're all individually digging these bugs out.  It would maybe even show Adobe as being proactive and supportive?

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 6, 2014 2:47 PM   in reply to LeeHarper70

    Is there some way users could be informed of a known bug when it's discovered?  Kinda like a press release but sent to people who are using the affected software?

     

    Surely this information could be fed to the Creative Cloud app?  So it pops up with a message one morning, a little like a news feed?  Or even just an email with the information would be useful.  A quick read and we wouldn't all be moaning that we've wasted working time and we're all individually digging these bugs out.  It would maybe even show Adobe as being proactive and supportive?

     

    Here's a list of known issues and workarounds on the After Effects team blog, which you can subscribe to:

    http://blogs.adobe.com/aftereffects/2014/01/known-issues-workarounds-a fter-effects-cc-12-2.html

     

    You can subscribe to the team blog for announcements like that.

     

    Also, we tend to broadcast the sorts of issues over various channels like Twitter and Facebook:

    https://blogs.adobe.com/aftereffects/2010/02/after-effects-team-on-twi tter.html

     

    I typically also broadcast such issues on various forums, including this one, Creative COW, Reddit...

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 6, 2014 2:59 PM   in reply to Todd_Kopriva

    Hi Todd

     

    Thanks, I didn't realise you can subscribe to that blog, so I just have done...  well, I tried to but when I click the Susbcribe / Email link (top right of page) it opens the same page back up and it's titled "Page not found".  I've tried that with being signed in and out and it does the same thing each time...  another bug!  Sorry!

     

    I'm not on Twitter and I don't tend to subscribe to industry pages on Facebook, I'll take a look at it though.

     

    As I said earlier, I'm not on forums very often, including this one, so I won't spot your broadcasts on Creative Cow & Reddit etc.

     

    I'll try the blog subscribe again maybe when it's fixed.  When will that be !? 

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 6, 2014 3:07 PM   in reply to LeeHarper70

    The typical way to subscribe to a blog is to use an RSS reader. You can paste the URL for the blog into any RSS reader.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 7, 2014 6:44 AM   in reply to Todd_Kopriva

    David, I'm sorry if I sounded like I was being harsh to you. I certainly understand your frustration. This is a really annoying bug and it's something that really seems like it should have been caught in testing before the last patch was released. It's just that Todd works so hard to keep the community notified about things and to help - even when situations are beyond his control. He posts here, on other forums (Creative COW, VCP, etc.), and the After Effects subreddit (that I moderate) and he goes above and beyond in helping user issues get resolved. I just wanted to make sure that you (and others reading the forums) understood how much he has been working to help us.

     

    Lee, I love your idea for a notification in the CC app. I would like to encourage you, however, to take part in some AE communities online. Talking with other AE users can really give you some creative and productive new ideas. I've learned workflow shortcuts I never would have dreamed of just by reading discussions in places like the the AE community on reddit. It's just a bonus that you're also informed of bugs and workarounds.

     

    Todd, is there a way for known bugs like this that are pretty wide-reaching to be announced in the CC app? If not, I think it would be a huge help. You've done a really good job with posting on various forums and the reddit community (nearly 5,000 subscribers! WOO!), but having the CC app push out a notification would be another great venue to get the word out. This audio issue, the Illustrator XMP data crash, and similar things like that really need to be announced to the user base as widely as possible and, since you've got the whole cloud thing going on, a bit of a notification in there would be a great feature addition. Sometime down the road, you could even have such notifications tailored to the operating system of the user, but a system-wide blast in the meantime would certainly be better than the forums posts alone. Thanks again for all the work you do. And thank the team for catching the bug in the update you guys were about to push out. We look forward to the less-buggy update next week.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 7, 2014 9:41 AM   in reply to Szalam

    I've already forwarded the suggestion to the folks in charge of the Creative Cloud desktop application.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 8, 2014 1:51 PM   in reply to Todd_Kopriva

    Thanks Szalam, I agree about taking part in communities online.  I'm already a Creative Cow member and I will take a look at the Reddit AE community too.  I don't always have lots of time to do this, I'm also a 3D animator so I have to share my forum/online time on 3DS Max related sites too.  It's great to learn from others and to help others too, so I'll try to do that more.

     

    Todd, that's great that you've passed the suggestion onto the CC desktop app people, I hope it's a useful suggestion.

     

    ... and I look forward to the AE update.

     
    |
    Mark as:
1 2 Previous Next

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points