Only getting 1 audio track in Premiere Pro 19

[Klipalex]

Hello fellow FFAStrans users.

I have recently encountered something very, very strange in regards to FFAStrans and Premiere Pro 19 Version 13.1.5 (Build 47)

I build my first FFAStrans transcoder and its working perfectly. I then exported that workflow and imported it onto a completely fresh formatted computer, and launched FFAStrans. For the first couple of days it was working completely fine, and produced the files that i needed.

The workflow is setup to create a proxy and also keep the original file. The original file is always in perfect condition and works like it should. It is also setup to follow source audio and put it into tracks.

The proxy however is acting super weird in Premiere Pro. Premiere can only see the first audio track, and always see the files as containing only a single mono audio track. When I import the file onto Premiere Pro 20 it works fine, and it will have usually 2 or 4 audio tracks, when I look at the audio tracks in VLC i can see all audio tracks there are.

[emcodem]

Hi,
could you please export and upload your workflow?

[Klipalex]

Yes here you go.

[Klipalex]

I tried importing my proxy into Resolve da vinci as well now, and it seems the proxy is working perfectly fine there. So it may be Premiere 19 thats the issue and not ffastrans.

[ThomasM]

Hey Klipalex,

maybe you try "Same As Source". This may cause the NLE to see a "Stream" with 1 ... 4 Channels in one "Track", so you would have to UnLink them manually.

regards,
tom

[emcodem]

Hm, mono tracks in a proxy is not common at all. Typically proxies follow the schema that browsers support, which is pairs of stereo channels.
My recommendation would be that you set your proxy to a fixed number of 2 channels each 2 tracks.

[Klipalex]

Thank you for trying to help me resolve this issue.

@ThomasM Sadly that doesn't work. I have tried already. It changes nothing really.

@Emcodem I have been doing this with mono proxies for years without any issues. The reasoning is i can then relink to my original high res file without changing any audio channel/mapping. So I dont want to setup my proxies to run in stereo.

Right now I am leaning towards just upgrading every project to Premiere 2020 since everything works there.

[emcodem]

Ok sounds fair. So i guess there is no need to debug what exactly is the issue with the files on the older premiere version, right?

[Klipalex]

I guess yes. But I would prefer to know why/how to avoid the issue rather than just sweep it under the rug, and blindly upgrade.

[emcodem]

Hey @Klipalex,

getting to the bottom of this could be lots of work. It would be best to get out which Premiere Version upgrade exactly fixed the problem and read their release notes - but as they cannot write every little stuff into the release notes, it might not even be listed, or grouped in a sentence like "format support improved).

The other question mark in your problem is that you say that everything worked fine for a few days but suddently then it made problems - if you'd like to investigate this, you would need to be able to reproduce the working and not working situation and check out what change caused the issue.

My guess (just a shot in the dark) is that it is as easy as that: there is a special premiere Version which has issues with this special track layout in the container you are using, probably it didnt like some bit in the header or such.

There is not much that comes to my head i could do to help you, it is mainly about having a working and not working Premiere Version.