VS10+ Pixellation
Moderator: Ken Berry
-
billy
VS10+ Pixellation
Xp media Centre Pentium 4 3.0 Ghz 80GB Hd + 160Gb HD 1GB Ram
Capturing from a Sony TRV480E via Firewire. New HP computer purchased July06. On playback the preview is covered by squares 'snowing randomly over the picture. This occurs when capturing as MPEG or DVD but not in AVI.
I have installed my original VS9 onto the same computer and the capture works perfectly so I use this for capture then edit on VS10.
When capturing on VS9 the buffer fills up and is flushed every 10 minutes or so, but when capturing in VS 10 this does not occur.
VS 10 is not an update version but a full original pack.
The computer is not online so there is no antivirus activated. Have installed the VS10update pack via a Flash drive after downloading with this computer.
All support from ulead has been totally unconnected with this problem but have reinstalled as per their last instruction. To no avail.
Capturing from a Sony TRV480E via Firewire. New HP computer purchased July06. On playback the preview is covered by squares 'snowing randomly over the picture. This occurs when capturing as MPEG or DVD but not in AVI.
I have installed my original VS9 onto the same computer and the capture works perfectly so I use this for capture then edit on VS10.
When capturing on VS9 the buffer fills up and is flushed every 10 minutes or so, but when capturing in VS 10 this does not occur.
VS 10 is not an update version but a full original pack.
The computer is not online so there is no antivirus activated. Have installed the VS10update pack via a Flash drive after downloading with this computer.
All support from ulead has been totally unconnected with this problem but have reinstalled as per their last instruction. To no avail.
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
This won't really help you. I too have a DCR-TRV480E and I bought it precisely to be able to convert my analogue 8 mm collection to digital by sending it *in DV format* to the computer (as well, of course, as having a back-up camera to my Canon mini-DV digital one). As you may have found, it transfers analogue well in DV format (I personally would say 'excellently'!!
)
DV is meant to be edited and can be re-encoded a number of times with no discerible loss in quality. On the other hand, there is considerable debate as to whether you should be capturing direct to mpeg-2, much less then editing it. Some argue that mpeg-2 is inherently a 'lossy' format and should not be edited at all. Others suggest it can take reasonable editing and also be re-encoded up to a point with no noticeable loss in quality taking certain precautions.
Your computer should certainly be up to the job of capturing direct to mpeg-2 format, and the fact that you do so with VS9 establishes that. Why it won't do so with VS10 is anybody's guess. VS10 came out after Ulead had been taken over by InterVideo and changes were apparently made in the coding which reflect some input of InterVideo technology. This in turn may have changed the program in some fundamental way(s). I don't know.
But I do know that if given the choice between capturing over firewire to DV format or mpeg-2 format, I would always choose DV. Then I would do all my editing in DV format, and only then, when I am satisfied with what I have done, would I convert it to DVD-compatible mpeg-2 and then burn that to disc. Sure, it may take more time, and sure, it will certainly produce much larger files (which I realise is probably an important factor to you with only 80GB hard disc space). But doing it "my" way will cause far less problems and usually guarantee a more reliable outcome.
DV is meant to be edited and can be re-encoded a number of times with no discerible loss in quality. On the other hand, there is considerable debate as to whether you should be capturing direct to mpeg-2, much less then editing it. Some argue that mpeg-2 is inherently a 'lossy' format and should not be edited at all. Others suggest it can take reasonable editing and also be re-encoded up to a point with no noticeable loss in quality taking certain precautions.
Your computer should certainly be up to the job of capturing direct to mpeg-2 format, and the fact that you do so with VS9 establishes that. Why it won't do so with VS10 is anybody's guess. VS10 came out after Ulead had been taken over by InterVideo and changes were apparently made in the coding which reflect some input of InterVideo technology. This in turn may have changed the program in some fundamental way(s). I don't know.
But I do know that if given the choice between capturing over firewire to DV format or mpeg-2 format, I would always choose DV. Then I would do all my editing in DV format, and only then, when I am satisfied with what I have done, would I convert it to DVD-compatible mpeg-2 and then burn that to disc. Sure, it may take more time, and sure, it will certainly produce much larger files (which I realise is probably an important factor to you with only 80GB hard disc space). But doing it "my" way will cause far less problems and usually guarantee a more reliable outcome.
Ken Berry
-
billy
Thanks for your quick reply Ken. 90% of my editing at this stage consists of trimmimng clips and adding or subtracting sound so capturing in MPEG2 does not appear to be a problem as the results when played on TV are good. I do have a second HD @160GB so space is not a big problem right now.
I get the same result with a Canon Mini DV camera. It would appear that there is an inherent fault in the software but it is strange that there are no other postings on similar experiences by others. Among the suggestions by Nelson Duay of Ulead support is that I download the latest version of Direct X. Have not as yet tried this but what is your opinion of this possible solution? Many of his answers have had no connection whatsoever with the problem so I do not think he understands the problem. Maybe he is just a Call Centre?
Is there anyone else out there with a similar problem????
P S I am in WA
I get the same result with a Canon Mini DV camera. It would appear that there is an inherent fault in the software but it is strange that there are no other postings on similar experiences by others. Among the suggestions by Nelson Duay of Ulead support is that I download the latest version of Direct X. Have not as yet tried this but what is your opinion of this possible solution? Many of his answers have had no connection whatsoever with the problem so I do not think he understands the problem. Maybe he is just a Call Centre?
Is there anyone else out there with a similar problem????
P S I am in WA
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
If you are running XP with SP2 and have the usual upgrades, I would be enormously surprised if you did not already have the existing current version of Direct X (Version 9.0c) already installed. So I think we can discount that as a reason for your problem. And as I say, we already know you can capture mpeg-2 just fine with VS9, which already required Direct X 9.0c... Soooo...
I can only repeat that asking any computer, even a well resourced one, to capture direct to mpeg-2 is a big ask. Yes, it works with VS9, but obviously it does not with VS10. I have already said I have no idea why this might be so. But again I can only repeat that you are better off anyway capturing and editing in DV format... So I will leave it to one of the mpeg-2 aficionados to comment further on your specific desire to continue capturing in mpeg.
I can only repeat that asking any computer, even a well resourced one, to capture direct to mpeg-2 is a big ask. Yes, it works with VS9, but obviously it does not with VS10. I have already said I have no idea why this might be so. But again I can only repeat that you are better off anyway capturing and editing in DV format... So I will leave it to one of the mpeg-2 aficionados to comment further on your specific desire to continue capturing in mpeg.
Ken Berry
-
joosuna
- Posts: 225
- Joined: Sat Dec 11, 2004 8:32 pm
- System_Drive: F
- 32bit or 64bit: 64 Bit
- processor: intel dual core 3 Ghz
- ram: 12Gb
- Video Card: nvidia
- Hard_Drive_Capacity: 2000
- Location: LosAngeles, California, USA
- Contact:
Billy, I have had on occassion a similar problem of pixation. I solved it when I noticed that upon capturing the video from my camcorder to the computer my settings were wrong. The ulead Video Studio 10 plus with Service Pack One, ... was recognizing the source of the video as DVD instead of AVI. Once I changed the setting..the pixation went away.
-
jchunter
Billy,
Your foot will not fall off if you capture Mpeg2.
Mpeg2 capturing, editing, and burning works pretty damn well in Video Studio 10+ for both standard definition and high definition video. Your macroblocking symptoms are completely abnormal. I suspect, as Joosuna said, that you are having cockpit errors in the capture stage by setting up inappropriate capture properties or letting Video Studio set default properties. Set every property manually and try another capture.
Your computer has enough punch to handle mpeg2 capture but still can fill the transcode buffer if you max out the quality setting. I usually limit my capture files to 5-10 minutes just because they are less twitchy to edit and this usually prevents the Transcode Butter Full message.
Your foot will not fall off if you capture Mpeg2.
Your computer has enough punch to handle mpeg2 capture but still can fill the transcode buffer if you max out the quality setting. I usually limit my capture files to 5-10 minutes just because they are less twitchy to edit and this usually prevents the Transcode Butter Full message.
-
billy
John and Joosuna,
Thanks for your replies. I will have another go, making sure of the capture property settings.
However, is there a clue in the sentence in my original post ..
"The buffer fills after about 10 mins. of capture when using VS9 but does not fill even after 25 minutes of capture in VS10+"
This is when using both versions which are installed on the same computer.
Billy
Thanks for your replies. I will have another go, making sure of the capture property settings.
However, is there a clue in the sentence in my original post ..
"The buffer fills after about 10 mins. of capture when using VS9 but does not fill even after 25 minutes of capture in VS10+"
This is when using both versions which are installed on the same computer.
Billy
-
limec
-
glangdon
Pixelation problem too
I have the same pixelation problem with MPEG2. MP4 works fine. I'm on VS10+ with SP1
Found a fix in one of the other threads.
----------------
At last the problem has been solved! SP1 has changed some files in
C:\Program files/Common files/ulead systems/mpeg. One of them was file
mpgvout.004. After replacing the mpgvout.004 by its an older version everything was Ok.
---------------------
Go to that directory, rename the mpgvout.004 to mpgvout.OLD, and then rename mpgvout.003 to mpgvout.004 and the pixelation goes away.... nice QA/testing process ULEAD?!?!
Found a fix in one of the other threads.
----------------
At last the problem has been solved! SP1 has changed some files in
C:\Program files/Common files/ulead systems/mpeg. One of them was file
mpgvout.004. After replacing the mpgvout.004 by its an older version everything was Ok.
---------------------
Go to that directory, rename the mpgvout.004 to mpgvout.OLD, and then rename mpgvout.003 to mpgvout.004 and the pixelation goes away.... nice QA/testing process ULEAD?!?!
-
limec
-
limec
