Russ Croucher

I have 5 master cut versions of videopad for my business and have discovered an error in the image stabilization process on Windows 10 versus Windows 7 of the latest version. VLC works great with Windows 10 however the image stabilization under Windows 10 comes up with many false hours instead of the actual 2 hours or whatever it is with Windows 7. Apparently the image stabilization must be looking at the header wrong or something but only under Windows 10. I have taken the exact same project and run it under Windows 7 and Windows 10 and a problem only shows up with Windows 10. Since I use handbrake as my last step (to change the encoder level) I can actually run videopad with Windows 10 and run it through handbrake and that corrects the problem. However, the intermediate step from the video is very very large because of the wrong length of the file. The length of the file should be approximately 2 GB per hour and since it has the wrong length it might be 2 GB per hour but it will be a huge file because it thinks is 10 hours long. When you actually use the film and TV viewer that came with Windows 10 it cannot display anything after the file because is not there and just locks up. So the workaround right now is to make sure handbrake is the last step and all the image stabilization is done with Windows 7. Has anyone else seen this type of problem? Since I have a good workaround I would just check periodically when it is fixed.

"Chris75" so you have tried a 16-bit TIF file which would produce about 100 MB file and do anything to it rotate it or reverse it and it would output a file of approximate the same size? When I do that exact same feature it takes my 100 megabytes file and crunches it down to a 20 MB file of only total 24 bits 8 bits per color but TIF format. The 256 bit option is not checked.

I'm frustrated because the 100 MB file I mentioned above has 48 bits of color 16 each for RGB. Once I mirror the TIF file, it is 1/5 the size and the color depth is only 24 bits which would be 8 bits for each RGB. I did see the 256 option and did not check it because I read about it and that would just defeat everything.

I have all 100 MB 16-bit TIF file that I want to reverse mirror and produce a 16-bit output TIF file and it seems like it only downsize it to 8 bits and converted to a 23 MB 8-bit TIF file. The filter and the structure of the folder works great but it seemed like it only outputs an 8 bit TIF file not as 16-bit TIF file. Is this true?

"borate" can you get someone in your support people to respond to my question in "pixillion" thread about a question about 16-bit TIF files. I can't get an answer if it can convert 16-bit TIF files are not working because all my outputs are a 8-bit TIF and nobody seems to be responding. -0-0- I'm sticking to 8.97 for now

I have tried the beta version 10.17 by dropping the entire DVD which includes 5 VOB files in the video. For some reason doing two of the files have no audio. So I started backing up on the versions until 8.97 works fine. So until this problem is solved. I will stick with 8.97. As a software guy I know that we fix things and break other things not realize it.

I am using video and 10.16 to read a DVD movie disc. It contains five .VOB files. Two of the 5 files have no audio. So I decided figure out what version caused the problem. The last version that works perfectly is 8.97. So I have decided to switch back to that version until this problem can be fixed. Has anyone else seen this problem?

I have not heard from anybody I'm trying to filter 16-bit TIF files is that possible? It seems that it downsize that the 8 bits which is not acceptable is this a limit?

I am using "Pixillion" version 8.09 to convert a 16-bit TIF file of 48 bits per pixel to reverse the image. The scanner requires the emulsion side of the image to be reversed to produce Optima and results. In using this program as the last step 2 reverse all pictures in a folder it downsizings the that TIF files to 8 bits. This is fine with JPEG but not 16 bit TIF files. Is there a solution?

Microsoft abandoned the flexibility of the CMD command processor about 20 years ago with the advent of 4nt. However, another company took over the concept that made the product much better. It has gone through several buyouts and now is handled by: https://jpsoft.com/ with TCC.exe. Some people may remember it as 4NT or 4DOS from years ago. They sell a registered version for development ($100) and have it as an installed free run time use for all the other computers. Well worth the trouble if you're software engineer. Here is a batch line that starts a VideoPad project in a different thread, waits 5 seconds (90/18), and then brings up the export window and writes the file. start NAME.VPJ & keystack /w90 ctrl-b enter The next line waits for video pad to become idle for one second before continuing. gosub :waitVideopad The next line terminates VideoPad since the file was written. keystack /W9 alt-F4 /w9 tab enter Here is the meat of of the code to wait for VideoPad to become idle. This is important because VideoPad flushes the keyboard buffer when it becomes idle. So all keyboard stuffing must be done after VideoPad has becomes idle. This routine makes sure that VideoPad will be idle before returning and makes it the active process for keyboard stuffing. :waitVideopad set pidnum=%@pid[videopad*]% set firstt=%@processtime[%pidnum%,3]% delay 1 set newt=%@processtime[%pidnum%,3]% if %newt% gt %firstt% goto :waitVideopad activate "videoPad*" return

