HunterEdits

Could be, I reverted to 13.0 because of this. I make hundreds of cuts on an audio track. I thought it had something to do with shift but perhaps it was some kind of track selection. But yes, I chose where I wanted a cut to go, *shift* and suddenly I'm looking at a completely different part of the timeline: the start of the clip and the place I was going to split is who knows where.

Would love to use the bug reporter but all I get from it is "err_connection_refused" and I just checked windows firewall and my router, nothing blocked. sigh I wish to split an audio track but not the video track because that imposes processing requirements and makes a mess. So I decide what part of the audio track to split at using the timeline marker. The way to split is L (inherited from movie maker lol). To split only the selected track, shift+L. The problem is when I press shift, the timeline marker jumps to the start of the audio segment for some stupid reason. But not 100% of the time. I don't really know what is going on, but I found in this version I frequently had to reselect the time I wanted to split it and reselect the track to split before I could do it. I guess someone added a "shift to jump to segment start" bind which conflicts with being able to split a selected track. Or something was changed to effectuate that.

So, the general way this is supposed to work is a project that meets the requirements for lossless processing will be processed and it will happen. So if more than 10% (or whatever it is) of the project has to be encoded then VideoPad says "forget that" and won't let you. But it's fine for a few little cuts, or subtitles. This project is 27 minutes, there are 0 video cuts, and it has two text clips; the first one is 2 seconds long, second one is 4 seconds long although that's not important. Basically I am just adding a sound track. If I delete the second text clip it renders. The four second subtitle. If I move the text clip 4 seconds left (earlier) it renders. It just won't render when I actually need the subtitle to appear. Settings make no difference (unless I want to encode the whole video and I don't). And that's really aggravating. I guess my video's expression will be silenced by VideoPad's odd requirements that I not say anything at that point in the video I wanted to mention something.

Haven't got any.

Why? Nothing is blocked. It happens on every browser, did not try it on a phone...

That form never works for me, which is why I posted this here. I get a "connection refused" error.

Hi. Videopad 13, I have a lot of audio to clean up and I am staring at waveforms. It is what it is; I can handle it when the track isn't selected. When the track is selected the background changes from black to a gray which is super hard to see detail on compared to when the track is NOT selected. I don't like these colors anyway, but it's just hard to read the bright green on gray. I was thinking you could even outline the track or something instead of lowering the contrast in it when it is selected. Tiny little bumps are like invisible against the gray. Thanks

It's the same. Opera says... "This site can’t be reached secure.nch.com.au refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED" Same with Firefox and whatever.

Neither is 15FPS. 60 sounds like a more reasonable default. But auto detect is probably best if it exists. That form is broken which is why I posted this. Same as the last topic.

The default setting for a new project to render in .AVI is 15FPS. It should be auto detect by default. I think I am going to forget this during editing and ruin a project.

Why? Because the form is broken! It won't work. Can't contact them. Report as follows.

Yeah, pretty much. Lossless encoding is great, but the second I touch something, (add something) that needs encoding, the colorspace goes to hell somewhere, I do not know where. Here are real examples from my latest video. I can't publish this. Green color on a menu gets turned into blue. A bright green bag, brown jacket, skin tone turns into a dull green bag, gold jacket, with yellowish skin. There is no red left in the image. Red seems to get leached out of scenes badly. Here is the group on one page, this should help you compare better. https://imgur.com/a/I9TBjb2 Does not matter which codec I use. I can select input colorspace in x264 and it still happens. Lossless rendering, MAYBE not, not sure, but I have no use for gigantic files much bigger than the source material anyway. Help!! Version 11.01. EDIT Ok looks like it's much improved in 11.08. Still washed out as usual but I can work with that. I don't know why I didn't update first...

So you're saying I cannot change the default codec.

I have a few small edits to make with a video, exported losslessly. The lossless segments are great because they aren't re-encoded. Source file is .5GB. Re-encoded segments use the default codec of H264 4-2-0. 4-2-0 subsampling treats all black as useless data which makes the picture very washed out compared to the lossless segments. Anyway, I could always select a third party lossless codec like Lagarith. But actually re-encoding the whole thing with Lagarith would make my video 30GB, that is useless to me. I just want VideoPad to use a codec like this for the small re-encoded segments done in lossless mode. Possible? Example of H264 interleaved with lossless copy https://www.youtube.com/watch?v=pqyAFHl_FN0&t=553s

Older versions don't include H265. Anyway, according to the product page at https://www.nchsoftware.com/videopad/index.html XP should be included. Thrawn wrote:

I didn't expect it, no. Is XP not a supported OS for VideoPad?

Just what it says on the tin. Doing so produces the following error: https://i.imgur.com/doumsWH.png Searches suggest this means a version of ffmpeg that won't work in XP is being triggered. These searches say if the newest XP compatible version of ffmpeg is used that this can be avoided, but due to the way VideoPad integrates codecs, there's no obvious way to drop in an ffmpeg file. Seemingly VideoPad includes two different versions of ffmpeg already; this may be a red herring. All I can tell you is it doesn't work. Reported though bug reports on 8.56 If you have any suggestions, please share them.

I see how it works, (although I don't see why you would want to duplicate your clip by copying a segment of it and extending it). What I wish would happen is that when you extend a clip, you lower its speed. Well obviously as borate implies, there's no more footage, hence extending it means slowing it down such that it fills the size you extended it to. Because I can slow a clip down to a speed percentage, but I can't (other than really tedious number checking) resize a slowed down clip to fit a gap. I don't mind still images but I have had issues with them in the past, particularly edited outside (in gimp) causing flickering or sound popping at the start or end of those segments. Also reduced quality. I mean, if ever there was a reason to avoid stills...

I want still frames (video extension for longer audio) or white noise (audio extension for longer video). I extend the clip length, but instead of getting a longer clip, videopad just starts duplicating the clip after where I already cut it off!

So, I've always had this major issue with VP. Let's say I need to insert some sound and I need to extend the video to match it. So, I find some point with still frames and I want to extend that ("play it slower") over the extra audio duration. That is not what happens. What happens is I split the video in still frames, for a clip consisting entirely of still frames. I extend it to the desired length. It REPLAYS video that would have been in that position before the audio pushed it out. Yeah. So it literally plays the video that was there before the audio was inserted, over the duration of the inserted audio, and video then REPEATS when the extended clip ends and the original video resumes. No idea why and it's super aggravating. I've looked for settings, some kind of secret knowledge so I know why this happens and how to make it not happen. No idea. Help!

I've been studying my project and it seems to me that other similar titles look better. The only difference in them is the text color. Could be optical illusion that they are better.

It is in his example. I was hoping for a setting or a procedure or something besides "it just works" because that gives me nothing to go on. Default renderer. I don't think graphics driver matters. I'm starting to doubt I'm reasonable, but what I can say is the preview is far more optimistic and I don't see why there should be any discrepancy at high quality levels, let alone the big differences I am experiencing. I don't believe it's relevant (or it shouldn't be, it's a text overlay) but the source data is 640x480 and I'm rendering it at 1024x768. Same result at 640x480 of course, I just hoped the text would be better and for unrelated reasons I need to upsize the format.

Nat: Ok, you can't see so well. I will try again. PREVIEW: RENDERED: One important point to make also is that the whole image is degraded, not just the text, although the most problematic part of the results are the text layer. Major: This was done in 5.2. Of course...here http://members.dslextreme.com/users/hwh/files/text title.zip I'm just about positive the same thing happens in 6.1.

Not sure how to interpret this silence. I guess it means "no one cares."

Probably related to all my other videopad quality issues, amiright? Text layers look great in preview and the editor. Rendered, they suddenly look a lot worse. I already tried setting the codec quantizer to 10 (just for testing) and it looks pretty much like this: PREVIEW RENDERED The bottom is an exact rendered frame of the top preview. Please note the bar on the E. Look at how jagged it is. Or the bottom curve of D, ooh, nasty. I already tried to fix this with effects. Sharpening of course accentuates it. I tried a blur of .04 which gave great results in the editor, that's what you see here in both pictures, but it really doesn't solve the problem as the bottom picture shows. Help!