[Jack Monkiewicz]

Thanks Michael,

I was hoping i didn’t have to dive into the black hole that is object buffers, and then try to compensate for them in AE, they just never look right when i do them.

Thanks for the help

[Jack Monkiewicz]

Hi adam, automatic keyframe isn’t highlighted, so i assume its not active.

[Jack Monkiewicz]

Hi Adam,

the spline is just a bezier spline on a picture i traced. Not sure if thats a primitive spline or not? the position points aren’t keyframed.

[Jack Monkiewicz]

Jim, out of interest what file type are you using in your project? I too have the dreaded low memory issue when ONLY using MXF’s, but apparently Steve would have me believe that my computer is broken and Vegas is fine.

If you can get advice from John Rofrano, it is generally very good.

Best of luck

[Jack Monkiewicz]

Steve, perhaps I do have a broken computer, one that runs every application faultlessly besides Vegas. Because that would be the only reasonable test right, if everything works, all of adobe, C4D etc etc, but Veags doesn’t. obviously its the hardware not the software…please! I would happily admit my hardware was the problem if it genuinely was, however your advice Steve make no sense, driver issue, fresh install will fix it, hardware issue….geeze!

Thanks for the advice Chris, I may try that in the future. At the moment i’m using MP4’s from the EX3 without issues. I made sure the clip browser was 2.6 and still had the MXF’s playing up. I also came across the fix of the preference setting’s you suggested and still had issues.

[Jack Monkiewicz]

Hi Steve,

The error that hundreds if not thousands of people are experiencing is that horrid ‘low on memory error’ that pops up at different stages for people. Mine happens when I attempt to render MXF’s. If i google search this error for sony vegas there is at least 30 pages of people asking about this error, offering fixes on youtube or simply giving up and letting others know that Vegas is bugged.

When I replaced my graphics card i obviously updated the driver that goes with it, so they were the latest version.

steve, you maybe 100% right that it is a driver issue, but i dont think is good practice by sony that clients have to struggle, wrestle with application trawling the net for fixes to issues that should not be there. you may argue that it is my responsibility to have the right drivers, i would argue that when i purchase a application all drivers and required software should be included or boldly stated where to acquire them to not cause issues.

is it okay for sony to have 100’s perhaps 1000’s of dissatisfied customer if 10,000 are happy? probably not the most effective way to compete with FCP or MC. as we all know, unhappy customers are much more likely to tell people of their experience than happy customers.

your last comment makes no sense to me if you’re suggesting its a driver issue, why would it be resolved with a fresh install of windows and vegas? and if this is what is required to run vegas my goodness gracious me.

[Jack Monkiewicz]

Thank you Stephen for your comments, however you have made some huge assumptions which aren’t accurate.

My system is in good working order, Sony Vegas is the only program which ever crashes. I also used After effects, Photoshop and various other applications other than adobe which have never, ever crashed or had issues.

All my drivers are current and up to date, i have replaced my video card twice to see of that was the issue.

I also have searched both this forum and the net generally for fixes to these issues, and the result is the error is probably more common than you would like to admit, probably hundreds maybe thousands of people experience these issues.

so far i have tested mikes suggestion that MXF’s converted from the older clip browser (2.0) could be playing a roll in the error. I have done a huge test render with the raw MP4 files from the EX3, added a number of effects to all the clips and rendered, so far so good.

so by the powers of deduction MXF’s are the issues, blame it on sony’s clip browser or editing software their is a fundamental problem.

[Jack Monkiewicz]

One way would be to have the folder with the clips open and vegas open, then select the top clip in the clip folder and scroll down to the last clip while holding shift and select that too. drag and drop in to the project media tab in vegas.

Or the another way is go to file – import – media, then choose the first clip, hold shift and click on the last clip, then select open

[Jack Monkiewicz]

not sure as the footage is given to me on hard drives. i’ll enquire into the version and confirm, if that is the solution i’ll dress up in a fairy suit and dance around the garden, because i’m honestly loosing the plot.

[Jack Monkiewicz]

Well apparently clips transcoded from an Sony EX3 through the XDCAM clip browser are riddled with issues.

two other people i know of have similar issues with the MXF format from EX3 downloads. Never had any issues like this when we used avi’s from tapes.

I can appreciate that no software is bullet proof and may have the occasional hiccup, but i cant render MXF’s without changing all the settings multiple times, making sequence super short and then nesting them. Otherwise i get the much hated ‘low on memory error’, and i can forget about adding effects.