SUCCESS! Apparently that was the problem being out of the country. I tried it again today the exact same card and it worked fine. I hope this thread helps other people that they wish to purchase the same thing and realize that that's out of the country could be a little bit more complicated

I'll try again that's a good point being out of the country. I usually use PayPal but that particular post as I have a PayPal button. My preference is to use PayPal. I will try again and then call the bank if it is declined. Thanks for your help.

How do I get the platinum support to work when I can get any my cards to work and I know they're all good good? And there's no PayPal but like it says there is. HELP! HELP!

I will say I just tried to purchase the platinum support with both the visa and a MasterCard and the cards were denied. I know the cards and for good. Also the site says you can try with PayPal but PayPal but is not there. Maybe you have someone check this out

ok, thanks

Okay since I have an outstanding question for can I go ahead and get the platinum support and that particular issue would be handled faster? What I really want in the end would be a version that truly waits for the export to complete before it exits rather than just abort the exit. I have to go through gyrations just to see if that file was completely written to completion before I kill VideoPad.

I just want to point out that I just tried in the last few days the new version 8.84 and it goes back to using the default filename from the project name . Thank you NCH. So I went ahead and renewed my licenses to the monthly subscription. Where can I find more information about the "platinum support"? Like how much it costs and what it provides etc. etc.

I just started from scratch and the problem went away so it must've been a fluke in my install. Everything seems be working fine now.

Okay officially I have rerun the program without the Matrox card in the computer and it just crashed with the Visual Studio error. I don't know how to include a PNG file but I have a copy of the error. I also have the 4 files I was trying to image stabilized that it crashed with all versions including 8.84. I know how to submit a bug with an upload but I don't know how to submit a bug with 4 uploads. Maybe you guys can help me -0-0- I just wanted to say with the other computer workstation having the same hardware I just image stabilized 36 files in one project taking 31 hours of video which took nearly 2 days to complete. I had absolutely no problem with that computer executing VideoPad. So I would like to figure out what is different about this machine.

I believe I figured out the problem. There is one additional difference between the 2 computers which I'm now testing but will take 4 more hours. The computer that's been failing after 4 image stabilization's has a card in it that I'm not using right now but may be causing some problems to VideoPad. It is an "Matrox VIO" analog capture card. It is a professional image capture card using analog which is what I use for all analog conversions. It has a VGA port on it that I am not using. They use these cards to do analog image capture up to 1280x1080 analog. These are use in medical imaging. Matrox no longer sells these analog cards since they have transition to all digital. However, I use these for my analog conversions. You can actually write code that will will do MP4 on the card. So it makes the little dongle that NCH sells with debut look like child's play (I have one). So now I am currently testing VideoPad with those exact same 4 files image stabilization without that Matrox card. If it works to completion that will show that there must be some type of problem using this image stabilization with a Matrox card installed. I will respond to this thread when the test completes.

I don't think you guys understand my problem. It's not a stabilization problem it's a computer problem possibly a memory leak. I have 4 files that I want to stabilize, I load the 4 files into one computer and save the project on that computer. I start the stabilization on all 4 files and on the 4th file the VideoPad crashes. In the temporary directory of VideoPad are 3 completed image stabilize files. Since it crashed on the 4th stabilization I do not have that file. I then take the exact same project with the exact same files to a different computer with the exact same hardware and it works fine. All 4 files are stabilized and put in the temporary directory. So I'm trying to figure out what is different about this computer. They were all running v8.55. I have also have also tried with the latest version of v8.84. If you look at my first post you'll see the the credentials of this workstation. My next solution will be to create an image file with the "Aronos" of the C Drive of that workstation and load the new workstation with that image. And see what that does. Now I would like to get the debug version and run the same thing on this computer to see if that will give you any information about the problem. It appears to be some type of memory leak or something like that.

You guys think I should download the beta version and it would give me debug information that would help you guys figure out what the problem is? I know this particular computer crashes sometimes based on the plug-in image stabilization and sometimes based on the Visual Studio error. If at the plug-in crash program does not crash it just says your plug-in did. When I get the Visual Studio crash it actually says do you want to send a bug report but I have no problem download the debug version and giving you the log file again may we can figure something out.

