labs icon indicating copy to clipboard operation
labs copied to clipboard

Timecode not shown onscreen when fed via audio in from a ZOOM F6

Open HanSooloo opened this issue 2 years ago • 48 comments

Using the latest Labs firmware (1.42.70) on my Hero 10 with a Pro 3.5mm Mic Adapter. ZOOM F6’s timecode output is connected to the mic adapter.

According to the LTC help page, I should see the timecode on the GoPro screen. However, I don’t see anything.

If I take the GoPro MP4 file and open it in Tentacle Sync Studio, that app can recognize the timecode embedded in the audio track without any problems. It’s just that the Hero 10 doesn’t recognize it.

36C3F465-E691-4FD8-B837-C1423A2226C2

HanSooloo avatar Jun 05 '22 19:06 HanSooloo

Please share a capture.

dnewman-gpsw avatar Jun 08 '22 19:06 dnewman-gpsw

https://drive.google.com/file/d/11UYAeY028gpWMH1dQLmqEQ-w-9b5X4l_/view?usp=sharing

Apologies for the blurry shot, but couldn't get GoPro to focus on the timecode displayed on the F6 properly.

HanSooloo avatar Jun 09 '22 13:06 HanSooloo

That helps a lot. The timecode is only being extracted from the left channel (this, I guess, is a camera bug), the F6 is placing timecode only on the right channel. So if you can swap the channels it will work (either the F6 menu, or hacking a cable.) image

dnewman-gpsw avatar Jun 09 '22 15:06 dnewman-gpsw

Thanks for the quick update. The F6 provides no options to set the timecode channel in their menu. I will open an issue with them.

Is there a way for the GoPro to do something here? Maybe an option to select the audio channel? I am not to keen on hacking a cable for this purpose.

HanSooloo avatar Jun 09 '22 17:06 HanSooloo

It is now listed of the Labs backlog to scan both channel for LTC. No idea when that can be done. Faster to change the cable, even a mono 3.5mm cable will likely work.

dnewman-gpsw avatar Jun 09 '22 17:06 dnewman-gpsw

I was able to use this cable to workaround the issue: https://www.amazon.com/gp/product/B08ZRYR6M3

Connected it to the GoPro and connected the Line Out from Zoom F6 into the White jack on the splitter.

EDIT: I can get apps to see the Zoom F6's timecode in the video file that the GoPro creates but the GoPro STILL does NOT show the timecode on the screen.

I still think there is another inherent issue in the GoPro firmware.

HanSooloo avatar Aug 14 '22 19:08 HanSooloo

I too am not able to get timecode to display on the gopro when syncing from the Tentacle Timebar or directly plugged in from the tentacle via stereo jack and the media mod or audio USB adapter. Audio timecode does not seem to be read by the gopro, as it does not change its time when plugged in, only when shown the QR code to sync from the timebar app.

Dandma avatar Sep 21 '22 15:09 Dandma

Tentacle Timebar will not cause the display to show timecode, so that part is working correctly. However I've not heard of a Sync Unit directly wired not working. When you add timecode audio via Media Mod, you should see the level meter with at least 7-8 bars, and the timecode will display in yellow first, then in green for about 5 seconds, then not display again until removed. All my cameras work (lots), although I only have the one Sync unit and one Media Mod for testing.
image If you record a clip, you should see an excellent signal level in your editor image. If you get good levels in both on camera and in the editor, please send me a short MP4 (or LRV is fine.)

dnewman-gpsw avatar Sep 21 '22 16:09 dnewman-gpsw

Thanks, here is a download to one file with the media mods and one with the audio adapter. both getting good left side signal. 16637818434558734164429719443106

image download of the mp4, lrv, and THM files from those two clips https://we.tl/t-wIljJxuVYr

Dandma avatar Sep 21 '22 17:09 Dandma

Yes, the audio seems good, and timecode is extracted by the desktop tools. Which camera model and Labs FW version are you using?

