[Keith Koby]

[Jeremy Garchow] “The problem I see with flattening a multi clip is that the audio would become a mess if the multiclip wasn’t in the primary storyline. There will need to be a structural change to X (like allowing connected clips to non-primaries) in order for flatting of multi clips to not be a total cluster.”

Yes the audio gets messy. When you use the x to 7 to x – “xml roundtrip” as I described earlier, you end up with the source audio cut up into a bunch of connected clips. I imagine the same to be true of the x to resolve process. It certainly is that way when you go x to pro… The audio guy goes, “why in the heck did you blade the audio to shreds?”

So perhaps an easier way to match a multicam angle cut in the project back to an original clip (selecting that as a range) would be a good solution. But even that is still messy because any color corrections you may have applied in the multicam angle will not be back on your original.

I’ll take the flattening and the ugly audio connections so that color that I may have applied in the angles comes through to the flattened clips in the timeline.

[Keith Koby]

Also, there are things you can do with regular clips that you can’t do to a multicam clip like stabilize. Also you may have clips from one angle that need to be color corrected in different ways depending on how zoomed in the image is. You can color correct in the multicam clip opened in its own timeline, but that is applied to all uses of your clip.

So it would be nice to have that functionality of 7 where you can collapse the multicam after you finished editing.

[Keith Koby]

By flattening, what is meant is that your cuts in the project link back to the original media, not back to the multicam synchronized clip.

[Keith Koby]

Just ran into this issue myself within the last week. Resolve might be your best bet.

I attempted exporting an xml then converting it to 7 with xto7 and then back to x with 7toX. It imported and was without the multi cam, however the 7toX conversion makes unstable timelines for me that cause X to crash. It’s always been my experience with 7toX. Maybe I’m doing something wrong with it.

I wish they would change this so that you could better color correct individual shots without leaving fcpx and/or also apply image stabilization to an individual clip.

Keith

[Keith Koby]

I should mention that we see this too on a few stations, but not on all. It seems like it effects only certain projects. Look at the folder where your backups are supposed to be saved and see if they are there.

Keith

[Keith Koby]

Franz – I thought maybe some socc- uh football talk around here would get some traction, but not really.

The second picture in the story of Tim Cook taking an AppleCare call is great.

[Keith Koby]

Hey Kevin,

Nothing too bad here since we are still using a lot of CS6 for AE. The CC licenses we rent are not seeing the usage we anticipated.

Just happened to hinder us because a producer opened CC instead of CS6. Good luck getting it up and running quickly.

Keith

[Keith Koby]

I believe fcpx has to process audio through the system audio, so you have to choose bm audio there on your main sound output.

However, to get the other crud like alerts to go through the display speaker, go to:

System Preferences -> Sound -> Sound Effects

Then choose Display Speakers on the “Play sound effects through:” drop down menu. This way you at least won’t get IM pings and error sounds through the bmd io.

[Keith Koby]

[Andre van Berlo] “I got this message back from neat video guys:

“protranscodertool is not part of Neat Video, so its behaviour
should not be affected by any adjustments in Neat Video
settings.

protranscodertool is a part of FCPX and I can see other people
reported a similar problem on Apple support website:
https://discussions.apple.com/thread/5808115?start=0&tstart=0“”

Hey Andre,

Be aware that sometimes when a process is “not responding” in activity monitor, it just means, the process is too busy to be bothered to respond to activity monitor’s badgering it to give a status. It might not mean that something has crashed or is not working. I would bet that Neat is making the protranscodertool so busy that it just can’t reply. Hopefully a new release will fix that.

Keith

[Keith Koby]

[Tim Wilson] “Telestream has been doing it since 2011, btw. So has Rhozet. Sure, your mileage will vary, but those options have been working fine for years, and I’ve seen only positive comments about both of them.”

As of last year when I checked, Harmonic Carbon (aka Carbon Coder, aka Rhozet etc) still was living with a requirement of running windows server in order to access the ProRes encoding. Also, they had a new requirement of using a multi-node farm in order to encode to ProRes. ca-ching, ca-ching!

Telestream requirements were the same for windows episode (you needed to be running windows server).

I’m not aware that either has changed.

Beware of the ffmpeg solutions because they are 8 bit processing going back to 10 bit codec. So if your source is 10 bit or better and you drop down to ffmpeg to make the ProRes, then you are dipping to 8 bit to ultimately go back to 10 with a lot of filler “0s”.

It seems that every NAB we see more officially licensed ProRes encoding/decoding solutions. Apple is employing a good strategy here. They do seem to have stringent requirements on granting rights to the licensee, but it is probably a really good thing for the industry that this is the case.