Michael Gissing
195
COW Coins
190
DaVinci Coins
3
Solve Coins
Forum Replies Created
-
Recently I was helping some people work out what to use to record and edit podcasts. I checked out Audacity to cover a free cross platform audio editor. However, It actually made a lot more sense to teach then to use the Fairlight page in the free version of Resolve. Audacity only had one advantage – being able to render the final as an mp3 but really as editing and mixing software it is awful compared to Fairlight.
So for free software to do almost everything, Resolve free is really hard to beat. Added advantage is some of these people also wanted to do vLogs so why learn different software when Resolve absolutely nailed everything. Oh and converting a wav to mp3 can be done online for free.
-
[Scott Witthaus] “And I guess ignored?”
No. There was a couple of extensive posts where this was discussed and in the end Kathlyn Lindeboom came up with a suggested compromise name – “ALL NLEs: The Great Debate”.
https://forums.creativecow.net/readpost/335/102528
Not sure how you missed this as you were active in the thread that day. Or are you still referencing Ron’s sticky thread dated before this? Pretty positive Kathlyn’s name will be the winner but we will see when the web site changes
EDIT: Sorry, I just read Tim’s post and lets all just wait and see rather than speculate.
-
I’m one of the lucky many that live in a 25fps world (actually most of the TV world is 25fps) but have had to deal with the small but influential 29.97/ 23.976 world and sort out the math to deliver speed corrected pitch correct audio mixes over feature length programs.
-
[Ted Coakley] n”Are you saying that the transfer house and I are wrong in our thinking that NTSC 29.97 or 30p is actually 29.975 or 29.976, and that it actually is just 29.970?”
Basically yes. A shift in frame rate by .1% was decided on all those years ago. Grab a calculator and subtract .1% from 30 and 24. You will see that 29.97 is correct and 23.976 is too. 29.97 is not an abbreviation. The only software that I have heard of that can give an incorrect frame rate like 29.975 is After Effects which is why I was curious if it had been used in the conversion to ProRes. With AE it is also necessary to spec 23.976 not 23.98. All other NLE and VFX software that I know of give options based on actual frame rates. AE allows for user defined frame rates and you have to be precise to the decimal points.
What FCP was trying to do to resolve the issue was varispeed the sound to play back 29.975. However the video rate couldn’t be shifted because a frame is a frame. FCP trying to be helpful with changing audio speed has been a constant issue with what was seen as a feature of the program has really behaved like a bug for many of us over the years. Hence people will ask about sample rates, bit depth and the killer problem of having a different default easy setup frame rate. That one really is a bug which will never be fixed. It only affects audio only not a QT file so I knew your issue was incorrect frame rate metadata.
I have no idea why the corrected file is now causing grief in Finder. It is possible that somewhere in the OS the original files metadata was stored and now it doesn’t cross reference.
-
“The Granny Smith Cultivar originated in Eastwood, New South Wales”. As a kid growing up in Sydney, not far from Eastwood, I of course knew this story.
A history of Apples can be found in Michael Pollan’s excellent book “The Botany of Desire”. From the original trees endemic to Kazakhstan many cultivars have appeared. Apples from seed are not true to type. Hence when a good variety turns up it is then grafted onto root stock. The book also talks about tulips, marijuana and potatoes so there’s some thing for everyone.
-
[Scott Witthaus]”Good question. IMHO the name “Apple Talk” makes no sense”
Which is why after a long series of debating on this forum that name was rejected and numerous more appropriate names were proposed. I’m keen to see what the final name will be and the continuing of intelligent debate.
-
Cinema tools will display 29.97 because 29.975 is not a real rate. Choose conform to 29.97 and it will just correct the metadata flag to 29.97 so FCP can play it correctly without sync drift.
Conform only changes the metadata. It doesn’t re-render.
-
I’m going to hazard a guess that the metadata in the file incorrectly has the frame rate set to 29.975 no 29.97. It makes me wonder if the DV was converted to ProRes in something like After Effects which can set frame rates with incorrect speed.
Final Cut Pro unlike most other apps tries really hard to apply incorrect metadata like that to what it can. In this case to the audio as a frame is a frame. This may be causing your audio drift.
If you have Cinema Tools, open the file in there and change the frame rate metadata to 29.97. (You should do this to a copy of the file just in case as this is not an undoable operation).
Try this file in a matching sequence and see what happens.
-
I’ve emailed you a simple timeline with three different ways to do the text from your video.
-
Mark, can you post a screen shot?