[Terence Kearns]

I’m having other issues which is impacting on my ability to edit video.

With some projects, Vegas takes a long pause before responding to the mouse. This happens when I switch away from the application and come back. It also happens when I first load the project. I didn’t mind having to wait around 10 seconds sometimes for the GUI to come back, but now I’ve been waiting for about 15 mins and still nothing.

I sometimes use veg files on the timeline – which seems to exacerbate the problem. But it’s hard to pin down.

I’m running an i5 processor with 8GB of ram and a GTX580. As you can see, there is no utilisation. However taskmanager says vegas is using 198MB of memory (top of the list for mem usage) and dwm.exe (Desktop Window Manager) is using 132MB (second in the list).

[Terence Kearns]

Thanks Frederic, I took your advice and followed your tutorial but I ran into a couple of issues.

I’m running windows 7 (x64) with Vegas Pro 11 (x64)
Visual C# 2010 Express with .NET framework version 4

VC doesn’t automatically references system.windows.forms, but no problems, I manually went and added the reference. I also went and added the reference to Sony.Vegas.dll

The DEBUG tab in the project properties does not have a
“start external program”

I had to assume some things
– that the project is to be a “class library???”
– that Sony.Vegas.dll is okay to be targeted with .NET version 4???

My debug tab has a section called “Startup Options” with 3 fields
– Command Line Arguments (text area)
– Working Directory (file location field)
– Enable the Visual Studio hosting process (checkbox)
…that’s it.

[Terence Kearns]

Thanks. The last and only time I used C# was to write two windows services as part of an automated lecture streaming application suite for a university. I just stumbled around until it worked (with lots of try/catch statements). I never formerly learned the language. I took a task-oriented approach and spent a lot of time on MSDN.

And now I’m stumbling around just trying to get Hello World extension up and running. PHP was my bread and butter, and of course some Javascript, but I want to get straight into writing an extension to house all my miscellaneous scriptings.

[Terence Kearns]

Thanks…

Just read the FAQ and now installing the free Visual C# 2010 Express from Microsoft.

[Terence Kearns]

Berry does offer that service too…

[Terence Kearns]

Thanks Kelly,

In answer to your query Mike, I have been in contact with Barry (the trainer) and he says that the version 8 course is pretty comprehensive although it is not up to day, most of the stuff still applies. I guess that goes without saying. But that’s all that seems to be out there at the moment.

Seems to me like there’s an opening for someone to really nail Vegas Pro 10 comprehensive training.

I’ll probably end up buying his comprehensive version 8 course (14 hours of training).

[Terence Kearns]

Thanks for that.

Certainly looks good for a person who is starting out.

I wouldn’t mind if he did an intermediate to advanced course. I think I have 90% of his Vegas 10 course sorted.

Looking more like I will just have to invest time trawling through the manual to make sure I’m not missing out on features that will be very helpful to my career.

For example, I have 16 hours of recorded event on 3/4 cameras. I was doing a multicamera edit and then going back and putting blends in where there were cuts – only to discover that all I needed to do was hold down the control key while changing cameras and the default blend would automatically be applied. That’s the kind of knowledge I don’t want to be missing out on.

[Terence Kearns]

How did you go? What did you end up getting?

I got an AF100 recently, and have no problems editing in vegas.

[Terence Kearns]

The atomos Ninja is awesome…. if you don’t have a 5DII. I believe that the EOS cameras in video mode do not output a signal that is free of overlays (at least the red record dot). They indirectly mention it in their FAQ on the atomos website.

On on this thread because I am looking at setting up a videography/photography business. I’m already an experienced photographer who owns a 5DII and a 7D. I’m currently doing some research with a view to getting a more purpose-built video camera, and colour sampling capability is way up on the priority list for me. I imagine a video camera and a hdslr would compliment each other well.

I looked at this video on Up-Converting EOS video footage
https://vimeo.com/19908622

Seems like a lot of extra work, but it does seem to be effective. I’ll probably do mostly wedding work, but I have also taken on a couple of other projects already. I’ll probably do greenscreening at some point.

I have an IT background (software development) and with respect to “how can up-sampling add information that’s not there”. Think of it this way, the information is there, it’s just not accounted for in every frame (due to the use of tweens) with the h.264 codec. It’s been suggested to use a codec (like ProRes) by getting a transcoder to account for the colour information in every frame (or at least a lot more frequently). I don’t know ProRes that well, I’m speculating. So that addresses the perception of “adding” information in the temporal dimension.

In terms of the 1:4 ration of luminance info to chrominance info, this would logically and clearly create problems when chrominance info (accuracy) is relied upon to perform some kind of mapping – ie, chroma keying. As some of you know 4:2:0 and 4:1:1 are all examples of a 1:4 ratio. 4:2:2 is an example of a 1:2 ratio and 4:1:1 is 1:1. Ideally, this is what you would use for accurate colour mapping/translation in the 2D plane.

Once again, by Up-converting, you may not be “adding information”, but you’re giving the file a finer (chromatic) resolution which can be used by the mapping software (effects software) to chop the image up into smaller blocks – and hence having finer edges for chroma keying.

Seems to me that the software is somewhat “lazy” (in terms of processing work) about “accounting” for every pixel in every frame on the fly. Up-Converting is just a way of “pre-accounting” to save the software from needing to rely on the CPU for extra real-time calculations.

So Thomas, Up-Converting is not adding information, it’s about making the mapping task easy enough for the Effects software to do a “propper” job of slicing up the pixels.

I suspect that as CPU processing power increases, the better video editing software will have a processing engine that “accounts” for every pixel on the fly regardless of input codec. Right now they need to be programmed to be “lazy” about it for reasons of practicality.

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.