I added a title track, added a title and chose a frame and go save frame to PNG and get an error Vs exports a corrupted png file.
Its saving a zero length .png file!
Note that save title as animation is also broken - all the files in animation are 0 length - last time i had such a bug it was because VS was terrible at working out the video footage size or other, this time nothing fancy normal 1920x1080. Looks like a math bug to me.
Actually now that i do some more exploring VS is unable to open/load PNG files altogether?
Have raised a ticket, with them, probably have to uninstall and re-install, although no idea why that would have any correct by design effect whatsoever.
VS accepts png files without any problems.
Do you have problems with all png files or only this one? Can you make it available to us for testing?
Could you give a more detailed description on what you are doing to create yur "frame" png?
Hmm, sounds like a re-install is on the cards for this evening. It must be my system.
Not only does it fail to save any "Title" timeline titles as a PNG, it fails to load "any" PNG files that I have created in Paint.net I don't know if it's a recent bug in Paint.net, (I update frequently) but the fact that VS is not saving/exporting to PNG either, tells me the installation is somehow relying on libraries that don't exist/corrupted. I wish I had some logs to read.
Will kick off the uninstall so long and hope I can still re-install. Pretty sure I saved the download cache files someplace, I only installed 2021 a short while ago, so had not used it often, will update on how that went in an hour or so.
uninstalled with the remove all settings boxes enabled, rebooted, run the setup app, and nothing changed.
VS just will not allow me to use any PNG file, even this file is deemed not valid https://upload.wikimedia.org/wikipedia/ ... G_Test.png
I think VS is struggling most because my default installation drive is D: not C: , assume there are some notes on how to deal with this, since I had similar pain with VS2019 I am sure.
What do you mean by struggling.
I always install to the default location on the C Drive so all I have on there are software
Installing video studio to D Drive and some files and folders will be installed to the C Drive irrespective of choosing another drive. So I do not see the point installing anywhere else
I guess it’s a personal choice
All my personal files, Images / Video are saved to the D Drive, well drives other than C
DavidK is the only person I know that has regularly installed outside C Drive, maybe he can help
New forum for PSP and VS users, register if you need help
Installed the product onto a VM, works just fine.
I have now uninstalled all other Corel products, deleted the folders, changed the system setting so we always install onto C: not D: and still no joy. Strange because as far I can see VS is working just fine, so the PNG plugin or module not working is rather bizarre. Probably time to re-install the O/S anyway, I seem to so this every 2 years .
Yes all logfiles are in C:\ProgramData\VideoStudio Log Files
but these are only installer logs, no logs for the actual program are in there.
I wonder if David has a few pointers on the D: drive pain before I grab a new disc drive.
LOL. Not a biggie, I need a clear weekend to b formatting the computer anyway. I just cannot remember how I got VS 2019 working on my system with 2 drives, it was 2 years ago. A good few other huge programs also did not play nice either. If I do reformat I'm definitely not going to do it that way again, getting old for being smart. Lockdown has been very quiet, not as much video opportunities.
I was quite amazed at how well VS worked running on a VM, that could always be a thing.
As Ken said . . But I'm awake and here . . so having read the topic, some observations. There seem to 2 intermixed issues here:
1. Loading png file. I've never had an issue inserting a png file into the timeline, or an overlay track, for any version of VS.
2. Problems running VS. I think the basic cause of the other problem(s) running VS is your choice of D: as the default drive. The OS normally installs to C:, usually no choice. Additionally, the default install of VS is to C:\, which includes a number of personalised files in the used group. Even with a custom install of VS to another drive, all the ultimate add-ons go to C:\, as well as the personalised files. And this may be the cause of your issues with 1. above. So some thoughts on this.
Ever since adam was a teenager, MS has used the C hard drive as the installation drive for the OS. Originally - when Adam was a boy - PC's had only one (1980) and then 2 floppy drives (A and B) one of them contained the OS, at that time DOS, so the first hard drive was C:, and as the OS got large - around the mid -80's - floppies were dropped and a hard drive became a system pre-requisite, still called C, and that was where the OS went, or came pre-installed (a much later commercial innovation). Also at the time, everything else went there too. Having everything - the OS, programs and data - all in the same store had some real performance issues - like reading a book by referring to the index every time the next page was due - and it was not long before an extra hard drive D: became an option for programs and data for those with the inclination to improve their system performance.
You can still install everything to C: - it's the default, and easy way, and many (lazy) programmers write installs expecting that. But spreading the storage of OS, programs and data to different drives gets you noticeable increases in performance, which are all related to the physical aspects of the hard drives being used. It was very pronounced in the early 1990's when hard drives were slow and 4Gb total storage (typical) on a drive was a LOT. 32bit processors had a lot to do with that size choice. Things have really improved since then, but the basic constraints for rotating HDD still exist, just reduced in scale.
With your default drive being D, I think you have parts of the OS, and application spread across 2 drives, because some installers are careful, whilst others "assume". A case in point is my VS installation of ultimate in a custom configuration: even tho I have specified which drive and folder I want the install to go to, the personalise files and every one of the plug-ins installs to C: because that's what the installer has assumed, and there's no reference in that to any user specified preference. Trying to use those plugins is going to look first of all to C: for their program or data . . .
Getting to a more conventional system approach, generating a system using C as the default drive, and (given the discussion involving D) applications and data on D: as far as you can specify, may require a complete system re-install, from the OS upwards. A restoration of a whole of drive backup of D: to the physical C: drive (essentially, copy the contents including system and hidden files as stored from D to C) may work, but I'm not sure that covers all the inter-program links that exist. If you do this, make sure that any SSD you have is also the physical drive for C:. If you have a second computer, start with that . .
Update late on 15th, FWIW
Just reviewed my reply here and realised there were missing elements useful for comparison, so here they are....
1. my systems have a default drive of C: for the OS and anything else unless otherwise specified in the app install program. I have never attempted to use any drive but C as the default for the windows operating system. The hardware has 4 internal storage drives, a mix of SSD (1) and HDD (3) totalling 1.75Gb, and I use the SSD solely for C: and the operating system if I have any choices at all. Sometimes, there isn't - installing just puts it in C - see comments above. The HDD are partitioned into logical drives (12) and I use each of those for specific types of data - utilities, email, applications, video, pictures, audio, documents, a scratch pad etc, one data type per drive. So for example if I want to use a video file I know it is always on a specific drive - J in this case. This approach is handy for finding VS re-link files, but also means I can add or remove applications like VS without removing any of the data they use that otherwise is installed in a default application tree. It also helps the backup regime because some data changes often over time, and others don't. So I backup 3 drives with frequently changing data regularly, and the others less often. It means I don't have to backup the entire system every time.
Why focus on one drive for the OS (C)? It's the most used drive in the system, and therefore the most likely to fail as a result of software corruption or outright hardware failure. If every application is also on it, an failure means replace everything - basically, get a new PC. If the only thing on the failed drive is the OS, then replacement is a lot simpler, cheaper and less time consuming: new drive, recover contents from last backup, which includes the registry, and you should be good to go. My preference, and I know others don't agree. Which is fair enough.
2. I always install VS in a 'custom' format, check that button in the installer (a conscious decision - it defaults to a default install all on C, so you have to stop and make the choice for a custom install), which means that I get to specify the drives/folders for that requirement and the various elements of it later in the installer
a. I specify the installation drive as G: - which is where I put applications that allow custom installs - and a folder with the relevant name eg video studio 2021. And that folder separation means I can and have multiple versions installed at the same time. And unlike the plug-ins, the Corel files do go there.
b. VS has since 2019 used shared content in various installations of the program. On the first installation, you get a choice of drive/folder for that. From memory, Corel calls this part content 2. Once specified for the 1st install, the location is in the registry and later installs cannot change it; it's shown in the installer, but the options button is greyed out and unresponsive. The only way to change it really is to uninstall every version, and then start again installing versions from the earliest one required and specify the change shared location at that time.
Despite all that, the personal folders for VS and all the ultimate plugins are installed on C - because the whoever wrote the installer just assumed it would be like that and made no effort to consider custom installs. However, it works, and the degrees of separation have been extremely helpful when drive failure occurs - re-installing or recovering everything is not required - just get the latest backup file for the drive involved and recover from that (after, of course, the failed hardware has been replaced and formatted for use).
100% concur David, as a once-upon-a-time developer I also know why this fails, I opted for an 1TB "M2" SSD for C:\ and then a 10TB drive split for D: and E: and generally this has worked OK, because smaller programs will install fine to D: more by luck than by good sw engineering practice. And for small apps that fail to run off D: , them sitting on your C: and SSD that you boot from it's not such a space waste. (I explicitly moved pagefile to D:, although I don't think anything hits my pagefile because I have a lot of male-sheeps in my machine) For other folk who use SSD, the Windows installer now apparently actually tries to "split" your pagefile off of any SSD volumes it detects by default, which was a handy thing to find out. I had also noted that the VS plugins did install on C:, which is not a huge pain, they are also small. I don't upgrade my VS every year, but have been disappointed when plugins I had in a earlier version fail to get loaded in a new version of VS. So now I make backups of the installers onto the NAS, although I don't have a full set for the versions I own as I'm missing the V7 free addons.
My main reason for "only" installing the OS on C: was really to try slightly reduce time spent making a manual backup of a mess of OS and user data every time I do a PC rebuild. Definitely like the idea of doing all video projects on a J: drive, to save time relinking projects. It's just very tempting to put all my video files onto the SSD to make working with editing faster, although I can still do that with a symlink I guess.
2. I'm going to try the custom install again, and from your description David, pretty sure that 2019 worked because I was manually installing each piece repeatedly until I got it to work for me. I have now done Normal VS2021 install about 6 times over after various environment tweaks and just leaving it to slowly install in the background while doing real work on my other PC. So worth another shot at a custom install now that I have reset most system settings. Re-installing and rebooting repeatedly has been a crazy experiment because I test software for a day job and I should know that trying again and again rarely yields a better result. LOL.
Will update you all if that works, otherwise definitely going to rebuild with this in mind so I can also keep on old version of VS for when upgrade gives me pain.
.
