New Info re: AVCHD transition "blips"

[michal_h]

Hello,
I've made a quick test of Corel VideStudio2010 (part of Corel DigitalStudio2010) and I can not see any blips after transition! This version is very simple so I hope next version of videostudio (X3?) will be soon...
Michal

[Black Lab]

That is promising news.

[mirwais]

Hello,
I've made a quick test of Corel VideStudio2010 (part of Corel DigitalStudio2010) and I can not see any blips after transition! This version is very simple so I hope next version of videostudio (X3?) will be soon...
Michal

but it doesn't smart-render

[michal_h]

Hello,
I've made a quick test of Corel VideStudio2010 (part of Corel DigitalStudio2010) and I can not see any blips after transition! This version is very simple so I hope next version of videostudio (X3?) will be soon...
Michal

but it doesn't smart-render

there is no info about smart render during rendring file but it looks some parts (w/o transitions etc) are much faster rendered

I can not see any picture deterioration while comparing original file and rendered file on 50' plasma TV

[pwholzel]

I can not see any picture deterioration while comparing original file and rendered file on 50' plasma TV

I do see picture deterioration in the output of the 2010 product, but I don't see the blips. If you do a cut in the middle of a pan of a landscape (for instance), you will notice that the picture becomes pixelated for a very short instant before and after the cut. It looks like the blips have been replaced by pixelation! Arrgghhh!

[Xyzzy2]

Hi!

I've rendered AVCHD to MPEG2 in 2010 and used transitions.

It seems that the blip problem has been solved by another problem- after every transition there is 1-2 frames missing :/

[Ron P.]

Hi!

I've rendered AVCHD to MPEG2 in 2010 and used transitions.

It seems that the blip problem has been solved by another problem- after every transition there is 1-2 frames missing :/

You realize that Corel just might correct this missing frame problem, by putting the blips back in, don't you??

[pwholzel]

I think I've found a free workaround for the stutters/blips. Please see my post here:
http://forum.corel.com/EN/viewtopic.php?t=36100

[pwholzel]

I think I've found a free workaround for the stutters/blips. Please see my post here:
http://forum.corel.com/EN/viewtopic.php?t=36100

Now that I look closer, I am seeing imperfections. I guess this isn't such a great method.

[pitje]

I am still waiting for a good solution or workaround for this very annoying problem. I worked hours ,to edit a 2H video documentary about the ritual burial in Sulawesi. After rendering ..i saw the disaster !
Is there any news from the Corel side ?
Basic material comes from a Sony HDR-CX105, memorycard, AVCHD files

[Ken Berry]

Nothing heard from Corel on this problem, though they have had it now for about a year. And frankly, I would not be holding my breath for a patch...

The only thing I can suggest in the meantime is something I suggested in another thread, which one user at least found worked. That was not to use transitions as such. Instead, since VS 12/X2 now has this facility, simply drag the beginning of one clip over the end of the preceding one just a little. That automatically madkes it a cross-fade without actually inserting a cross fade transition ... and the blip. That means you are limited to only cross fades and cannot use all the other transitions, but at least you have the most commonly used transition available ... without the blip.

[laidback]

Nothing heard from Corel on this problem, though they have had it now for about a year. And frankly, I would not be holding my breath for a patch...

The only thing I can suggest in the meantime is something I suggested in another thread, which one user at least found worked. That was not to use transitions as such. Instead, since VS 12/X2 now has this facility, simply drag the beginning of one clip over the end of the preceding one just a little. That automatically makes it a cross-fade without actually inserting a cross fade transition ... and the blip. That means you are limited to only cross fades and cannot use all the other transitions, but at least you have the most commonly used transition available ... without the blip.

On reading this, I think the problem could be the following..

The Transition FX/s may have been designed for 30 fps, and when they are mixed with Pal 25 fps, VS refers from the FX frames to the next clip to the wrong frame after whatever FX has been inserted to the time line..


My other guess would be, the Proxy file used may be 30 frames and also the FX 30 frames, but when the proxy files frame is referred to as to which frame is to be rendered to the Original clip it starts at the wrong place..

If you have contact with Corel, maybe my thoughts should be mentioned to them,
Err~I hope I have nailed this glitch, and if so - I hope corel sends me all there latest Video editors fur fwee!

Cheerio then Guys N Gals,

Pete..

[Ken Berry]

The only problem with that theory is that if you look at the extremely long thread on the transition glitch (including this one, if you look at the first poster on page 1) you will find that there are NTSC users who also experience the blip problem...

[laidback]

The only problem with that theory is that if you look at the extremely long thread on the transition glitch (including this one, if you look at the first poster on page 1) you will find that there are NTSC users who also experience the blip problem...

Aha! So obviously its got nothing to do with the proxy template, nor the frame rates, but I feel it narrows it down to something to do with the FX's..

sorry, if this was mentioned and or suggested earlier, its just that I have a massive memory problem..

Ok I will go over the threads again, and hopefully my stupid short memory of mine wont fail me any further..

Cheers,

Pete..

[pwholzel]

FYI, the blips/stutters occur regardless if there is a special effect transition or just a normal cut.