Jack11223344

Hi Softball: I can see that you CPU usage is low which seems abnormal. 64G Memory is also good. I can't reproduce the issue here. Could it be the disk problem? Thanks Jack

HI, the reason that the first clip and NLE reverse are fast is most likely because of the lossless export, no re-encoding needed. If you try to use a different resolution other that the original, you can see the difference. Yes, the reverse algorithm can be optimized but not an urgent job. We will consider this in the future release.

Hi equalthree, which version were you using? Please try to update to the latest version from our website and try again.

Thanks everybody for reporting, this bug will be fixed in the coming release. Cheers Jack

Thanks everybody, this bug will be fixed in the next release.

Ok, I see. We might need to improve this. A work around can be export that part to a video firstly and replace the clip with the video. This exporting will be faster.

Thank for your help, this bug will be fixed in the next release. BTW, there is a clip in track 3, at 31 seconds with speed change 9000, seems strange. That causes the exporting slow.

Thank you all for your help, we have identify this issue and will be fixed in the next release. Cheers Jack

Hi Wendy, thanks for your help. We are planing a new release today to fix this problem. In fact, the exported video can be play with sound using VLC player. Other player can't. But anyway, the next released version won't have this issue.

We will make some improvement about this in the next release.

Hi GodGabriel2000: If you can explain in more detail about the (1, 2, End) - (2, 2, End) issue, we can take a look into it. Also, when exporting, try fix frame rate, increase fps, such as 60, will this fix this issue? Regards Jack

Thanks for reporting, with your help, I am able to identify this bug and will be fixed in the next release.

Hi minotto : I can't see the original project, if you can restore it, I will look into it. Cheers Jack

Hi pixellphoto: We are able to identify this bug, this is caused by too many video tracks, in the project > 60 and thus cause a memory issue. A temporary fix is to avoid using more tracks. In you project, you can merge to fewer tracks say < 10. We will fix this bug asap, if not the next release, the one after next release. Thanks borate and pixellphoto for reporting.

Bug is confirmed. Will be fixed in the next release. Work around is, when upload to youtube directly in vidoepad, in the setting dialog, choose 60 fps instead of 30. Thanks Jack