Jump to content

Russ Croucher

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

255 profile views

Russ Croucher's Achievements


Expert (5/7)



  1. No I'm perfectly happy with MPEG-4. I just tried it to see what would happen. Now I have a short 12 minute video I can verify one way or another.
  2. Thanks for heads up. I am planning from now on to always stick with MPEG-4. I thought I would try it and see what the deal is. It seems like I have less issues with MPEG-4. I will check the media tab options thanks.
  3. I'm still having encoder problems with the latest versions of videopad. Maybe this is a different problem but I have isolated it down to a small file that I have uploaded that I'm going to share with everybody to understand the problem. I have verified this with 10.78 and 10.86. I'm still currently using 10.78 because 10.86 as a problem with the ctrl-A(select all) keystroke and is very slow loading large files.So I have stayed with all my procedures with 10.78. Since the image stabilization produces the exact same file. Here is the Raw 12 minute MP4 file: https://1drv.ms/u/s!AuSetTxgq7JxqN1gpKIv4cFD3ZAUzQ?e=Kbe9Al Here is the project used to load the file above: https://1drv.ms/u/s!AuSetTxgq7JxqN1gpKIv4cFD3ZAUzQ?e=219kR5 I started the image stabilization with "H264" in its largest file size. Here is the output: https://1drv.ms/u/s!AuSetTxgq7JxqN1gpKIv4cFD3ZAUzQ?e=IDu56Q This is the file with the audio error. The audio is delayed several seconds. Here is the exact same file that works in "mpeg4" mode. The only difference in the image stabilization is selecting this mode versus H264. https://1drv.ms/v/s!AuSetTxgq7JxqN1iR0yrms4ZF8HnXQ?e=kXfK0Z I also want to point out that this is only a Windows 10 problem and it does not pop up with Windows 7. This may be a codec issue. I just wanted to post here to get some input from you guys. I made a pointed reduce the file size down to just 12 minutes so is it easier problem to understand.
  4. Borate, That's a simple solution visually. But how do you send that to a computer without a mouse? I do need to read the length of the video file. I prefer to not write software to do that solution. My script software will give me the size of the file but not the video length of the video file. So maybe I need to make a request for possible improvement that you could enter the cursor as a percentage not as in time. What you think? Thanks for your quick response. I love videopad and prefer not to write my own software since you have a good product.
  5. I'm trying to split a large MP4 file into 2 smaller pieces in the middle. This sounds asked quite easy with the mouse with either videopad or prism. However, doing it with a script without a mouse is rather difficult. Is there any way to set the cursor in video to a percentage rather than in time? I know how to split a file into pieces from the mouse but I don't know how to make the mouse go exactly to 50% the file. Where can I go to get help on how you enter the time in the start time/end Time/cursor positions? Is there any way to entered as a percentage of total? Which is a better process to use Prism or Videopad? For a little history of what I'm trying to do, I have USB flash drives larger than 64 GB that are always formatted exFAT. However, some computers do not understand that format (chrome book). I can't use NTFS because that is only read only on a Mac computer. This is because the falling out between Windows and Apple years ago. So Windows does not allow Mac to write NTFS. However, using backdoors I can format all flash drives that I want to FAT32 format. However, this has its own problems that you cannot have a file larger than 4 GB. So my solution is to split all videos to be less than 4 GB. That way I can have large USB flash drives and large files in two pieces. I'm having trouble reading the length of a video file. This is not the size of the file bytes. Maybe you guys can give me some insight.
  6. Here is the solution to the problem. It seems it must be some type of video discrepancy between pinnacle 23 and videopad. I chose to use MP4's as an output to pinnacle 23 because videopad says it only see 640x480 because of the aspect ratio except for version 7.51. I couldn't use any type of lossless output because I was converting AVI's to MP4 so the solution is to run the AVI directly over to the computer that's going to be doing the image stabilization and even though video pad sees it is 640x480 it image stabilizes it in 720x480. I know this because I steal the image stabilized file in the temporary directory of video pad. And the properties of the image stabilize file says it 720x480. I've done this on my fastest workstation which has all the temporary storage done on a M2 SSD give me 3.5 GB/s transfer. So that one hour file AVI took 1:10 on that single core workstation. So the solution is solved thanks guys.
  7. Yes I know the the source file is a customer's private file. I wasn't really expecting you to import my file I would figure you could use something that's an AVI file and compare the difference. I'm looking at the difference in the speeds between 7.51 and 8.0 and beyond. It's a good 4 times difference. It's a very big file. A full one hour of this file took video pad 30 minutes with 7.51 and 3 hours with 10.52 with the same project file. I'm just try to get some ideas from you guys with what I should do.
  8. In putting this FireWire issue with videopad to bed, it was determined that an AVI file stored in 720x480 that now comes in videopad as 640x480 will be stored with all its resolution at the 720x540 and keeping the aspect ratio correct. So in converting the AVI file with the latest version of 10.52 I converted to an MP4 at 720x540. I thought the version 7.51 went away forever. However, I was wrong! Now the problem is 7.51 is 6X faster then 10.52. I don't know if it's because the least compression is faster or what. I'm in the process of trying to figure that out. Normally converting a one hour AVI file will take about 30 minutes on my PC(While I'm retrieving the next file with Pinnacle 23). But the same file in 10.52 took 3 hours. So being the software engineer I am I decided to try to figure out which version slowed down. So I created a one minute project and put the results in 7.51 and all the versions afterwards to determine where the problem seems to slow down. In my 1 minute example it is only a 3X difference so I must've not of chosen the worst 60 minutes. But the results are still the same. Here is my cloud link to the 1 minute project. https://1drv.ms/u/s!AuSetTxgq7JxqNtLprij_LAxTsuuSA?e=j0oqSi Here is the output in MP4 file which is 3 or 4 times larger than the following versions. However, it's much faster https://1drv.ms/u/s!AuSetTxgq7JxqNtLprij_LAxTsuuSA?e=j0oqSi Here is the output in MP4 of the following version I have which is where it seems to slow down and the file is much smaller in version 8.0. https://1drv.ms/v/s!AuSetTxgq7JxqNtNlGvgQmg5qiXwNg?e=B6o2Vl So the problem seemed to arise with the following version that I stored on my computer which was 8.0. Maybe you guys can shed some light as what I can do by not using 7.51 because so much faster. Remember my only goal here is to get the file converted into something that video pad can use to pass on to the image stabilizer. Maybe I shouldn't even have to transfer to MP4, maybe just use the original AVI should be good enough what you think? I have always avoided that issue because the 640x480 resolution -0-0- I just verified with 10.52 with the encoder output level at 25,000 kbps still takes full 2 minutes. Where 7.51 only took 30 seconds. So clearly it's not the encoder level. So looks like I'm still stuck the 7.51.
  9. The reason I do not want to choose any other output export from H264 MPEG is because then I could not use the "lossless" mode. All operations with a video pan use lossless. This would mainly be to split a file in the 2 pieces writing an A and B version. If I would take the exact same MP4 file and then run it through handbrake it would work. So please explain to me why I must run a lossless export through handbrake to work. There must be something in the header that makes it not desirable for Mac computers. All outputs from videopad are always output in the full resolution with the max size. Then they are sent to handbrake and used to set the encoder rate to the level that makes sense for the input that was originally used. I would expect any output after that like splitting the file into 2 pieces would be lossless and not affect the encoder scheme. Explain to me if this is not true. It should work with Mac computers unless there is something in the header that makes it not work.
  10. I only export MP4's which Mac computers read. The links appear to be the same but they're not. 1 of them was exported with videopad and the other one was exported with the open-source handbrake which is the one that works on the Mac. I did try the MP4's with a new iPad with no problem. I submitted a bug request but got nowhere. Only the videos that are modified by videopad cause a problem with Mac computers. I know MOV's would fix the problem on the Mac but I'm not going to export the videos twice. Especially since the workaround is to make sure everything runs through handbrake after videopad.
  11. I have a business of transferring older videotapes to the modern world to MP4 and flash drives. I have submitted this bug which was 10.52 already but I thought I would throw it out here and see if anybody else's had a similar problem. For customer privacy reasons I have shortened my example to 1 minute in length. My procedure is: transfer all analog into videopad using Debut in the largest format. Then import all the files into videopad to image stabilize them. Then once all the stabilization is complete I steal the image stabilize files from the temporary directory that videopad uses. Then I passed the entire collection of image stabilize files to it open source handbrake to downsize it to the appropriate size necessary so no loss occurs in the process. That process works great with the exception that all my flash drives are forced to be "FAT32". All flash drives 64GB and larger are formatted "exFAT". Some computers do not accept this format. I found out a way I can force all flash drives to be formatted FAT32. The problem with that is it does not support files greater than 4 GB. So I use videopad and split the file into 2 pieces after the end of the entire process. I make an A and B version. Now for the problem, all these files cannot be read on some Mac computers because they were finally process in the end by videopad and not handbrake. My customer that has a mac says the video quits about 8 to 10 seconds. Here is the 1 minute video segment from the latest version of video. https://1drv.ms/u/s!AuSetTxgq7JxqNsn-R79gKQWISN7DQ?e=sfGGrh Here is the same 1 minute segment process with handbrake https://1drv.ms/u/s!AuSetTxgq7JxqNsn-R79gKQWISN7DQ?e=DeP9gn Maybe you guys can give me some enlightenment on this problem. ,
  12. Okay I'll start the transfer to my cloud since it is 13GB.
  13. I have a customer privacy issue with the original full AVI file. This also is not necessary since I'm trying to understand a little bit about the internals of how videopad operates. If I were to reduce the AVI file I would have to use videopad and to chop it. What version would I use? Then it's not the original version. I guess I could provided in PM of some sort if really necessary.
  14. Okay I have a project file I'm using here it is: https://1drv.ms/u/s!AuSetTxgq7JxqNsdqdg1U2lOKMgSig?e=EZUOQp It reads an AVI file into the system so it can be exported. The project was created with 10.52 but seems to work with 7.51. The AVI file read in the property say 640x480 in 7.51 but 720x480 in 10.52. I was told this file since it is ace 720x480 file an AVI would be read in at that same resolution regardless of what the property say. However, my question is what is given to the image stabilizer? Here is the output in 7.51 mode one minute of the export. https://1drv.ms/v/s!AuSetTxgq7JxqNsfTG19tYclWga2MQ?e=oVczFK For some reason 7.51 is three times larger than the new version which 10.52 is three times smaller. https://1drv.ms/v/s!AuSetTxgq7JxqNseUBz6x9MwLKO0qQ?e=7ItL6A Thoughts? Help?
  15. My issue is with all later versions of videopad they seem to come up with the properties in the bin directory of 640x480. So is that what is sent to the image stabilizer or can't send 720x480 even though the property say it's 640x480? 7.51 is the only version I have in recent history that comes up with properties of 720 x480 because of an aspect ratio bug. I must store the file as a mp4(720x480 or 540) version before he gets reloaded into videopad to do the image stabilization on different computer. I don't care too much about the aspect ratio before the image stabilization. I only care about it afterwards. I am trying to determine if I can use a later version to read a this pinnacle file 23 AVI, do image stabilization in videopad with at least 720x480, write it out as MP4, and then send to handbrake for final processing at the appropriate encoder level. As you can see I have a very detailed order of which things must occur. Are you saying if I read in AVI of 720x480 which it says is 640x480 and I specifically say store it out as 720x540 it will write it out correctly without any loss?
  • Create New...