.MOV files “break” Sony Movie Studio 12

wormbog wrote on 1/26/2014, 7:08 AM

.MOV files “break” Sony Movie Studio 12 – Black video preview and renders

Sony Movie Studio 12.0 is consistently showing a black preview screen and black rendering of .MOV clips after I put a certain number of source files in my project media bins or clips on the timeline, and the program even crashes and shuts itself down. Although the video goes black in the preview and also the renders, the audio still plays perfectly fine. The cursor moves along the timeline and the frame numbers and time advances on the controls under the preview window.

I am using Sony Movie Studio Platinum Version 12.0 (build 1184) 64-bit version.

I am using .MOV clips from iPhone 4.

My PC is running Windows 8.1, I have an i7-3770 CPU at 3.40 GHz, and 12.0 GB of RAM. I use AVAST free antivirus. VLC Media Player is my primary media player and my file assocations for all video and audio file types are to VLC Media Player.

At the time this problem started I was using the current version of iTunes and Quicktime (7.7.4). During my past week of frustrating troubleshooting and forum searching, I have tried several other versions of Quicktime including 7.7.3, 7.7.2, 7.7.1, 7.6.0. None of them has worked or made any difference.

It appears to be immediately related to the number of clips I add to the project (in the media bins). Once I get a certain number of .MOV clips in the bins (maybe 20 or 30, I don't know the exact number), I get black preview and renders, only the audio plays. These are puny little clips, too. They range from .5 seconds to 1 minute, between 50MB and 1.25 GB.

But if I then remove of a few of those clips from the project media bins, the preview and rendering works fine again. It is like the program cannot handle loading beyond a certain number of .MOV files in the project media bins. The only thing that seems to work is lowering the number of source .MOV clips in the project media bins.

It also looks like File I/O Surrogate (not visible) 32-bit process in my Task Manager is choking when it gets to over 1000 MB. Leading to this ERROR REPORT upon program crashing:

---------------------------------------------------------------------------------------------------
Problem Description
Application Name: Movie Studio Platinum
Application Version: Version 12.0 (Build 1184) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\SYSTEM32\ntdll.dll
Fault Address: 0x0000000077692779
Fault Offset: 0x0000000000042779

Fault Process Details
Process Path: C:\Program Files\Sony\Movie Studio Platinum 12.0\x86\FileIOSurrogate.exe
Process Version: Version 12.0 (Build 1184)
Process Description: File I/O surrogate (not visible)
Process Image Date: 2013-08-21 (Wed Aug 21) 18:26:36
---------------------------------------------------------------------------------------------------------

I have been searching these forums for an entire week and tried many ideas people have given, but nothing has worked for me or made any difference.

Here's what I have tried already:

1 “Mute all video” is not checked. My video track is not muted.
2 Compositing mode is on default setting.
3 I tried increasing and also decreasing “Preview RAM” from the default 300 MB up to 1000 MB at one point, and as low as 0 MB at another. No difference.
4 I lowered the “Maximum number of rendering threads” to 1, from my default of 16.
5 I turned “GPU acceleration of video processing” to “Off.”
6 I unchecked “Close media files when not the application.”
7 I tried closing the project, I tried restarting the SMS program, I tried restarting my computer entirely, I tried running CCleaner, I tried defragmenting the source clips folder on my 2 TB hardrive, which has about 1 TB of free space remaining.
8 “Draft” and “Auto” Preview quality.
9 Adding my SMS program installation folder to my list of exceptions in AVAST antivirus.
10 No tracks are set for “Solo.”

Some other “solutions” I read about that I did not try because I think they are completely unacceptable or very unlikely to work or are just plain stupid, include,

1. Reinstalling Sony Movie Studio on a regular basis. I've done it a few times and the problem always comes back.
2. Registry cleaning or hacks.
3. Proxy editing
4. Converting my source files into other file types.
5. Breaking down my 4 minute project into 3 or 4 pieces and combining them together at the end.
6. Stopping all processes in msconfig at startup
7. Downgrading to a 32-bit version of Sony Movie Studio

--------------------------------------------------------------------------------------------------------
Here are some screenshots of my project and preferences:

http://imgur.com/bMbJuaF

http://imgur.com/MeFh1bB

http://imgur.com/UlqOeZN

---------------------------------------------------------------------------------------------------
And here is the Mediainfo from one of the .MOV files:

General
Complete name : C:\Users\Michael\Documents\Movie Studio Platinum 12.0 Projects\_raw materials\IMG_5064.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 138 MiB
Duration : 54s 508ms
Overall bit rate : 21.3 Mbps
Recorded date : 2013-03-02T19:21:53-0500
Encoded date : UTC 2013-03-03 00:21:53
Tagged date : UTC 2013-03-03 00:22:05
Writing application : 6.0
Writing library : Apple QuickTime
Model : iPhone 4S
Make : Apple
com.apple.quicktime.make : Apple
com.apple.quicktime.creationdate : 2013-03-02T19:21:53-0500
com.apple.quicktime.software : 6.0
com.apple.quicktime.model : iPhone 4S

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Baseline@L4.1
Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 54s 508ms
Source duration : 54s 520ms
Bit rate : 21.2 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 24.000 fps
Minimum frame rate : 23.077 fps
Maximum frame rate : 25.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.426
Stream size : 138 MiB (100%)
Source stream size : 138 MiB (100%)
Title : Core Media Video
Encoded date : UTC 2013-03-03 00:21:53
Tagged date : UTC 2013-03-03 00:22:05
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 54s 507ms
Source duration : 54s 544ms
Bit rate mode : Constant
Bit rate : 64.0 Kbps
Channel(s) : 1 channel
Channel positions : Front: C
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 418 KiB (0%)
Source stream size : 418 KiB (0%)
Title : Core Media Audio
Encoded date : UTC 2013-03-03 00:21:53
Tagged date : UTC 2013-03-03 00:22:05

------------------------------------------------------------------------------------------------------

What's up with this? I see that the forums are riddled with some variety of this very problem going back to 2009 even. This software should be able to handle a few short .MOV clips without completely crapping itself to death. Sony advertises that it can handle .MOV files. So can it or can't it?

It seems that using upwards of 20 little “standard” .MOV clips from an iPhone 4 should not “break” this otherwise fabulous software.

Comments

musicvid10 wrote on 1/26/2014, 10:43 AM

You might try the VMS 13 trial with QT 7.7.3. It has been hinted to fix some problems.
Unfortunately, Quicktime libraries are still 32 bit, and there is nothing Sony can do about that except wait.
You might try converting to avi in Gopro Studio as a workaround.
Apple really doesn't like Windows NLEs using its libraries, so full cooperation is never likely

wormbog wrote on 1/26/2014, 11:11 AM

Thanks for the reply musicvid10. I might eventually try the trial 13 as you suggested. But I do not ever see myself buying another version of this program if this problem cannot be addressed without workarounds. I paid for Version 12 and it failed to do what it claims it can in its advertisements.

I do not have GoPro Studio, nor am I familiar with it. I am not crazy about the idea of converting to another format to make it work, but if I had to do you think converting to MP4 using Handbrake would be a reasonable alternative to .MOV? Would I still have this blackout of the preview and renders if I used clips in MP4?

musicvid10 wrote on 1/26/2014, 11:48 AM

Gopro studio is free, and it was expressly designed to convert "similar" mov fies LOSSLESSLY to Cineform, a Vegas friendly codec since day one! That's why I suggested it, with the disclaimer that I have no earthly idea if it will work for you.

No, I don't suggest using Handbrake to create an INTERMEDIATE, except in the absence of better alternatives. It takes both knowledge and experience with the command line settings to do this correctly.

I pointed out but a few of the constraints that Sony faces in dealing with Apple's PROPRIETARY libraries, which are costantly changing. So rather than continue to point fingers, why don't you make your case with Apple and see what kind of response you get from them?

wormbog wrote on 1/26/2014, 3:38 PM

Thanks for the tip about GoPro Studio. That sounds like a great idea. I will definitely try it. It is an extra step that should not be necessary, but if it works then I will do it.

It sounds as though we both agree on one thing. Sony Movie Studio advertises it can handle .MOV files, when in fact it cannot.

Thanks musicvid10. I appreciate the advice.

Anyone else? I am still hopeful there is a way to make .MOV files work in Movie Studio 12.0, and that there is some "techy person" out there who can provide a solution to this File I/O Surrogate 32-bit crash problem.

musicvid10 wrote on 1/26/2014, 4:00 PM

I'll thank you not to put words in my mouth; I've worked with Vegas in my nonprofit for over a decade.
Again, you're putting the blame on Sony, rather than Apple's mercurial 32 bit libraries, which Sony has no control over, legally or otherwise. It's not just a Vegas issue, but affects all Windows NLEs in various ways going back as long as I can remember. FileIOSurrogate errors are one symptom, not the cause.

Until Apple releases 64 bit libraries that are not broken on purpose (imagine that!), or offers a licensing solution (ha!), blaming the abuse on the victim will get no one any closer to a solution.
Best of luck.

wormbog wrote on 1/26/2014, 8:27 PM

So then the end result is that .MOV is not really supported in Movie Studio 12.0?

Markk655 wrote on 1/26/2014, 9:27 PM

1. Have you tried a new project? Open up a second instance of MS12, select all of the clips, copy and paste into the second instance (create a new project)?

2. Are you really taking video at 24 fps with the 4s? What app are you using? I didn't think it did that natively.

musicvid10 wrote on 1/26/2014, 9:54 PM

"So then the end result is that .MOV is not really supported in Movie Studio 12.0?"

Another sweeping generalization -- there are as many MOV formats as there are jelly beans in a five gallon jar. I work with multiple MOV formats every week, with only occasional bumps in the road. Your issue with iPhone 4 is not unheard of, but is far from universal, either. So I wonder if you are after a solution, or dramatic effect? Either way, best of luck ;?)

