Comments

malowz wrote on 5/31/2014, 5:59 AM
try to disable "close media files when not the active application" on preferences > general
Zayed wrote on 5/31/2014, 3:10 PM
This time it's freeze ..... at less before become white clips
Now it's freezing :(

Do you know other solution to fix this problem ?
malowz wrote on 6/1/2014, 6:38 PM
the codec is updated?

how much memory your pc has?
Zayed wrote on 6/2/2014, 2:25 AM
Memory
Memory Type DDR3
Memory Size 32 GBytes
OldSmoke wrote on 6/2/2014, 7:59 AM
It seems to me Vegas is not able to create the peaks either, Make sure that your temporary Vegas folders are ok and on a drive with sufficient space. If all of it is located on a spinning disk, try to Defragment the disk.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

vtxrocketeer wrote on 6/2/2014, 3:08 PM
In Vegas 12, I encountered a limitation on the number of DNxHD clips that Vegas would accept. If I recall correctly, that number is about 50, regardless of clip length. Anything over 50 produced the erratic behavior that you mention. I won't speculate as to the cause, but it appeared to be related memory, as my Vegas projects with lots of DNxHD clips consumed almost the entirety of my available RAM.

I finally transcoded to Cineform for those projects in which I would otherwise use more than 50 clips in the media pool.
Zayed wrote on 6/4/2014, 12:27 PM
How to transcoded to Cineform ?
NormanPCN wrote on 6/4/2014, 12:37 PM
Anything over 50 produced the erratic behavior that you mention.

Could be a Quicktime thing.
Zayed wrote on 6/4/2014, 12:59 PM
SO I have to download the last version of quick time from apple.com ?!??!
rs170a wrote on 6/4/2014, 1:06 PM
What version do you currently have?
Newer versions may not always play nice with Vegas so be aware of that issue.

Mike
rmack350 wrote on 6/4/2014, 1:49 PM
Vegas uses FileIOSurrogate to load files from 32-bit codecs or subsystems or whatever. Apple Quicktime is 32-bit. Since it is 32-bit it can't use more than 2GB of memory, and neither can FileIOSurrogate.

If you open task manager you'll probably see FileIOSurrogate using lots of memory.

I also use a lot of quicktime media but it's all 720p DVCProHD (tape-based), which is much like a DV codec. FileIOSurrogate uses a lot of memory but I can easily load 200 or more Quicktime files into Vegas. I've never hit a limit. My system has a total of 6GB installed.

I'm going to assume that you're DNxHD footage just requires FileIOSurrogate to use a lot more memory. A solution for you might be to use something other then DNxHD, preferably avoiding Quicktime. Maybe there's a better solution, but it's not coming to mind.

Rob
Zayed wrote on 6/4/2014, 1:54 PM
I install the last version of DNxHD and Quicktime and still the problem show up to display black clips

the funny thing that I divide the projects file .... like Part #1 in project and open a new project called part #2 and it's work but this not RIGHT ..... I want it the hole clips in one time line ..... my project duration is One min .... just one min

My PC is good .... how I can increase the memory ?
vtxrocketeer wrote on 6/4/2014, 3:21 PM
Maybe there's a better solution, but it's not coming to mind.

How about the one I mentioned? I already suggested transcoding the DNxHD clips to Cineform avi's. (Or Lagarith, which is free.) Ah, but here is a possible catch: I used Cineform's old, creaky but reliable NeoScene to perform the transcode. Obviously, if Zayed can't get the DNxHD clips onto a Vegas timeline in the first place, he can't use Vegas to transcode.

One kludge of a workaround would be to load, say, 25 DNxHD clips into a project, transcode, rinse, lather, and repeat.

My DNxHD clips are recorded at 220 MBPS. They are huge, and since most of my work is stage shows ranging 1 - 2 hours long, I have many gigabytes of DNxHD clips on my timeline. But I have ONLY 1 - 4 total clips in my media pool, and Vegas does not balk. It just seems to have a real problem with the number of individual clips over ~50, which I do not approach for my normal fare.
rmack350 wrote on 6/4/2014, 8:00 PM
How about the one I mentioned?

Yours was the solution that I could think of. Nothing better came to mind. Transcode out of DNxHD to something else.

I have no idea if this problem is specific to DNxHD but he's going to be limited to 2GB of memory if he uses Quicktime, or probably any other 32-bit codec.

Rob

CJB wrote on 6/4/2014, 8:54 PM
Your project is 1 min long but you have 50 DNxHD clips? How long are the clips total in GB? I imagine that since Vegas does not create subclips that you are loading the entire length of your 50 DNxHD clips not the edl points that show up as events. In otherwords if your DNxHD file is 10min at 20GB and you only use a clip that is a 2 second edit VP probably still loads the 20GB into memory. That may be a lot of memory since they are big files.
john_dennis wrote on 6/4/2014, 9:05 PM
If the issue really is the number of files that can be handled, have you considered creating multiple projects with about 20 clips on the timeline then nesting them into your project to produce the edited version?

Or you could put 20 clips on a timeline and render to new track using Sony MXF HD422 1920x1080-24p 50 Mbps. It should give you respectable results and would be a lot quicker than being dead in the water.

In the example that you showed, the cursor was at 23 minutes?
Zayed wrote on 6/5/2014, 1:00 AM
But I never face things like this in Avid media composer !!!!

My total clips that I shoot with Black Magic 4K is 555 Clips .... each clip not more than 1 min or 2 min >

My PC is good so I all ready convert the 4k Clips to DNxHD !!! and I spend a lots of time for edit after that I face this problem and I can't re-edit again because of time !!!

What the best solution for me ?
ushere wrote on 6/5/2014, 2:47 AM
ah, 4k!?

now we're talking....
vtxrocketeer wrote on 6/5/2014, 8:04 AM
Do you mean to say that you have 555 DNxHD clips at 4k resolution, each clip at least 1 minute, making for an attempted 9 hours of 4k footage in your media pool?!

Now you have at least two or three solid suggestions in this thread for getting your project completed.
john_dennis wrote on 6/5/2014, 8:28 AM
"[I]...and I can't re-edit again because of time !!![/I]"

When time is of the essence, I usually try to work within the limitations of the current bug rather than try to fix the bug and miss the deadline. The problem definition is not complete, only the symptoms.

I would select all the portions of the timeline that show normally in the preview and render that to a new file using DNxHD or whatever.

Take the newly rendered file into a new project and try to add the additional clips until the project is complete or the bug shows up again.

File a bug report with SCS. We are not developers here. If Vegas, DNxHD or Quicktime is broken we're only going to be able to diagnose and possibly arrive at a workaround while someone else fixes the underlying problem.

Zayed wrote on 6/5/2014, 9:20 AM
You are Right John but it's really sad

I have 555 Clip ( HD 1080 DNxHD ) and in my half edit (30 Sec) I just use 25 Clips only !!!

and this black thing show up !!!!

I will send a message to SCS and I hope they can fix it :(


No one have other solution ?
musicvid10 wrote on 6/5/2014, 9:53 AM
DNxHD in Vegas uses the Apple Quicktime libraries for MOV decoding.
The Quicktime libraries for Windows are still 32-bit, regardless of your OS.
In the real world, the chances of Sony writing all its own Quicktime libraries for its products are pretty slim -- Apple and Sony compete in the same markets.
john_dennis wrote on 6/5/2014, 11:04 AM
If the problem really is the number of files and you want to keep working in the same project you might consider this:

Go back to the 4K source and render the last few working files and all the additional files that failed before to one new DNxHD file and add it to the timeline instead of all the smaller files.

I don't want to apply a value judgement to what's sad or not.