Clicks and pop with muvo

hi all
i have a muvo tx 28mb
i have experienced playback issues . while listening to music i can hear click or pop randomly.
my firmware is .02.0
should update it or i can damage my player?
i am thinking change earphones bundled with muvo..could be a solution?
any suggest?
thanks in advance

Similar Messages

Clicks and popping with recording and USB interface-HELP!!!

I've submitted this twice, got some responses, but has twice been ignored into oblivion. I apologize for the reposts, but this is VERY IMPORTANT, and I've been struggling with this issue for MONTHS now dealing with countless hours of lost time trying to fix it to no avail.
I'll try to include as much detail as possible.
I use:
MacPro 2 x 2.66 Dual-Core Intel Xeon
3 GB memory
Logic Express 8.0.2
245.13 GB empty space on Hard Drive
THE PROBLEM:
When I record, I get computerized clips/pops
http://www.moogiex.com/clickpop.mp3
http://www.moogiex.com/morecackling.mp3
I record via a PreSonus Audiobox USB. This problem did NOT start when I got the AudioBox, but several months after.
When I simply monitor the sound going through the box, the sound is fine.It's something between the Box, and the computer output. My guess is some incompatibility with Logic Express or Core Audio and the AudioBox.
It is NOT the microphone or the cable (the pops occur with anything going in, 1/4", XLR, different inputs).
The clicks START with Logic Express. If there are any recording program open when Logic Express is open, and I record, I get the SAME pops.
It did this both under 10.5.6, 10.5.7, and now 10.5.8.
It is NOT clipping.
When I'm recording with LE:
—There's 1.27 GB of FREE Memory while I'm recording.
—Logic Express is only using 6.7% of CPU while recording (of only one of the four processors), and about 90-95% of CPU space is free on all four processors.
—This happens on ANY audio input, and it doesn't matter how many other tracks, how long it is. I just started a brand new file and it does it.
—This happens when I use ANY input into my computer, but is STARTED by LE.
Here are my Logic Preferences
Core Audio- ENABLED
System Memory Requirement 66.0 MB
Device: AudioBox USB
I/O Buffer Size: 1024
I/O Safety Buffer- UNchecked
Recording Delay: 0 samples
Universal Track Mode- CHECKED
24 Bit Recording- CHECKED
Software Monitoring- CHECKED
Independent Monitoring Level- Checked
Process Buffer Range: Large
ReWire Behavior: Live Mode (Higher CPU Load)
Maximum Scrub Speed: Normal
Scrub Response: Normal
There is *no* driver with PreSonus' AudioBox. It is simply "compatible." Here's what System Profiler says:
AudioBox USB (plugged into my Mac Pro's front bottom port):
Product ID: 0x0301
Vendor ID: 0x194f
Version: 1.08
Speed: Up to 12 Mb/sec
Manufacturer: PreSonus Audio
Location ID: 0x00200000
Current Available (mA): 500
Current Required (mA): 500
Here's what I've tried:
—Disabling CoreAudio, shutting LE 8 off, restarting LE 8, enabling CoreAudio again. This worked ONCE. It hasn't worked since.
—Disabling CoreAudio, shutting LE 8 off, SHUTTING DOWN, RESTARTING, opening LE 8, enabling CoreAudio again. This also worked ONCE. It hasn't worked since.
—"CPU Saving Mode"
—I/O Buffer to 256, 512, and 1024 (default) (IMPORTANT?—speed of popping actually INCREASES with larger buffer?)
—I/O Safety Buffer checked and unchecked
—Changing Recording Delay samples
—Pretty much fiddling with any of the controls
—Disabling Airport does nothing (was previously working fine with Airport running)
—Quit all applications, open up QuickTime (pro) or Audacity, and record something. It records perfectly. I go back to LE and the clicks and pops are gone, but only until I use anything with effects, then the clicks and pops return. This works SOMETIMES.
—Reset the preferences, and that has worked ONCE, and then the clicks and pops came back (albeit not as prominent, but they were still there).
—I trashed all files related to Logic and reinstalled. Worked ONCE.
—Restarting does help, but only temporarily, as soon as any pull is put on Logic, the problems return.
—Using a different USB port. I thought this was the solution because the problem shortly went away with regular use of Logic, but problem came back.
—Uninstalling Logic, Reinstalling Logic Express, same deal.
PLEASE, PLEASE, PLEASE HELP. I have a lot of money sunk into all this equipment that's practically useless with this recording issue.

Man, I feel for you on this.
I would love to see what your pops and clicks look like in your waveform. If you can take a snapshot of it and post the pic here that might help the diagnosis.
Your audio files certainly SOUNDS like you have a clocking problem. It really sounds like your CoreAudio driver/MacPro and your USB interface are not locked up in sync - as in: which is master and which is slave? I know some interfaces include a software control panel that allows you to set the status of the interface clock to slave to the computer or to be the master. It sounds like yours doesn't come with drivers but is there any control panel for this Presonus device?
Another place to check is in Applications>Utilities>Audio Midi Setup
On the left under "Properties for <your interface>" what does it say for the clock source?
Also in this panel, to the right it should have a button for "configure device". What happens when you click it? For example in my case it automatically launches my Apogee Duet Maestro control panel. In your case it might launch something similar, although I think you mention that you never installed anything, which I find strange to begin with - that this thing should just work out of the box with no driver at all.
I've struggle with w similar problem with my Apogee Duet, although nothing of this magnitude, maybe 4 or 5 clicks per 3 minutes of audio and these turn out to always be sample drops where 5-10 samples in a row are all the same in the waveform, as if my interface and computer stopped talking for a milli second. I did find that if my Apogee Duet was chosen as the default or system output in the Audio Midi Control Panel I mentioned above then the clicking was more frequent, as if choosing the audio interface for any system output caused a conflict with choosing it for Logic. I thought this was strange but you might want to investigate that further too.
At any rate, it does sound like a digital clock syncing issue to me by the sound of your audio. What effect does changing the sample rate of the recording have on the problem?
Let me know if any of this leads to anything.

Clicks and Pops with Apogee Ensemble/Duet since upgrade to OSX-ML

Problems with Clicks and Pops in Logic 9 (9.1.8 64 bit) since I upgraded to
Mountain-Lion (10.8.2) Does not really matter if I change the Buffer from 128
to 512! It is not very often but not acceptable. I made an additional
setup with external HD an installed SnowLeopard again. With this
OS-Version I can run without any problems with Buffer-Sices 128 or 64. Same
problem I had with my DUET as well. Would switch back to SL but some
of the programs I bought from Apple are not compatible with older OS
than Mountain-Lion. I also made a complete new ML installation from
scratch with only Logic Pro 9 and the needed USB-driver for my
Yamaha-CP1 but still the same thing. I do not see any
processor-Problems. I have an iMac (Mid 2010, 2,8Gh i5, 16 Gbyte Ram,
512 Gbyte Crucial SSD) Strange thing is that if I change the amount of threads used from
"Auto" to anything else it seems that the amount of Clicks will change for a
while. But it is not really reproducible and after a short time it reapears. Any idea what I can do to
fix this problem? Could it be that the driver is not that stable than
it was under SL?
Apogee Support told me after some correspondence more or less, that I am the only one with this issue... ?!?!?
I already changed cables, switched to USB-Keyboard instead of bluetooth, disabled WLan, installed a 2nd Harddisk and reinstalled the OSX and LOGIC a couple of times without any effect. The only way to get the Ensemble or the Duet working ist to switch back to SL which can't be the solution as it should be fully compatilbe with Mountain Lion. At least this can be read on the support pages fom Apogee!
Is there anyone with the same kind of problems?

Ok, folks...finally figured it out. Thank you so much for being willing to brainstorm with me on this. Here's the deal:
As I was searched online forums I found some discussions regarding different firewire chips they put into different models of the macbook pro's. Apparently you can have the TI (texas instruments) chip or the Lucent chip, you can discover which by holding down 'apple' and 'S' right after the welcome sound when you're booting up your MBP. As you search through the info it should say TI or Lucent by firewire.
Apparently, the Lucent chip is known for causing issues with different devices...this is the chip I have in my MBP. Someone on another forum said they bought an external firewire bus and just put it between the computer and interface and it solved the problem...so I thought 'what the heck.' I went and bought one and it worked perfect! Crazy.
So, now I need to talk to apple and i'm hoping they'll be willing to swap my chip for a TI one or at least cover the cost of the firewire bus.
Thanks again for helping me out. Hopefully this thread helps the next guy so he won't have to spend 3 months troubleshooting like I did.
God bless

Clicks and Pops with X-fi Titanium PCIe

I am having trouble with my X-fi Titanium PCIe where I am getting clicks and pops every so often. The problem is during any audio, music, movies, netflix etc. I am connected thru optical spdif and I have tried with Dolby Digital Live both on and off, and the clicks are always there.
I checked IRQs and the X-fi is sharing IRQ 16 with my video card and a couple other devices. My thinking is that this is the problem, but of course in Windows 7, there is no way to force an IRQ change. My board only has one PCIe x1 slot and I'm not sure what else to do.
I would appreciate any help or input.

Hi MuzicEngineer,
Certain motherboards may allow you to reassign the IRQ of your devices. You might want to check with the motherboard vendor to see if this is possible. Also if you have not already, feel free to write to our Customer Support for assistance.

Clicks and pops with flex time and fades

I am getting clicks and pops on tracks using flex time and fades. Any suggestions?
Thanks

Probably the simplest solution to this bug (it appears to not be creating zero crossed edits when creating a fade over flexed audio) is to cut the area to be faded into small region and render (or bounce in place) the small section, then fade it.

Clicks and Pops in Audio even with High Buffer Values

Dear Community,
I'm running into a problem with my Mac Pro 2008 for which I need urgent help.
I have a Mac Pro 2008 which I use to do some audio production and mixing.
I use 10.8 Mountain Lion for some time now, mainly with Avid Pro Tools 10 and Logic Pro 9.
My audio interfaces of choice are the Echo Audio Audiofire 8 and an Eleven Rack (USB) which I never use simultaneously. For tracking guitars and bass I use the Eleven Rack but for mixing and adding other instruments I use the Echo Audio because of its multichannel capabilities.
I had this configuration for many months / years without any kind of problem and being able to use very low buffer values (128, 64 and even 32 bits) with very low latency values (ideal for tracking guitar with software monitoring).
Now I'm running with problems with audio clicks and pops in all audio streams independently of the audio interface I use.
I've tried every tip I found on the web for optimizing my mac for audio with no success.
Independently of the buffer I establish in Pro Tools or Logic (or any other audio software, for that matters) I always get the same harsh, distorted audio, with permanent clicks and pops. It's the same with pre-recorded audio or when using just an armed track with software monitoring. Even when using just Amplitube 3 in standalone mode, I can't get audio working correctly. Raising the audio buffer to 4096 (!!!) or lowering to 64 is the same. The output get garbled, distorted, harsh, with permanent clicks and pops (on the Audiofire or the Eleven Rack).
I've already tried reinstalling drivers, mangled with all audio preferences possible with no success.
I'm considering, as a final option, to reinstall the OS and all audio software from scratch but this is the very final possibility because of the long long hours needed to do so.
Does anyone have some idea about this?
Could anyone help me?
Best Regards,
Luis Mota

Luis, the sound you're describing does not sound like a clock problem.
Sync set to "Internal"
To check you can go to Settings/Synchronization uncheck "Auto Enable external sync".
I'm guessing like most Mac users you have the operating system set to auto update, if so the system may have updated on it's own so you can't be sure you're running the same system that worked perfectly in the past.
I disable every "auto" b.s. Apple/OSX tries to force on users... for pro audio users, it generally causes problems.
Here's some things to try.
1. Set the Mac's audio preferences to use only built-in audio for both recording and playback. Do so in both System preferences/sound and Audio-MIDI Setup. Turn off the Mac, unplug and audio interface you have hooked up. Restart the Mac, Plug in an audio interfaces (doesn't matter which one) open Logic, go to Preferences Audio and select the installed interface, even if it's selected already, set buffer to 256.
Any difference?
2. Create a New User account and try running Logic from there.

Clicks and pops when running Mainstage 2 with Guitar Rig 5 in Mavericks.

**I've read that this may be unsolvable but I hope someone can help me**
Hello everyone,
I very recently upgraded to the new Macbook Pro 15" Retina as my 2010 Macbook running Snow Leopard is on it's way to Apple heaven. This means I am now on Mavericks and **** is ******, it's my fault for not upgrading sooner so I am to blame in some respects. Here is my issue.
My set up is fairly basic:
Mainstage 2.2.2 (I can't upgrade to 3 as the synths we use are not 64bit compatible.. another nightmare due to my lack of upgrading in the past)
Axiom 64 MIDI controller via USB
Guitar Rig 5 controller via USB (audio interface)
In Mainstage we have the L output for virtual instrument parts and the R output for guitar parts. These are globally panned L and R.
The L output from Mainstage goes through the Guitar rig footcontroller out the L output through a DI and then to the mixing desk. The R output goes through the Guitar rig controller out the R output and straight to the guitar amp. Simple way to do both keys and guitar.
We never had any problems with this in Snow Leopard. With Mavericks this setup is unusable due to the clicks and pops shooting through the guitar amp. It doesn't matter whether the voume on the guitar itself is turned up or down it's still all "click POP.. CLICK pop pop click" Mainstage just seems to be sending these pops regardless if anything is being played or not.
When I ran the same session through my Focusrite Saffire Pro 24 there was no popping on the virtual instruments so I'm thinking it could be a guitar rig issue.
Can anyone help me with this? I'm sure a lot of people are finding the same thing... **** I know a lot of people are getting the pops without guitar rig involved. For now I'm going to continue to use my old Macbook but I'd LOVE to have the new one running smoothly!
Thanks a lot!

**I've read that this may be unsolvable but I hope someone can help me**
Hello everyone,
I very recently upgraded to the new Macbook Pro 15" Retina as my 2010 Macbook running Snow Leopard is on it's way to Apple heaven. This means I am now on Mavericks and **** is ******, it's my fault for not upgrading sooner so I am to blame in some respects. Here is my issue.
My set up is fairly basic:
Mainstage 2.2.2 (I can't upgrade to 3 as the synths we use are not 64bit compatible.. another nightmare due to my lack of upgrading in the past)
Axiom 64 MIDI controller via USB
Guitar Rig 5 controller via USB (audio interface)
In Mainstage we have the L output for virtual instrument parts and the R output for guitar parts. These are globally panned L and R.
The L output from Mainstage goes through the Guitar rig footcontroller out the L output through a DI and then to the mixing desk. The R output goes through the Guitar rig controller out the R output and straight to the guitar amp. Simple way to do both keys and guitar.
We never had any problems with this in Snow Leopard. With Mavericks this setup is unusable due to the clicks and pops shooting through the guitar amp. It doesn't matter whether the voume on the guitar itself is turned up or down it's still all "click POP.. CLICK pop pop click" Mainstage just seems to be sending these pops regardless if anything is being played or not.
When I ran the same session through my Focusrite Saffire Pro 24 there was no popping on the virtual instruments so I'm thinking it could be a guitar rig issue.
Can anyone help me with this? I'm sure a lot of people are finding the same thing... **** I know a lot of people are getting the pops without guitar rig involved. For now I'm going to continue to use my old Macbook but I'd LOVE to have the new one running smoothly!
Thanks a lot!

Image won't open after right click and "open with" command using Editor PSE 10

Can't see image after right click and "open with" Windows XP command using Editor PSE 10. The editor opens but no image appears. I have to use the open command from within Editor

Make sure you have chosen the application PhotoshopElementsEditor.exe and not a shortcut.
To manually associate a file format with an application:
In Windows Explorer, right-click a file whose file association you want to change. For example, if you want to change the file association for all jpeg files, click a jpeg file.
Choose Open With > Choose Program from the pop-up menu.
In the Open With dialog box, click Browse and then locate and select the exe application file.
Checkmark "Always use the selected program to open this kind of file" and click OK.
Note:If you choose a program from the Open With menu in step 2, instead of selecting the Choose Program option, this check box is not available, and the file association won't work.

Logic 8.2 and OSX 10.5.6 And Amplitube 2 Clicks And Pops??

I have what I think is a pretty fast comp...I never had issues really running Amplitube until it seems I upgraded from earlier Leopard to 10.5.4...Thats the only plug in that causes clicks and pops...Ive got latest update for Amplitube and Logic..but they havent released update in a while for Amplitube...Any ideas?? Has anyone heard of this issue yet..Is there something Im missing or is this a typical situation of upgrading my system to far? Thanks,

Oh... oh! comp = computer!
Sorry, I re-read this post several times and I couldn't figure out why having a fast compressor would cause clicks and pops... I thought maybe the attack was set so fast that it was causing artifacts. I must be working too hard...
FWIW, I don't have any issues with Amplitube 2 on 10.5.6 with Logic 8.0.2. Buffer size, perhaps?

Sound clicking and distortion with X

Anyone else having sound clicking and distortion with their X-Fi Card? Its rare in most games, but I have a couple games where its very common Eve-Online for example. I have a X-Fi Fatalty FPS.

Using Asio4All will introduce a higher latency than using Creative X-Fi ASIO / Bit-Matched -mode, so the later is recommended. If you get distortion make sure that your volume is not turned up to max, it should be around 0db in the mixer, which corresponds to about 80%. If you get cracks/pops then it's due to the bad performance of the ASIO drivers of the X-Fi. The latest beta also says to remove cracks/pops and some distortion problems in audio creation mode, maybe try them.
Again, here is a list of real latencies as measured on my own system, using the latest stable driver (not the beta one):
Rate = sample-rate
Comp = latency compensation in ms (by how much the real latency differs from what the application/driver reports
Low = lowest no of buffers (in samples) that I was able to use
Real = real measured latency (in contrast to what the application/drivers reports)
ASIO4ALL
Rate Comp. Low Real
44k hb: +12.5 112 23.6
48k hb: +6.18 80 12.2
44k kb: +15.5 80 19.1
48k kb: +6.20 80 9.53
48k kb: +5.66 80 8.99
96k: +6.71 80 8.38
192k +5.78 144 8.03
Creative X-Fi not Bit-Matched
Rate Comp. Low Real
44k: +9.05 44 13.3 !most times glitches!
48k: +8.29 48 12.4
88k: +9.73 88 12.9
96k: +8.94 96 12.0
Creative X-Fi Bit-Matched
Rate Comp. Low Real
44k: -0.65 44 3.61 !most times glitches!
48k: -0.61 48 3.47
88K: -0.27 88 2.86
96k: -0.25 96 2.79
Delta Audiophile 2496
Rate Comp. Low Real
32k: +0.15 64 6.09
44k: +0.11 64 4.42
48k: +0.08 64 4.04
88k: +0.05 64 2.20
96k: +0.10 64 2.08
Message Edited by Timur on 06-03-2006 09:18 AM
Message Edited by Timur on 06-03-2006 09:22 AM

Click and Pops in Audio Playback

I am using a MOTU 824 Mk3 with L7P 7.2 and a Dual G5 tower. This system worked very well for quite awhile but recently there are click and pops in the audio on playback only, meaning the clicks are not in the actual audio files and they do not get recorded.
The clicks were occurring randomly, maybe 1 or 2 per minute. I increased the buffer size to the max of 1024, now the clicks occur every so often, maybe I'll hear 1 while listening to 10 minutes of audio.
I am not using L7 in demanding applications right now. Normally 1 stereo track with 2 or 3 plug-ins, though the number of plug-ins does not seem to matter. I could have no plug-ins running and still would hear the occasional click.
I don't think it is the MOTU interface because I do not have this problems with other programs. For example, if I run Waveburner playing back identical audio, Waveburner never clicks or pops.
Anyone have any ideas? It's starting to drive me crazy. It's possible this all started when updated from 7.1 to 7.2 but I do not know that for sure, it could have been happening before I upgraded.
Thanks in advance!!

I believe this problem is due to having the plug-in Soundflower from Cycling 74 active through an aggregate sound driver. When I changed the sound driver to another aggregate sound driver w/o Soundflower, thereby de-activating Soundflower, the problem seemed to go away. I need to do some more checking though to make sure it really is gone and it was Soundflower.

Removing clicks and pops

I see the manual makes reference to the program being able to remove clicks and pops in audio but I can't for the life of me find this option in any filters that came with the program.
Can anyone tell me where to find this filter?
Many thanks.
Steve

drag the file onto your icon form your dock. soundtrack will open up, i think it might be in the actions tab on the left. try this out.

Analysis not working.. Clicks and Pops, etc.

I'm trying to remove clicks and pops, clipped signals and power line hum from an audio track (registered using an iPod mic in a big room so it's full of noises) with the latest Soundtrack Pro 2-
I did a Noise Reduction then applied the following Analysis: Clicks and Pops, Power Line Hum, Clipped Signal. After the processing, I click in each item in the list and fix it. The problem is that 90 per cent of the times the Click/Pop/Clipping is not fixed. I can see it alters the waveform but you hear pretty much the same thing as before...
Do you have any experience on that?
Thanks

This is a tedious process you're trying to do. What it really comes down to is zooming out the audio until you have clicks and pops of about .5-1 sec. Then you really have to go over and over the really bad ones until you've covered it from all angles. What ultimately happens is you reveal layers of the pops. As you take out one layer another appears. When you isolate the problems they all begin to fix easier. The program is really very adept at finding the rest of a pop that only appeared partially on the surface at first.
Good question - patients is a prereq. virtue here: Good Luck.

Clicks and pops for no apparent reason

Old Today, 05:17 PM #1
USCRash
New User
Join Date: Apr 2008
Posts: 12
Default Clicks and pops, audio dropouts
I don't know if anyone else has this problem, but it's driving me crazy. I can't have any other program open while running soundtrack pro, even Activity Monitor, without getting clicks and pops and the occasional audio dropout. These issues are not present in the audio file -- they are digital artifacts that seem to only be an issue in STP.
The multitrack project I'm using was created from a sequence in FCP, and when playing the original sequence in FCP, there were no audio problems.
It doesn't appear to be an issue with my amount of RAM (2GB) because Activity Monitor was showing over 70% free. The processor (2.66 Intel Core Duo) doesn't look like it's being taxed all that much. Is there some kind of buffer setting that I should change? It's obnoxious. Every time I use some other application (Mail, Firefox, Acrobat reader etc.) I have to restart the computer before opening up Soundtrack again.
Also, has anyone noticed that it takes a loooooong time to save a project?

I notice quite a bit of issues with RAM as well. I just went up to 7 Gig to have some extra for the OS and my project just hit 3.7G of RAM which of course STP couldn't handle and it wont save and sometimes beach balls.
So, I've split my project into two projects for now and will continue to do so even more if the memory footprint keeps increasing. There is some really poor memory management happening related to duplicate clips. Hopefully they are aware of it and do something OR figure out how to use 64-bit memory space like EXS in Logic.

FCPX + Lion + Cannot handle AAC or Apple Lossless audio in H.264! (Clicks and Pops)

This is a problem I've been having since I upgraded to Lion, and I've posted this response in other forums, but wanted to start a fresh one with a video I created of my findings. In a nutshell: FCPX in Lion cannot handle AAC audio in H.264 files since it will create audible clicks and pops when it subsequently renders the footage. This ***** because the iPhone 4 for example records as H.264 and AAC for the audio. Below are my findings:
So I think I figured it out! (I'm pretty sure FCPX + Lion has issues with compressed audio formats, ESPECIALLY AAC and Apple Lossless!) There's a video of my findings below:
1. I tried doing exactly the same thing I was trying to do on my machine on a co-worker's Snow Leopard MBP, and it worked out fine (it was just importing an iPhone 4 .mov and exporting it in FCPX). The output file was pretty much the same as what came in.
2. I found out that only movies from my iPhone 4 were coming out all crazy in the audio, yet my Canon T2i files were fine. Both are H.264, yet the Canon T2i records audio as Linear PCM, while the iPhone 4 records audio as AAC.
3. So I got an idea to use screen flow to record a youtube video and record the computer's audio. Then I decided to export with different formats, both as HD NTSC standards and as web standards with H.264.
4. I found out that both NTSC and H.264 standards were perfectly fine, SO LONG AS THE AUDIO WAS LINEAR PCM (or uncompressed!).
5. I then exported the same clip (both times as H.264) and ONLY changed how the audio was rendered (either Linear PCM/Uncompressed or AAC) and VOILA, I got click and pop artifacts ONLY in the AAC version. The ones that were output as uncompressed audio were totally fine!
CONCLUSION:
Final Cut Pro X on OS X Lion has issues with compressed audio, MAINLY AAC and Apple Lossless! Anything that is Linear PCM/Uncompressed should be fine! For example, MPEG 4 AAC Enhanced Low Delay at 320K came out 95% OK, one or two clicks.
So if any of us are working with material where the audio came to us already as AAC (like an iPhone 4), then we have to rip the audio out somehow first (like through VLC for example) and import it separately as an uncompressed file.
Here's a youtube video showing exactly what I'm talking about:
http://www.youtube.com/watch?v=FDw4btShH0s
Anybody else have any thoughts on this before Apple comes out with a fix?

I was having the same problem and spent several hours on the phone with apple working with one of their 3rd level support guys. Their is deffinatley a issue with Lion and FCPX. I was told they would escalate to a FCPX engineer and they would get back to me in two days. In the mean time I went to my local apple store and was able to recreate the issue on every machine I tried. Apple did call back and confirm that there is an issue with the way FCPX and Lion handle the import and export of AAC files. They said there would hopefully be fixed in a future update.
The best work around I found is to take your AAC file and convert it to a WAV. I used compressor to do this and it seems to have solved the problem.

Clicks and pop with muvo

Similar Messages

Maybe you are looking for