Nigel O'neill
Forum Replies Created
-
I made the switch from XP to Vista (briefly) then to Windows 7 when it first came out. Gone were the constant hangs and inexplicable blue screens. Have not looked back since!
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Ron
Refer to post
https://forums.creativecow.net/thread/24/940930#940930
although it does not indicate which font was affected :-(, it is a possible solution, especially if the problem just started occurring.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
With my rig, I typically get a 1:1 render time. I work with HDV mainly, with some AVCHD and MXF files thrown in from B-cameras.
I do weddings as well on the side, and my longest render was 2.5 hours for 90 minutes of multicam footage, but my render was a 2 pass variable bit render set to Good.
For straight CBR renders I typically get 1:1 or less.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
I do tolerate user submitted footage, but only if it contributes to the end result. For example, I would include snippets from a phone or a hand held inferior camera for a high-school graduation DVD for ‘off the wall footage’, but would only do so if enhanced the end product in some way.
I also do back stage work for some theatre productions, and sometimes the crew get up to shenanigans when my camera is not around, so out comes my camera phone. Most people do not react to camera phones the same way they do for a ‘real camera’, and are likely to act naturally. I guess it is a case of making a judgement call as to whether including such footage adds value to the overall production. If it does not, leave it out.
I find it difficult to associate the delivery of high quality professional projects with cell phones and flipcams. Those words do not belong in the same sentence together 🙂
Whilst these devices can shoot in HD, such as the iPhone4, they are typically handheld (and wobbly), have lousy sound, contain massive amounts of picture noise in poor light, and pretty much run on auto for everything. Yuck!
They are a gadget gimmick IMHO.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
I have seen an editor experience this same problem. We used Nero to work around it, but the real fix came when the DVD burner was replaced (under warranty). With a different model, by the way.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
In your project properties, set the deinterlace method to blend. Render your output and see if the problem remains.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
They probably shot that on a Sony PDWF800 Professional Camera that cost $50K!
🙂
Although, if you are looking for a cinematic feel, the new NEX-VG20 camera with SLR lenses and a huge sensor can give you the cinematic depth of field look you may be looking for. The sensor is massive compared to traditional CCD/CMOS, hence it is able to provide depth of field. As a wedding videographer who shoots on auto, that might be worth a look. Unfortunately, I do a lot of theatre work where full manual control of iris, gain, focus, white balance and shutter speed is required.
Here’s a review. The author is pretty negative about the NEX-VG20 mainly because of ergonomics and lack of manual controls, but if that does not bother you, take a look:
https://www.eoshd.com/content/3898/sony-nex-5n-versus-fs100-and-nex-vg20-hands-on-comparison
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
[chrisabel noyes] “I use AVS video converter. Would you recommend that from now on i convert the MKV files into AVI?”
Chrisabel, the point I am trying to make is you don’t know what AVS Video converter is doing to end up with the AVI/WMV file, and whether it is adhering strictly to Microsoft specifications.
MKV is not supported by any editing program as far as I am aware, probably because MKV has an open specification and is a playback/player only supported format. The players are open source.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
[Dan Thompson] “Unless someone REALLY likes what you’ve done and DILIGENTLY tries to find and get in touch with you, nothing happens. I only had 2 contacts from the whole 7 years, and they wanted me to donate everything. Dan”
That’s the impression I get (re: donation), but I am an experienced member of a movie making club for amateurs, and what better way to get new inexperienced members upskilled than something that pays (a little) to produce a real product? We have sponsors (local businesses) and an energetic advocate who just needs the time of some reasonable talent. It pays the rent (sometimes), but as a hobby, is bonus.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
[chrisabel noyes] “Apart from the WMV, with were originally MKV files that i converted to WMV (but again, i’ve been working with these files for sometime and had no problem) “
WMV’s are a terrible format to edit in. I would avoid using WMV files and stick to AVI’s.
I suspect that the MKV to WMV/AVI conversion process may not conform strictly to the WMV/AVI specifications, hence your issues. I presume this is a 3rd party tool. Has it been updated recently? If so, the developer may have altered the conversion algorithm, which is why problems may be surfacing now, but not earlier.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6