TOPIC:

I am getting noise crackling all around the video at random points, even though I've heard some people get this only at cut points (but no, I am getting them all over)

- this issue persists throughout edit and on the export file.



Has anyone faced it and found a solution or did Final Cut Pro support crew already gave up on us?

I've found this to be an issue in 2012, as well, just from Google Searching.

This can sometimes be caused by an audio sample rate mismatch or a non-standard sample rate. What is the sample rate of the source audio and what is the sample rate of the project? You could try optimizing the footage to see if that cleans it up.

I really haven't experienced this before.

However - both project and video's audio recording are set to 48kHz

What's the fix? I still haven't found one :/

Can you post a sample clip?

It would also help to share some specs - which Mac, OS version, FCP version, audio interface/speaker setup...

Most audio issues I've come across were due to either sample rate mismatches (rare), poor quality source recording (not so rare), or over-processing.

here's the specs and issue happening recorded: vimeo.com/824261430?share=copy

please let me know if you knoww the solution

First things, QuickTime Player will drop frames or otherwise ignore certain issues with A-V files. Final Cut Pro, being an NLE, is more picky/demanding.

Your video in the inspector from QT Player says 29.99 fps. That is not 30 frames per second. If you recorded/created the problem file in OBS, or other tools, it is likely the file was made with a variable frame rate, or a non-standard frame rate. If you were to process the file with Compressor or some other tool and set the output to 30 fps exactly (with other appropriate settings, then those clicks/pops should go away. It's hard to say for sure without having access to a file to test.

Addendum: You could try optimizing the file in FCP to see if that fixes it. However, it will create a ProRes 422 file, which may be much larger than the source file. As stated above, you could try using a different tool to process the file and see if that helps.

DaveM wrote:

First things, QuickTime Player will drop frames or otherwise ignore certain issues with A-V files. Final Cut Pro, being an NLE, is more picky/demanding.

Your video in the inspector from QT Player says 29.99 fps. That is not 30 frames per second. If you recorded/created the problem file in OBS, or other tools, it is likely the file was made with a variable frame rate, or a non-standard frame rate. If you were to process the file with Compressor or some other tool and set the output to 30 fps exactly (with other appropriate settings, then those clicks/pops should go away. It's hard to say for sure without having access to a file to test.

Addendum: You could try optimizing the file in FCP to see if that fixes it. However, it will create a ProRes 422 file, which may be much larger than the source file. As stated above, you could try using a different tool to process the file and see if that helps.

- I see what you're trying to state. However - I've been using Filmic Pro before as well and always had it set at 30 FPS.

If I check any of the files and list out the video specs - every single one states 29.99 FPS and had no problems, whatsoever

I as well tried recording with the Huawei's native camera app, set at 30 FPS - it gives me calling of 30.15 or 30.16 FPS

Unsure why it's not strict number, as I'm quite new to videography thing, but I've never run into this issue before until last two months and I've been editing now for a almost a year inside a Final Cut Pro.

Many applications that record audio and video, as well as some cameras, create files with a variable frame rate that averages to what your chosen frame rate setting is. So, the resulting files may have a displayed frame rate that is slightly higher or lower than the expected value (as you mentioned).

Player applications and other consumer-level tools may not have a problem playing back these files. However, for a "editing" tool like FCP it will be hit and miss whether these types of files work well, or not (as in your case).

If you could post a sample file with the issue to Dropbox or a file transfer service, we could try to look at the file. You might try recording another file to see if the issue was just with the one file.

Again, if you transcode the source file using Compressor to ProRes it should fix the issue. The free Shutter Encoder app, though less user-friendly, may work, too (along with others).

Addendum: Professional video standards don't specify the use of variable frame rates. Professonal-level gear doesn't record with variable frame rates. Ufortunately, mobile phones, and many webcam or streaming applications that can record may do so using variable frame rates (it's far cheaper than requiring the strict conditions needed for professional-level quality).

DaveM wrote:

Many applications that record audio and video, as well as some cameras, create files with a variable frame rate that averages to what your chosen frame rate setting is. So, the resulting files may have a displayed frame rate that is slightly higher or lower than the expected value (as you mentioned).

Player applications and other consumer-level tools may not have a problem playing back these files. However, for a "editing" tool like FCP it will be hit and miss whether these types of files work well, or not (as in your case).

If you could post a sample file with the issue to Dropbox or a file transfer service, we could try to look at the file. You might try recording another file to see if the issue was just with the one file.

Again, if you transcode the source file using Compressor to ProRes it should fix the issue. The free Shutter Encoder app, though less user-friendly, may work, too (along with others).

Addendum: Professional video standards don't specify the use of variable frame rates. Professonal-level gear doesn't record with variable frame rates. Ufortunately, mobile phones, and many webcam or streaming applications that can record may do so using variable frame rates (it's far cheaper than requiring the strict conditions needed for professional-level quality).

- Thank you for taking your time, Dave! I really appreciate you sharing the years behind your knowledge!

I am just really confused as of it used to work before, even though the previous files as well had the same settings. However - now it doesn't work.

That's what really makes me think about what could go wrong.

Here are just 3 of the examples I've uploaded that have been seen causing this issue (even though there's more of files):

www.dropbox.com/scl/fo/oalntfhwn7phf4qjs...bqg6yiqhj0awfwzn819y

This is what I see in Invisor



The frame rates are all over the place, which can cause this problem. Can't tell you why other material wasn't showing this problem. Unfortunately iPhones and I guess the Android camera are all shooting variable frame rates, which is a major pain. On earlier cameras the media had to be optimized in FCP to avoid video tearing.

Tom, thanks for posting the screenshot. I opened all three files in Invisor, as well, and can hear the noise when all three files are played back in FCP. I don't hear the noise in the Finder or QT Player. So, that confirms what the OP experienced.

I brought all three files into FCP, then "optimized" them to ProRes 422. The noise was reduced a bit but not completely.

I was a bit surprised. I then took "problematic.mov" and transcoded it to ProRes 422 and Apple Devices 4K (HEVC 10-bit) using Compressor presets (no settings changes made). Both of these files played back without any noise that I could hear after importing them into FCP.

So, it seems that FCP is a bit less robust, somehow, when transcoding these files.

Oh, and to be clear, I only played back the files in the Browser.

zhincic , when you are going to make videos, you might want to prepare your smartphone prior to starting record. It might be helpful to reboot/restart your phone and then turn off other apps besides the one you're using to record. It may be that other apps, especially those that access the Internet, are using resources on the phone that might cause the frame rate to jump around more than it would with nothing else running.

I'd suggest possibly turning off auto-updates for apps because changes to apps could affect recordings (and if an app was updated between recording sessions where some files previously were fine but later ones weren't, the update may have created the issue).

And, you might check into the app you're using to record and make sure you are using the same settings each time, and that those settings are optimal. On an older phone, there may be "high quality" settings that stress the phone's resources too much.

Just some things to consider...

I just ran a test where I used Shutter Encoder 17.1 to transcode "first.mp4" to ProRes 422 and H.265 (using the unaltered settings).

The ProRes 422 output played back fine in FCP, but the H.265 file did not. In addition, the files created by Shutter Encoder were significantly larger than those created by Compressor. Go figure...

---

And, finally, I imported the files "problematic.mov" and "first.mp4" into DaVinci Resolve Studio 18.4.1, making no changes to the default settings.

Both files played back just fine in the source Viewer (i.e., not having been edited into a timeline). I have no idea if, or what, Resolve does under the hood different from FCP, or if it is just more forgiving with these kinds of files...

DaveM wrote:

I just ran a test where I used Shutter Encoder 17.1 to transcode "first.mp4" to ProRes 422 and H.265 (using the unaltered settings).

The ProRes 422 output played back fine in FCP, but the H.265 file did not. In addition, the files created by Shutter Encoder were significantly larger than those created by Compressor. Go figure...

---

And, finally, I imported the files "problematic.mov" and "first.mp4" into DaVinci Resolve Studio 18.4.1, making no changes to the default settings.

Both files played back just fine in the source Viewer (i.e., not having been edited into a timeline). I have no idea if, or what, Resolve does under the hood different from FCP, or if it is just more forgiving with these kinds of files...

I must say you are the kindest person to help with such info and testing.

I didn't even know variable frame-rate is a thing on phone, before your mentioning.

--

I have however disabled auto-updates and almost all of the phone notifications way before, but that doesn't seem to be a solution as all of the footage you tested was recorded with them turned off.

--

Guess I know what's causing the problems now, but think I'm gonna be switching to DaVinci as it seems to be having updates more often, as well + it doesn't take my time to jump from software to software to solve some of those technical things (even though that DaVinci is much more of technical software)

I hoped I helped, at least a bit...

I had been focusing on using the video clips in FCP or DaVinci Resolve and not testing anything to do with the source, the smartphone.

I have an older iPhone and the built-in camera app, as well as Filmic Pro (actually now Film Legacy, since they went to a subscription model, which is BS). Both of these apps seem to record with a variable frame rate (in my brief testing. I have a MOVI iPhone "gymbal" and its app also records variable frame rate files. I couldn't see any setting in these apps for a strict/constant frame rate.

The only app I have that does create constant frame rate video files is the Moment/Pro Camera by Moment app. It's actually quite a nice app (so long Filmic Pro).

Unfortunately, Pro Camera by Moment only has an iOS version (no Android). If I need to record video with an iPhone, this would be what I'd now use to record video (most likely).

So, using the Moment app if you're able, should help avoid the issue you've been experiencing.

I'd say that it's worth trying to stay with FCP, as it's much more enjoyable and fluid to use for actual timeline editing than any other NLE. You're right in saying that Resolve is quite complex. Lots of "dials and switches", with which you can easily/accidentally make mistakes. Resolve is very nice for doing color work and now even audio.

Addendum:
You might want to be careful when recording if you use the built-in microphone on your smartphone to not record audio that's too loud. Even, a cheaper wired microphone might work better. Keeping your voice level as constant as possible might also help with the automated audio level controls that are part of many apps.

Also, for recording a talking head (like in your sample clips), there is no real need to record 4K/UHD sized video. HD should be just fine and less taxing on the phone.


Cheers.

I may have been a bit unkind towards Filmic Pro (and other apps) for not recording with a constant frame rate.

I did a bunch of tests, using different frame sizes and frame rate settings, with the built-in Camera app, Filmic Pro, Moment, and MOVI.

I imported all of the clips into FCP and didn't have any issues with any of the files. My files used both AAC and PCM audio, 44.1 and 48 kHz sampling rate, different recording quality (bit rates), and HD and UHD/4K frame sizes.

Since you mentioned that other files seemed to work (if I recall correctly), I am left wondering if some setting in the app(s) you used had been changed. I'd suggest you review your phone settings and app settings for the microphone used (if more than one option), as well as auto gain control. My recordings were set to use auto gain control.

Since your sample files seemed to have pretty loud audio levels, I wonder if the levels were too loud at certains spots and the "limiter" in the app may have resulted in the clicks/pops in the recordings. Having the "auto gain" function turned off could make this more likely. Usually, when recording audio you don't want levels to go above -12 dB max, and often people record so that the average is around -20 dB, or thereabouts. Proper microphone placement can help with keeping ambient noises as low as possible.

So, it seems I was somewhat wrong about the variable frame rate aspect of the issue, since I couldn't replicate things in my test recordings (most of which used variable frame rate settings). I apologize for going a bit astray focusing on the files once transferred to the computer, instead of considering the actual recording part of the process.

Hello there
I've an issue similar and I'm fearing horribly worse, every clip and every project in my library for the new film I'm working on has sound issues all of a sudden. It's the same MO for all. I start the clip and the sound just intermittently cuts out sporadically at first as if a limiter has been hit repeatedly then faster and followed by a horrible scrunchy grinding noise and the whole video slows down to a crawl and then stops if I haven't stopped first. I've checked my levels and they are well below ANY over limit thresholds, this is happening to footage which has been playing fine for nearly a year. Any ideas at all anyone ? oh and a weird last thing , sometimes when I try and stop the calamity , the spacebar has no effect and I'm left with a "Runaway train" scenario which if anything at least keeps me on the edge of my seat . EEE fun and games here ! Help x

Ian, you might want to create a new topic and re-post there. It seems your issue is different...

To start with, try deleting your FCP preferences, and reboot your Mac in Safe Mode, log in, and restart again normally:

How to Boot a Mac in Safe Mode

This may help purge various temporary/cache files, and do some system maintenance. You might also try deleting any render files and other generated media in FCP (select the Library icon in the FCP sidebar, then choose File -> Delete Generated Library Files). You might also turn off background rendering if that is on (in FCP preferences).

zhincic wrote:

...Guess I know what's causing the problems now, but think I'm gonna be switching to DaVinci as it seems to be having updates more often, as well + it doesn't take my time to jump from software to software to solve some of those technical things (even though that DaVinci is much more of technical software)

Your reported case is a valid issue to examine. I tested it on Resolve Studio 18.1.4, Premiere Pro 23.3.0, FCP 10.6.5, iMovie 10.3.5 and iZotope RX10 Advanced 10.4.0.1926 on Ventura 13.3.1(a) on an M1 Ultra Mac Studio. The only one that showed the audio noise problem was problem was FCP.

However if you think Resolve will somehow solve all problems, you are mistaken. It is a great NLE and I use it every day. The user manual is over 4,000 pages and it's very complex. Like all software, it has bugs and problems. Unlike FCP, data corruption problems are not unknown on Resolve. Below are statements from Resolve users I've seen reported in the official Blackmagic forums. I have personally experienced data corruption when using Resolve's media management feature, but I've never seen anything like that with FCP.

That said, Resolve's rate of progress on features and performance has been impressive the past few years.

---

forum.blackmagicdesign.com/viewtopic.php?f=21&t=137161

"I am used to work on both systems and I have no doubt that FCPX is much more stable. There are certain features on DaVinci that just don't work. That said, I'm using DaVinci right now even with this instabilities because it has by far better color tools, an Audio DAW included and BRAW Support, but FCPX is by far more stable and fast."

---

forum.blackmagicdesign.com/viewtopic.php?f=21&t=137984

"We are seeing an increased frequency in crashes and it appears to be linked to Collaboration but I cannot confirm this is 100% the cause. We use a combination of Mac and PC workstations running DR16.2.8 all on the same internal network. Our media and PostgreSQL database reside on an SNS EVO shared project/media storage server.When we switch off Collaboration, the crash frequency drops significantly (from 6 times per day to 1 every other day) but there are the occasional crashes which we have come to expect from DR."

---

https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=137773

"I'm sorry to be a party pooper here but I use both Avid and DVR heavily and DVR is by far more system intensive and demanding than Avid. If you find Avid unstable on your unsupported older Mac you will almost certainly run into problems on long form editing with DVR"

---

https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=138974

'I am getting corrupt files when I use Media Management to trim used media. The generated files have no content, they open showing "media offline".'

---

"Same for me, when I copy & trim media in media managment the result is broken, black video"

---

https://liftgammagain.com/forum/index.php?threads/davinci-resolve-17-1-1-media-managment.15767/

"Media management is still a bit of a mess - sometimes it works totally flawless, but most of the time I get an error along the way. Still not able to figure out why that is, or seeing a pattern - seems totally random."

---

https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=139317

"Even on the big Mac system we have (16 cores, 256GB of RAM, two 4TB SSDs, Radeon Pro Vega II Duo GPU, 16TB SSD source drive), we get some lag with complex timelines over an hour. I solve it by breaking the timelines in half at about 20-30 minutes. Episodic TV usually tops out at 45 minutes, and we can do that if it's not weighted down with a lot of NR and complex OFX plug-ins. If we do run into a lot of OFX, we just cache it and call it a day."

---

https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=139705

"I spend lots of money to finally be able to use Resolve as intended. But as it turns out the UI sync issues I've reported over the last 3 years are real bugs and are not fixed by throwing any amount of money at."

---