files sync in browser not sync in timeline...

I think, but i am not completely sure, that since the latest update 10-5-3, there is a strange sync problem. some clips in the timeline are out of sync. When i move the clip with the audio to the browser the problem is gone, when i place the clip back on the timeline it lost its own sync again. Anybody familiar with this problem?

Could you give some details about the clip? Is it a synced clip or original video and audio file? What are the specs of the media? What are the project properties?

I have a project with a lot of material. 70% is shot with my own Sony, 30 % is shot by a hired cameraman with a panasonic , i think.
I am editing for half a year and everything worked well together. But now all of a sudden. that second camera material is out of sync. And when I take is to the browser, it is fine. And when I place it back on the timeline the audio is more then a second late .
the clip is synced and I can play the original or a proxy, the problem is the same...?

Verify sample rates of the two cameras' clips.

sample rates are all 48 kHz

i tried a few more things
i made a new library, a new project,
I imported one clip and the problem is the same, the audio is 1 sec and 12 or 13 frames late.
when i open the clip in quick time everything is fine

Please give the complete media specs and the project properties you’re using.

Oh, OK, I know what's wrong. It's broken! (I've no clue... sorry)

Hello Tom Wolsky,
sorry for my ignorance, but where can I find what you ask?
media specs and project properties?

in the attached picture you can see clearly that after placing the clip on the timeline, the first 1,5 sec there is no Audio. All the audio is 1,5 sec to late...?

So not a synced clip, a clip with VANDA. Can you please give the clip properties and project properties? Do the frame rates match?

clip properties:  4k  24p, stereo
project properties: 1920x1080 25p

Try the media in a 24p project to see if it works. Are you delivering 25? Is that why the project's 25? For the time being I'm suggest editing in the 24 project if it works and then sending to Compressor to do the frame rate conversion.

Oh, and use feedback to report the problem. The more who do the quicker the problem will float to the top of the pile. There are already widespread reports of at least two significant buds in 10.5.3.