Skip to main content
talented_member1587
talented_member1587
Known Participant
January 12, 2022
Question

PR 2022 Audio Crackle on Timeline Playback - yet again!

  • January 12, 2022
  • 2 replies
  • 815 views

It seems these days when you resolve a tech issue and can get to back work, just wait, because Adobe will push that problem back onto your lap again sooner than you had hoped. Today the audio crackle on the timeline is back AND making its way into the exports as well. And it's not something on the original sound file - it's a playback/export issue.

 

Specs:

Macbook M1Pro Chip (New as of 12/2021)

16GB RAM

1TB SSD (internal)

2TB SSD (external for media)

 

I'm unclear about the issue of mixed media when it comes to sound. I work with mixed media and so some audio is 44100 and other is 48000. Adobe Sr. Tech help had me set my sequence settings to 48000 to resolve this issue back in December. My Zoom H6 and GoPro are recording at 48000, whereas the iPhone is at 44100, as are the stock audio/music clips I get from Envato; so maybe that mismatch is the issue? My current edit has more 44100 (with some 48000 mixed in). And the audio crackle is really bad on playback and in the export.

 

My questions:

1) Is the 44100/48000 even the potential culprit of this issue, or is it like the Rec.709 color space issue and now my sound also needs an "interpret" of some kind? Yes, I'm using mixed media with Variable Frame Rate. I can't help it - it's what comes to me from iPhones and GoPros. Is this just another battle wound in the war of Adobe vs the mixed media content creators?

2) I took someone's advice and cleared my cache and restarted, and that seemed to solve the worst of it. But the crackle is still coming in at random places. If I export out to Audition to do my mix, will Audition resolve the mismatched settings?

3) is there something I'm not thinking of that could be causing this very random crackle and pop on the timeline with my audio?

 

I'm spending more time on here looking for tech solutions to problems that didn't exist before the 2022 updates than I actually spend on the creative part of my edits. Adobe software now feels like a never ending labor camp, instead of a tool that lets the creator soar high and wide with their projects. And we pay for the privilege of being in this prison. And Adobe is probably very contented knowing that users like myself have so many YEARS invested in learning and perfecting their Adobe workflows that the daunting idea of jumping ship and moving over to another editing solution is keeping our money pouring in each and every month. Lordy!

This topic has been closed for replies.

2 replies

R Neil Haugen
R Neil Haugen
Legend
January 12, 2022

I've seen several users have troubles with mixed 44.1 and 48k media. Some of the Audition ACPs suggest using MediaEncoder to t-code the 44.1 audio to 48k as a general first attempt to fix that problem. And I've seen users that simply exported the audio out of Me as a wav file, and replaced original audio with that, and fixed their issues.

 

Might or might not work, but worth a quick test run at least.

 

Neil

Everyone's mileage always varies ...
chrisw44157881
chrisw44157881
Inspiring
January 13, 2022

Neil, thx. I forgot I did not explicitly mention .wav as PCM audio is usually standard in Prores, but yes, that is a good thing to transcode to as well. both video and audio. non-vfr and non-audio compressed should fix the problem.

    talented_member1587
    talented_member1587Author
    Known Participant
    January 13, 2022

    This may be a broader question than this one subject of crackling audio - but iPhones (and I assume GoPro's as well?) do have an option for creating video files that are "compatible" (vs. "efficient") that, on the iPhone at least, come with a slew of pseudo-warnings about what will be lost by choosing a "compatible" format.

     

    As I see it, the obvious "loss" is smaller file sizes. And while I'm not sure if a day of shooting is going to overload my maxxed out iPhone 12 storage or not, I tend to export what I shoot daily anyway to dropbox (where I have unlimited storage). And if that would save me this nightmare of incompatible video files, then perhaps that's worth considering?

     

    But we also tend to shoot at 24 fps, and it seems that "compatible" mode on iPhone forces a 60 fps. That may not be the worst thing, as I do believe I can still edit 60 fps along with 24 and 29 fps files that I get from Envato stock and from other creators who contribute to our projects, and export that "mixed" media used together in one sequence? So I'm curious what other "down sides" I may be looking at by stepping away from "efficient" and going to "compatible" with iPhones and GoPros. I think I'll ask that question in it's own thread as well. So feel free to pop over to that thread to answer (or copy and paste). Apologies to Forum managers if I'm breaking a rule of doubling up - but I think this issue is worth seeing by a wider audience than the ones looking at this particular thread.

    chrisw44157881
    chrisw44157881
    Inspiring
    January 12, 2022

    you probably know what I'm going to say, but you might as well try it to see. encode your variable video with free shutter encoder into another non-vfr format( it even has prores now!) and see. you can also make a separate test with transcoded 44.1 and 48khz audio. perhaps the sampling interface library has some bugs as well.

    talented_member1587
    talented_member1587Author
    Known Participant
    January 12, 2022

    actually I didn't know you were going to say that and I'm happy to try anything!! I have plenty of time it seems since Adobe Sr. Sr. Tier 2 tech now has to get back to me after 2 hours in a video session with supposed "sr" tech trying to see why all the exports of my project look like garbage. They seriously have no clue what's going on with this program. I've never seen such a hunt and peck session like that in my life. I should have filmed it. They literally clicked everything and exported a couple dozen duds... it's almost getting funny - except it's not. But all joking aside, in case it isn't reading in this response, I really DO appreciate your suggestion and will try that in the time I'm waiting for this supposed sr. sr. sr. tier 2 to call me. Would be nice to have SOME solution to all of this...

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices