Showstopper waveform redraw issue in 10.0.3

Yes. Both video thumbs and audio waveforms turn solid blue until playback is stopped. Also note that storyline does not scroll forward when play head reaches right edge of timeline. Must then manually scroll storyline to find out where play head is. This, in turn, causes thumbs and waveforms to turn solid blue.

Frames are not being dropped. Render/background indicator doesn't show anything going on. Does it with optimized and low-res media in both performance and quality playback modes. Can't say for sure these issues are new with 10.0.3 but they are very annoying, especially when trying to fine tune audio. Will continue to experiment with settings and let you know if I come up with a solution.

Working ok for me, all three scopes displaying whilst playing back.

1920x1080

2x 27" thunderbolt displays

1x 12TB thunderbolt raid

latest 17" MBP, 2.5ghz i7

8GB Ram

even works when playing back vision from internal HDD.

Tony

no problem here... wavesforms have always been visible during playback, edited or not. 10.0.3. MacPro 2008, OSX 10.6.8 - John

Hey Christopher. I thought maybe this issue became apparent after updating to OS 10.7.3 but see that you're still on 10.6, so that's not the problem. I've tried everything I know (which isn't much) including trashing prefs, etc. No luck!

Problem is 100% repeatable on my system: Fill visible timeline with one or more clips totaling about 5 minutes duration. Now zoom in a couple of times so roughly half of the footage is outside the timeline window. Park play head towards right end of visible footage and start playing. Play head will ultimately disappear when it reaches right edge of window. Clips won't scroll in window, so, while project continues to play, manually scroll timeline to the left to "find" the play head and get it back into window. Now all video thumbnails and audio waveforms suddenly disappear and are replaced with solid blue background (solid green if connected audio clips). Missing stuff immediately re-appears if play is stopped.

Can't believe we are the only ones out there having this problem. Anybody else have experience, hopefully a solution, for this issue? Thanks much.

10.0.5 has the problem as well.

The only way I can get it to redraw is to repeatedly zoom in and out until it re-appears. A real pain!

MacOS X 10.6.8

2008 Mac Pro 2.8GHz

12GB RAM

4 years later and that is still a problem. so annoying.

MBP 16Gb Ram, Flash SSD (or whatever is called) discrete GPU, so it's not processing power

Did you ever find a fix ?

BrzIphone wrote:

4 years later and that is still a problem. so annoying.

MBP 16Gb Ram, Flash SSD (or whatever is called) discrete GPU, so it's not processing power

Did you ever find a fix ?

What version are you using? What exactly is the problem you experience. I have never seen the problem described in this thread and, as you say, a lot of time has passed, and FCP X is now at version 10.2.3.

You should start a new thread, detail exactly what happens to you and if possible post some screenshots that help make it clear.

If indeed this was a common problem that stayed over 4 years and more than a dozen updates, you can imagine there would be an outcry, which has not happened. I don't deny you have a problem, but it clearly is not one that is widespread.

Yeah I thought about creating, but this seems so on track with the issue that I am having. OR really I didn't think was an issue and a feature??

So I made a little video to show https://vid.me/OYer , this is a safe site to click... .

BUT what happens is, while the playhead is moving, and I hit command+B the rest of the waveforms disappear until I hit space bar....

I can live with it, and I have been leaving, it would be awesome if the waveform never disappeared....

Thanks for pitching in. As far as versions I am on the latest for everything 10.2.3, and latest El Cap with all updates.

I see what you mean. I can confirm that the same thing happens to me. I never had tried this, because I don't use the blade very much, and not "on the fly".

I am curious: do you blade very much, and why?

yep that is pretty much all i use. Youtube videos. I shoot tons of material and I cut off part where I speak wrong , a word wrong or whatever.

So I hit play and cmd b cmd b cmd b all the way 🙂

I Don't think that's going to happen until computers are fast enough to simultaneously reprocess codecs for playback and rebuild clip containers. You're probably looking at some way away in terms of hardware capabilities.

I get it, BUT I thought that is what the original poster is talking about that it worked on 10.0.2?

Unless I understood him wrong.

But I totally get what you are saying.