[Bouke Vahl]

You really do not read, do you?
I am saying that the number reflects a frame rate, not a fieldrate. But it is used wrong, like in a typa. Everyone knows that I ment typO, but that does not mean that I wrote that, not that it means that.

So one more time, the number reflects the frame rate, not the field rate.
The I or P means that the frames are Interlaced (i) or Progressive (P).

I don’t give care that 90% of the world makes the same mistake. Something that is wrong does NOT become right if everyone starts believing in it.

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

Good you figured that one out.
This is a known flaw (and not the only one) in the specs over here.
All broadcast here (SD as well as HD) is XDcam style, but to annoy as many people as possible, some geek wrote specs as difficult (and as it turned out flawed) as possible, without simply stating ‘make XDcam and all is fine’.

Watch out for burned in subs as well, they are specced to have illegal (super) black outlines, that might get your work rejected for being conform specs.

(I recently had a huge fight with a broadcaster who send me wrong leader / trailer material. Parially wrong field dominance (so, not fixable), beserk audio levels, fade out where there was none intended, out of spec video levels.)

If you need to do commercials, contact me as I’ve got some nice tools for that.

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

My point is the bullshit in notation nowadays.
50p means 50 PROGRESSIVE frames per second.
So
50i means 50 INTERLACED frames per second, thus 100 FIELDS per second.

From your wikipedia link:
> Resolutions of 1080i60 or 1080i50 often refers to 1080i/30 or 1080i/25 in EBU notation.
Sad, but true, and a cosy rocking chair close to the furnace in hell.

And yes, I do know this stuff, and perhaps a tiny bit more.

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

[Shane Ross] “50i also runs at 25fps”
No, the framerate is the framerate. 50 runs at 50.
There is no 50i as standard, only 25i. (Perhaps it does exists if you overcrank a camera)

I don’t know who came up with the term 50i, but he should be shot.

And, 25i is only smoother on fast motion, at the cost of playing half the resolution. (And that is a good thing.)

Just had to get that out.

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

Hi Jeff,
Call me a stranger if you want, but some people here know I’m around the digital video stuff for some 25 years.

And (as I stated, it was some time ago) I DID read the brightsigng manual, and what was in the manual DID NOT work.

So, how much experience do you have on the subject to recommend a ‘best course of action’?
(Of course reading the manual is a start, but sadly, in theory there is no difference between theory and practice. In practice however…)

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

Bitrate and quality are related, but not as much as you think. A good encoder putting in lots of effort can achieve a better quality at 1/3 of the bitrate. But at a low bitrate, the math to decode is more complex.

For Brightsign (it has been a long time since I’ve cursed on one) it’s trial and error.
If its pure about bitrate, forget MpegII and try H264 (or X264).
(It ‘could’ be the memory card is too slow, but i highly doubt that…)

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

AE is a compositing / effect app.
Switching (multicam editing) is for an NLE. Switch to ANY nle and do that part of the work there.

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

I think they mean -18 LUFS

And that is not so hard if that is the only demand.
(Getting commercial now…)

Export a Wave from your sequence, and put it in this:
https://www.videotoolshed.com/handcrafted-timecode-tools/loudness-change/

Set the desired LUFS to -18 and let it do it’s thing.

(But, -18 is kinda loud, -24 for US and -23 for Europe is standard.)

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

[grinner hester] “It’s a math thing. It’s why your 30 second spots are actually 29:20”

Yo Grinner,
Math is my middle name.
Difference is 0.1 %
So, a ’30 sec’ spot (In TC notation, if it does not roll over a 2 min. mark) is 29.97 seconds.
Still, food for lawyers if people find out, and will be big fun if there is a retroactively demand for a refund for on air add time.
(Believe it or not, over here was a claim to cellphone providers who sold subscriptions with a ‘free’ phone. People found out the cost of the phone was in the subscription, and they won…)

btw, your last name is my ex wife’s first name. Where does it come from?

Bouke
http://www.videotoolshed.com

[Bouke Vahl]

As the char did encode the first time, it should be properly supported.
Now, only thing (besides stuff under the hood that is invisible) I can imagine, do you have enough loading time?
(Old captions need time to load as they are encoded in a very old way for analogue TV.)
What happens if you have just this caption and play back starting some 5 sec. before it should come up?

What happens if you encode your file and look at it in VLC?

Are you going to broadcast? If so, why not ask your broadcaster to have a look at a sample file?

Bouke
http://www.videotoolshed.com