How do you get FCP to use the timecode from WAV files off the Zoom H4n? at DVinfo.net

Adam Woodworth · May 28th, 2009, 02:43 PM

I have a Zoom H4n digital audio recorder, and it is supposed to have timecode metadata in the broadcase wave .WAV files that it records. However either the H4n isn't working as advertised, or I can't get Final Cut Pro to recognize the timecode.

Does anyone have any experience with the H4n? I can't find any info on the timecode and FCP anywhere... I saw that someone was having problems getting it working with Sony Vegas so it could be that the files just don't have the BWF header written correctly. But thought I'd see if anyone else has used the H4n and it's timecode support.

Thanks!

Dan Brockett · May 28th, 2009, 06:43 PM

Hi Adam:

I am looking through the H4N owners manual. What leads you to believe that the H4N is capable of recording in .BWF format? Same with the TC metadata, the manual makes no reference to TC in the files.

I don't think the H4N has either capability. If it does have some sort of TC capacity, it automatically resets to zero for each clip so I couldn't see too much use for all of those repeating TC values.

Dan

Adam Woodworth · May 28th, 2009, 06:54 PM

Hey Dan,

Take a look at page 51 of the manual, under "Variety of WAV Files".

Also check out this page, seach for BWF in the page:

H4n Handy Recorder

They both say that the WAV's it records are supposedly BWF compliant and have timestamp and marker metadata.

Adam

Robert Lane · May 29th, 2009, 09:49 AM

Why keep guessing? Ask the manufacturer.

Adam Woodworth · May 29th, 2009, 09:56 AM

I did already. No response yet to my e-mail and they aren't answering their tech support when I called.

Robert Lane · May 29th, 2009, 04:52 PM

Quote:

Originally Posted by Adam Woodworth

I did already. No response yet to my e-mail and they aren't answering their tech support when I called.

That's not good. I find it interesting that the opening line from their "contact us" page reads: "Catch us if you can". Maybe they meant that literally since they're playing hard to get?? Odd and ironic.

Noah Kadner · May 29th, 2009, 05:07 PM

Yeah I'd go with a different piece of gear like a Sound Devices- those rock.

702T Portable Audio Recorder | Sound Devices, LLC

Not cheap but worth every penny.

Noah

Adam Woodworth · May 29th, 2009, 06:56 PM

Well, part of the point of the Zoom H4n is for the built in stereo mics for picking up ambient sounds.

Anyways, even without timecode I can get what I need mostly via the file's timestamp and a little elbow grease.

Robert Lane · May 30th, 2009, 10:14 PM

If you ever want to step-up to a pro-piece of gear but keep the same small-ish form factor, both Noah and I are big fans of the Olympus LS-10. It bested the Zoom in our tests and in the world of compact, stereo "Flash" recorders it's impossible to beat for the price. It also uses ISO standards for file and output types.

And unlike Zoom you'll find Olympus tech support readily available and accessible.

Nigel Barker · May 31st, 2009, 02:36 AM

Quote:

Originally Posted by Robert Lane

If you ever want to step-up to a pro-piece of gear but keep the same small-ish form factor, both Noah and I are big fans of the Olympus LS-10. It bested the Zoom in our tests and in the world of compact, stereo "Flash" recorders it's impossible to beat for the price. It also uses ISO standards for file and output types.

Glancing at the specifications the Olympus is more comparable to the much cheaper Zoom H2. Unlike the Zoom H4n there is no XLR input, no phantom power & no four track recording. Is the sound quality so much better as the functionality does look much less?

Andy Mees · May 31st, 2009, 02:45 AM

Am not working with BWF here, but reading the FCP6 release notes, it states ... Some Broadcast Wave Format (BWF) audio files contain metadata in the evolving iXML format (for details, go to www.ixml.info). If you import a BWF file containing the appropriate iXML metadata, Final Cut Pro can calculate the timecode rate and mode (drop frame or non‑drop frame).

The thing that grabs my attention there is the first word "Some" which seems to suggest that there is room for variation, or perhaps it just means that some BWF files don't have that info (probably more likely). Either way, maybe the Zoom files are out there in variant land? That said, have you tried using BWF2XML? It predates FCP6 and was once th ebest bet for working with BWFs in FCP ... might be worth grabbing the demo and seeing if it is more able to interpret the embedded data you need: BWF2XML - Communicating with BWF and Final Cut Pro XMLs

Adam Woodworth · July 3rd, 2009, 05:45 PM

The folks at Zoom finally fixed this BWF problem with the H4n. The new firmware released a couple weeks ago, version 1.40, fixes the timestamp info in the BWF WAV files.

I tried it out, it works. FCP recognizes the timestamp info and displays the media start & media end timestamps as expected (that is, as time of day when the file recording started/ended).

Markers work too -- if you make markers when you're recoding with the H4n then they'll show up in apps that support it. FCP doesn't seem to, but iZotope RX showed them.

