Premiere speeds up the audio playback in videos itself!

Since the latest update the entire playback is speed up across all my premiere pro projects. I can’t find the fix either. What people describe below is a lot of tech info that doesn’t address the problem at all. It would be great if adobe can fix this.

This sounds like a media interpretation or audio-conforming issue rather than the project frame rate itself. Since some clips from the same interview are normal and others play at roughly 2× speed, I would first check whether the affected files have different audio sample rates, variable frame rate metadata, or were encoded differently.

Try importing one affected clip into a new project and check its clip properties and audio sample rate. Also try interpreting the footage with the correct frame rate and, if possible, transcode one problematic file to a constant-frame-rate format before importing it again.

If the problem remains, clearing Premiere's media cache and testing the same file in a new project can help determine whether it's a cache issue or something specific to the source file. If you can provide the affected file's codec, frame rate, audio sample rate, and MediaInfo details, it should be easier to identify the exact cause.

Reading thought this tread, my guess would be that the metadata of the file is being interpreted incorrectly.  
You are using the Black Magic camera app on a mobile phone?  If you can provide an example file that shows the issue here that would speed up a potential fix immensly.
My guess, and this is just a guess, is that the camera app is setting the metadata of the file to a set sample rate.  For instance 48k, and that is written to the metadata of the file.  
But, the hardware is sampling at a much lower sample rate, like 16k.  So only half of the audio data is being sampled.
Premiere can only rely on the file metadata for playback, so Premiere thinks the file is set to 48k, and tries to playback at 48k, but the audio data was actually sampled at 16k.  So it will sound really off.
These numbers are only used here as examples and guesses.  This is why it is necessary to get a sample file that shows the issue from you.

How could this happen?  It could be something as simple as connecting a recording device, like an external blue tooth headphones with a microphone that changes the device sample rate to 16k, but the software still thinks it at 48k and writes the metadata at 48k.  Or a wireless lav mic. 

Again, just guesses as there is very little info from the original post to go on.

Upload a faulty clip to test.

I have a feeling you do not understand the concept of variable framerate: its not the framerate itself you set in the app but its the framerate mode set by the phone.

The reason PeruBob asked for MediaInfo data on the file is to see if it is VFR or CFR … variable framerate or constant framerate. That is a huge difference. There’s another possibility I’ll add below.

VFR, recorded by some drones, most screen capture apps, and most phones, auto-changes the actual number of frames recorded per second by how much motion it ‘sees’ in the image. So your 25fps shot may actually vary from say 21.2 to 26.3 fps within the clip. That’s hard for most NLEs to handle, as they all prefer CFR as from serious cine cameras.

So with VFR, sometimes you get odd playback of the audio. That’s one possibility.

The other, as someone who uses a couple BlackMagic cine cameras, is what the camera was set to for high-speed capture … on my rigs, I can tap one button and get between 50% to 150% faster video recording, but the audio stays the same. So there’s half again to nearly three times the video frames recorded compared to ‘normal’ speed recording.

It’s pretty slo-mo to watch, but the audio is still only ‘normal’ speed. So if I’ve got it set to 2x … double speed slo-mo … the audio will last only half the length of the video clip. If I then select the video and do a speed change, I can get that to match correctly at ‘normal’ viewing speed.

So this might be where the issue comes from also. We need the data from the file header to know.

Please use the free MediaInfo and post a screenshot of the properties of one of the problem media in tree view.
https://mediaarea.net/en/MediaInfo

Try Preferences > Audio Hardware and set Input to None.

If that doesn’t work, try updating or rolling back your graphics driver directly from the video card manufacturer’s site. If NVIDIA, do a clean installation of the latest Studio Driver (NOT the Game Driver).