Rick Shorrock
Forum Replies Created
-
Yep! This works particularly well if you use the DSLR Controller app. That is, if you can get past the 15fps frame rate during live view.
-
I’ve used it mainly for composition during moving shots and the motion lag doesn’t bother me at all. But having the tablet hooked up helps me by keeping my eye away from the magnifying eyepiece that I have attached to the flip out screen on my DSLR.
-
How about this: Get a tablet or a smartphone, a hot shoe adaptor and an app called DSLR Controller and use that as a monitoring device. The app is 8 bucks, and it lets you not only monitor the output of the camera, but control the camera’s functions as well. I use an Android 9 inch tablet with DSLR controller this way, and it really helps.
-
Thanks for that! I appreciate it!
-
Not to hijack the thread or anything, but nesting projects appears to create it’s own problem over time. After having a nesting problem using ToasterEdit on a Newtek Video Toaster system at our local television station (seemingly black video after final rendering of projects nested within one another), I was told by Newtek Support that after several nested projects, that you need to go into the AppData folder and delete pre-render files, because the system gets confused as to what file to use in the final render. I followed his instructions and it stopped the problem. I was told this will also stop the same problem from occurring within other NLE’s.
-
Got it! Seems to load faster than the previous version.
-
Exactly my point, Angelo. Magic Bullet Looks and The Neumann Films products do essentially the same thing, just in a different manner. I’ve noticed that in most everything film, there’s a way to do something and spend a lot of money, and there’s a way to do something really similar and not spend so much. And that was my point behind the post.
-
I think there’s a few things you can still try. I don’t know if they’ll help you troubleshoot the problem, but try a RAM preview of your timeline before you do your render. Make sure your project properties match the properties of the clips in your timeline before you do so. Then when you pick the correct 720p template that you want, modify it and change to bit rate to something like 4Mb/sec for a constant bit rate. But if there’s a lot of detail and fast movement in your video, you can use variable bit rate with a high at 10Mb/sec and a low side of 4Mb/sec. Vimeo and Youtube love the AVC/AAC settings like this in an MP4 wrapper, and I find it’s pretty much all I need for 720p delivery. This may be a good compromise for you if you have a project that you need to finish quickly, and can’t wait till you get your problem completely solved.
-
Wow…you apparently know your stuff. I had been reading that AMD was going to start combining CPU with a GPU, but had never thought of buying one till I saw the deal on NewEgg’s site. But it seems to work well for me with editing, so with the price being so low, I’m pretty happy.
-
Either way, that’s a sweet system. I used to edit on an AMD dual-core system…slowly! The CPU was slowly overheating, so I bought an AMD APU (CPU and GPU combined)- based kit. It’s got the AMD A10-5800K Trinity 3.8Ghz APU with DirectX 11 Graphic AMD Radeon HD 7660D, MSI FM2-A75MA-35 Micro ATX motherboard, 16Gb DDR3 RAM and LITE-ON DVD burner. And the kit came with an ultra high gloss Micro-ATX case with 400W power supply. I spent less than 350 dollars for this kit, with free shipping from NewEgg. And it appears that Vegas approves of the APU! If I render my timeline (on Vegas Pro 12) with OpenCl or CUDA assistance, the timeline renders significantly quickly!