[Joseph Hung]

It’s back in 8.0.1. Both in PPro and in export.

work.tulpapictures.com
Twitter/Vimeo/Facebook: @TulpaPictures

Mac Pro 2.4GHz 12 Core Intel Xeon (5,1) 32GB RAM
Macbook Pro 2.3 GHz Intel Core i7 (8,2) 4 GB RAM
OSX 10.8.5
Adobe CC
FCS3
Davinci Resolve
AJA Kona LHi/Blackmagic
MSI Twin Frozr GeForce GTX 680 4GB GPU
EVGA GeForce GT 640 4GB GUI
RocketRAID 4322 SAS
ProAvio 8TB RAID5 SAS
Own Cams: BMCC 2.5K EF, GH3, Hacked GH2, 5DMKII

[Joseph Hung]

It appears that this is not discussed that widely, but I did find some threads of problems that have the same symptoms. Anyways, it’s the AAC encoding, and here’s the white paper about the encoder delay and synchronization. Hope this helps people out.

Technical Note TN2258: AAC Audio – Encoder Delay and Synchronization

work.tulpapictures.com
Twitter/Vimeo/Facebook: @TulpaPictures

Mac Pro 2.4GHz 12 Core Intel Xeon (5,1) 32GB RAM
Macbook Pro 2.3 GHz Intel Core i7 (8,2) 4 GB RAM
OSX 10.8.5
Adobe CC
FCS3
Davinci Resolve
AJA Kona LHi/Blackmagic
MSI Twin Frozr GeForce GTX 680 4GB GPU
EVGA GeForce GT 640 4GB GUI
RocketRAID 4322 SAS
ProAvio 8TB RAID5 SAS
Own Cams: BMCC 2.5K EF, GH3, Hacked GH2, 5DMKII

[Joseph Hung]

Reinstalling FCP7 did not work. This is insane. I guess I’ll just remap to Command + Left/Right Arrow and live with it.

[Joseph Hung]

I think I know what’s going on.
In Premiere Pro CC, I created a custom FCP7 keyboard layout. since PPro wouldn’t allow me to use the FCP keyboard shortcut Option + Left/Right Arrow keys, I had to remap to use Command + Left/Right Arrow.
For some reason, this screwed it up for FCP7. In FCP7 Keyboard manager, I can remap the Nudge Left/Right 1 Frame with the same keys from above in PPro: Command + Left/Right Arrow. Now it works in FCP7 using these new remapped keys, and not the original config.
So apparently, altering FCP7 shortcuts in PPro inherently changes the keyboard prefs for FCP7? That’s crazy, and I’m very frustrated I spent so much time trying to get a simple keyboard shortcut back.
So far, I’ve uninstalled PPro CC, and trashed prefs. I’m reinstalling FCP7. If this doesn’t work, then I’ll just have to live with it because trashing prefs doesn’t seem to bring back the original FCP7 keyboard prefs.

[Joseph Hung]

REALLY odd. I rebooted, still the same. I have no idea what to do other than reinstalling FCP7?

[Joseph Hung]

@Todd Terry, yes that is expected, that you would absolutely get the credits for DP even if you weren’t operating the camera yourself. Does your friend use that footage where he had a cam op on his reel? I’m sure he did, because that makes sense. In the case of my friend, who had a second unit with it’s own second unit DP, I argued that it would not be “fair” or “right” to use that footage in his reel if he cared about his relationship to that crew and DP. If he doesn’t care, then that’s his own perogative and how he wants to conduct business with other people. Burn that bridge if it means that much to him. He wants to use it, because there’s some great stuff there, and he directed the second unit DP of what he wanted, what to get, etc. but you know, he’s feeling guilty for considering it 🙂 And of course, he’s still gonna get credit as THE DP, and the second unit will get their own credit as “second unit” and “second unit DP.”

[Joseph Hung]

Hi Bill thanks for chiming in. Yes, I feel the same way. Ethically, if I were the “supervising DP” I wouldn’t want to do that, unless I specifically needed to, and in that case your solution would make sense. I argued that it’s not professionally scrupulous to use, say, your heli aerial crew’s footage in your own reel. Even though you directed them on what to get, how to get it, what you want, etc, and you weren’t operating and it wasn’t you ultimately running the camera and crew. On the other hand, my friend thought it was totally fine to use the footage, since it was your vision in the first place. However, I don’t think you would be keeping the DP and crew as friends once they see your reel.
I guess the question comes down to what specificity your reel is aiming at.

[Joseph Hung]

I’ve got the same question, and seems it’s still speculative. Does anyone know for sure? I guess if you remove support for the GUI card on the .txt file P Pro will automatically go to the supported card, which is the one being used for GPU Compute in Resolve?

I’ve just posted this same question here:
https://forums.creativecow.net/readpost/3/948531

Your help and insight is appreciated

Joseph

work.tulpapictures.com
Twitter/Vimeo/Facebook: @TulpaPictures

Mac Pro 2.4GHz 12 Core Intel Xeon (5,1) 32GB RAM
Macbook Pro 2.3 GHz Intel Core i7 (8,2) 4 GB RAM
OSX 10.8.5
FCS3
CS5.5
Davinci Resolve 10
Blackmagic Intensity Pro
MSI Twin Frozr GeForce GTX 680 4GB
EVGA GeForce GT 640 4GB
RocketRAID 4322 SAS
ProAvio 8TB RAID5 SAS
Own Cams: BMCC 2.5K EF, GH3, Hacked GH2, 5DMKIII

[Joseph Hung]

Could be drive health or RAM health. Usually I find that when weird problems like this arise, and everything says it’s fine, it’s something to do with a drive or memory stick, etc. Run some testing software to determine if a drive or stick is dying.
It shouldn’t be your cabling, but I would just double check your cables to rule out that problem, as cables do go bad from time to time.

work.tulpapictures.com
Twitter/Vimeo/Facebook: @TulpaPictures

Mac Pro 3.0 GHz 8-Core Intel Xeon (2,1) 16GB RAM
Macbook Pro 2.3 GHz Intel Core i7 (8,2) 4 GB RAM
OSX 10.6.8
FCS3
CS5.5
Blackmagic Intensity Pro
NVIDIA GeForce 8800 GT 1GB VRAM
RocketRAID 4322 via dual MiniSAS
ProAvio 8TB RAID 5 Dual Mini-SAS
Panasonic Lumix GH2 (hacked) & GH3, Canon 5DMKII & III, 7D, Panasonic HVX200A, Panasonic DVX100A

[Joseph Hung]

Of course it does, dang it. Thanks for the help!