Talk:ShowFrameNumber - Revision history

Admin: /* size argument */

2016-03-20T13:15:59Z

size argument

← Older revision		Revision as of 15:15, 20 March 2016
Line 60:		Line 60:
	b.bih.biHeight = height * 8 + 32;		b.bih.biHeight = height * 8 + 32;

	[https://msdn.microsoft.com/en-us/library/windows/desktop/dd318229%28v=vs.85%29.aspx Here] they say that biWidth/biHeight specifies the width/height of the bitmap in pixels. It seems to me that width/height are ~~alread~~ measured in pixels. Guess i'm missing something. [[User:Admin\|Admin]] 14:14, 20 March 2016 (CET)		[https://msdn.microsoft.com/en-us/library/windows/desktop/dd318229%28v=vs.85%29.aspx Here] they say that biWidth/biHeight specifies the width/height of the bitmap in pixels. It seems to me that width/height are already measured in pixels. Guess i'm missing something. [[User:Admin\|Admin]] 14:14, 20 March 2016 (CET)

	[[Category:Talk]]		[[Category:Talk]]

Admin: added comment about size

2016-03-20T13:14:15Z

added comment about size

@@ Line 41: / Line 41: @@
 :Inserted an "unclear" tag, like this: roses are blue<sup>[[(unclear)]]</sup> -- [[User:Raffriff42|Raffriff42]] 06:28, 1 January 2016 (CET)
 ::Good question. I will ask Ian. [[User:Admin|Admin]] 18:20, 3 January 2016 (CET)
 [[Category:Talk]]

Admin at 20:33, 3 January 2016

2016-01-03T20:33:05Z

← Older revision		Revision as of 22:33, 3 January 2016
Line 33:		Line 33:
	</pre>		</pre>
	:::::v2.60, no error, wrong time readout --[[User:Raffriff42\|Raffriff42]] 20:31, 3 January 2016 (CET)		:::::v2.60, no error, wrong time readout --[[User:Raffriff42\|Raffriff42]] 20:31, 3 January 2016 (CET)
			::::::Mmm that's curious. When i use v2.60, i also don't get the error. However when I use the latest CVS (as i was doing, compiled with VC2010), i get the error. See http://www.wilbertdijkhof.com/avisynth.zip. I don't see any relevant code changes in ShowSMPTE though. I don't have VC6 anymore, so i can't run its debugger to see what's going on. Will ask Ian to look at it. [[User:Admin\|Admin]] 21:33, 3 January 2016 (CET)

	=====ShowSMPTE: fps argument=====		=====ShowSMPTE: fps argument=====

Raffriff42: code sample

2016-01-03T19:31:49Z

code sample

← Older revision		Revision as of 21:31, 3 January 2016
Line 26:		Line 26:
	::::ShowSMPTE(clip, x=320, y=240, font="georgia", size=24, text_color=$ff0000)		::::ShowSMPTE(clip, x=320, y=240, font="georgia", size=24, text_color=$ff0000)
	::::I get the error. [[User:Admin\|Admin]] 19:29, 3 January 2016 (CET)		::::I get the error. [[User:Admin\|Admin]] 19:29, 3 January 2016 (CET)
			<pre style="width:68em;margin-left:10em;padding:0.2em;border:none;">
			Colorbars
			AssumeFPS(24.25)
			ShowSMPTE
			return Last.Info
			</pre>
			:::::v2.60, no error, wrong time readout --[[User:Raffriff42\|Raffriff42]] 20:31, 3 January 2016 (CET)


	=====ShowSMPTE: fps argument=====		=====ShowSMPTE: fps argument=====

Admin at 18:29, 3 January 2016

2016-01-03T18:29:36Z

← Older revision		Revision as of 20:29, 3 January 2016
Line 21:		Line 21:
	:: env->ThrowError("ShowSMPTE: rate argument must be 23.976, 29.97 or an integer");		:: env->ThrowError("ShowSMPTE: rate argument must be 23.976, 29.97 or an integer");
	:::*hi Admin; I ran the test with ''AssumeFPS'' as above, not ''fps''=; I knew ''fps''= enforces correct input as you say -- [[User:Raffriff42\|Raffriff42]] 19:06, 3 January 2016 (CET)		:::*hi Admin; I ran the test with ''AssumeFPS'' as above, not ''fps''=; I knew ''fps''= enforces correct input as you say -- [[User:Raffriff42\|Raffriff42]] 19:06, 3 January 2016 (CET)
			::::Post your exact script please. If i use the script:
			::::clip = BlankClip()
			::::clip = clip.AssumeFPS(24.25)
			::::ShowSMPTE(clip, x=320, y=240, font="georgia", size=24, text_color=$ff0000)
			::::I get the error. [[User:Admin\|Admin]] 19:29, 3 January 2016 (CET)

	=====ShowSMPTE: fps argument=====		=====ShowSMPTE: fps argument=====

Raffriff42: correction

2016-01-03T18:08:42Z

correction

← Older revision		Revision as of 20:08, 3 January 2016
Line 20:		Line 20:
	:: else if (abs(_rate - rate) > 0.001) {		:: else if (abs(_rate - rate) > 0.001) {
	:: env->ThrowError("ShowSMPTE: rate argument must be 23.976, 29.97 or an integer");		:: env->ThrowError("ShowSMPTE: rate argument must be 23.976, 29.97 or an integer");
	:::*hi Admin; I ran the test with ''AssumeFPS'', not ''fps''=. I ~~should have been more clear.~~ -- [[User:Raffriff42\|Raffriff42]] 19:06, 3 January 2016 (CET)		:::*hi Admin; I ran the test with ''AssumeFPS'' as above, not ''fps''=; I knew ''fps''= enforces correct input as you say -- [[User:Raffriff42\|Raffriff42]] 19:06, 3 January 2016 (CET)

	=====ShowSMPTE: fps argument=====		=====ShowSMPTE: fps argument=====

Raffriff42: reply

2016-01-03T18:06:16Z

← Older revision		Revision as of 20:06, 3 January 2016
Line 20:		Line 20:
	:: else if (abs(_rate - rate) > 0.001) {		:: else if (abs(_rate - rate) > 0.001) {
	:: env->ThrowError("ShowSMPTE: rate argument must be 23.976, 29.97 or an integer");		:: env->ThrowError("ShowSMPTE: rate argument must be 23.976, 29.97 or an integer");
			:::*hi Admin; I ran the test with ''AssumeFPS'', not ''fps''=. I should have been more clear. -- [[User:Raffriff42\|Raffriff42]] 19:06, 3 January 2016 (CET)

	=====ShowSMPTE: fps argument=====		=====ShowSMPTE: fps argument=====

Admin at 17:20, 3 January 2016

2016-01-03T17:20:41Z

← Older revision		Revision as of 19:20, 3 January 2016
Line 15:		Line 15:
	:Inserted a warning re: non-integral frame rates with ShowSMPTE -- [[User:Raffriff42\|Raffriff42]] 06:28, 1 January 2016 (CET)		:Inserted a warning re: non-integral frame rates with ShowSMPTE -- [[User:Raffriff42\|Raffriff42]] 06:28, 1 January 2016 (CET)
	::If I understand it correctly, the timecodes will always be off for non-integral frame rates. That is, unless you treat them all as drop frames, and count how much frames should be dropped every minute (note: this will not be the SMPTE standard anymore). Perhaps better would have been to throw an error for non-integral framerates and not being one of those standard drop-frame ranges. [[User:Admin\|Admin]] 17:52, 3 January 2016 (CET)		::If I understand it correctly, the timecodes will always be off for non-integral frame rates. That is, unless you treat them all as drop frames, and count how much frames should be dropped every minute (note: this will not be the SMPTE standard anymore). Perhaps better would have been to throw an error for non-integral framerates and not being one of those standard drop-frame ranges. [[User:Admin\|Admin]] 17:52, 3 January 2016 (CET)
			::Edit2: Did you actually run that script (with source fps = 24.25)? AviSynth throws an error in my case. Relevant code:
			::rate = int(_rate + 0.5);
			::...
			:: else if (abs(_rate - rate) > 0.001) {
			:: env->ThrowError("ShowSMPTE: rate argument must be 23.976, 29.97 or an integer");

	=====ShowSMPTE: fps argument=====		=====ShowSMPTE: fps argument=====
Line 21:		Line 26:
	:On testing, it seems the frame rate is overridden, throwing off the real time reading. Would not be useful in the above scenario.		:On testing, it seems the frame rate is overridden, throwing off the real time reading. Would not be useful in the above scenario.
	:Inserted an "unclear" tag, like this: roses are blue<sup>[[(unclear)]]</sup> -- [[User:Raffriff42\|Raffriff42]] 06:28, 1 January 2016 (CET)		:Inserted an "unclear" tag, like this: roses are blue<sup>[[(unclear)]]</sup> -- [[User:Raffriff42\|Raffriff42]] 06:28, 1 January 2016 (CET)
			::Good question. I will ask Ian. [[User:Admin\|Admin]] 18:20, 3 January 2016 (CET)

	[[Category:Talk]]		[[Category:Talk]]

Admin: added remark

2016-01-03T16:52:59Z

added remark

← Older revision		Revision as of 18:52, 3 January 2016
Line 14:		Line 14:
	[[User:Raffriff42\|Raffriff42]] 04:08, 29 December 2015 (CET)		[[User:Raffriff42\|Raffriff42]] 04:08, 29 December 2015 (CET)
	:Inserted a warning re: non-integral frame rates with ShowSMPTE -- [[User:Raffriff42\|Raffriff42]] 06:28, 1 January 2016 (CET)		:Inserted a warning re: non-integral frame rates with ShowSMPTE -- [[User:Raffriff42\|Raffriff42]] 06:28, 1 January 2016 (CET)
			::If I understand it correctly, the timecodes will always be off for non-integral frame rates. That is, unless you treat them all as drop frames, and count how much frames should be dropped every minute (note: this will not be the SMPTE standard anymore). Perhaps better would have been to throw an error for non-integral framerates and not being one of those standard drop-frame ranges. [[User:Admin\|Admin]] 17:52, 3 January 2016 (CET)

	=====ShowSMPTE: fps argument=====		=====ShowSMPTE: fps argument=====

Raffriff42: reply

2016-01-01T05:28:18Z

← Older revision		Revision as of 07:28, 1 January 2016
Line 13:		Line 13:
	ShowSMPTE ## time is wrong		ShowSMPTE ## time is wrong
	[[User:Raffriff42\|Raffriff42]] 04:08, 29 December 2015 (CET)		[[User:Raffriff42\|Raffriff42]] 04:08, 29 December 2015 (CET)
			:Inserted a warning re: non-integral frame rates with ShowSMPTE -- [[User:Raffriff42\|Raffriff42]] 06:28, 1 January 2016 (CET)

	=====ShowSMPTE: fps argument=====		=====ShowSMPTE: fps argument=====
	I don't quite get the '''fps''' argument; is it to force a different framerate for timecode display purposes? For example, to show 24fps film frames on a 30fps video clip?<br>		I don't quite get the '''fps''' argument; is it to force a different framerate for timecode display purposes? For example, to show 24fps film frames on a 30fps video clip?<br>
	[[User:Raffriff42\|Raffriff42]] 04:17, 29 December 2015 (CET)		[[User:Raffriff42\|Raffriff42]] 04:17, 29 December 2015 (CET)
			:On testing, it seems the frame rate is overridden, throwing off the real time reading. Would not be useful in the above scenario.
			:Inserted an "unclear" tag, like this: roses are blue<sup>[[(unclear)]]</sup> -- [[User:Raffriff42\|Raffriff42]] 06:28, 1 January 2016 (CET)

	[[Category:Talk]]		[[Category:Talk]]