There's actually a number of DVD burning programs in the Mac AppStore. Most seem to have mediocre reviews though.
Read More...

DSLRs do present some challenges.
Audio: generally not very good preamps but there are solutions ranging from Juicedlink,Tascam attached recorder, Zoom 4N or even a Rode shotgun mic for DSLR.

Canon DSLRs with the free Magic Lantern firmware get around the record duration limit for several of their cameras.

The Lumix GH3 doesn't have a record limit. It's a micro 4/3 sensor (close to super 16) rather than APS-C (close to super 35 which has potentially shallower depth of field).

I believe there's a hack for Nikon cameras to open up the record limit.

The other issue is that there's a desire to record a "clean" HDMI out signal to an external recorder to get around the limitations of the H.264 codec (impacts grading for example). Each of the above cameras have a way around that. Some Nikon models now have clean out for example.

Which DSLR to buy really depends on budget and desired feature vs limitations.
Read More...

I actually had been getting by with Photoshop CS2 for some time. I did have a job where I needed to check a client supplied file and used the 30 day free trial of CS6 for that. Since there's no upgrade path from CS2 to CS6 I was actually contemplating buying Photoshop CS6.

With some irony, I'm not reluctant to get the still available CS6. For my own work Pixelmator (or Acorn?) may be fine. For client compatibility I'm faced with ugly options since I really have not motive to subscribe to Photoshop CC. I really don't like the idea of paying Adobe every time I need to check a client file. I really don't like the idea of buying Photoshop CS6 as it may not be compatible with a client created CC file.

I certainly do hope my clients look to alternatives.

I do hope Pixelmator improves import compatibility even if it involved purchasing a plugin.
Read More...

My main concern about Pixelmator is importing client Photoshop files.
Often I have to check client PS files for issues or minor fixes.
Of course this is all the more reason to run from CC. I really can't see subscribing to CC primarily to check and tweak client files. I do hope Pixelmator improves PS import compatibility.
Read More...

I haven't worked with GoPro 3 files extensively yet but I have used them.
On my 2008 8 Core MacPro if I import them directly into FCPX I have no problem editing them but skimming them skips significantly. This makes it hard to find exact points in shots. I compare this with AVCHD which I've also worked with natively (both are H.264) but skims fluidly. My guess would be something about the GoPro GOP structure is a bit harder to handle natively. On a newer Mac (quad i7 Sandy or Ivy Bridge) it might be more responsive.

You can import the files directly though. If it doesn't handle well, you can transcode to ProRes within FCPX or you can set FCPX preferences to do that on import. Since FCPX does its own transcoding there's no need to use external transcoders.

I haven't tried using GoPro Cineform Studio to transcode to the Cineform codec though. It would be an interesting comparison between it and FCPX's internal ProRes transcode.

But you can import directly in FCPX and/or transcode to ProRes in FCPX.
Read More...

This can be tough one because really depends on the target audience and what you think their internet connection can handle. The other big factor is the content. For example, fast action sports would need a higher data rate (resulting in a larger file) than a video of talking heads.

Jan Ozer did an article which is a bit dated but he inspected some YouTube videos to see what data rates they were using.

www.streaminglearningcenter.com/articles...-new-hd-formats.html

The data rates might be a bit higher now but one way to check is find a YouTube video with similar content to yours and pick the frame size(s) you're interested and download the files and check the data rate setting. You can use a free app like MediaInfo (what you see Ozer using in his article) but if the files can play in Quicktime after downloading you can use Show Movie Inspector to see the data rate used.
Read More...

I think some wedding videographers are delivering files with file players like Western Digital TV or Roku and build in that cost instead of disc. The couple feels they're getting a "gift" since they can use the player for other things. I know that's not quite the same as doing a run of 20 discs but one can deliver files via DropBox or equivalent.
Read More...

Tom Wolsky wrote:
That's assuming the settings that worked in one component are fine for the rest of that component. Ideally I'd like the Loudness Audio Enhancement analyze a specific component set.

I guess this is where we get into the feature requests for some kind of aux bussing. The unique issue with Audio Components is that, unlike audio generally, you can make an individual series of components (i.e. all Camera 2 Ch2) into a Compound Clip.

I brought this Audio Component issue up because, while I've seen post written about compound clipping the audio for processing and the feature requests for audio bussing at least, I haven't seen anyone talk about the specific issues around Audio Components because they can't even be Compound Clipped for processing.

I think I may need to formulate an elegantly written feature request.
Read More...

Working on a two camera multicam shoot of a panel discussion with audience participation. The result is that I've checkerboarded the editing with audio components from the two cameras.

What I'd want to do is run each component through either the Loudness Audio Enhancement or through the Audio Compressor plugin.

Much to my chagrin there's no way to compound clip a single audio component type (Cam 1 Ch1) and, apparently, no way to command click such files to apply the same Enhancement. In the latter case as soon as one selects a second clip the Enhancement feature is no longer available.

I'm guessing my only options are to either Break Apart the Audio (Ugh) or apply the processing one clip at a time.

I'd love to hear of any other workarounds.
Read More...

For those working with the Beta, I'm curious how it plays with other plugins or build in FCPX features. It seems the video demo shows mostly in built features of the plugin.

For example: how well does it work with the Color Board for tracking a matte?
How well does it track when masking part of a clip (in story line, connected, compound clip) for an applied effect?
Read More...

Makki wrote:
Yes, they're using the discontinued MyCometG3 x264 component. I suspect that will be broken with 10.9.
Read More...

I think in order to learn "modern" English one must watch a group of Tweeners Texting. One may come to understand there's not a word or phrase in the language that can't be expressed in 4 characters or less.
Read More...

BTW I find one good method of trouble shooting is creating a New User Admin account. That pretty much assures a completely fresh set of user settings and preferences. If you still have troubles there then it's a system, not user based problem.

Another thing to do, is to use Apple's Combo Updater for the OS as it does a much cleaner job than the software update through the App Store. Sometimes that can take care of system related issues.
Read More...