AUDIO PROBLEMS / Static Sounding Voice and Voiceovers

[Tanya26316392knej]

All of a sudden -- my voice on some of the clips and any voiceovers I do -- is very static sounding and distorted sounding. Everything always sounded great before. I record on my I Phone 7 but edit on my MacBook air. I record voiceovers directly into the mac with no external mic. I had the mac mic checked out today. It's fine. I've uninstalled and reinstalled RU -- the problem is still there. Help Please!

[robmdavis]

I'm having the same issue. I have tried editing the sound in Audition and other programs but even though it sounds fine in the other programs when I import it back to Premiere Rush it sounds like staticky chipmunks! How do I fix this?!!!!!

[Kevin-Monahan]

Hi there, @robmdavis,

I read that you are having problems with imported audio. What are your export settings in Audition? Are you exporting a .wav in 48 kHz? Let the community know. Sorry for the frustration.

Thanks,
Kevin

[robmdavis]

The Audition settings are unimportant. No matter what program I use to adjust the sound when it imports back into Rush it's like Robotic Chimpunks. It's obviously something with Rush. I wonder if anyone else is having this problem with the program?

[Kevin-Monahan]

I have not heard of anyone having this issue. Are you on the desktop version? If so, what are you system specs. Perhaps I can reproduce the issue to help the team out with filing a bug.

Thanks,
Kevin

[robmdavis]

I'm using an iMac M1 desktop. I have the latest version of Rush (2.8) installed. I'm about to test the file using my iPad's version of Rush to see if it's reproduced there. 

[robmdavis]

The file imports and works just fine in the iPad version of Rush. So, it's something about the desktop version.

[Jim30867115tmzu]

I, too, am now having this disturbing issue. I even used Adobe Rush earlier this morning with zero issues. Now, I end up  with a lot of static and/or the chipmunks whenever I import a video into Rush. I just uninstalled and reinstalled Rush, but it did not help at all. What a shame that such a great program has now turned sour.

[Jim30867115tmzu]

Oh . . . and I even tried importing a video that I worked on and completed yesterday. After I finished with it in Rush yesterday and finalized it, it was great. Yesterday, it imported into Rush with zero issues. When I just now imported it into a new blank Rush project, behold the chipmunks! So, I will have to use Corel Visual Studio to try and do my projects from now on. That is indeed a shame, because I (like all of you) pay a monthly fee for Adobe Cloud which includes Adobe Rush. Terrible but true!

[Jim30867115tmzu]

In an effort to try and help illuminate this problem (and not just cast stones, because I really do love the way Adobe Rush works when it works correctly), here is a bit more (helpful, I hope) info:

1) I saw that were six "optional" updates in "Windows Update" that all pertained to my "Realtek" sound card. So I installed them and then rebooted. No change in this bizarre Rush behavior.

2) Then I tried creating a new blank project in Rush, then imported one of their own available "music" soundtracks to Rush. When I then played it in Rush, the same "static" noise was overriding the sound. 

3) Lastly, I opened up Corel Visual Studio to work wtih my video file. It works perfectly after I imported my video; no sound distortion at all. 

The issue has GOT to be a Rush malfuction (in my admitteldy amateur opinion), based on the tiny things I did above.

So unfortunately, I'll be using the Corel program until and unless Rush can be fixed. 

Again, hope this info might be helpful. 

[robmdavis]

At least now it's plain I'm not imagining things. Adobe kept a work order open on my issue but kept asking me to jump through hoops (most of which I had tried on my own). I don't have time to give to a program that I use perhaps once a month or so to help them run down the issue. I can be more productive using other programs. I like the former ease of use of the program and hope they eventually find the issue and fix it, but they changed something in the latest update that created this problem.