JimmyRustle

The balloon effect is still subject to split-testing and is not available for all users yet. We put the description in the help doc pre-emptively anyway.

Hi PSFerriera, Unfortunately the 2 second fade-in default is hard-coded into the program. I will file an item on our track list for making it so the user can choose this value.

Actually, we have a relatively new feature where you can drag and highlight a part of the sequence and select 'Export selected region'. In your case it might be a bit tricky to get the exact right selection.

Big changes on this release. Bugs fixed: Fixed effects not displaying on batch editor properly if hardware acceleration is on Fixed some visual artifacts related to the green screen effect Fix a possible crash after using the Resolve Missing Files dialog Fix possible crash when dragging points on mask effect Fix control panel hiding automatically on the full screen preview even when the user is trying to edit something on it Fix audio scrubbing bugs Fixed can rename a locked track Disabled click-to-play on the preview if previewing an audio clip Fixed negative duration is visible on the speed change dialog if clip is reversed Fixed Pan audio effect sometimes not displayed in the list when it should be New features: New effects, radial blur and circular blur Added looping mode to preview Added aspect ratio changing effects (letterbox, stretch and crop) Added a 'drop position' tooltip when dragging clip from bin to sequence Improved auto-match logic for export User can now choose which YouTube channel to upload to when exporting to YouTube Design changes: Effects such as Zoom now have better quality when you zoom in on the clip Removed the concept of 'Preview Resolution'. Now we preview and cache at the size at which the docked clip preview actually appears. Not longer letterboxing clips when previewing a single clip, as a result of the above changes Added the concept of sequence output resolution. Match Content will get the median aspect ratio of the clips on the sequence and letterboxes all clips to that aspect ratio if necessary. The above changes will improve performance (no longer caching and rendering letterbox "checkerboard" when there is no need to, no longer caching at a resolution greater than what can be displayed on the docked clip preview), and gives a better "what you see is what you get" factor (better match between preview and export).

Those two progress dialogs ("Generating" and "Loading") are probably more intrusive than they should be. We could try making it more invisible to the user by having the icons generate/load in the background without showing a dialog of any kind. That would solve the problem of it auto-closing the welcome dialog.

The "Loading effects and Transition icons" should only really come up once. It is just loading the thumbnails for certain effects and transitions for when you look at them in the popup menus. If it somehow can't find that folder, then it would re-generate the folder with all the icons. I can't think of why it would always appear for you, however.

Bugs fixed: Fixed transition bugs from last version Fixed incorrect scrolling for text clips. Split button not appearing on storyboard mode Thumbnails slow to update for certain clips when applying Flip, Rotate etc. New features: New audio fade options, including audio ducking. Volume and pan sliders added to storyboard mode New text scrolling mode: top-to-center General preview and caching improvements

Hi Nat, I think this is intended behaviour? Makes sense to me at least, and I believe this is the way it's been working so far. When you only have a Left clip (Clip A) in a transition and no Right clip (Clip B), we take a transparent frame and treat it as the Right clip. So in the case that you add a Fade through White to a singular clip, it will flash white in the middle of the transition, and the rest of the transition is just fading in to the Right clip. Which in this case is a transparent black frame so that you'll see Clip A -> Flash white -> Dip to black. This is logical to me and is consistent with the way that the other transitions work, but I can see how a user might want the transition to end at white. In that case we should actually add a new transition, Fade to White as opposed to Fade through White. But I don't think this transition would be useful at all the in the regular two-clip case. Regarding the Fade transition however, I do think it initially seems a bit illogical. But here's the tooltip description of the transition: "Fade to Black, then Fade into the following clip". So really, its more like a Fade through Black then a Fade to Black. (techinically, Fade through Transparent would be a better name). So here's what happens in the singular clip case: Clip A -> Totally black at halfway point -> Fade to Clip B. As mentioned before Clip B is really a transparent frame so it pretty much just stays black from a viewer's standpoint. So again I do think this makes sense, although the tooltip was changed some time ago to 'Gradually make faint and disappear' which is far less descriptive to the user as to what is actually happening, so I'll probably change it back. Since it's only two transitions which may be confusing to the user when applied to a singular clip, it is possible we could handle these as a special case and progress the fade twice as slowly so make it end at what was previously the middle of the transition. But at the moment I don't see it as a huge issue. Thanks for investigating, however.

VPJ is not a video format, actually. It is a VideoPad project file. It describes everything in your project such as clips, effects & transitions applied, cuts and edits made, and much more. When you have been editing a video you can save and load to a VPJ file to save your progress. Also, a VPJ file is very small. It sounds like you want to Export your edited video. After dragging your clips from the project bin to the sequence and making your edits, go to the Export tab and try one of the many export options. ('Video File' is a good starting spot). Here you can choose from many output formats, including mp4. There are also many quality options available. You can also upload directly to YouTube to save a bit of time.

Yes, take a look at the various timer animations we provide in the Add Title on the Home tab.

