Trouble with NTSC frame rate., MS renders 29.97 but I need exactly 30.

[ArthurVKuhrmeier]

Hello ladies, hi guys,

I experienced some problems with the frame rate. Moviestorm renders at 29.97 fps. As I edit the film in iMovie I need exactly 30 fps!!! The problem is, when I export the film some frames are dropped, others are doubled resulting in annoying jolts.

How can I export from MS at exactly 30 fps??? Can I create (hack) options for the frame rate myself, e.g. 30 fps and 120 fps?

Thanks in advance,
Arthur

[aroundworld]

Hello ladies, hi guys,

I experienced some problems with the frame rate. Moviestorm renders at 29.97 fps. As I edit the film in iMovie I need exactly 30 fps!!! The problem is, when I export the film some frames are dropped, others are doubled resulting in annoying jolts.

How can I export from MS at exactly 30 fps??? Can I create (hack) options for the frame rate myself, e.g. 30 fps and 120 fps?

Thanks in advance,
Arthur

Hi Arthur,

29.97 and 1/30 (30FPS) is negligible and shouldn't be causing an issue. What might be causing the issue is the program you're using to convert the WEBM video to .mov or MP4, AVI or what ever format you're choosing, so take a look at that.

I would suggest rendering at a lower FR out of MS like 24 FPS and then set up the project prefs in iM as 24 fps and see of that doesn't fix the issue.


Hope that helps.

Steve A

[Ben_S]

I'm afraid the only frame rate options are from this bit of code:

CODE

        CINEMA_24   ( 1, 24, "24 (Cinema)" ),
        PAL_25      ( 1, 25, "25 (PAL)" ),
        NTSC_30     ( 1001, 30000, "30 (NTSC)" ),
        CINEMA_48   ( 1, 48, "48" ),
        PAL_50      ( 1, 50, "50" ),
        NTSC_60     ( 1001, 60000, "60" );

The frame rate being the second number/first number.

As this is part of the compiled code, it would not be very hackable.

[aroundworld]

I'm afraid the only frame rate options are from this bit of code:

CODE

        CINEMA_24   ( 1, 24, "24 (Cinema)" ),
        PAL_25      ( 1, 25, "25 (PAL)" ),
        NTSC_30     ( 1001, 30000, "30 (NTSC)" ),
        CINEMA_48   ( 1, 48, "48" ),
        PAL_50      ( 1, 50, "50" ),
        NTSC_60     ( 1001, 60000, "60" );

The frame rate being the second number/first number.

As this is part of the compiled code, it would not be very hackable.

Ben, these are all progressive, correct?

[Ben_S]

Ben, these are all progressive, correct?

That depends on how you define progressive in this context. They are not implementing any sort of social reform, certainly.
I think according to wikipedia, the use of the word progressive to describe framerates is more about transmission, rather than video output.

Our output is certainly not interlaced unless you do something clever to make it so.

[aroundworld]

That depends on how you define progressive in this context. They are not implementing any sort of social reform, certainly.
I think according to wikipedia, the use of the word progressive to describe framerates is more about transmission, rather than video output.

Our output is certainly not interlaced unless you do something clever to make it so.

I believe social reform happens when they conform 16mm to 35mm film.

[ArthurVKuhrmeier]

Hi Steve,

thanks a lot, you where right. After converting a webm video the frame rate ends up in strange 30.3 fps...!? If I convert a lossless avi there is no problem at all: clean 30 fps.

Hi Ben,

thanks for a closer look to your code. What I consider one of the downsides of the new MS 1.5 is the poor list of frame rates -- especially compared to 1.4. If the code is that easy, it would be great if you'd add some more. For proper slow motion you definitely need much higher frame rates, even 120 fps is not as much as it seems.

I suggest you change it e.g. like this:

CODE

        CINEMA_24   ( 1, 24, "24 (Cinema)" ),
        PAL_25      ( 1, 25, "25 (PAL)" ),
        NTSC_30     ( 1001, 30000, "30 (NTSC)" ),
>       FULL_30     ( 1, 30, "30 (full)" ),
        CINEMA_48   ( 1, 48, "48" ),
        PAL_50      ( 1, 50, "50" ),
>       NTSC_60     ( 1001, 60000, "60 (NTSC)" ),
>       FULL_60     ( 1, 60, "60 (full)" ),
>       SLOW_120     ( 1, 120, "120" ),
>       SLOW_180     ( 1, 180, "180" ),
>       SLOW_240     ( 1, 240, "240" ),
>       SLOW_320     ( 1, 320, "320" ),
>       SLOW_480     ( 1, 480, "480" ),
>       SLOW_640     ( 1, 640, "640" );

That would be cool, giving us filmmakers much more possibilities.

What say you?
Arthur

[Ben_S]

That might well work.
Doing a render at 240 frames per second is glacial, though.

[primaveranz]

That depends on how you define progressive in this context. They are not implementing any sort of social reform, certainly.

[ArthurVKuhrmeier]

Hi Ben,

I never really thanked you for adding slow-mo to Moviestorm. Thank you. And to all the staff involved.

That might well work.
Doing a render at 240 frames per second is glacial, though.

You think so? Then check this! It's a post with video presenting the new Storming Show. In the first episode you can enjoy slow motion rendered at 240 fps...

Love and success,
Arthur

[lucindamc123]

Good, I always render in Lossless Huffy and it imports great into Sony Vegas Pro which is what I use for film editing.