Problems importing many media files at once

MisterRider wrote on 8/12/2012, 7:50 AM
Hi everyone,

I am a media professional and long time Vegas (11) user with a peculiar problem. It appeared this week when I started importing my video files taken on my iPhone 4S during summer vacation. I plan to edit a home video together using these files. They are standard HD files taken at the 4S's native resolution (full HD) using the AVC codec - ie no tampering or transcoding - just drag and drop. There are by no means a huge amount of files - less than 400, with the total footage weighing approx 25 Gb.

The first problem occurs during the actual import (via the Import dialog or via drag and drop). When I select multiple files and import them, Vegas freezes. I'm presuming this is whilst creating the peak (SFK) files - but there is no dialog to say that this is what's happening. I find I'm able to import maybe 10 files at a time without Vegas freezing - any more than that, and I have to re-start the program. So, in order to import 300 files, I have to do ten different import operations!

Now, once the files are imported, a second problem occurs: when I drag some of the media files to the timeline, either they are greyed out in the Media Manager, or they simply only let me put audio up on the timeline. The files will also not open in the Trimmer, nor will the play on the timeline. Sometimes restarting Vegas will fix the problem temporarily, sometimes not.

A third problem now occurs when re-opening the project file: I get a dialog box that gives the following error:

"An error occurred while opening the media file: xxxx.MOV
What do you want to
o Specify a replacement media file
o Ignore error and leave media file offline
o Idnore this and all subsequent errors "

This occurs starting around file 240-ish - but even if I re-associate all the rest of the files (the last quarter in the list) I still cannot access or play those files within Vegas.

Now, if I delete a number of files (say about 350) from the project and re-open, it works fine.

Also, I've tried re-importing manually, dragging and dropping directly to the timeline, and after around 30 files, only the audio track will import to the timeline. For example, I drag and drop 000.MOV thru 030.MOV to the timeline - good; works. Then, I grab 031.MOV and drag it to the timeline - only the audio appears. But then, I start a new project, drag and drop 031.MOV to the timeline, it works just fine!

I'm on a 64 bit system with 16 Gb of RAM. I'm running Vegas Pro 64 bit. I've had (SD) projects previously with *many* more media files than this. I have my dynamic RAM preview set to 512K, I've tried the FileIOSurrogate kill, and no, my files aren't corrupted.


What am I not doing right here? Vegas is essentially unuseable.

Any help appreciated!
Thanks,

T

Comments

set wrote on 8/12/2012, 9:08 AM
I always import lot of media files at once. I usually import them from standard Windows Explorer.
Yes, once you drag in, the Vegas may get freezes. Just keep click, don't release it, wait until Sony Vegas run again.

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

videoITguy wrote on 8/12/2012, 10:14 AM
Tim - you have given quite an explanation and the detail is much appreciated of your dilemma.

Many people do file reports that a file here or there does cause timeline freeze. 99% chance this is always caused by something non-compatible or even non-standard about the certain files. Again many people report this so it is altogether very common.

In your case I suspect your source device is culprit - I have no idea how it creates file metadata - but I bet it is hardwired into the device..hence it likely does not deliver what Vegas actually accepts.

You should try importing your files into a transcoder (read that different software) - I have used Movavi for this purpose. It translates files into standards that other programs can accept.
OldJack wrote on 8/12/2012, 11:42 AM
Sounds like it could be a memory problem.
farss wrote on 8/12/2012, 4:06 PM
Nothing corrupted, no hardware problem, just how Vegas has worked and continues to work.
For some reason Vegas wants to scan all the files before it gets to the building peak files (SFK). If you try to do anything else while it is doing this it may get lost.
My procedure to get around this is:

1) Select the files in the Explorer window.
2) Make cappuccino.
3) Drink cappuccino.
4) Then RClick the files and select "Add to project media"
4) Have a three course meal and several cappuccinos while it builds the SFK files.

By comparison PPro takes just as long before I can get going however it avoids the appearance of being locked up and no amount of prodding seems to cause it to actually lock up. With Vegas, you've just got to be patient or you can lock it up.


Bob.
MisterRider wrote on 8/12/2012, 9:03 PM
Thanks for the response, IT Guy. My source device is the ubiquitous iPhone. Of all the devices, this one is surely one of th most common, so I'd like to assume that I can edit its native footage! It films in full HD and uses the (very standard) H264 codec in a MOV container. Also, like I said, I can import 30 or so clips no problem- so, I don't think the file type is the problem. I'm running 16Gb (yes, sixteen) of RAM, so there's no way it can be a memory issue.

Care to try again?
Please!

:) T
MisterRider wrote on 8/12/2012, 9:07 PM
Lol Bob- I like (and have tried) your solution. I have managed to coax Vegas into building all the sfk files without crashing. But AFTER that- in the second part of my problem- Vegas disassociates the files (gives the error) and will not reassociate them. Nor will it preview video. Nor will it allow some clips to be put on the timeline from the Media Manager. However, when I reduce the number of clips in the project (from 300 to 30, say) it works. Sorry, but I can't just have 30 clips in my project - plus I'm running 16Gb of ram, just for this purpose.

Thanks for the speedy response- help!

T
PeterDuke wrote on 8/12/2012, 9:27 PM
When I drag a big group of AVCHD files to the timeline from the explorer pane, apparently nothing happens for quite a while (many seconds). Then an outline of the clips appears on the timeline. Then the video thumbnails start to appear in each clip. Then the audio peak files start being created.

