search

DFTi / Scribbeo

Scribbeo on iOS (Available on App Store)
1 stars 0 forks source link

Fix drop-frame timecode reading in Scribbeo #37

Closed zedsaeed closed 12 years ago

zedsaeed commented 12 years ago

In all of my timecode tests, the only type of timecode that came up incorrectly in Scribbeo was drop-frame timecode. We should fix this issue.

mixflame commented 12 years ago

In progress

zedsaeed commented 12 years ago

Perfect Jon! Just leave aside the PDF issue for now. Well done. This df issue should be right up your alley.

mixflame commented 12 years ago

Sure, no problem. Thanks. Can you upload the test file you were using to app.scribbeo.com port 44301 ? The one I have is too short to really test & reproduce.

zedsaeed commented 12 years ago

Jon: The file I used in already on app.scribbeo.com: 44301. Go into the Old Test Files folder, then into Drop Frame folder. There is a 12 min DF file with the name: vt_24p_2997_dftc-ipaddailies. Ignore the "24p" business. (Just Edvin being over efficient.) That's the 12 min DF file I used for my testing.

mixflame commented 12 years ago

Got it. Found it.

zedsaeed commented 12 years ago

Excellent Jon! If anyone can solve this, it is you. Keep me informed of your progress.

mixflame commented 12 years ago

Hi Zed, can I get any confirmation about the burnins on that file? For example, using my TC Calculator, FreeTimePro on iPad.. I get these values from tc:

24P and TC reading from Scribbeo: 01:08:26:05 TCR burn in: 01:08.26:23 (what format is this? I can't convert to this value with any calculator.. and the burnin seems wrong because the calculator shows a different value) FreeTimePro conversion to DropFrame (2997): 01:08:30:10

LMK, THX

zedsaeed commented 12 years ago

J:

Ignore the tcr that reads 01:08:26:23. That's the 24 fps TC that edvin put on,min his infinite wisdom. Use the other TC burn onscreen.

Zed

On Aug 22, 2012, at 6:09 PM, "Jon Silverman" notifications@github.com<mailto:notifications@github.com> wrote:

Hi Zed, can I get any confirmation about the burnins on that file? For example, using my TC Calculator, FreeTimePro on iPad.. I get these values from tc:

24P and TC reading from Scribbeo: 01:08:26:05 TCR burn in: 01:08.26:23 (what format is this? I can't convert to this value with any calculator.. and the burnin seems wrong because the calculator shows a different value) FreeTimePro conversion to DropFrame (2997): 01:08:30:10

LMK, THX

— Reply to this email directly or view it on GitHubhttps://github.com/keyvanfatehi/Scribbeo/issues/37#issuecomment-7957259.

mixflame commented 12 years ago

Sure, no problem. I have been ignoring it. The real problem is, though I can get that NDFTC TimeCode to match the (generated) inhouse Display TC, I cannot get that value to be converted to the onscreen "correct" Dropframe timecode (your TCR track burnin). Can't ascertain the FPS of your TCR track burnin. But, I can keep cracking and I have an inkling that it may be 23.97 (PAL DF). Thanks, and I will keep hunting.

kfatehi commented 12 years ago

Can't ascertain the FPS of your TCR track burnin lmao. We will need to get cohesive soon to grind stuff out if you're not slamming these things out on your own. You went from a hard problem to an even harder problem. If you want to do something with immediate positive results you should help Zed and me turn the TDS use cases into cucumber scenarios INPUT.

Get off C for a little while, I need it to stop kicking your ass for a few minutes so you can be NPP.

kfatehi commented 12 years ago

No more working on this until a test is written.