Jump to content

Nomad Help - original audio file sounds stretched or slow??


Jason Manzano
 Share

Recommended Posts

I also posted this in the official zaxcom forum, but thought I would double my chances for a quick answer.

I had a client call me today about a single one of my files (out of several) sounding slow. I was sure it was an import problem on their part, at worst a mirroring problem, but when I went back and listened to the original .marf file on the nomad it does sound as if it were stretched or slowed down. I have never experienced anything like this. I have had the nomad since it was first released and have been on version 7.27 for at least a few months with no problems. The file was 24bit 48k 23.98. No other files sound like this and no setting changes were made for that take. I need to know why this happened so I can prevent it and know if I can I save this file for my client. I will, of course, start by updating firmware. Any suggestions?

Link to comment
Share on other sites

Maybe load the file into WaveAgent and see if the TC metadata is what you think it is, and if the file duration makes sense.  Do you have another take with the same talent speaking so you could compare the relative pitch of their voices and the BG?   How much slowness are we talking here?  Did your client complain because the file would not sync to picture?  If you sent a ref feed to camera you could compare the sound of that audio with your file and know for sure if something is odd with your recording.

Link to comment
Share on other sites

Thanks Philip.  I just loaded into wave agent.  Everything looks fine.  It is the expected TC, bit rate, sample rate.  File length is more difficult because I do not remember exactly how long the interview was.  I am audibly comparing it to other files and it definitely sounds like they are talking about 50% slower along with the typical under-modulated lower pitch quality. I did send a reference to camera (and am suggesting they use for this track).  I am now asking them to upload me the reference track for comparison.

Link to comment
Share on other sites

I really want to hear about the ref track comparison before I speculate further.   This doesn't sound like an editor ingest issue, like the old FCP bogus pulldown problem re TC, since the OP is playing it is Wave Agent and hears the problem there.  It would be great to know how much longer the problem file is than the ref track, if that is the case.

Link to comment
Share on other sites

Talked to Zaxcom's software engineer.  This seems to be a unique problem.  Sounds like it booted up at a different sample rate for that one take (it was powered down before and after take).  I am going to use the reference file (when I receive it) to match length and send it back to my client.  I was recommended to put a couple seconds of tone at the head of takes for a while to use as an internal reference if it happens again.  Hopefully with my firmware update this won't happen again, if it does then it needs to be serviced.

 

Thanks all for your input!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...