@plevintampabay My only guess regarding your crash is that when you ran the old version it read some cache files generated by the newer version (stored somewhere in your AppData folder). Cache files are not required to be compatible between different versions of VideoPad and may result in a crash if there is a mis-match. This is why we delete all cache files on install or re-install. So trying to revert to an older version by replacing the Program Files (x86) files probably wouldn't work perfectly. We can't give you an exact release date, the decision to release lies with the testers. But I'd say with a bit of luck we can get a new release this week. 😃

Thanks for reporting this issue, we have already fixed it locally. We'll get a new release out soon when some other new bugs are fixed too. Answering the question about loading newer project files into older versions of VideoPad, there is a notion of a 'project file version' that we maintain. As long as two versions of VideoPad have the same 'project file version', the older version can try to load newer version's project. If the project file versions do not match then VideoPad does not even attempt to load the project and displays an error. The reason is that some versions of VideoPad project files are so drastically different that it makes no sense for the older version to try to interpret the data that the newer version has encoded. The last time we incremented this internal project file number was with the release of v7.01, which had some significant changes as to the way that 'in' and 'out' points were stored. Pretty much, any project created with a version number equal to or greater than v7.01 will not load in any version equal to or less than v7.00.

Some minor fixes: Fixed cursor flickering between two icons when dragging from project window to storyboard window New replace and insert icons cursors used when dragging from project window to timeline window Fixed 'Cut' option working even on a locked track. Fixed certain bubble-tips can display on top of the welcome dialog Fixed FX and Fade buttons working incorrectly in some cases when track is collapsed Fixed Rotate and Flip right-click options not working on image sequence clips New feature: 'Show Alpha Mask' mode on Green Screen effect. Displays the alpha channel in black-and-white, helps you fine-tune the green screen parameters.

Thanks for your comments! I'll see what's going on with the website change-log, looks weird to me.

General improvements / new features: Green Screen improvements: add new Feathering parameter. This has a similar effect to the Fading parameter (make pixels semi-transparent) but it only affects the boundary between the foreground image and keyed out background. Both can be used to make leftover green pixels blend in with the new background. Note that Feathering is significantly slower than Fading, especially as the Feathering value gets large. 'Brightness' mode in Green Screen changed to 'Color + Brightness', giving a better key overall. Improved performance when reading from cache Improved performance when caching effects Bugs fixed: Fix selecting alternate audio stream not longer working Fix .VOB files not imported correctly Fix 'Help' button working incorrectly in Export Wizard. Fix 'Alt' modifier not disabling ripple-editing when resizing a track clip from the start. Fix sequence preview can freeze when playing beyond the cached region. Fix export wizard buttons not working for Vista users in some cases Fix certain clips being added to the wrong bins Fix possible crash when Custom tab is selected. Fix videos with non-square pixels not displaying with correct aspect ratio in some cases

Fixed in new version, v7.04

Hi @Nationalsolo The export wizard menu options not working should be fixed in v7.04 now.

Hmm, where is that change log? On the NCH website? I think that may be automatically generated based off our commit comments or something, meaning it's not particularly readable for non-NCH developers. Probably wait for us to write a proper release note on this forum (I can do that today). To answer your question to the best of my ability though, "VPClip architecture" changes means we have been doing a lot of non-user-visible work on the underlying architecture of our clip class. The old design was very prone to speed-change related bugs, and we've been fixing those kinds of bugs over and over again. Hopefully these changes make things less bug-prone for the future. New level caching I believe is just an improvement to the way effects are cached. Without going into implementation details, it should be faster.

Confirmed as a bug. From my testing, the issue first occurs in v7.02. We'll get it fixed.

If the option to upload directly to YouTube is not working, did you try exporting separately and then uploading to YouTube yourself? Click the 'Video File' button in the Export Tab.

v7.02 Fixed hamburger menu, etc. can annoyingly get activated by accident when using Alt to freely drag track-clips Fixed possible crash when double clicking on storyboard timeline Fixed image sequence clips and ExpressAnimate clips not rendering correctly, since last version Fixed incorrect info displayed when viewing properties of a image sequence clip Fixed speed change bugs on clip preview Fixed speed change issues in narration dialog Fixed small redraw issues on play overlay New feature: save project as template v7.03 Fixed Radius parameter not saved / loaded from project correctly when using Spotlight effect. Fixed duplicate thumbnails in templates dialog Fixed save project as template failing in some circumstances Fixed 'Use This Frame as Storyboard Frame' not applying instantly on storyboard Various caching improvements and optimizations

The <alt> issue is fixed! Since v7.02

Fixed in new version, v7.03

Not sure how the code right now picks which channel to upload to. This does look to be an oversight by us, the user should be able to specify a channel to upload to from the UI. This has been filed as a suggestion on our track list.

You can do a search on this forum for 'Release Note'. Not every new feature/bug fixed is listed but you should still get a decent idea of what's been changed.