Jump to content

Russ Croucher

Members
  • Posts

    237
  • Joined

  • Last visited

Everything posted by Russ Croucher

  1. Is there any way with VP to do H265 encoding? I do that when I go to phones and tablets. I know I choose my machines based on what it's going to use for. If I'm going to use it for VP primarily I choose less cores and brute speed. If I'm doing something like handbrake I choose dual processors of 8 cores to give me 16 cores total at maybe 75% CPU speed. With that many cores I can get handbrake to do about 200 fps at my rated encoding output level.
  2. I will investigate your support link that's a good idea. I do find I seem to get better response by creating a thread. I never know if a bug report ever gets installed. I wish I could move everything to Windows 10 but I have my analog imaging cards are stuck it Windows 7 which is not a problem because most analog stuff was done 20 years ago when we were not even in XP. We were doing Windows 2000. Clearly you can see from my procedure above that I am not married to any one particular product. I use the best solution to solve a problem in reasonable timeframe. I chose handbrake because it works so well with many processors and cores. I like the way VP handles most other operations. I never did get FireWire to work with VP. I really don't care because I have a good solution that works with pinnacle. I try to stay with Windows 7 for my work machines to keep from getting updates anyway. So all my Windows 7 machines have updates turned off. I wish I could do that with Windows 10 but I can't. I regularly do image backups on everything so I can go back to a year ago if I need to. I wish VP and image stabilization used more cores.
  3. Clearly you jumped on my procedure on how I do things using handbrake and not concentrated on the bug I'm try to report. I have chosen to use handbrake because of the choice of using all 16 cores when using multiple CPUs. I tried your above concept only got 45% CPU usage under videopad but 95% under handbrake. I mainly chose handbrake because I never found a very good way to do de-interlacing on the videos that need de-interlacing. MiniDV and HDV do not need de-interlacing and makes the quality worse if you try to turn it on. Also handbrake is very nice because you can drag entire folder and it will convert it at the encoder level you desire. Videopad has "small", "medium", "default", and "extra-large" and custom. I don't want to deal with custom. I know the encoder level I need to be better than the recorded system that's what I use. So I really wanted this thread to concentrate on the Windows 7 bug and does videopad no longer support Windows 7 or should be abandoned in its support list. It sounds like you tell me you will no longer support Windows 7 just because Microsoft has abandoned updates. This is something that us people that use the product actually like better because it is more stable. We don't want the latest greatest wonderful thing we want something that works every time use it.
  4. Actually Microsoft stop supporting W7 in January 2020. But your product info says it supports Windows XP all the way through Windows 11. I actually prefer Windows 7 over Windows 10 because you can turn off the updates which you cannot do with Windows 10. Windows 10 also no longer allows you to format FAT 32 on USB drives greater than 32 GB. So all my flash drives that are larger must be formatted under Windows 7. They did this to push their NTFS file system which Mac computers do not support fully. All the USB flash drive companies have a format called exFAT which chrome books do not support. So all flash drives that leave this place must be formatted FAT 32 to be compatible with all computers. But they have their own limitations like 4 GB file size. Since you cannot turn off updates with Windows 10, I have many copies of all my images as backups and if I go back too far as a lot of updates have to update on Windows 10. And I consider my windows 7 machines as work horses they are made to do a job that's it. Internet browsing and job maintenance is done with Windows 10 What's going on in the software is the code is asking the operating system what the format of the video is in under Windows 7 is reporting wrong when it looks at the header and gives the wrong answer. Windows 10 seems to have fix this problem. There are several utilities that report the video itself independent of the operating system. The reason I use handbrake instead of videopad is because handbrake uses all 16 cores of my dual processor system. Videopad does not. I use videopad for many things but not for the final step which handbrake is much faster because it uses all the cores. Remember it's all about speed. I'm actually tickled that when I started this business several years ago image stabilization was taking 200% of the actual time because of the speed of my fastest processor now with my SSD's given me 3.5 GB/s I have got that down to 85% of real-time. But then again that's handed off to handbrake for the final step. I was just trying to report the bug I do know I will be doing all my final FireWire processing with Windows 10 because of this bug. I will use Windows 7 more for the analog processing.
  5. For several years I have been complaining that the image stabilization in videopad must have all the resolution of the inputs so that no loss of information will occur. Example, if you have a video of 720x480 with a bad aspect ratio you must have more bits going to the image stabilizer than the video produces. The aspect ratio on 720x480 would be better at 720x540 without loss of detail. 640x480 produces the same aspect ratio but has a loss of 80 bits from 720 down to 640. I now have proof that the problem that occurs in videopad in Windows 7 different from Windows 10. Even though the header clearly describes the video to be 720x480 Windows 10 must have fixed a problem that Windows 7 had reported the wrong information to the user of the file. So under Windows 7 videopad produces a problem that is not apparent under Windows 10. However, videopad can do several things to alleviate this problem even though the problem is in Windows 7. My procedure is to use Pinnacle 23 to use their FireWire to download videos to an AVI file under Windows 7 or 10. Then videopad is loaded to image stabilize the file with the latest version 10.96. Then the final procedure is just to use the temporary files from the image stabilization to run them through handbrake to produce the final MP4. Here is a complete cloud directory of two raw FireWire AVI files and the image stabilize files in both Windows 7 and Windows 10. It shows that under Windows 10 everything is fine. But under Windows 7 several of the files were only image stabilized at 640x480(loss of 80 bits from 720 down the 640). One file was stabilized at 854x480. https://1drv.ms/u/s!AuSetTxgq7JxqOFT5VfvcJbTP23xzw?e=7rUKaM One interesting problem which I do not understand because all the settings under Windows 7 and Windows 10 are the same but the Windows 10 files are much larger than Windows 7. I chose the "larger file sizes" under both, "progressive" under both, and "HDV" for image stabilization under both. Maybe someone can help explain why Windows 10 uses larger files even though this is using the same version of videopad which is 10.96.
  6. I want to update my Pixillon version 8.19 to the latest version but it's longer than 6 months so I would have to get a license and I'll be more than happy to buy several license if the following problem has been fixed. I having trouble converting 16 bit TIF files (48 RGB bits) to a horizontal flip. The result works but only at the 8-bit level producing a 24-bit RGB result. If it now handle 16 bits I would be more than happy to buy several licenses for my business. Right now I have to do the conversion with Photoshop. Here is an example folder of my problem. I have a source TIF file of 92 MB that I run through the program to do a horizontal flip and the result is a 20 MB file only of 8 bits in depth (24 bits total). If somebody could tell me this problem has been fixed on the new version I will do an upgrade. https://1drv.ms/u/s!AuSetTxgq7JxqOEME-5nW7K2G8jEsg?e=HddMUB
  7. I guess I need to learn how sequences work. I created scripts before we had sequences years ago. Where do I learn about these? I created a procedure several years ago before you had sequences that would take one MP4 file to import into video pad "I .mp4" do whatever operations the project specified and write the file out to a new name (name of the VPJ) in a different directory. It would then cycle through the next file and VPJ do all this automated. That way I could setup a computer just to be doing that without an operator involved. So that turned out to be my solution to the problem. I manually do the 1st operation on how to do the export which would be to stretch the output and save the project file. Then I can execute this automated batch file. The only issue is they must be a numerical order. This is the way I wrote the script file. If they are out of order it just stops. So in the end this project is actually empty it does nothing it's all in the exporting with it stretched. I use this project concept a lot for changing the clip's speed or adding some user video effects. Something that the batch files don't allow you to do.
  8. This is a perfect case of how to use the to extend the aspect ratio. All my MP4 files are in 1440x1080 and need to be 1920x1080. How I do that in a batch mode? I don't know what filter the select for the aspect ratio.
  9. Thanks for the good tip. I will do the image stabilization with that file and use the transform to change the aspect ratio. I don't care how long it takes in the end cents all automated anyway. I just don't want the extra step of their which it sounds like you got a fix for me. I'll let you know how that goes.
  10. Yes I know that would work because you forced a reencoding of the file. You cannot specify lossless if you want to stretch the file. I ready know that works. I'm talking about a lossless file that flickers with some versions This must be done after the image stabilization. So it is done with the wrong aspect ratio 1440x1080 (smaller file size) image stabilize and then stretched. What you're asking me to do is re-encode all the files 1st and then image stabilize it and that will take too long. Remember I have hundred the files. HDV native file is 1440x1080. And since I cannot get FireWire to work with video pad I use pinnacle 23. I then image stabilize the file and then stretch it to produce the correct aspect ratio of 1920x1080.
  11. You have the original file but it's not 5 minutes it was only 1 minute I'm sorry. I not gonna post the one hour and 20 minute video because the problem is obviously clearly there in the 1 minute section of it. I know if I posted a 1 minute video of the reencoding it would work I want to know what's going on with this lossless version with pinnacle 23. The file is called "1minSource.mp4".
  12. Let me clarify what I did which will explain it in more detail. I imported the entire video (one hour and 20 minutes) using pennacle 23 with FireWire. I I then use the lossless version of 10.96 video pad to extract the 1st 5 minutes. I then use different versions of video pad to extract 1 minute sections of those 1st 5 minutes and stretch them and see which ones work and which ones did not. I found that version 10.06 works okay the rest do not. So I'm assuming that there some type of anomaly with pennacle 23 and video pad that is causing some issues with the lossless mode. I do realize if I were to probably take those 5 minutes from lossless mode and re-export them and re-encode them using video pad would probably work fine. So I'm saying that something in the lossless mode is causing it issue in the later releases of the code. As long as I have one version which is 10.06 that fixes the problem I will probably use that to do all the stretching for the next few releases. There was several releases after that that I don't know if worked or not because it did not load my project file correctly. But I do know that 10.43 does not work. Do you think I should submit this is a bug report or you think this thread will be enough to give the developers an idea of what's going on. I have tried it on both Windows 7 and Windows 10 with the same problem. I don't have a Mac in-house.
  13. That's why I specifically included the entire folder that includes a lossless 5 minute MP4 file created in the latest version of videopad in 1440x1080 and the project that shows the Flickr with the different versions recorded in 1 minute sections of each version. Only 10.06 work without flickering. I have not yet submitted this is a bug report because I wanted to see if anybody else had problems. These files were originally imported with pinnacle 23 because I have not been able to get videopad to work with FireWire. Then my example file has been lossless output cut down to 5 minutes with videopad. You can use my examples above and you can see the Flickr in the files depending on the version.
  14. I have many HDV videos that are recorded at 1440x1080. However, the aspect ratio is wrong. It needs to be 1920x1080 to be correct. So after the image stabilization I use the stretch mode of the export to force 1920x1080. In the last several versions of videopad it causes a flicker on the display every couple of seconds. I have a workaround that going back to version 10.06 works okay. I have collected a folder with several different versions that I have tested with this problem. I cannot remember the beta directory name but I can try it also. I have created this link to see if anyone else's experience any type of problems with this anomaly. Here is the link to my folder that has a 5 minute video with several different versions. https://1drv.ms/u/s!AuSetTxgq7JxqMYTTk4DnG9fqasxcA?e=eZFa8d
  15. 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.
  16. 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.
  17. 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.
  18. 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.
  19. 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.
  20. 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.
  21. 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.
  22. 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.
  23. 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.
  24. 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.
  25. 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. ,
×
×
  • Create New...