May 28th, 2009, 02:43 PM	#1
Adam Woodworth Regular Crew Join Date: Jan 2005 Location: Cambridge, MA Posts: 55	How do you get FCP to use the timecode from WAV files off the Zoom H4n? I have a Zoom H4n digital audio recorder, and it is supposed to have timecode metadata in the broadcase wave .WAV files that it records. However either the H4n isn't working as advertised, or I can't get Final Cut Pro to recognize the timecode. Does anyone have any experience with the H4n? I can't find any info on the timecode and FCP anywhere... I saw that someone was having problems getting it working with Sony Vegas so it could be that the files just don't have the BWF header written correctly. But thought I'd see if anyone else has used the H4n and it's timecode support. Thanks! __________________ Bourbon: It's hard being a small time gangster. http://www.bourbonmovie.com

May 28th, 2009, 06:54 PM	#3
Adam Woodworth Regular Crew Join Date: Jan 2005 Location: Cambridge, MA Posts: 55	Hey Dan, Take a look at page 51 of the manual, under "Variety of WAV Files". Also check out this page, seach for BWF in the page: H4n Handy Recorder They both say that the WAV's it records are supposedly BWF compliant and have timestamp and marker metadata. Adam __________________ Bourbon: It's hard being a small time gangster. http://www.bourbonmovie.com

May 29th, 2009, 09:56 AM	#5
Adam Woodworth Regular Crew Join Date: Jan 2005 Location: Cambridge, MA Posts: 55	I did already. No response yet to my e-mail and they aren't answering their tech support when I called. __________________ Bourbon: It's hard being a small time gangster. http://www.bourbonmovie.com

May 29th, 2009, 06:56 PM	#8
Adam Woodworth Regular Crew Join Date: Jan 2005 Location: Cambridge, MA Posts: 55	Well, part of the point of the Zoom H4n is for the built in stereo mics for picking up ambient sounds. Anyways, even without timecode I can get what I need mostly via the file's timestamp and a little elbow grease. __________________ Bourbon: It's hard being a small time gangster. http://www.bourbonmovie.com

July 3rd, 2009, 05:45 PM	#12
Adam Woodworth Regular Crew Join Date: Jan 2005 Location: Cambridge, MA Posts: 55	The folks at Zoom finally fixed this BWF problem with the H4n. The new firmware released a couple weeks ago, version 1.40, fixes the timestamp info in the BWF WAV files. I tried it out, it works. FCP recognizes the timestamp info and displays the media start & media end timestamps as expected (that is, as time of day when the file recording started/ended). Markers work too -- if you make markers when you're recoding with the H4n then they'll show up in apps that support it. FCP doesn't seem to, but iZotope RX showed them. __________________ Bourbon: It's hard being a small time gangster. http://www.bourbonmovie.com

May 28th, 2009, 06:43 PM	#2
Dan Brockett Inner Circle Join Date: Feb 2006 Location: Los Angeles, California Posts: 2,109	Hi Adam: I am looking through the H4N owners manual. What leads you to believe that the H4N is capable of recording in .BWF format? Same with the TC metadata, the manual makes no reference to TC in the files. I don't think the H4N has either capability. If it does have some sort of TC capacity, it automatically resets to zero for each clip so I couldn't see too much use for all of those repeating TC values. Dan

May 29th, 2009, 09:49 AM	#4
Robert Lane Go Go Godzilla Join Date: Nov 2004 Location: Scottsdale, AZ USA Posts: 2,823 Images: 15	Why keep guessing? Ask the manufacturer.

May 29th, 2009, 05:07 PM	#7
Noah Kadner Better than Halle Berry Join Date: Feb 2004 Location: Los Angeles, CA Posts: 435	Yeah I'd go with a different piece of gear like a Sound Devices- those rock. 702T Portable Audio Recorder \| Sound Devices, LLC Not cheap but worth every penny. Noah

May 30th, 2009, 10:14 PM	#9
Robert Lane Go Go Godzilla Join Date: Nov 2004 Location: Scottsdale, AZ USA Posts: 2,823 Images: 15	If you ever want to step-up to a pro-piece of gear but keep the same small-ish form factor, both Noah and I are big fans of the Olympus LS-10. It bested the Zoom in our tests and in the world of compact, stereo "Flash" recorders it's impossible to beat for the price. It also uses ISO standards for file and output types. And unlike Zoom you'll find Olympus tech support readily available and accessible.

May 31st, 2009, 02:45 AM	#11
Andy Mees Major Player Join Date: Mar 2006 Location: Kuala Lumpur, Malaysia Posts: 645	Am not working with BWF here, but reading the FCP6 release notes, it states ... Some Broadcast Wave Format (BWF) audio files contain metadata in the evolving iXML format (for details, go to www.ixml.info). If you import a BWF file containing the appropriate iXML metadata, Final Cut Pro can calculate the timecode rate and mode (drop frame or non‑drop frame). The thing that grabs my attention there is the first word "Some" which seems to suggest that there is room for variation, or perhaps it just means that some BWF files don't have that info (probably more likely). Either way, maybe the Zoom files are out there in variant land? That said, have you tried using BWF2XML? It predates FCP6 and was once th ebest bet for working with BWFs in FCP ... might be worth grabbing the demo and seeing if it is more able to interpret the embedded data you need: BWF2XML - Communicating with BWF and Final Cut Pro XMLs