dnewman-gpsw avatar Sep 21 '22 17:09 dnewman-gpsw

Hero 10 Labs Version 1.46.70

Dandma avatar Sep 21 '22 17:09 Dandma

Yes, of course, I should have looking at the metadata in your sample clips. I now have, and I see obviously nothing wrong. This is a tad baffling, as the same firmware, same camera, and same device work perfectly here. I will need to think more on how to debug this.

dnewman-gpsw avatar Sep 21 '22 22:09 dnewman-gpsw

Is there a way to reflash that firmware, or roll back? They are all flashed off the same download, so maybe an issue with that? Or my default QR Control app setting that I showed all of them after covering to labs?

-------- Original message -------- From: David Newman @.> Date: 9/21/22 6:25 PM (GMT-05:00) To: gopro/labs @.> Cc: Dandma @.>, Manual @.> Subject: Re: [gopro/labs] Timecode not shown onscreen when fed via audio in from a ZOOM F6 (Issue #61)

Yes, of course, I should have looking at the metadata in your sample clips. I now have, and I see obviously nothing wrong. This is a tad baffling, as the same firmware, same camera, and same device work perfectly here. I will need to think more on how to debug this.

— Reply to this email directly, view it on GitHubhttps://github.com/gopro/labs/issues/61#issuecomment-1254294885, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3GOMXZY3GT6QVYKODIXZ7DV7ODN3ANCNFSM5X5PZYXA. You are receiving this because you are subscribed to this thread.Message ID: @.***>

Dandma avatar Sep 21 '22 22:09 Dandma

All downloads are signed, they is no way to have a bad install. Reinstalls are not necessary. Non-Labs version are available on GoPro.com

dnewman-gpsw avatar Sep 22 '22 02:09 dnewman-gpsw

I suppose tomorrow I'll try going back to regular gopro firmware, then back to labs and see if that helps.


From: David Newman @.> Sent: Wednesday, September 21, 2022 10:50 PM To: gopro/labs @.> Cc: Dandma @.>; Manual @.> Subject: Re: [gopro/labs] Timecode not shown onscreen when fed via audio in from a ZOOM F6 (Issue #61)

All downloads are signed, they is no way to have a bad install. Reinstalls are not necessary. No Labs version are available on GoPro.com

— Reply to this email directly, view it on GitHubhttps://github.com/gopro/labs/issues/61#issuecomment-1254449714, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3GOMXYNRPASSWTZ65QRLXTV7PCOBANCNFSM5X5PZYXA. You are receiving this because you are subscribed to this thread.Message ID: @.***>

Dandma avatar Sep 22 '22 02:09 Dandma

Made some progress! I found that switching the tentacle to output 23.976 timecode finally brings up the displayed timecode on the gopro. I can then switch it back to 29.976 and it then works on that frame rate. I also put it down to a basic 1080p setting. Not sure if that helped or not.

This is so far only working with the media mod, not the audio adapter. Have you ever gotten the audio adapter to work with it, or do I need to go buy some more media mods to have this work?

20220922_101839

Dandma avatar Sep 22 '22 14:09 Dandma

Workaround found! Setting the gopros and tentacle to 23.976/24fps. Jam syncing on tentacle properly displays the timecode with both the media mod and audio adapter.

Then changing the gopro and Tentacle back to my desired 29.976 frame rate and re-sync enables the timecode to display and sync as expected.

Seems to be an bug with non-24fps framer rates we are dealing with.

20220922_113112

Dandma avatar Sep 22 '22 15:09 Dandma

Using my audio adapters, getting it to work was not repeatable with my 4 camera test. Still works with the media mod, but no longer able with the audio adapter. Going to have to just use the tentacle timebar to get approximate timecode rather than jam synced for my shoot Saturday it seems.

Dandma avatar Sep 22 '22 21:09 Dandma

I was able to reproduce this error here, only at 29.97. Most testing was done at either 23.98, 24 or 25 fps. I hope to look it this lead in the next few days.,

dnewman-gpsw avatar Sep 23 '22 05:09 dnewman-gpsw

It will be addressed in the next labs release, as I have it working better at 29.97 now.

dnewman-gpsw avatar Oct 01 '22 16:10 dnewman-gpsw

Thanks for the updates @dnewman-gpsw ... do you know when the next labs release will be?

HanSooloo avatar Oct 03 '22 19:10 HanSooloo

Just wanted to thank everyone here for putting in the work to get this issue fixed. I've been using Timebar with mixed results. Can anyone confirm that the Atomos UltraSync ONE also allows for jam sync capability via LTC on the Hero 9 with media mod? I am considering going with the Atomos TC (or possibly Deity) solution because it seems to offer wireless capabilities that Tentacle does not offer.

fitzpb avatar Oct 28 '22 03:10 fitzpb

Is there any way to re-open this ticket? I have now acquired enough cabling to swap the audio that the ZOOM F6 generates from Right channel to Left channel. However, with the mic adapter, I cannot get the timecode to show up with any of the settings.

I also took my original file, swapped the audio channels and fed the new file to the GoPro from my MacBook ... and no LTC info is shown on the GoPro. I actually now have 2 GoPro 10's, with the same adapter, and the issue repeatable on both.

HanSooloo avatar Dec 03 '22 02:12 HanSooloo

Not sure about the GP10. I bought a GP11 and immediately updated the firmware to GoPro labs. I can jam sync directly from the F6 into the GP11 via media mod even with the LTC being pumped through right channel. Are you using the most up to date GoPro Labs firmware? Perhaps it's a GP11 vs GP10 thing. My GP9 was super buggy with TC, but the GP11 has been absolutely perfect with no issues whatsoever.

fitzpb avatar Dec 03 '22 03:12 fitzpb

There are bugs fixed for LTC in HERO11. There will be a HERO10 update likely in the next few months.

dnewman-gpsw avatar Dec 03 '22 08:12 dnewman-gpsw

Not sure about the GP10. I bought a GP11 and immediately updated the firmware to GoPro labs. I can jam sync directly from the F6 into the GP11 via media mod even with the LTC being pumped through right channel. Are you using the most up to date GoPro Labs firmware? Perhaps it's a GP11 vs GP10 thing. My GP9 was super buggy with TC, but the GP11 has been absolutely perfect with no issues whatsoever.

Thanks for the update @fitzpb ... what frame rate are you using in your Timecode settings on the ZOOM F6?

Did you make any changes to make it work, or pretty much defaults?

HanSooloo avatar Dec 03 '22 15:12 HanSooloo

Using standard 29.97 in the F6 and 4K/30p (which is 29.97) on the GP11. All default settings. I use the same settings in my Tentacle Sync ap too.

fitzpb avatar Dec 03 '22 21:12 fitzpb

29.97 was the trouble on HERO10. All other frame rates should work well. Patch is needed for 29.97 on H10, already out for H11.

dnewman-gpsw avatar Dec 03 '22 21:12 dnewman-gpsw

@dnewman-gpsw thanks for the update. So, just like @Dandma, I could get the Hero 10 to show the timecode on the screen with a Media Mod when the frame rate was set to 23.976. At that time, I could also switch the frame rate to 29.97 and keep it going.

However, with the official Mic Adapter, no matter what frame rate I choose, Hero 10 DOES NOT show the time code.

Can you please confirm that there are 2 distinct fixes:

  1. Timecode can be read/displayed using Mic Adapter.
  2. Timecode can be read/displayed for frame rates other than 23.976.

HanSooloo avatar Dec 04 '22 01:12 HanSooloo

Only bug found was related to 29.97, that was fixed on HERO11. Just found a new issue with Mic Adaptor, it doesn't currently receive the audio until capture starts, and the timecode is displayed (and read) when the not recording. This a likely a system code change, the code Labs sit upon. Looking into it.

dnewman-gpsw avatar Dec 04 '22 19:12 dnewman-gpsw