Skip to main content
Participant
July 22, 2025

Premiere not displaying proper TC & FPS of PolyWav audio file

  • July 22, 2025
  • 8 답변들
  • 481 조회

1. Export polywav audio file from severl mono audio tracks from Tentacle sync studio 

2. Import into premiere

3. Premiere displays incorrect FPS metadata as well as inaccurate TC (displays as 00:00:00:00)

    - File was exported as 23.98, yet it is displayed as 29.97 in premiere

    - File's timecode starts at 12:52:49:00 yet is displayed as 00:00:00:00

4. Timeline does not show individual track names that are written into polywav file 

 

When compared to the latest version of Davinci resolve (screenshots below) it shows accurate FPS, Timecode, as well as the individual track names displayed on the timeline when using the same file. 

 

Screenshots attached below and notible areas circlced in red.

 

Version: 

Adobe Premiere Pro

Version 25.3.0 (Build 84)


Audio Files Available for Download

8 답변

NickMidwig작성자
Participant
July 30, 2025

Sounds good thanks!

jamieclarke
Community Manager
Community Manager
July 29, 2025

Hi @NickMidwig - I’ll go ahead and file this as a bug for now. We’ll keep you updated as we learn more.

jamieclarke
Community Manager
Community Manager
July 25, 2025

Hi @NickMidwig - premiere currently does not read the track names or the iXML data.  Please see this article: iXML renamer

 

Im asking the team about the Timecode issue.

NickMidwig작성자
Participant
July 25, 2025

Hey @jamieclarke 

 

I am working off an SSD formatted as Mac OS Extended (Journaled). I just added a new Polywav file that is under 4gb at this link below

 

POLYWAV Under 4gb link

 

Seems the polywav that is under 4gb is properly reading timecode and FPS. It does seem premiere is not seeing the track names in the timeline. 

 

Thanks!

 

jamieclarke
Community Manager
Community Manager
July 24, 2025

HI @NickMidwig -  I haven’t seen that behavior in media files before thank you for taking the time to share more details.

is your file system formatted as fat32?

Are you able to get the polywav file under 4GB to test whether file size is the issue? In the meantime, I’ll check with the team and see if anyone else has encountered this.

NickMidwig작성자
Participant
July 24, 2025

Hey @jamieclarke - Appreciate you taking the time to look into this. Not sure what happened with the original dropbox link

 

but here is a direct link to the PolyWav Audio file.

 

This file is 18gigs so let me know if the size is an issue for downloading and I can create a smaller file. 

 

The polywav file is the one that is not interpreting the FPS or TC properly, the other files in that dropbox link were just provied to show you how I built the Polywav file. This Polywav is being read properly by the latest version of Davinci. 

 

I'm wondering if there could be an issue with the wav file being larger than 4gigs with this note in the media file properties? 

 

WAVE (BW64 for length over 4 GB)

 

 

 

jamieclarke
Community Manager
Community Manager
July 22, 2025

Hi @NickMidwig -  Thanks for submitting your bug report. We need a few more details to try to help with the issue.
Please see, How to Report a Problem.

 

In your preferences under media, if your Indeterminate Media Timebase is set to 23.976 does your file import properly?

I do not see a poly file in your dropbox link.

 

I imported the file "20250626_125249_01LAV_001" and it matches the correct timecode of 12:52:49:00


Sorry for the frustration.

R Neil Haugen
Legend
July 22, 2025

When you start in the Project panel, and right-click/Properties for the wav file, what does it show?

Everyone's mileage always varies ...