Bouke Vahl
4
Apple Final Cut Pro X Coins
8
COW Coins
Forum Replies Created
-
I don’t get it. It IS plain text, isn’t it?
If you need to do a ‘save as’, that will be two mouse clicks…Send me the file and I’ll have a look.
Bouke
http://www.videotoolshed.com -
I bet Subbits can open it.
https://www.videotoolshed.com/product/subbits-subtitler/
Don’t forget to set the framerate correct before making an attempt.Bouke
http://www.videotoolshed.com -
re- read what I wrote. Others CANNOT as Apple wont let them. The source for DNxHD is open, but Apple chooses not to implement it.
Now, you can go torture yourself with a company that makes you hurt, I’m not that kind of guy.
Enjoy.Bouke
http://www.videotoolshed.com -
The most logical cause to the problem then seems that there is a framecounter somewhere that shouts the current TC as frames and that is converted to time with the wrong FPS as base.
Now, the only problem is to find out what exact part of the production process it was.Bouke
http://www.videotoolshed.com -
[Robert Withers] “Am I clueless because I use low-end tools? Or do I have to use low-end tools because I’m clueless? There’s a koan for you.”
I don’t know what a koan is, I’m Dutch.
And I dont know if it is one or the other, but if you do not know why you use the tools you do, you are indeed clueless.
What I ment was that shooting 24 fps makes no sense whatsoever for 99% of the content produced.Bouke
http://www.videotoolshed.com -
Well, my previous reply goes for you as well. bouke (at) videotoolshed (dot) com 🙂
Bouke
http://www.videotoolshed.com -
[John Rofrano] “It is 32-bit because it is discontinued.”
Very strange logic…[John Rofrano] ” the codecs I was referring to which are still valid and current codecs that those companies are selling and they haven’t bothered to upgrade them to 64-bit (which they will have to do now if they want those codecs to remain current)”
A codec has nothing to do with 32 or 64 bit operating systems. The same way as the strory in a book has nothing to do with the way it is printed. It is the encoding / decoding routine that needs to be implented. That was done inside QT, and Apple killed that.
Next, it is NOT up to the codec companies to do anything, as they cannot alter the OS / FCPX. It is Apple who needs to do it, or at least open up to other developers to give them the opportunity to do so. And they refuse.[John Rofrano] “At some point, it is technically not possible to support the past and move forward at the same time.”
Yes, but then explain, why can I still get fuel for ANY car EVER made?
Why can I call an ancient / antique phone on a landline from my cellphone? How come the copper from a landline is now used to transport analogue signals as well as my 200 Mb internet connection?
How come 4:3 black and white mono TV sets are still supported by all broadcasters, and their specs require you to keep them in mind?You may be right that old stuff should die, but that point still is not now, that will take at least 10 years or perhaps way more.
Bouke
http://www.videotoolshed.com -
-
You are missing something very fundamental, giving us more info.
Is it really 24 fps, or is it 23.976? The only ones who shoot true 24 are the top budget features and the very low end stuff made by the clueless.
How short is the first known drift at what TC, and how long is the last known drift at what TC?
Reason, 23.976 is a non-drop frame format, so the TC WILL drift from the time on the wall (the ‘real’ time)
running 0.1 % slower than the TC can display (it is rounded to frames), you’ll be off at the end of a day.
(Shooting day of 10 hours gives you 10 hours * 60 minutes * 60 seconds * 0.001 = 36 seconds difference.Does that match (a bit) with what you are seeing? Then you know where to start looking.
Premiere might read the files wrong, so check the TC in another app.
The display of the cam might be wrong, what does the cam say if you watch the footage on that?
I don’t think there is a reading error in the operators, it’s hard to make a constant mistake. But it is not hard to tell someone the wrong digits. Sadly, I don’t know the cam, so I can’t comment on that.Bouke
http://www.videotoolshed.com -
[John Rofrano] “because I have several 32bit apps”
So, does this not undermine your own statement?
Next, how expensive would it be for Apple to create support for 32 bit apps? 100.000? 1 million? 10 million?
Even if it was 10 million, that would be (guessed) something like 1/2000 part (0.05%) of the desktop hardware turnover of one year. (And that is NOT apple’s cash cow.)
So, money can’t be the issue. (And apple had a similar program when they switched from Motorola to Intel.)
But, a lot of people like yourself have a lot of old stuff they want to continue to use. And it is no argument that updating is a choice, as Apple forces you to do so. On a phone not updating is just highly annoying and it will happen eventually when you make a tiny mistake, but on a desktop it is impossible when you need a new machine, as it will not run an older version of the OS.So, IMHO, your arguments are void.
Bouke
http://www.videotoolshed.com