Four years ago, I wrote a tutorial explaining the differences between containers and codecs, and how they affect issues such as yours, if you're interested. As you can see, problems with Quicktime libraries and certain MOV formats did not start the day you purchased Movie Studio. Hope you find a solution, but my patience with your attitude has passed.
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=12&MessageID=660127

wormbog wrote on 1/27/2014, 6:02 AM

Thanks musicvid10. Anyone else? I am interested in a solution.

wormbog wrote on 1/27/2014, 6:54 AM

Markk655, thanks, I will try the new project idea. It's worth a try. As to the 24fps, that's just the regular old camera app. Never messed with any settings.

wormbog wrote on 1/27/2014, 7:07 AM

The part I don't understand is why I can add a certain number of clips and it works perfectly fine. But once you cross a certain threshold (whether it be number of clips or perhaps total size of clips) then the software suddenly chokes and is completely crippled. But it was working perfectly fine before the clip that broke it's back. Other people on these forums have observed this and mentioned it, too. I may have missed it, but I have not seen this "number of clips in the project bin" issue addressed. Is there something to this? I was working with about 20 .mov files for several hours with no issues whatsoever. Then I add a few more clips. And croak. The software bites the dust.
(They were not bad files. They were the same as the other clips I'd been working with. When I removed a few files from project bins everything went back to working normal again. But then I added a few different clips. Same thing. Croak. )

zdrawko wrote on 2/1/2014, 1:38 AM

Hi
I've had the same problem today, suddenly the mov files that were working before went black in the preview window and on the timeline.
What worked for me?
1. to uninstall the quicktime. I was installing some old versions of 7.7 - didn't work, then i've tried 7.6, now it works, but...
2. I was also downgrading the itunes to 9.03
http://www.oldapps.com/itunes.php?app=fcb15bbc01980e478a6cf939b62b36ff

Restarted MSP12 and boom ...it works again.
Until I will find other bug :)
I hate you sony

