whats happening to video studio x9
here is my post on Facebook
MEMy VideoStudio x9 ultimate crashes with mov files, whats going on?
Like · Reply · 1 October at 02:46
Corel VideoStudio Hi Angus : Sorry to hear that. Please kindly try updating to version x9.5 if you already haven't and let us know if it helps resolve the crash issue : http://www.videostudiopro.com/en/support/updates/ - Thanks!
Product Patches and Updates
Find updates and patches for former and current versions of VideoStudio Pro and DVD MovieFactory.
videostudiopro.com
Like · Reply · 3 October at 17:15
ME I had already done that on the 1/09/2016. how can I tell if it has actually updates the software. in Help/about it come up with this

Like · Reply · 7 October at 15:54
ME I presume the 19.5 bit means it 9.5 version?
Like · Reply · 7 October at 15:55
ME I'll import a MOV file in the the library. some times if it's at a time several it will freeze up before it finishes importing them all. if it just a couple it imports then fine but if you click on one to play or put it in the time line it will freeze up. I have tried it with MOV files from a Fuji camera and an iPad and an action camera and the same thing happens all the time. I am running in 32 bit. Just comparison MTS video files from a Panasonic camcorder work OK as does an AVI file from a Hitachi camcorder.
Like · Reply · 7 October at 16:10
Corel VideoStudio Hi Angus : thanks for the heads-up. Yes, 19.5.0.35 is the updated version. Please kindly copy your above note and send us a direct message through Facebook along with your registered email address and we'll gladly report your issue to our development team for further advise. Thanks!
Like · Reply · 7 October at 17:45
done as they asked but as yet I have had no reply or communication.
I am using a optiplex 760 pc running 32bit windows 10 pro and 2.94 usable gig of ram. I know it's not the best and most upto date pc's for video editing but I also run movie plus x6 from serif for which there hasn't been any updates for years and that works fine with the same MOV files, so I can only conclude it's something to do with the way VS handles the Mov file or there is something wrong with the program..