MOV files should behave similarly, but have to operate via Quicktime. Have you tried using earlier or later versions of Quicktime?
PeterDuke wrote on 8/12/2012, 9:35 PM
I try to avoid having too many clips on the timeline at once because it slows Vegas down. More than 1000 DV AVI clips used to cause problems, and 400 MOV might be just as bad. I therefore try to work on smaller parts and combine at the end. I am able to do this with AVCHD and Vegas 9c because that version smart renders AVCHD.
MisterRider wrote on 8/12/2012, 9:47 PM
Hi Peter. I am using the most recent version of QuickTime which should be compatible. As I said, my problem now is trying to use more than 30 or so HD clips on the timeline without Vegas disassociating them or refusing to play the video.
MisterRider wrote on 8/12/2012, 9:53 PM
Hi Peter- while I appreciate the response, I think we can both agree that "400 MOV might be just as bad" is just speculation. I'm running 16Gb of ram. Does anyone know if there is a max number of clip? I doubt it, as Vegas just seems to reference them, as does any NLE. Is there a theoretical point at which performance seriously degrades? And moreover- my clips wont even PLAY on the timeline when there are more than 30 or so. Surely the max is nowhere near that. But now *I'm* speculating. :)

Thoughts?
PeterDuke wrote on 8/12/2012, 9:54 PM
I suggest you try earlier versions of Quicktime as well. Sometimes Apple comes out with a new version of QT which doesn't play well with Vegas.
videoITguy wrote on 8/12/2012, 10:00 PM
To the OP - my original post is as good as where I posted IT in the earlier part of this thread. You are importing a container called MOV?

MOV is a form of Quicktime that can have many variants of codec within the container itself. It only takes a slight variant in the file's metadata or even the variant of the name of the extension of the file that can and will play tricks on the device (here that be Vegas) to read it properly. I think you better try transcode as I suggested.
MisterRider wrote on 8/12/2012, 10:34 PM
Thanks for the response, ITguy. I'm not sure what you mean by your original post is "as good as where I posted IT." As for the MOV extension/container, it was actually invented by Apple, so one can only assume that the meta data is not playing any "tricks" as it is a native format.

But again, I must stress that the importing of the file is only part of the problem- and one for which I have found a work-around. So, I have my tricky MOV files imported- all 300 - 400 of them. Upon project re-load, Vegas will disassociate them from the project and give me the aforementioned error. However, when I reduce the number of clips, they will play fine. But I seem to be reducing to a ridiculously small number - thirty or so. With 16gb of ram, we can count memory issues out. So, If the clips will play fine within another context (a smaller project) I don't think the meta data has any bearing.

Over to you,

T
videoITguy wrote on 8/12/2012, 10:42 PM
I can not be sure of what you are facing but there are many variables so I only make claim to what i have stated.

I seriously consider your references to "understanding" what container, format, and codec all really mean to be sort of short of the mark.

I see your problem can likely be fixed by re-wrap of the container -that could be as simple as renaming the file extension - BUT more likely there is a metadata problem caused by the hard-wiring of your phone device. Try transcoding and see if 31 files or whatever play better.
Zeitgeist wrote on 8/13/2012, 12:25 AM
I import 500 sony avchd m2ts files to vegas11 without any problems. Timeline takes about 15 minutes to load & build peaks. I have 8 gigs of ram.

Try installing whatever software that came or is available on the web for your phone on the vegas computer. Load only one clip on the timeline to see if things improve. Use the File import dialogue. In preferences turn off media goes offline.

Hope that helps in some way. Good luck.

If all else fails use a mac & lose vegas.
videoITguy wrote on 8/13/2012, 12:54 AM
IPhone 4s hardwired for these video and audio specs-

Video formats supported:
H.264 video up to 1080p, 30 frames per second, High Profile level 4.1 with AAC-LC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; MPEG-4 video up to 2.5 Mbps, 640 by 480 pixels, 30 frames per second

Simple Profile with AAC-LC audio up to 160 Kbps per channel, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; Motion JPEG (M-JPEG) up to 35 Mbps, 1280 by 720 pixels, 30 frames per second, audio in ulaw, PCM stereo audio in .avi file format.

Audio formats supported:AAC (8 to 320 Kbps), Protected
AAC (from iTunes Store), HE-AAC, MP3 (8 to 320 Kbps), MP3 VBR, Audible (formats 2, 3, 4, Audible Enhanced Audio, AAX, and AAX+), Apple Lossless, AIFF, and WAV.
farss wrote on 8/13/2012, 3:04 AM
"I'm running 16Gb (yes, sixteen) of RAM, so there's no way it can be a memory issue."

The opposite is actually true, the more memory you have the more likely you are to have a memory problem. RAM is quite unreliable plus as buss speeds run faster errors are more likely even if the RAM itself is fine especially using unbufferred non ECC RAM, there's a reason enterprise class PCs use that kind of memory.

As you load more clips onto the T/L it seems Vegas has to buffer more data which in turn uses more of your RAM. Putting two and two together it could be a RAM problem. There's certainly nothing to be lost running a few passes of Memtest.

The other thing I've found helpfull is reducing the number of thimbnails. I use head, mid, tail and that's enough for me to see what I'm working with. The other tip which may help is to reduce the amount of Preview RAM. Before doing any of this though run Memtest. I'm inclined to think nothing I've suggested is going to fix your problem but it's worth a shot.

Bob.
Paulo Ribeiro wrote on 10/6/2015, 12:36 PM
I've allways had problems importing a large number of files at once, it doesn't matter if they're AVI or MOV or whatever. At a certain point Vegas (Pro 8) gives me an error message and freezes or crashes. I don't even care anymore what it says. I think the problem has to do with codecs with high compression ratio, like H264 or any other. The solution i found is to join all those clips into one and import it to the timeline. It works, at least so far. The problem is i have to cut everything again.
rmack350 wrote on 10/7/2015, 12:09 AM
(Didnt realize i was replying to a 3 year old post. A waste of effort.)

Rob