created files are seen as wrong framrate by resolve
- lukeyounge
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 12
- Thank you received: 0
6 years 7 months ago #6331
by lukeyounge
lukeyounge replied the topic: created files are seen as wrong framrate by resolve
Thanks for having a look Daniel
The clip can be modified in Resolve, but doing this then creates motion effects (judder in moments). It is truly being seen as 24p. It is not a settings import issue. This is not user error issue.
Thanks
The clip can be modified in Resolve, but doing this then creates motion effects (judder in moments). It is truly being seen as 24p. It is not a settings import issue. This is not user error issue.
Thanks
Please Log in to join the conversation.
- Daniel Beasley
- Offline
- Administrator
Less
More
- Posts: 641
- Thank you received: 29
6 years 7 months ago #6330
by Daniel Beasley
Daniel Beasley replied the topic: created files are seen as wrong framrate by resolve
We have had a look at this, but we are unable to reproduce the problem you are having.
We imported a 25p clip that worx4x had created into Resolve and made sure that the Project settings were all set to 25p. Looking at the clips attributes it showed the frame rate to be 25p.
If you right click on a clip and go to "clip attributes" are you able to manually change the framerate?
We imported a 25p clip that worx4x had created into Resolve and made sure that the Project settings were all set to 25p. Looking at the clips attributes it showed the frame rate to be 25p.
If you right click on a clip and go to "clip attributes" are you able to manually change the framerate?
Please Log in to join the conversation.
- lukeyounge
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 12
- Thank you received: 0
6 years 7 months ago - 6 years 7 months ago #6329
by lukeyounge
lukeyounge replied the topic: created files are seen as wrong framrate by resolve
It shows them as 25p.
Worse than that some subclip - ie parts of a longer clip, cut up into several smaller clips by W4X - will show as 24p, others as 25p - FROM THE SAME CLIP.
Worse than that some subclip - ie parts of a longer clip, cut up into several smaller clips by W4X - will show as 24p, others as 25p - FROM THE SAME CLIP.
Last Edit: 6 years 7 months ago by lukeyounge.
Please Log in to join the conversation.
- Daniel Beasley
- Offline
- Administrator
Less
More
- Posts: 641
- Thank you received: 29
6 years 7 months ago #6328
by Daniel Beasley
Daniel Beasley replied the topic: created files are seen as wrong framrate by resolve
Hi Luke,
This is an odd one. If you put one of the clips from the original project (not one made by worx4X) into Davinci Resolve does it show them as 25 or 24p ? Will have to download Resolve myself to see if we can reproduce it.
This is an odd one. If you put one of the clips from the original project (not one made by worx4X) into Davinci Resolve does it show them as 25 or 24p ? Will have to download Resolve myself to see if we can reproduce it.
Please Log in to join the conversation.
- lukeyounge
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 12
- Thank you received: 0
6 years 7 months ago #6326
by lukeyounge
lukeyounge created the topic: created files are seen as wrong framrate by resolve
Hello
Well this is the strangest problem I've ever seen.
Some clips are being interpreted by Resolve as being 24p when in fact they are 25p. This is occurring independently of any xml or project. They appear as 25p in quicktime/the finder/fcpx but Resolve sees them as 24p.
- This is across 2 macs and a pc.
- Resolve Ver 14.
- OSX 10.13.3
- Files were created by Worx4X ver 1.0.39.
Any ideas?
Well this is the strangest problem I've ever seen.
Some clips are being interpreted by Resolve as being 24p when in fact they are 25p. This is occurring independently of any xml or project. They appear as 25p in quicktime/the finder/fcpx but Resolve sees them as 24p.
- This is across 2 macs and a pc.
- Resolve Ver 14.
- OSX 10.13.3
- Files were created by Worx4X ver 1.0.39.
Any ideas?
Please Log in to join the conversation.
Time to create page: 0.143 seconds