Remote Editing - Is it possible to easily & quickly share Source Timecode?

MBP 16" M1 MAX, 64GB RAM, 32 Core GPU

2hour 1080p30 ProRes Proxy Source File

My TimeCode720p Preset (HEVC): 13:44 (2.45GB)
My TimeCode480p Preset (HEVC): 7:15 (1.16GB)
My TimeCode240p Preset (HEVC): 3:31 (376MB)

I guess if you don't have to read anything on screen, such as powerpoint text or screen sharing demos, 240p works fine. 

Good question. I always quote a producer for this topic: "I've logged the interviews using timecode, because I know you like that" No Shit!! It's true that "Days of editing saves hours of logging"

Here's my input:

1. The transcriptions services Speed Scriber, Otter, Simon Says, Builder, etc. DO include Source timecode in the printed and on screen versions of their transcripts.
2. FCP DOES export Source Timecode to Frame IO, if it's present, or indeed from clips in the Browser, or Compressor.
3.  If not using a Transcript, Frame IO is your best bet, even the worlds most technically inept producer CAN figure out how to drop markers on clips and there is a superb app for IOS.
4.  FCP DOES NOT read embedded timecode on Mp4s unless they are imported from within a card structure, via the import window.- This can cause serious workflow issues on large productions, but not really here.
5.  FCP DOES NOT export BWav files that contain timecode. Long time request.
6.  The latest version of FCP 10.6.1 DOES NOT require Monterey.
7.  No matter what you do, or which NLE you use, Producers will routinely ignore timecode, even when it is present, BURNED in- 2 inches high. They will misquote it, leave off the seconds, and muddle the hours, it's just the way it is. if on the page an annotated print out works best.
8.  QT player now FINALLY does display embedded timecode like QT7 used to. Click on numbers to toggle between TC, Frames and ABS time.

So I don't think your problems are really FCP related, although audio files with TC would be a great feature, to have. Frame IO is really the best bet, or print out the transcripts and write down some numbers.

If your friendly producer can't get it together and insists on using ABSOLUTE time, then just put the clip in a Compound clip IN FCP  (starting @ 00:00:00:00) edit with those instead.

I can't think of anything I do in Broadcast TV, where it is cost effective to NOT have a Producer pull their own selects from Interviews using an NLE. FCP is the fastest and easiest one out there for a lay person to master, so if Apple would give us better collaboration that would be fab. Currently Post Lab drive is excellent and the best solution.

Bluebicycle, after many years of TV broadcast, and many years of other forms of video work before that, I 100% agree with you. To have a client, producer, director, whoever, post comments, and have those comments as markers on my FCP timeline, pretty effortlessly, nothing is faster or more accurate. Thank goodness for Frame.io which I've use professionally for years now.

indeed, the clients love it, sort of empowers them, and when I think of the decades of working backwards with notes and timelines.

Believe you me when a client has close to 8 hours of old film to review you create something they can get through four hours of footage in 1/4 the time by making a four panel canvas (1/8th the time if mastered the 2x speed I mentioned above). Creating two lower res versions covering four hours runtime each timeline beats the beJesus out of eight one hour timelines. Sent these two out for review just today.

if a client has 8 hours of footage, they have 8 hours of footage.

 Is any of this content concurrent? Can't think this would work for anyone I know. So confusing. Watching back rushes can be a joyous endeavour, where you start to formulate ideas in your head, and add annotations.
Even with a comprehensive bunch of timecodes, sent to an editor, it's light years away from using FCP itself and the skimmer, or dropping markers in FrameIO.

Range Based keywording and Ratings are the most efficient way to log, from inside FCP itself. Or if building a narrative only, use  the amazing Lumberjack Builder and you don't even need FCP.

The time it takes to assemble all those clips (8 hours worth) into that configuration, then lay the timecode on top of each one, the increased export time of it all, and the super poor quality of tiny video, I'd never spend that much time just for a client to review what they want to keep or not. Frame.io is still way, way faster. I'm with Bluebicycle on this one. Stop creating unnecessary extra work for yourself.