Glans:

If the tearing doesn't exist when playing any other format in any other video player, how come it exist when playing video in avid?

Some thoughts from me - a non-technical user of MC.

The playback in Avid is the playback of your sequence on the timeline.
It may be having a tough time rendering on the fly.

The playback in other video players is not from your Avid timeline.
It is from a completed project that has already been transcoded into an avi, mpg, qt etc. etc.

Two completely different scenarios.

Your video card is not a supported one for Avid.
So, it is possible that your video card cannot play the Avid timeline correctly.

Whereas your video card will have no problems playing back a finished movie in Media Player etc. etc.

Maybe the solution lies in the video card...... or even in the Quicktime version you are using.
Or a combination of both.

Regards,
Douglas

drbgaijin:

Glans:

If the tearing doesn't exist when playing any other format in any other video player, how come it exist when playing video in avid?

Some thoughts from me - a non-technical user of MC.

The playback in Avid is the playback of your sequence on the timeline.
It may be having a tough time rendering on the fly.

The playback in other video players is not from your Avid timeline.
It is from a completed project that has already been transcoded into a navi, mpg, qt etc. etc.

Two completely different scenarios.

Your video card is not a supported one for Avid.
So, it is possible that your video card cannot play the Avid timeline correctly.

Whereas your video card will have no problems playing back a finished movie in Media Player etc. etc.

Maybe the solution lies in the video card...... or even in the Quicktime version you are using.
Or a combination of both.

Regards,
Douglas

The card is the same as a Quadro, the difference is with it's tweaks and pricetag. It's just that one has been tested, the other has not, doesn't mean it's not working.

As for that, a quicktime reference plays of my sequence as well, but it doesn't have any tearing.
I can play 1080 25p footage at 185x with two color correct layers without trouble, how would a DV resolution without any effects be a problem to render? The tearing exist at all resolutions and framerates.
I also believe that there are someone in here who said he has a qualified card but with the same tearing.

My dollor goes to this problem having something to do with windows vista. Mainly because the Vista overlay is turned off when using Avid and that makes the tearing appear when moving windows and browsers around, while when the overlay is on it's smooth and synced.

There are more then me with this problem, so I do not believe it's because of my system specs and setup.

I've had this issue with FSP in a range of versions dating well back prior to MC 3.0, with a range of authorised and non-authorised cards.  I've always assumed that the issue was caused by working with 50 Hz media on displays that can only run at 60 Hz.  After scanning the posts here, apparently not.  And like others here, it doesn't matter whether I have vertical sync active or not.

An early post from Mark Burton suggested console (?) commands

To turn on type 'FSP Locked'

To turn off type 'FSP Unlocked'

Dont know if the works. 

I have the problem here with MC 3.1.3 on

Qualified 8600's, with qualified 3500 cards setup as per readme, correct version of QT, happens with both XP SP3 and Vista 64 with 8GB's RAM

Tried the console commands - no love...  Would appear that quite a few of us have had this problem - and for it to have made the bug list means that Avid have seen this too.

carlgmi:

Tried the console commands - no love...  Would appear that quite a few of us have had this problem - and for it to have made the bug list means that Avid have seen this too.

It might be a Pal only issue, would expalin some of it

I must admit I have always viewed the FSP feature as an imperfect way of monitoring and espeicially colour grading, so when I experienced tearing I figured it was part of the cludge (having previously monitored of a mojo).  Rather than asking or waiting for a fix, I was, and still am, very keen to see Avid release a monitoring only solution at a sensible price (for what you get) and not the Mojo DX.

Now that I see I am not alone, and in the absense of any entry priced monitoring hardware, I would be very keen to see this fixed, more from a client perspective than anything else.  For grading, SD via mojo is still my solution.

And if QT player can get it together on the same monitor without tearing, then surely the edit app can too?

Hi Folks,

take also a look into this old thread.

http://community.avid.com/forums/p/63436/412058.aspx#412058

The FSP Problem was described often in the past. I am wondering why it is now so heavy present in the community. In this old thread I described my way to minimize the problem. In version MC 3.5 I was able to eliminated the bug by this procedure.

And I also think it`s really time that Avid spend some words and solution to this thread.

Good luck to everyone

Robert Kreuz

r.kreuz:

take also a look into this old thread.

 

http://community.avid.com/forums/p/63436/412058.aspx#412058

might be the force with you........, my young jedi

robert

I must be on the dark side then as my triple buffering is on (and it was from your thread that I first tried it) and I still get tearing.  Running a Quadro, correct nvidia driver and QT version on Vista...

Mind you, I cant find a setting in my nvidia panel to force only 2 on the max pre-render frames?  Are you on XP or Vista?

I am on Vista,

hope this image insert will work to show you, where you can find "max prerendered frames" . I am from Germany, may be there is a mistake in translation.

Well, the only thing I can give you yet is a smile of knowledge of this darksidetrip and a loud scream shoud out to AVID. They have to be the ones who work on this problem not their clients. 

So Avid I can only repeat, put your Pinacolada away and give us an answer to this.

Think we have to bomb this thread with entries, until we breakdown the community highscore. May be then have someone pity to us.

r. kreuz:

IF you check the earlier posts in this thread, you will see that Marianna is very much on top of this situation. I"m sure she is doing everything that is possible to expedite this issue as rapidly as possible.

Good evening Larry - in germany now it`s 3:00 am

Yes, I red the entrie from Marianna. But this one is from 12. and 13. August now it`s Sept 21.

Sorry, I am and surely the other editors who filled this thread working in a business and not in a knitting-club.

For my part, for some clients I do administration on their avid systems. And with every new Avid update I have to check out new bugs. My time I invest to cool down the clients, to read threads like this and try out settings - AVID could not pay me back. 

And the only that I / we get back is "give me a few days" - sorry. If I say to a client "give me a few days to solve this problem" and need this time span, I could close my office.

And by the way, this is not the first thread about the tearing problem, is known since version 3.0 - came out last year.

peace

Robert Kreuz

www.feuerundauge.com

r.kreuz:

...where you can find "max prerendered frames" .

You can see from my settings options that I have triple buffering ON, Vertical sync ON, but there is no option for Max Pre-rendered Frames at all.  This is on an Quadro FX 3500 running MC3.5.4 with the certified and supplied nvidia driver 169.47 on Vista Biz 64???  Where is my pre-rendered frames setting?  Does the 3500 not support this feature perhaps?  I had a few settings different to yours which I have swapped but the end result is the same, still tearing.

Whilst the client preview is an issue, I'm not really sweating this too much because, as mentioned earlier, I await a monitoring card or having to bite the bullet and buy a DX Mojo...  I need better colour grading in HD  so have a long shopping list of monitors and hardware that await the end of this downturn...!