Jump to content

Dougie

Members
  • Content Count

    130
  • Joined

  • Last visited

Posts posted by Dougie

  1. Sometimes if you expand the timeline as far as you can, you can see the gap between clips (it's usually about 1 frame). Then you can move the 2nd clip back to fill it in.

  2. For folks like PaulX, I've had the same problem but only with slow motion clips .When the render reaches a slow motion clip, it quits. My work around is to do the slow motion effect to the individual clip(s) first (before doing any final edit), and rendering that as a new clip. Then the new clip(s) can be added to the time line during the final edit and the video will render out fine. No guarantees, but it works for me.

  3. I agree with borate about the computer. Most editors today working with HD footage really won't get by with just 2 gigs of memory and just 2 cores. I had an old eMachines with a set up like that. I changed the memory to 8 gigs (which is about all you can do with those) and it worked okay with Videopad but was still sluggish. Does it play smoothly even though it's out of sync?

  4. A simple way, if the audio is exactly the same delay throughout, is to unlink the audio from the video, then move it back until you get the best match. For some reason I find that even if I unlink the audio, I have to move it down a track or the video will still move with it. But the question to me anyway is why the sync is off?

  5. Yea, there is some approach to how VP works that is different then most editors I've tried. Many allow for editing with effects, transitions, etc without the need to re-render every clip or effect after every change, but rather renders during the actual export. This, of course, means often much longer exporting times, but greatly helps speed up the editing process. Others can be sped up by using smaller, less resource intensive proxy files that don't require heavy use of cpu time. I use Adobe Premiere that way and it's much faster on the same machine. Some even have proxy programs built-in. Then others (Edius with it's Edius HQ format is one example) allow for conversion to a program specific format designed to work quite smoothly with-in that editor (and detail is not lost). VP is apparently an all-at-once attack on the resources design, and I believe that is it's problem.

     

    All I know is that 3.00 through 3.14 have all promised to fix this issue and none really have. Perhaps the programmers need to reconsider their approach.

  6. I had the same problem yesterday installing 3.14. What is happening is that the 3.14 installer is finding references in the windows registry for earlier VP trial installs that have expired (possibly a 3.12 trial) that VP uninstall doesn't remove, and it's using that data to determine how long the new install has been around. I used Revo Uninstaller (it's free) and searched for "videopad", then deleted whatever it found, then 3.14 installed properly. Note however that if you do this, and have any other versions of VP installed, Revo will probably wipe them out too.

  7. Does anyone know what changes are being planned for the next Videopad release? 3.12 was a nice release, but it is still slower then 2.41 was. It is almost perfect as an editor, and would be if the speed (particularly render speed) were improved. One nice addition would be a 'Proxy' feature for easier editing of HD files. Several editors, both pro and 'consumer' level, now have this.

     

    Also improvements to the chroma keyer would be nice, such as a matte setting with black and white level adjustments. Very hard to get a clean key without a matte setting.

     

    Anyway, just wondering what's in the future for Videopad. Thanks!

  8. I believe that the versions 3.xxx are designed so that the overlay tracks become labled only if you use them. This helps to keep the timeline uncluttered. If you keep in mind that that's where they are, you'll be fine. It's does show (as the grey line) when you open Videopad. I doubt it can be 'pre'-labled them, unless you are a software code wizard.

  9. Or you could make sure you are on line when you try to export your movie. If you need a codec you don't have, Videopad will automatically download it before it exports. Also Mewize is right. Any of those characters in any part of a filename will abort the export.

  10. I agree. I want to make it clear that my agenda is not simply to put down Videopad. It's a nice little editor with a lot of potential. But there's just something quirky about the written code of the software that is creating these problems. And really what it comes down to is the experience of the end user. The most beautiful peach in the world is worthless if it's sour. I plan to stay with it, but it certainly needs more work.

  11. We've been over that before and I doubt it's the problem. I use several pro-type editors as well on this same machine (Edius 7 and Premiere Pro 6.5) without these problems. I use Videopad for fast projects that don't need high precision, in which it's quite useful. I agree with you that 3.10 has been the best of the 3.xx's, and hope we can eventually get the latest version features with the reliability that 2.41 had.

  12. Reading all these fault posts on versions 3.xx gives one the feeling that perhaps these versions were a quick response to user complaints (particularly the 'I won't buy it this way' type), and perhaps they should have gone through longer beta testing before their release. It really started going downhill after 2.41!

     

    Perhaps NCH should collect all these complaints, and sit back to take whatever time is required to come up with a good, well working version before the next release. I'm willing to wait!

  13. I mentioned this before and got no rewponse. Sometimes I will put a clip on the timeline (it can be the very first clip, or several clips down the line) and it literally takes several minutes for the green line (clip render line) to start moving. Other times it renders quite quickly. This happens wether it's a very short project or a long one.

     

    I usually delete the cache(s) before I start new projects, so I doubt that's the case. From reading this forum, I find I'm not alone with these kinds of problems. Someone recently posted that these problems started after version 2.41, so what did they change in the software code that is causing this?

  14. Hi brko. Windows 7 64 bit comes with a built-in emulator called WOW64, which allows most 32 bit programs to run on 64 bit Windows. I have 64 bit windows and Videopad runs fine for me. So that is not your problem. However, I have found that if I mix different still image "frame" sizes, original image size or say a 4:3 and then a 16:9 and so on in any combination, I'll often get a crash! I do not know what causes this, but I get around it by using the Crop effect to make all my stills the same frame size as my video clips (for me usually 16:9). This usually eliminates the crashes, and looks better anyway during playback.

     

    After I load my pics in the bin, I place them one at a time in the preview window BEFORE adding them to the timeline, then click the Effects button and drop down to Crop and click that. A box will open with the image and a choice of 4:3 or 16:9, and you can drag the red box surrounding the image to re-size it. The new size will show in the preview screen. Once satisfied, you can click on the green down arrow and it will place the image on the timeline at the new size. You may loose a bit of larger images doing this, but playback of the finished video will be smoother.

     

    Anyway, it works for me.

×
×
  • Create New...