c_major

It seems you are using an older version. We only put in the processor option recently. Please try the latest build - v11.38. We also applied a lot of fixes since 11.01.

Also could you let us know which VideoPad version you are using? Is it 32 or 64 bit? Could you please try the latest build (v11.38)?

Hi, We do aware of many crash and hang reports from users using Intel GPUs. We are working on solving this issue. Could you please try avoid using Intel GPU for now? You can chose CPU only from Options > Editing > Video Processor. We will be grateful if you could help us run further tests to identify the problems. Thanks for reporting issues and sorry for the inconvenient.

Hi RenderSys1608, We are struggling to find the cause of this issue since no one in the team is able to reproduce it. It would be nice if you could share the project files to us so we can check it out. Please PM me with the link if you want the files stay private. Thanks.

@jsnpi500 Hi, we've found a bug in the new sound normalization since your report. It's now fixed and will be released soon. Thank you!

Hi Russ, VideoPad always read the file as 720x480(which how it was stored). You can manually add a "custom" export resolution - 720x540 and select "stretch". I guess your problem is that since export settings are saved in project file, when you start a new project the settings restored to default? Maybe you can try just replace the clip and export again in the same project?

Video processing is computational intensive. We do intend to reach 100% usage of both CPU and GPU to maximize performance when necessary computation need to be done. We aware of overheating issue on some older CPUs but we do not want to compromise performance which we think it's more important and apply to every user. If overhearing become an issue, I think you should shutdown the machine and let it cool down for a while.

The new GPU pipeline has been released with the latest version v10.21. VideoPad now supports hardware decoding and encoding on all GPUs (if the hardware have video processing capability).

We've just had a new release v10.18. The "failed to load file" issue should be fixed now for Windows Store build. Sorry again for the inconvenience and thanks for the patience.

We've realized that there is an error in current Windows Store build (v10.7) that causing issues on loading video files. We have fixed the issue. It might take a few days for going through the testing process before the fixed version gets release. Sorry for the inconvenience and thanks for reporting the issue to us.

We are improving project templates. We also testing changing the name to "Video Maker Wizard". Half of the download will have the name changed.

Hi Russ, I've asked around about 16-bit TIF. We don't support processing 64 bit per pixel formats.

The best way to avoid quality loss is to use lossless export - by leave the default export options. VideoPad support lossless transcoding for h.264 and MPEG4 codecs. Video data are simply copied from the input video to the output, without the trimmed section. Please note that if the input and output format does not match or the codec is not supported, the video must be re-encoded. Re-encoding is always lossy.

Hi Takis, Thanks for reporting issues to us and sorry for the inconvenience. Could you please try out the 32 bit build for v10.16? Update: We couldn't reproduce the flickering using your project. Could you please also try use the debug build below and export the project? It will generate a trace log file in: C:\Users\[user name]\AppData\Roaming\trace_VideoPad.txt Please also check your PM for my email address. Thank you.

We used a separated data set for each export progress. Editing the project will not changes previous export result. We will investigate these areas.

It seems your bad experiences are mostly because of the performance of the user interface rather than video processing. We will investigate these issues and work on improve them. Thanks for reporting issues to us.

Thanks for the info. May I ask what kind of graphics card you are using? v10.16 introduced a redesigned GPU acceleration pipeline which support encode and decode video files using your graphics card. In most cases we've tested this will help boost performance. If you find the issue persists please use the last stable version v10.12 instead.

Please note that we have dropped Window XP support for 64 bit build. Please still go to our home page to download if you are using Windows XP.

We were drawn to the pipeline work after this discussion and overlooked this idea. Thanks for bringing it up.

We were unable reproduce some of the issues mentioned above. If it's possible, could you please share the projects files that can reproduce these issues, especially the ones present in v8.99? Thanks, VideoPad Team

Are you using v9.04 which has some know issues. We have reverted the release to v8.99 on the web site. Please download it again see if that solve your problem.

To anyone that encountered crash issue, if you are willing to help us to track down and fix the bug, please install and try using this debug build to reproduce the crash: If the crash happened in the debug build, internal information will be written into a trace log: C:\Users\[User Name]\AppData\Roaming\trace_VideoPad.txt Could you please kindly PM me and post the text in the trace log to me? BTW: I've reverted this release since the crash issue so there will be limited number of users would encounter this issue.

VideoPad v9.04 is released with a new video processing pipeline that would utilize GPU acceleration much better than it was. We are monitoring this release closely. If you found this version crash or any other problem please report the issue here. Thanks, VideoPad Team

I've filed the suggestions. Thanks!

You have to do stabilize before aspect ratio conversion, is that because of you want to output back to analog TV format (non-square pixels)?