NTSC frames

HI, thanks for this tool

I don’t understand why “NTSC frames”, in selection, are 29 fps, when it should be 23.976 and/or 29.97 fps. My suggestion is to include those fps, thanks. At the moment, I have to translate NTSC frames to time.

In Audacity 1.3.4, NTSC frames are close to 29.97 fps as they should be.
You are probably looking at drop frames, or non-drop frames.

Thank you steve

I know what drop and nop drop frames are.

37:46.827 = 2266.827 seconds
NTSC frames (Audacity) = 65737

fps = 65737 / 2266.827 = 29.0 (and thats wrong)


\


I’d prefer 23.976, since to sincronize I previosly remove the pulldown from video

Your pictures show 37:46.848 (2266.848 seconds), and 65738 frames, not 37:46.827 (2266.827) seconds and 65737 NTSC frames, but that still works out wrong.

When I run your test I get: 37:46.848 = 2266.848 = 67937 NTSC frames which looks about right to me.

I’m using Audacity 1.3.4 on Linux - you’ve not said what version or platform you are using, but I do notice that you have “Snap to” (Ajuste a) selected, which will move your selection a little each time you change the time format - that could account for the small differences between your quoted figures and the pictures, but it doesn’t account for 29 fps instead of 29.97 fps.

Audacity ® 1.3.4-beta (Unicode), the lastest I think

Win xp sp2


PAL 25 works fine

OK, I’ve tried it with Audacity 3.1.4 beta (Unicode) on Win XP Pro SP2

Again I get 37:46.848 = 2266.848 seconds = 67937 NTSC frame

Is this problem repeatable? If you generate a tone exactly 16 minutes and 40 seconds duration, what length does Audacity report in NTSC frames? (At the moment I’ve no idea what is causing the problem for you, I’m just curious about it).

29000 frames

very strange

Edit: :bulb:

I don’t know why, but I’ve changed the language from Spanish to English and:

29970 frames

stranger, how is possible this ?

:bulb: And, if a language pack can change the fps, is it possible somehow to have 23976 ¿?

Edit_2: 29970 only with English; any other language, 29000

Very curious indeed. I’ve just tried it in English, French and Spanish, and they all work correctly (29.97 fps).

Perhaps you have some corruption somewhere, or running the Windows 98/ME version on XP? I’ve really no idea. The only suggestion I can think of is to download a fresh copy from http://audacityteam.org/download/beta_windows and completely remove your existing version (including the config file which I think needs to be removed manually), then install the fresh version.

No lucky. I’ve remove appdata and registry entries.

No, win xp alone.

I’ve also download the standalone version, w/o installer, the same.

29000 is an exact number, corruption is unlikely

In Audacity 1.3.4, the settings are held in a configuration file rather than the registry (this includes language settings).
Documents and Settings_user name_Application DataAudacityaudacity.cfg

Thats what I referred to appdata; I also removed it.

http://rapidshare.com/files/111352682/audacity.cfg.html

Try this version (after completely removing your existing version)
http://easyspacepro.com/audacity/audacity-win-unicode-1.3.4.exe

No lucky, 29000

In that case I definately can’t help you - that is the exact same installation file that I used for installing Audacity on my XP machine. There must be something (hardware or software) about your computer that is messing it up. It’s quite ironic that you are one of the few people that want to use this feature, and it doesn’t work on your machine.

The only solution that I can think of (short of getting another computer or re-installing Windows) is to use Linux. I don’t know if you want to go that far with it, but it would be an interesting experiment to try running Audacity from the Live CD version of DSL http://www.damnsmalllinux.org/ (or any other Live CD Linux)

Thank you very steve.

Actually I need 23.976 fps :slight_smile:

I’ve read there are some differences in european windows xp, maybe it’s related. For example, I cannot use latest versions of muxman (an authoring tool) for this reason (for it and that the devoloper doesn’t fix this yet).