Russ Croucher Posted May 13 Share Posted May 13 I'm not sure if this is a bug or just a change in the code. Version 13.81 was the last version that allowed me to click on a MP4 file and use the option "open with" videopad. It would take the MP4 file and put it in the bin directory allowing me to then choose other selections. Now it treats the MP4 like it's stabilizing the video which is one of the options in the menu. This file does not need to be stabilized. All versions since 13.81 seem to do this. I just downloaded a new version today v16.15 and is still present. Is this a bug or is this the way is normal operation now. I could change all my scripts to handle this if it is permanent. Link to comment Share on other sites More sharing options...
borate Posted May 13 Share Posted May 13 From the command line, this code works on this PC. using version 16.15 (64). "C:\Program Files (x86)/NCH Software/VideoPad/videopad.exe" "C:/Users/<PC name>/Videos/static.mp4" Or, from Windows Explorer (file manager), right-click an mp4 and then Add To Videopad Project or Open With Videopad. No stabilization offered either way. Link to comment Share on other sites More sharing options...
Russ Croucher Posted May 14 Author Share Posted May 14 Thanks for clarifying that I didn't think it was a bug it looked more like a characteristic. So instead of l listing the MP4 file on the command line I will open it up and then use control M, add the file inside of videopad. So now apparently all MP4 files on the command line are treated that needed to stabilize. I don't know if you remember but I have a procedure script that uses both PhotoStage and videopad in combination that can handle up to 100,000 slides in one procedure that calls PhotoStage with 200 slides each. Then it glues everything together with videopad. Link to comment Share on other sites More sharing options...
borate Posted May 14 Share Posted May 14 The command line above simply opened the file in VP - no need for stabilization. Link to comment Share on other sites More sharing options...
Russ Croucher Posted May 14 Author Share Posted May 14 I just tried it with my MP4 videopad.exe small.mp4 And it brought up the stabilization dialogue. But I know that will go away once I load videopad alone and then just say control M and bring the file in that way. Link to comment Share on other sites More sharing options...
borate Posted May 14 Share Posted May 14 Doesn't happen here. Check your Windows file associations... Untitled.mp4 Link to comment Share on other sites More sharing options...
Russ Croucher Posted May 25 Author Share Posted May 25 You must be running Windows 11. I have verified all my systems Windows 7 and Windows 10 and on the MP4 files I say open with videopad and always comes up with the image stabilization. I thought this was a commandline issue but it's not I just say open with on the old versions it worked fine but now it always comes up with image stabilization on Windows 7 and Windows 10. Most of my systems are not compatible with Windows 11 and I don't want to go there anyway. I have several Windows 7 machines that Microsoft in their wisdom thought they were fixing things when they went the Windows 10 but made things impossible. Example, you cannot format any type of media greater than 32 MB as FAT32. That is they are trying to push NTFS when certain machines like a chrome book does not support efat. I can still use third-party routines on wpm7 to format media up to any size I want FAT32. Microsoft has figured out how to get away from that and Windows 10 and 11. Also you cannot turn off updates on Windows 10 and 11 easily. Link to comment Share on other sites More sharing options...
borate Posted May 25 Share Posted May 25 Using 64-bit version 16.18 on the Windows 10 Pro laptop, the command line loaded an .avi. No stabilization. So still unable to replicate your results. Link to comment Share on other sites More sharing options...
Russ Croucher Posted May 26 Author Share Posted May 26 Success!!!!!!! I just tried it with version 16.15 same problem with Windows Explorer right clicking open with "videopad". I then check for an update v16.19 and tried the same problem again and it's gone!!! So there must've been some type of problem. I will now try mice scripts to make sure they all work with 16.19. Link to comment Share on other sites More sharing options...
Russ Croucher Posted June 3 Author Share Posted June 3 Bad news for Windows 7. Apparently the program does a version check for not Windows 10. Rather than greater or equal to Windows 10. All Windows 10 versions seem to work but my older Windows 7 which I keep around because I don't want Windows 10 on that machine. Link to comment Share on other sites More sharing options...
borate Posted June 3 Share Posted June 3 Did you check out the PROPERTIES | COMPATIBILITY tab? Link to comment Share on other sites More sharing options...
Russ Croucher Posted June 3 Author Share Posted June 3 Actually that's going the wrong way. That would be like for Windows 10 are 11 to be compatible with old Windows 7. But you can't make Windows 7 be compatible with the future what it doesn't know. Link to comment Share on other sites More sharing options...
borate Posted June 3 Share Posted June 3 Makes sense, but Videopad literature states... If the latest release isn't working on Windows 7, you might want to contact NCH. Link to comment Share on other sites More sharing options...
Venera_Oxductions Posted June 21 Share Posted June 21 My reply won't be very useful to you but in case, I right-click an MP4 under W10, "open with ", then VP, and it adds it to my current project. Version 16.22 here. I just used it once to see how it behaves. Never tried the command line. Besides, I can't help wondering now , why do you run VP with a command line ? Do you llike launch batch exports or other batch jobs ? Link to comment Share on other sites More sharing options...
Russ Croucher Posted June 23 Author Share Posted June 23 Venera_Oxductions, I started with command line years ago. In fact 40 years ago (81). We started before Windows existed. Microsoft abandon the command line concept about the time of Windows NT. They decided other ways to handle mass installations and what they had completed was enough. So another company took over and ran with the concept and expanded it greatly in the early days. There was a company called 4DOS and then they graduated to 4NT. Then they decided to sell their part to JPsoft.com who now supports it all the way through Windows 11. You get a license for development($100) on one machine and then they have a free download for the runtime version on all your workable machines. I could've wrote the software in C++ or C# but decided that the scripting is easier to follow since it's interpreted. It also has tremendous power to be able to stuff keys into another project and I can monitor the CPU execution while it's running. I love the NCH tools as they have a tremendous product but they are not expandable enough. Example they have a program called PhotoStage which is awesome but it only handles 250 photos if you include the filename scrolling on the bottom which I do. If you don't have that option you can typically do over 1000 photos. I have a business that converts photos and videos to slideshows and one customer gave me 9000 photos to convert. And I have a program written on this command line that submits PhotoStage 200 times to execute those 9000 photos only to stitch them together with videopad. To execute this mass batch file took 24 hours on a 6 core XEON workstation with 32 gigs of RAM all SSD (M2 2 GB /second) no hard drives. I have 10 of these machines and demand speed. For the 1st 30 years of my life in computers I was writing assembler, C, and C++ software for Public Safety radios for policeman and nuclear inspection using Nvidia graphics chips doing ray tracing of soundwaves. But then I had a wake-up call that said personal videos that I do are much more important even though they're not hard. Now the shoe is on the other foot and I'm using NCH software that they have many engineers writing code and I just complain when it doesn't work right. I have a website that could be of interest if you have any questions (centralvirginiavideo.com). Here is a demo I have a PhotoStage and using videopad using the batch file concept. I chose to use these batch files because they are easy to look at and understand as opposed to C# or C++ code. https://1drv.ms/f/s!AnzxHv3YmYSCvT6aB9WtarKbgZNJ?e=pr5aBi Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now