You can change the frame rate at any time. Ideally, you would go to each keyframe and nudge it to where the Current Time Indicator can go to at the new frame rate, but you could also just render the Comp and spot check it for any issues with the picture.
If you have several Comps nested, changing the frame rate and adjusting keyframes can take a good amount of time.
For your needs, I'd use 23.976. This is good for the web render. It can also be turned into 29.97 via 3:2 pulldown.
Does the business lobby tv (digital signage) system require 1080i? Or will it play 1080p?
- If it will play 1080p (you may need to send over a test file), then you should be fine (the same MP4 that you upload to YouTube may also play on the tv).
- If it requires 1080i, you can enable 3:2 pulldown in the Render Settings to get to 29.97 frames per second from 23.976.
If you are talking projects that do not contain video shot with a camera of real things you can change frame rates to anything you like at any time because keyframes are based on time not frames. The only "nudging" of keyframes to a specific frame that is ever required comes when you need some movement to stop or start on a specific frame because of things like frame blending.
The bigger question is what do you want the motion to look like. 29.97 is a video standard in the US, 25 is a PAL standard and things look more like TV at those frame rates. 59.94i is not usually 59.94 interlaced frames per second or approximately 120 fields per second, it is usually 29.97 interlaced frames per second where each frame is composed of two fields. 29.97P is exactly the same as 29.97I when you have identical fields - both fields are the same slice of time. The only visual difference between 29.97 interlaced and 29.97 progressive is that interlaced footage has fields that are different slices in time. Almost ALL broadcast over cable or the air is interlaced whether it is in an NTSC or a PAL country. There are very few channels that broadcast at high frame rates (59.97P) because the data rate is twice as high and bandwidth costs money. That's just how TV broadcast works.
The biggest difference between film rates 23.976, 24 and 25 and 29.97 or 30 fps is the potential problems you will have moving graphics horizontally or vertically. The higher the frame rate the smaller likelihood that you will run into critical panning speeds that cause the image to judder and become unwatchable. It is easier to animate at higher frame rates. Lower frame rates (24) produce more film like motion blur and a little more of a cinematic look, but you have to be much more careful with the speed of your camera moves and your animations.
Adding 3:2 pulldown is only necessary when you are converting 24 or 23.976 frame rate video to 29.97i (interlaced) because it only can be done with interlaced footage. Most folks make the mistake of thinking that 29.97i and 59.94i are different frame rates, they are not in most cases, it's just different terms for the exact same frame rate and the exact same number of fields. There are exceptions so you have to test your interlaced footage to see what you actually have.
So now are you completely confused? Make it easy on yourself. Unless your client has specific specifications for frame rate and interlacing and your client knows what they are actually talking about (many do not - and it's your job to know the difference) use the frame rate that gives you the look you want with the least amount of work. In almost every case anything above 29.97 will be played back at that frame rate anyway when you look at it on TV. 24 fps projects require more care in camera moves and animation speed than 29.97 (30) so if you choose to work at 24, or even 25, make sure you preview your animations full size at full speed to check for unacceptable motion artifacts because they are a lot more common than you think.
There are very few channels that broadcast at high frame rates (59.97P) because the data rate is twice as high and bandwidth costs money
Surely it's only the uncompressed data rate that would double with a doubling of frame rate, unless it was really complex content (eg. very complex motion/noisy picture).
eg. from the EBU:
The above says that 1080p50 won't require more bitrate than 1080i25 for broadcasts.
The above says 1080p50 gave the same or better results than 1080i25 at the same bitrates
The only time that I've been asked to delivery p50 instead of i25 for broadcast is for on demand. The same goes for delivering p59.94 instead of i29.97 (which is i59.94).
In regards to the original post, if the TV will play p24 then the user may be able to encode one file for both web and TV. If the TV will play p25 or p30, then those are fine as well.
Not that I've done any thorough testing, but I've noticed that p50 files encode to a slightly smaller file size than i25 if encoding to MPEG2 and about the same if encoding to H264 (assuming the same bit rate). Rendering to broadcast quality CODECs, like Apple ProRes 422 (HQ) or Animation, I've always had the p file be larger than the i file.
Sorry for this issue. Did you ever find a solution? Please let us know if you have or if you still need help.