Cross-fade was ok twice and once with a glitch. Also, the text I put on the video (letters moving up) did not give any distortions as it does from the timeline (for the entire length of the text running). However, remember that I found this quite random. Obviously, this isn't any kind of proof that this is a rule - I gave it a try only twice and I might have done few things in a slightly different way.
Quite interestingly, I found it impossible to copy and paste onto the overlay tract the entire project which has been opened from a previously saved file - I had to put the video clips onto the timeline make a project and then copy and paste.
When I was making an AVCHD disk or file, there were no other applications running - on Windows I use this computer only for video editing (Linux is for all other applications).
regards,
Przemek
it looks our problem could be solved only by corel
and if corel advised us to buy another sw we probably can not expect some patch we can only wait for videostudio 13 and hope the problem will be solved
I've just tested one more thing and I wonder if anyone can repeat this. Namely, I copied video files from my camera with Pixela Image Mixer (bundle software with HF100) to my hard disk. This software copies files from your SD card to hard disk and changes the extension from mts to m2ts. They're just two different extensions and there are no differences between the two files, but I gave it a try. Then I edited those files in X2 and saved as a file (same as the first clip properties). The glitches almost disappeared - they are really tiny. There was no transcoding and two minutes of video footage took about 5 minutes to render. Next thing I did was to make an AVCHD disk from the same project. It is quite interesting but the software started transcoding it and it took about 20 minutes to finish and burn the disk. The results are as usual - glitches and slightly worse quality. I must add that with mts files (copied directly from the SD card) the glitches are in both instances the same - both on files and AVCHD disks.
Can anyone confirm this, or am I just seeing things? It seems to be so random.
Why is there a difference between creating a video file and making a disk - I did tick "do not convert compliant mpeg files" (tried it about ten times changing settings) but alas! The software does the transcoding ... I need to add that I checked the properties of the clip, marked all the necessary boxes in the burning module etc.
Has anyone managed to burn an AVCHD disk without the software transcoding the files?
In that thread, Efenstor mentions that clips of 10 seconds or less will inevitably be re-encoded.
What length clips are you working with?
My dabblings thus far have been with short test clips, and I've yet to get anything close to acceptable results. I intend to try Efenstor's Nero Vision workflow, and having acquired a large SDHC card, also try out some longer test clips.
Hi
This problem seems to be very similar to a problem I reported in the past for SD videos, see here: http://phpbb.ulead.com.tw/EN/viewtopic. ... 1863#71863
Videostudio produced short distortions at the beginning of transistions or titles. Main difference is that my problem was only seen with smartrenderer turned on.
Because the blips weren't seen on every transition or title I found out that the position of the cut point is related to the problem.
Therefore I could remove the blips by moving the startpoint of a transition or title by shifting it for one(or more) single frames.
See my solution here: http://phpbb.ulead.com.tw/EN/viewtopic. ... 1938#71938
Would be interesting to know whether my solution will also work for this problem.
Regards
Sektionschef
As described in here: http://lists.mplayerhq.hu/pipermail/ffm ... 44013.html, the cause of all the problems is a bit too advanced encoding method new cameras use. It's proper to the AVC specification but simply not implemented correctly in the most decoders:
they are using field-based interlacing (aka PAFF), with 2 bframes. Their top field for b-slice uses temporal bdirect mode, whereas their bottom field in b-slice uses spatial prediction bdirect mode. Support for this prediction is incomplete in ffmpeg, hence the artifacts you're seing.
Hence the question: is it possible to use an alternative H264 decoder in Video Studio? I've noticed that the decoder it uses is registered as a usual DirectShow filter (ULead H264 Decoder), I searched for some setting mentioning this name is INI files and the registry but couldn't find anything. Is there a way to replace it?
This forum was built for Corel (InterVideo and Ulead) customers and guests who want to share their knowledge and ideas in this community. All discussion in this forum should be related to Corel (InterVideo and Ulead) products only (except for General Discussion section). The following rules were put together in order for us to have a positive and enjoyable community experience.
This is a Corel forum, and thus posts concerning other competitor's products are not allowed...
This forum was built for Corel (InterVideo and Ulead) customers and guests who want to share their knowledge and ideas in this community. All discussion in this forum should be related to Corel (InterVideo and Ulead) products only (except for General Discussion section). The following rules were put together in order for us to have a positive and enjoyable community experience.
This is a Corel forum, and thus posts concerning other competitor's products are not allowed...
Hi Ron,
Sorry about the violations.
So from reading the rules again I would assume the discussion which ensued be allowed in the "general discussion" section of the forum? Could a link in this discussion pointing to the "general discussion" section be permitted? I for one have both programmes and use both. I think other AVCHD users might find the various work arounds and alternatives useful information.
Regards
I reported the transition and title "blip" problem to Corel, and after several exchanges of information, the tech support person has asked me to upload "some sample videos for us to test". (I am assuming they mean raw clips from my SR-11, not video out of Pro X2 that exhibits the problem. But in case they mean a Pro X2 video, I will send one of them along with the raw clips.)
The raw clips I want to send them are fairly long and I'd prefer to cut them down to maybe 5-7 seconds each, which is long enough to see the problem with the transitions. How can I trim raw clips to a shorter length without rendering to a new file? I want to send them clips that are unaltered from what the camcorder created, other than the length.
I got to discourage everyone who's concerned, Power Director 7 Ultra has similar problems with smart render as well and is not a solution. The only avantage is has is the GPU-accelerated H264 decoding.
dalemccl
Better make a new, short clip. There's no safe way to cut existing clips.
Also send them this link: http://www.efenstor.net/external/original.mts
This is my problemous clip, made with Canon HF100.
What is discouraging is that Corel appear to show some interest in looking at an AVCHD problem with a Sony SR11 camcorder, but no interest if it's a Canon.
@Efenstor - PD7 has CUDA h264 encoding, not just decoding. Come on Corel, catch up!
2Dogs wrote:What is discouraging is that Corel appear to show some interest in looking at an AVCHD problem with a Sony SR11 camcorder, but no interest if it's a Canon.
I doubt that Corel has more interest in the Sony SR-11 than the Canon camcorders. It is probably more related to the differences in individual customer service reps that happened to handle our problem reports. The one who is handling my report seems genuinely interested in researching the problem. The fact that I have a Sony probably isn't a factor in his motivation.
Efenstor wrote:
dalemccl
Better make a new, short clip. There's no safe way to cut existing clips.
Also send them this link: http://www.efenstor.net/external/original.mts
This is my problemous clip, made with Canon HF100.
Thanks. I will make new clips. I downloaded your file and will include it when I send them my clips, and will mention that it came from a Canon HF100.