Wednesday, March 4, 2015

Dealing with Convergent Design Odyssey Q+ in post

We've started using the Convergent Design Odyssey Q+ to record directly to ProRes 422.

In addition to the more robust codec, we wanted to save time as well.  But there are a few things that we didn't expect.

For one, it records clips in sections that need to be assembled in post.  

CD has an app for that, the "CD Prores Transfer" available here:
https://convergent-design.com/software.html

From CD website:
"The ProRes Transfer Tool copies and combines Odyssey 7Q & 7Q+ ProRes (.mov) clip files into a single file.

Odyssey 7Q & 7Q+ ProRes files have a 4GByte size limit within the Odyssey, therefore any ProRes recording on the Odyssey that exceeds approximately 2 1/2 minutes will create more than 1 ProRes file for that clip.

This tool allows to have each ProRes clip as a single file rather than multiple files.

This tool also optimizes Odyssey 7Q & 7Q+ ProRes files for playback efficiency on a computer and in editors."

I wonder what else except assembling the tool does to optimize and make playback more efficient?

The thing is that this unexpected step makes the post slower, as one needs to process the original Odyssey files before editing and create a new set of files. Which by the way doubles the amount of data.

Second, we use the Analog input to record reference audio in order to facilitate syncing when the audio recorder is not using Timecode. FCPX does that fairly well.

But we found that the audio is 3 frames early in the recorded ProRes files. So that's another step to adjust the audio by +3fr. slowing us down as well.

Apart form these two quirks, so far so good.

Monday, February 16, 2015

DaVinci Resolve LUTs (on Mac)

To use LUTs with DaVinci Resolve, copy them to:

HD / Application Support / Blackmagic Design / DaVinci Resolve / LUT


Restart Resove for the LUTs to appear in the drop-down menus.

Note that the folder structure is respected, that's a great way to keep your LUTs organized.

Thursday, February 12, 2015

Adobe Premiere Pro Merged Clips export without audio

This is a problem that's been there since at least August 2012 !

HELLOOOOO????  Adobe what the ???  TODAY the problem STILL EXIST !

It's like Photoshop not rendering certain colors, "SORRY the red does't work folks."


It was supposedly fixed in PP 2014.0.1, but clearly it's still there in 2014.2 (v8.2.0)


• Exporting merged clips could generate silent or missing audio
Try it: merge a clip with some audio, Export the Merged Clip to AME, it renders SILENT.

Using Queue Export via AME, or direct Export, same thing.  So clearly this Premiere BUG is still there, or it CAME BACK which is even WORSE.


No audio on export

This question is Not Answered.

 Lockwood Media Group Aug 27, 2012 7:31 PM


I'm baffled by this problem and really need to find a solution ASAP. I am using creative cloud, and files fed directly into media encoder are exporting silent audio tracks. Media encoder appears to complete the export, but the resulting files have no sound.

If I export the same clip from premiere pro from the timeline it works just fine and audio is present.

My theory is that media encoder isn't conforming the audio clips it imports. Any thoughts or fixes? Has anyone here had this issue? Thanks!

https://forums.adobe.com/thread/1056445

http://blogs.adobe.com/premierepro/2014/12/premiere-pro-cc-2014-2-release.html#more-2919

Monday, January 26, 2015

FCPX (10.1.4) Missing Plug-in (Effect) difficult to track down - pt1

FCPX shows a really haiku like "something's wrong" message in the form of a road sign: yellow triangle with a question mark in the Browser.

It does not tell you what is wrong.  So you have to dig inside the project.

When it's some media missing, you finally get to where the problem lies, and you get a red screen and a line of text that tells you "Missing File", so you finally know what's wrong and you can remedy.

But in the case of missing plug-in, no explanation. I get a red screen where the plug-in is missing, but it does not tell you anything else.  Hard to know what's going on.  Granted, the red screen looks different, a strip of film with some sort of overlay layer  - hint  hint.



It would be so helpful and immediate to have at least a line of explanation: "Missing Plug-in", or "Missing Effect" would be great. Just like we get "Missing File" when some media is gone awol.

In addition, or alternatively, the question mark/yellow triangle could pop onto the missing plug-in in the Effects window, and / or in the Video Animation. (Currently nothing happens.)

That would make tracking down missing plug-ins a breeze.


Next would be to display some Metadata (Right-Click) for the plug-ins, which would give you the info as to where the hell they are coming from, say if you want to download or buy them to finalize a project.

Currently you only have the name and that's it.  Good luck tracking down the developer, especially with generic names like "Vignette"...

I can see how using many custom Effects / Plug-ins can quickly become a troubleshooting nightmare when sharing projects.

Update:
After digging into the FCPX manual, I have to say there is a pretty thorough list of alerts. 
Still it would be so helpful to have text in addition to the icon itself (like the Missing File one), so one doesn't have to learn all these...


Thursday, January 8, 2015

FCPX (10.1.4) and LUT Utility and Neat Video Pro noise reduction

Got myself the LUT Utility from Color Grading Central and its working great... With (most) global adjustments to the image.

Qualifier, Power Windows... do not play nice.

What works:
- Color Match
- Color Wheels
- Primaries
- RGB Mixer
- Curves

What is ignored - as one would expect:
- Sizing
- Data Burn-in

What does not work (screws the LUT):
- Qualifier
- Power Windows
- Blur


Well it makes perfect sense since LUTs are mathematical transforms of the color space.

We are used to so making many tweaks to the image at once that it blurs boundaries.  Wouldn't it be nice if they all followed?

Anyway, make sure to disable all no-go adjustments in Resolve before exporting your LUT. And if your image looks funky... Well you know where to look.

---

Here is something else:

I also use Neat Video Noise Reduction Pro plug-in for FCPX, and when I do it must be above LUT Utility in the list of Effects.

If LUT utility is applied first, I can't select a noise profile in the Option window of Neat, the window is empty - all black or all white, no image.

I suppose it's good practice to always put LUT Utility at the top of the list of effects.


Tuesday, January 6, 2015

Red Giant Universe 1.3.1 crashes FCPX 10.1.4

Red Giant Universe craps FCPX out!

Knoll Light Factory EZ, be damned!  As soon as I hoover over the lame demo plug-in - shit it's just too easy!  Sure as crap FCPX gives me the dreaded beach-ball of death!

I'm Uninstalling this stupid package right now, (Universe 1.3.1 if u need to know.)

Sorry Red Giant, fix this please!

Thursday, January 1, 2015

Sony A7s footage import in Avid MC, FCPX, Resolve, Adobe

Avid MC 8.3 doesn't like the Mp4 (AVC) files created by the Sony A7s.

I can actually AMA link, but there is no image, and Avid gives me a "Wrong Format" instead of an image.  Now, the AVCHD .MTS footage from the A7s imports just fine in Avid.

FCPX 10.1.3 and 10.1.4 import the Mp4s, BUT IGNORES THE TIMECODE!
Here is a frame grab of the import window, All clips start at TC 00:00:00:00


Resolve Lite 11.1.2 imports them, BUT IGNORES TIMECODE as well.  ;((

Adobe (CC 2014) Premiere, After Effects and Adobe Media Encoder imports them just fine WITH Time Code.


Adobe has the upper hand here people...

Apple, BMD, Avid please make the A7s AVC files recognized properly!



Notes:
I have the latest XAVC Sony Plug-in installed for Avid: PDZK-MA2_v3.32  PDZK-MA2_v3.40
I have the latest XAVC Sony Plug-in installed for FCPX: PDZK-LT2_1.2.1


What's your experience with A7s footage?  Leave comments!