I just installed Version 11 of VideoStudio which was an upgrade from Version 9. I tried to import a MOV file created by my Nikon DigiCam, and instantly Version 11 shuts down. No error, just shuts down. I'm glad I didn't uninstall Version 9 as that's what I have to use now.
What gives?
Thanks in advance.
Chip
Running VideoStudio 11
Moderator: Ken Berry
-
Ron P.
- Advisor
- Posts: 12002
- Joined: Tue May 10, 2005 12:45 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Hewlett-Packard 2AF3 1.0
- processor: 3.40 gigahertz Intel Core i7-4770
- ram: 16GB
- Video Card: NVIDIA GeForce GTX 645
- sound_card: NVIDIA High Definition Audio
- Hard_Drive_Capacity: 4TB
- Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
- Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter
- Location: Kansas, USA
-
mrheckman
VS11+ exits when inserting MOV file
The same thing happens to me when I insert MOV clips made by my Panasonic Lumix camera: VS11+ simply exits -- immediately -- without even an error message. VS8, however, has no problem at all.
How do I find the MOV properties to determine the codec that it uses?
If it is due to the use of an H264 codec, what do I do? Is there a way to add this codec to VS? This is kind of a deal-killer, if VS can't support these files.
How do I find the MOV properties to determine the codec that it uses?
If it is due to the use of an H264 codec, what do I do? Is there a way to add this codec to VS? This is kind of a deal-killer, if VS can't support these files.
-
mrheckman
VS8 works but not VS11!
OK, I'll try "Super", but any idea why the MOV files work just fine in VS8 but crash VS11? How could VS11 lose compatibility? Is this something to take to the "real" tech support, or is that you?
-
Black Lab
- Posts: 7429
- Joined: Wed Dec 15, 2004 3:11 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- Location: Pottstown, Pennsylvania, USA
This is just a user's forum. Ulead reps very rarely visit. If you have a problem, by all means, submit a Technical Support Form.
This forum is great for finding answers for things that you may have missed, workarounds, and things like that. But if you have real technical problems I think all too often people post their problems here with the expectation that Ulead will read it and respond with a fix. The proper way to get their attention is with the Tech Support Form.
This forum is great for finding answers for things that you may have missed, workarounds, and things like that. But if you have real technical problems I think all too often people post their problems here with the expectation that Ulead will read it and respond with a fix. The proper way to get their attention is with the Tech Support Form.
Jeff
Dentler's Dog Training, LLC
http://www.dentlersdogtraining.com
http://www.facebook.com/dentlersdogtraining
Dentler's Dog Training, LLC
http://www.dentlersdogtraining.com
http://www.facebook.com/dentlersdogtraining
-
mrheckman
Technical support form
OK, thanks for the suggestion. I just did that, but it only allowed me to submit a request for a product that I already have registered (VS8). Hopefully, they will treat it as a request for technical support for VS11.
-
mrheckman
MOV properties
Well, I've submitted a tech support request and am waiting for an answer, and I've tried SUPER, but haven't been able to get a good result when converting to mp2. For some reason (I hope it is just a setting that I haven't tried yet), the rendered video is very pixelated and the colors/brightness are slightly off. I'll keep trying different settings, however, before I give up on it.
In the meantime, using SUPER I've found the properties of the MOV files that crash VS11+. Does any of this mean something to you experts? Is anything non-standard?
Format : QuickTime
Format/Info : Original Apple specifications
Format/Family : MPEG-4
File size : 5.44 MiB
Bit rate : 11 Mbps
StreamSize : 1.52 KiB
Video #0
Codec : M-JPEG
Codec/Family : M-JPEG
Codec/Info : JPEG compressed
Bit rate : 11 Mbps
Width : 640 pixels
Height : 480 pixels
Aspect ratio : 4/3
Frame rate : 30.000 fps
StreamSize : 5.41 MiB
Audio #0
Codec : RGB
Codec/Family : RGB
Bit rate : 64 Kbps
Channel(s) : 1 channel
Sampling rate : 8000 Hz
Resolution : 8 bits
StreamSize : 31.3 KiB
In the meantime, using SUPER I've found the properties of the MOV files that crash VS11+. Does any of this mean something to you experts? Is anything non-standard?
Format : QuickTime
Format/Info : Original Apple specifications
Format/Family : MPEG-4
File size : 5.44 MiB
Bit rate : 11 Mbps
StreamSize : 1.52 KiB
Video #0
Codec : M-JPEG
Codec/Family : M-JPEG
Codec/Info : JPEG compressed
Bit rate : 11 Mbps
Width : 640 pixels
Height : 480 pixels
Aspect ratio : 4/3
Frame rate : 30.000 fps
StreamSize : 5.41 MiB
Audio #0
Codec : RGB
Codec/Family : RGB
Bit rate : 64 Kbps
Channel(s) : 1 channel
Sampling rate : 8000 Hz
Resolution : 8 bits
StreamSize : 31.3 KiB
This is the quicktime file decoder that VS11+ uses, you have another one in the same directory under your VS8 directory. Maybe try using VS8's version in VS11+ (as a test).
If you navigate to the below directory highlight this file, hit "F2" and rename it to uvqt.vio_VS11+
Then copy the same filename from the VS8 directory into the VS11+ directory and see if VS11+ can read your quicktime file.
C:\Program Files\Ulead Systems\Ulead VideoStudio 11\vio\uvqt.vio
The properties you posted don't look correct to me, somethings different or wrong in it and I can't remember what it is compared to my mjpeg files.
Something in it that says MP4.
Before you try the file swap maybe rename the file from MOV to MP4 first. Hopefully VS11 won't crash.
You will also see a uvMP4.vio file in the above directory. Be careful not to mix the files and retain the originals from VS11+
If you navigate to the below directory highlight this file, hit "F2" and rename it to uvqt.vio_VS11+
Then copy the same filename from the VS8 directory into the VS11+ directory and see if VS11+ can read your quicktime file.
C:\Program Files\Ulead Systems\Ulead VideoStudio 11\vio\uvqt.vio
The properties you posted don't look correct to me, somethings different or wrong in it and I can't remember what it is compared to my mjpeg files.
Something in it that says MP4.
Before you try the file swap maybe rename the file from MOV to MP4 first. Hopefully VS11 won't crash.
You will also see a uvMP4.vio file in the above directory. Be careful not to mix the files and retain the originals from VS11+
-
mrheckman
Let's see what tech support can find.
I tried both of those suggestions. Renaming MOV to MP4 only generated a "wrong format" (or something like that) error when I tried to import it to VS11+. Using the uvqt.vio file from VS8 had no effect. But thank you for the suggestions.
Meanwhile, Tech Support asked me for an example file that causes the problem, which I've uploaded to their FTP server. I'm keeping my fingers crossed that they can recreate the problem and find a solution.
Meanwhile, Tech Support asked me for an example file that causes the problem, which I've uploaded to their FTP server. I'm keeping my fingers crossed that they can recreate the problem and find a solution.
-
mrheckman
Ulead Tech Support response
Here is Ulead Tech Support's response:
<<
The compression of the MOV file that you uploaded has H.264 compression, you can see this by checking the properties of the clip in video editing programs or Quicktime player. Sorry, VideoStudio doesn't support this compression which is mostly saved by digital cameras. We suggests to convert this first into AVI using Quicktime Pro before importing into VideoStudio to edit.
>>
Quicktime player, Sony Vegas Movie Studio, and VS8 all say the file is compressed using "Photo - JPEG". No application that I have used says that the file is compressed using H.264. I do, however, have some files that I know to be encoded using H.264. All of those programs correctly identify the H.264 files. How did Ulead Tech Support determine that the file I uploaded is compressed using H.264? Is it possible that the video compression method is incorrectly labeled in the file but these applications are still able to figure it out while VS11 can't?
And did Ulead really lose support for H.264 between VS8 and VS11? Did they decide to not pay Apple for a license, or something?
FYI, Sony Vegas Movie Studio 6.0 has no problem with the video. I still have to try Premiere Elements, Pinnacle, and other programs to determine if they have any problem. I am used to Ulead's interface and hate to change, but I also hate to have to buy a converter to regain a feature that was in an older version of VS.
Thanks again to all of you who offered suggestions.
<<
The compression of the MOV file that you uploaded has H.264 compression, you can see this by checking the properties of the clip in video editing programs or Quicktime player. Sorry, VideoStudio doesn't support this compression which is mostly saved by digital cameras. We suggests to convert this first into AVI using Quicktime Pro before importing into VideoStudio to edit.
>>
Quicktime player, Sony Vegas Movie Studio, and VS8 all say the file is compressed using "Photo - JPEG". No application that I have used says that the file is compressed using H.264. I do, however, have some files that I know to be encoded using H.264. All of those programs correctly identify the H.264 files. How did Ulead Tech Support determine that the file I uploaded is compressed using H.264? Is it possible that the video compression method is incorrectly labeled in the file but these applications are still able to figure it out while VS11 can't?
And did Ulead really lose support for H.264 between VS8 and VS11? Did they decide to not pay Apple for a license, or something?
FYI, Sony Vegas Movie Studio 6.0 has no problem with the video. I still have to try Premiere Elements, Pinnacle, and other programs to determine if they have any problem. I am used to Ulead's interface and hate to change, but I also hate to have to buy a converter to regain a feature that was in an older version of VS.
Thanks again to all of you who offered suggestions.
-
mrheckman
Decided to go with VS10
I tried editing the video files that crash VS11 in VS10 and (using Quicktime 6.5 to avoid the screechy sound problem in VS10 -- see http://phpbb.ulead.com.tw/EN/viewtopic. ... hlight=mov for more information) had no problem editing and rendering the files as Mpeg2. VS11 crashed no matter what version of Quicktime was installed. Since Ulead says that VS10 does not have H.264 support, these files clearly are not H.264. (But I already knew that because VS8 had no problem with them, either.)
I also tried the MOV patch solution (described in http://phpbb.ulead.com.tw/EN/viewtopic. ... 2298#62298 ), without success.
Alternatives presented in this and other threads include first converting the files to AVI using conversion programs such as Quicktime Pro (see
http://phpbb.ulead.com.tw/EN/viewtopic. ... hlight=mov for details about audio settings), SUPER (see http://phpbb.ulead.com.tw/EN/viewtopic. ... hlight=mov for the settings), and MP4Cam2AVI (found at http://sourceforge.net/projects/mp4cam2avi -- see http://phpbb.ulead.com.tw/EN/viewtopic. ... 543#110543 for settings), or using another video editing program to convert the files (I tried Vegas Movie Studio 6 and Adobe Premiere Elements 3, both of which had no problem with the files). One objection I have to converting the files first is the potential loss of video quality with multiple renderings, although I believe this can be mitigated with the proper choice of settings/formats. My main objection is that I enjoyed simply being able to drag and drop the video clips from my camera directly into the timeline without any preprocessing.
Hopefully, Ulead Tech Support will look further into this and other problems with MOV files because many people, like me, want to use VS to edit video clips from our digital cameras. Many, if not most, of these cameras generate MOV files (with and without H.264). Clearly, given the large number of threads devoted to issues with MOV files, this is a big problem with VS. Meanwhile, I can use VS10. Thanks again to all of you who had suggestions and I hope this thread will be of some help to anyone else who runs into the same problem with MOV files crashing VS11.
I also tried the MOV patch solution (described in http://phpbb.ulead.com.tw/EN/viewtopic. ... 2298#62298 ), without success.
Alternatives presented in this and other threads include first converting the files to AVI using conversion programs such as Quicktime Pro (see
http://phpbb.ulead.com.tw/EN/viewtopic. ... hlight=mov for details about audio settings), SUPER (see http://phpbb.ulead.com.tw/EN/viewtopic. ... hlight=mov for the settings), and MP4Cam2AVI (found at http://sourceforge.net/projects/mp4cam2avi -- see http://phpbb.ulead.com.tw/EN/viewtopic. ... 543#110543 for settings), or using another video editing program to convert the files (I tried Vegas Movie Studio 6 and Adobe Premiere Elements 3, both of which had no problem with the files). One objection I have to converting the files first is the potential loss of video quality with multiple renderings, although I believe this can be mitigated with the proper choice of settings/formats. My main objection is that I enjoyed simply being able to drag and drop the video clips from my camera directly into the timeline without any preprocessing.
Hopefully, Ulead Tech Support will look further into this and other problems with MOV files because many people, like me, want to use VS to edit video clips from our digital cameras. Many, if not most, of these cameras generate MOV files (with and without H.264). Clearly, given the large number of threads devoted to issues with MOV files, this is a big problem with VS. Meanwhile, I can use VS10. Thanks again to all of you who had suggestions and I hope this thread will be of some help to anyone else who runs into the same problem with MOV files crashing VS11.