vkmast wrote on 2/1/2014, 2:54 AM

>>>I hate you sony<<<
So you didn't read any of the posts by musicvid10 in this thread?

wormbog wrote on 2/1/2014, 7:42 AM

Thanks for the info, zdrawco. I will try the same. If it's not too much trouble, can you report back if it goes bad again. Often fixes get things working again, but then it never seems to last. That's been my experience, at least.

Ivan Lietaert wrote on 2/1/2014, 8:03 AM

In my opinion, you have memory issues with your system.
I use the same OS as you and run VMS12. My system, though, is 6 years old (!) and low spec compared to yours (only 3GB ram). I did a large project on it with many audio and video tracks and many, many events, total runtime was 42 minutes (rendering to a 6GB file) without ever crashing once - working on the project took about two months.
The main difference is that I run the OS and VMS from a 90GB SSD. Since I did that upgrade, VMS has been running without issues and crashes.
It does take an effort to migrate to SSD (you need a clean install of Windows and all your software), but it is really worthwhile.

wormbog wrote on 2/1/2014, 5:02 PM

Hmm, interesting. But I really don't think I have memory issues with my system, or if I do it is VMS12 causing the problem, not my system. But it sounds like the SSD setup you have is working great. Nice.

zocesu wrote on 3/3/2014, 6:27 PM

I absolutely confirm your issue as well as your frustration, having the exact same issue with movs from a Nikon P7700. In my desperation I even tried renaming h.264 movs to mp4, but of course with no effect (except you can see the thumbnail in Windows Explorer ;-).

Hoping so much that someone will find a real fix for this. I just don't get it, why movie studio needs to access all files at the same time, when putting them into the media bin. My guess is that the excessive memory use of FileIOSurrogate.exe is directly related to that. If one could tell Vegas to access the files only when it needs to, that might help.

lvd500 wrote on 5/20/2014, 1:21 PM

Has anyone solved the issue of "too many .mov files" causing black preview and rendering?

This is absolutely not a memory issue. I am using a new 64 bit machine with 8GB of RAM. The files I'm using are iphone 5 and less and average about 15 seconds. As in previous posts, there is an threshold the software seems to accept and when you go over that, the preview and rendering go black screen. Deleting any of the .mov files seems to bring it back. I'm using Movie Studio Platinum V13

trenzterra wrote on 10/20/2014, 7:48 PM

I have this problem too! Have a laptop and desktop with both 8GB RAM with Intel i5 2nd and 3rd generation processors and both exhibits the same problem with MOV files from my Nikon 1 J1.

In the end I found this tool that works fine: http://www.thinbasic.com/community/showthread.php?12273-V1-MOV2MP4-tool-to-simplify-mass-conversion-of-MOV-files-to-MP4-V1-2

It basically converts the container from MOV to MP4 format so no re-encoding is needed. Of course it's not the ideal solution but what can we do..?