These are using the same software with the exception of new licenses with your software. All drivers are up-to-date. I will be more than happy to use the debug version to help figure out what the problem is. I have not tried version 8.84 on the unit that works all the time. However it worked fine with 8.55. That particular unit has crashed with the plug-in error after 3 times. However, this particular version with the project file bombs on the 4th time to a Visual Studio error. Then when I rerun VideoPad it said did it crash? It seems like the Visual Studio crash the software treated differently than if a plug-in crashes.

I thought this was a number of processor processes with image stabilization but now I realize it is not. I'm having a problem on one of my fast computers with the image stabilization process of VideoPad version 8.84 crashing after about 4 video files. I have exactly 2 computer workstations with the same configuration here it is: They both have a PCI based SSD that produce about 1.3 GB/s transfer rate, 32 GB of RAM, 3.5 GHz XEON, and 512 GB C Drive SSD SATA.. The only exception is one of them has 1 TB SSD and the other one is only 512 GB. I am migrating to the 1 TB PCI SSD size. So I have configured VideoPad put all its temporary files on this fast SSD. I also have it store the temporary image stabilization files on the same SSD. So this new workstation receives all the customers files and I load up VideoPad and start the image stabilize on the all the files as a group (ctrl-A). From prior testing I know this will take one hour per video hour to stabilize all files. Then once the image stabilization is completed, I steal all the image stabilize files in the temporary directory. However, now for my problem. My 2nd new workstation which receives these files from the same customer crashes after about 4 image stabilizations. I know this because I have 3 completed image stabilization temporary files. So somewhere in the 4th stabilization it crashes. So I'm able to take 3 the the files and consider those completed. I restart the image stabilization on that computer minus the 3 that I started and it works again and crashes after 4 files. It has done this many times. So I'm trying to figure out what is different between these 2 machines. I originally thought it was a number of processes because I did determine that hyperthreading was turned on on the 2nd computer I turned it off and the problem still occurs. So I have a project that has exactly 4 files 640x480 that I want to image stabilize and it crashes on the last file (visuals studio crash). Sometimes it has crashed with plug-in crashing. But this particular project crashes with the Visual Studio issue. So I took this exact same project (with the 4 data MP4 files) and put them on the first workstation and it works to completion without crashing v8.55. Both computers were using VideoPad version 8.55. I updated the one that's been crashing with the latest version to 8.84 and still crashes on the 4th image stabilization. I'd like to download a debug version so she can find out what the problem is can you help me? It sounds like a memory issue but I don't know. Every time I restarted it seems to work a little farther after I kill the temporary directory.

I thought this was a number of processor processes with image stabilization but now I realize it is not. I'm having a problem on one of my fast computers with the image stabilization process of VideoPad crashing after about 4 video files. I have exactly 2 computer workstations with the same configuration here it is: They both have a PCI based SSD that produce about 1.3 GB/s transfer rate, 32 GB of RAM, 3.5 GHz XEON, and 512 GB C Drive SSD SATA.. The only exception is one of them has 1 TB SSD and the other one is only 512 GB. I am migrating to the 1 TB PCI SSD size. So I have configured VideoPad put all its temporary files on this fast SSD. I also have it store the temporary image stabilization files on the same SSD. So this new workstation receives all the customers files and I load up VideoPad and start the image stabilize on the all the files as a group (ctrl-A). From prior testing I know this will take one hour per video hour to stabilize all files. Then once the image stabilization is completed, I steal all the image stabilize files in the temporary directory. However, now for my problem. My 2nd new workstation which receives these files from the same customer crashes after about 4 image stabilizations. I know this because I have 3 completed image stabilization temporary files. So somewhere in the 4th stabilization it crashes. So I'm able to take 3 the the files and consider those completed. I restart the image stabilization on that computer minus the 3 that I started and it works again and crashes after 4 files. It has done this many times. So I'm trying to figure out what is different between these 2 machines. I originally thought it was a number of processes because I did determine that hyperthreading was turned on on the 2nd computer I turned it off and the problem still occurs. So I have a project that has exactly 4 files 640x480 that I want to image stabilize and it crashes on the last file (visuals studio crash). Sometimes it has crashed with plug-in crashing. But this particular project crashes with the Visual Studio issue. So I took this exact same project (with the 4 data MP4 files) and put them on the first workstation and it works to completion without crashing. Both computers are using VideoPad version 8.55 because that was the last version that use filenames as the project name. It sounds like a memory issue but I don't know. Every time I restarted it seems to work a little farther