Premiere Productions (w/LucidLink) -Proxy sound not working when switching between MacOS and Windows

@jamieclarke - I'm not sure I'm afraid, it was created before I joined the project.

I tested creating a new local Production (using 25.4.1 B3) and starting from scratch, which showed an interesting link.

Before I get into it, here's some context.  This is using footage shot on a Sony FX6 (XAVC-I) in an .MXF wrapper with 8 audio channels.

Audio channel usage

Ch1 = Intermittendly used

Ch2 = Never

Ch3 = Internal scratch mic (always on)

Ch4 = Internal scratch mic (always on)

Ch5 - 8 = Never

H.264 (.mov) proxies were created using Davinci Resolve, with the audio channels set to "Same as source" for export.

I've also tested with .mp4 and ProResProxy, but the result was the same.

Process I followed

MacOS

1. Production created
2. Project created
3. Media imported (via Media Browser)
4. Proxies linked
5. Footage made offline (hard drive disconnected)

Everything works and plays back as expected.. despite footage being offline and proxies being used.

Windows 11 Pro

1. Open Project
2. Everything automatically linked and all video was able to playback fine
3. Only some clips had sound

I eventually figured out that, after opening a project where the proxies were last attached on a Mac, only Ch1 (and presumably Ch2 as well) audio plays back.  There is nothing for Ch3 or Ch4, despite the fact that they are constantly recording.

This is what led to me thinking there was 'no' audio, because in instances where there's not Ch1 or Ch2.. no audio shows up at all.  I hadn't noticed that only Ch1 was playing before.

When you import the original file… all channels play as expected

When you import just the proxy… all channels play as expected

When you reattach the proxy… all channels play as expected

However, when I then switch back to Mac (after reattaching the proxies in Windows), it show the same behaviour with only sound from Ch1 and nothing from Ch3 or Ch4.

I think this is why B_CAM (which is a Sony A7s) has been fine all along, because both the original file and the proxy are only 2ch.

Hopefully that makes sense?  Let me know if I need to clear anything up!

Hi @jamie_mac - What version of Premiere did you make the production in?  As a test can you create a new production locally with a new project and then import your media same test just with new projects and let us know if that helps. It's strange that it's only certain files.

Thanks for the insight @R Neil Haugen - glad to hear that it's possible at least!  I'll head over to the LL Slack when I get a chance.

However, for what it's worth, I ran a test taking Lucid completely out of the equation by using my local NAS and I experienced the exact same behaviour.

This involved making a copy of the whole Production, moving it on to my NAS along with the media.  I then opened up that project on Mac and pointed all the media towards the NAS.  I then switched to Windows and in fairness everything linked automatically.  However, the sound on A_CAM day #2 was missing again until I reattached the proxies.  At which point it was missing on the Mac.

Not sure if this still points towards Lucid, or if it's more likely that it's a Prem issue?

Long-time LucidLink user, we had a ".poc" filespace ... proof of concept.

I'm all PC, my partner down in Cape Town all Mac, and we've never had any issues, but then, all our media and projects are on the filespace on Amazon S3 servers in London. We've both got well above 300Mbps low-latency internet, and that's worked fine. I've never even pinned a file to local storage.

Biggest framesize has only been full 4k, for full video clips. Some of Mo's Ae produced graphic clips have been up to 6k as I recall. But we've had up to five video tracks and 8/9 audio tracks on a sequence without issues.

So we've never worked proxy only.

My suggestion: go immediately onto the LucidLink Slack channel as the help there is fast and good, both from staffers and other heavy users.

Yes - cache is stored locally for each system.

Wierdly - the issue primarily impacted all the A_CAM (FX6) clips from the second shoot day (three day shoot).  The other two days ocassionally had issues, but nowhere near as consistently.

However, I could not for the life of me find any difference between the three days.

The proxy and media file paths were the same (relative for their date), I checked the files using MediaInfo and the only difference was their file size and duration, the file names were the same format, I checked that the file extensions were consistent (upper vs lower case etc...), the same export preset was used to make them, and the audio channels matched the rushes (8 ch Mono).

Hi@ @jamieclarke - yeah, I noticed that but nothing I didn't seemed to impact it, so I just assumed it was a difference in how Premiere was implemented on Windows vs. Mac.

Here's the process I follow:

1.  Highlight clips in Premiere
2. Right click > Proxy > Attach Proxies
3. Attach Proxies dialogue box (Use Media Browser to attach files = Unchecked) > Attach

MacOS

Via Finder dialogue box - find the LucidLink filespace from the sidebar (e.g. jm-projects) and navigate to the correct file.

Windows

Via Explorer dialogue box - find the LucidLink filespace from the sidebar (e.g. jm-projects) and navigate to the correct file. 

There is also the option to navigate to the < Lucid (L:) > drive which has been mounted.  

Although, having tried both of these options and it didn't seem to change the file path within Premiere.

I would try attaching using the Media Browser popup on Windows, but the LucidLink filespace doesn't show up on Windows in that instance, only the L: drive.

Hi @jamie_mac - Is it every file that doesn't have audio or only certain files?  Is your cache stored locally for each system?

Hi @jamieclarke - thanks for the response.

Here's a screenshot for the same project on both Mac and PC (with LL Filespace name redacted).

Based on that article, we'd already changed the name of our LucidLink mount points, which LL support confirmed was the correct thing to do when I spoke to them.  They also said that this could be the possible cause of this issue, however, it didn't help and they didn't have any other immediate suggestions.

The team and I are up against various deadlines, so I'm not going to be able to pull together more info at the moment.  I'll try and sort more details later!

Thanks!

Hi @jamie_mac -  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.

Can you share a screenshot of your metadata columns "Proxy Media File Path" for the media clips on mac and windows.

Have you contacted Lucidlink?

Here is an article: Optimizing Adobe Premiere Pro settings for smooth playback with LucidLink Filespaces

Sorry for the frustration.