Comments on: SMPTE 12M Timecode Support for Silverlight http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/ Ideas on technology and media Sat, 08 May 2010 11:52:53 +0000 hourly 1 http://wordpress.com/ By: Curtis http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-154 Curtis Wed, 28 Apr 2010 16:23:38 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-154 Your technique is fine if the timecode of the video is continuous, but I have a customer that will supply video with discontinuous timecode (stuff still only roughly edited with starts and stops). Is there any Windows compatible library for reading the timecode stream rather than just doing calculation based on start time? Your technique is fine if the timecode of the video is continuous, but I have a customer that will supply video with discontinuous timecode (stuff still only roughly edited with starts and stops). Is there any Windows compatible library for reading the timecode stream rather than just doing calculation based on start time?

]]> By: John Deutscher http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-130 John Deutscher Wed, 06 Jan 2010 17:03:16 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-130 Gern geschehen. Lassen Sie mich wissen, wenn Sie irgendwelche Fragen zu sehen. Danke Gern geschehen. Lassen Sie mich wissen, wenn Sie irgendwelche Fragen zu sehen.
Danke

]]> By: Polling Video – A Viable sub-second alternative? - Jesse Liberty - Silverlight Geek http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-129 Polling Video – A Viable sub-second alternative? - Jesse Liberty - Silverlight Geek Thu, 31 Dec 2009 04:27:52 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-129 [...] regard to my intended use of embedded “heartbeat” markers.  Mike Loynd (WL) referred me to this fascinating article by John Deutscher (PM for IIS Media).  That caused me to experiment with [...] [...] regard to my intended use of embedded “heartbeat” markers.  Mike Loynd (WL) referred me to this fascinating article by John Deutscher (PM for IIS Media).  That caused me to experiment with [...]

]]> By: [Silverlight] TimeCode aus .wmv auslesen - Forum Fachinformatiker.de http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-122 [Silverlight] TimeCode aus .wmv auslesen - Forum Fachinformatiker.de Fri, 06 Nov 2009 16:05:51 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-122 [...] [...] [...] [...]

]]> By: John Deutscher http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-120 John Deutscher Thu, 29 Oct 2009 18:51:25 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-120 There are no current workarounds other than to stretch out the length of the file and put in a marker where you want the end to be and to pause / stop when you reach that point. However, this workaround will change other behaviors. For instance, you won’t get MediaEnded events using that technique since you’ve effectively invented you own MediaEnded event that happens before MediaEnded. Beyond that, the only other workaround that even remotely comes to mind is build a <a href="http://msdn.microsoft.com/en-us/library/system.windows.media.mediastreamsource%28VS.95%29.aspx" rel="nofollow">MediaStreamSource </a> and handle all of the samples yourself, but that is a fair amount of work. There are no current workarounds other than to stretch out the length of the file and put in a marker where you want the end to be and to pause / stop when you reach that point. However, this workaround will change other behaviors. For instance, you won’t get MediaEnded events using that technique since you’ve effectively invented you own MediaEnded event that happens before MediaEnded.

Beyond that, the only other workaround that even remotely comes to mind is build a MediaStreamSource and handle all of the samples yourself, but that is a fair amount of work.

]]> By: Sergey Novikov http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-119 Sergey Novikov Thu, 29 Oct 2009 10:25:32 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-119 Hi, John. Do you have any thoughts about workaround on 1% ussue with mediaelement, or do you have contact of someone I can ask about it? Hi, John.
Do you have any thoughts about workaround on 1% ussue with mediaelement, or do you have contact of someone I can ask about it?

]]> By: John Deutscher http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-118 John Deutscher Mon, 26 Oct 2009 23:31:30 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-118 Kalyan, I'm assuming you mean that you want to validate the entry of some timecode? Usually that should be done at the UI level, but I also do it when parsing strings passed into the timecode class. In the Timecode.cs file I just used a Regular Expression to validate the format of the timecode and then checked to see if the data was in the expected range. Regex = "(?\\d{2}):(?\\d{2}):(?\\d{2})(?::|;)(?\\d{2})" You actually can just split the string on ":" and ";" and validate the ranges on the results. I think each of my functions validates the range of the frames specifically for the specific format (25, 24, etc..). Kalyan,
I’m assuming you mean that you want to validate the entry of some timecode? Usually that should be done at the UI level, but I also do it when parsing strings passed into the timecode class.

In the Timecode.cs file I just used a Regular Expression to validate the format of the timecode and then checked to see if the data was in the expected range.
Regex = “(?\\d{2}):(?\\d{2}):(?\\d{2})(?::|;)(?\\d{2})”

You actually can just split the string on “:” and “;” and validate the ranges on the results. I think each of my functions validates the range of the frames specifically for the specific format (25, 24, etc..).

]]> By: Kalyan chakrvarty http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-117 Kalyan chakrvarty Mon, 26 Oct 2009 12:48:20 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-117 John, How can i validate the TimeCode in a efficient way, so that i can catch the wrong entry. Can you please help me regarding this issue. Kalyan John,

How can i validate the TimeCode in a efficient way, so that i can catch the wrong entry. Can you please help me regarding this issue.

Kalyan

]]> By: John Deutscher http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-116 John Deutscher Sun, 25 Oct 2009 01:17:26 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-116 Sergey, The 1% issue at the end of a video was something I had not seen before in testing. I went back and looked some more at it and asked around and it is apparently a known behavior of the Silverlight MediaElement runtime. Seeking at the last 1% of a file results in the runtime seeking to the lesser of the NaturalDuration *0.99 or 1 second. There were designed reasons for this I believe. The issue that you found in the conversion for PAL was also addressed in my latest updates to the Timecode class. I have actually been switching from decimal math to float for some of the functions to fix some precision rounding issues. Sergey,
The 1% issue at the end of a video was something I had not seen before in testing. I went back and looked some more at it and asked around and it is apparently a known behavior of the Silverlight MediaElement runtime. Seeking at the last 1% of a file results in the runtime seeking to the lesser of the NaturalDuration *0.99 or 1 second.
There were designed reasons for this I believe.

The issue that you found in the conversion for PAL was also addressed in my latest updates to the Timecode class. I have actually been switching from decimal math to float for some of the functions to fix some precision rounding issues.

]]> By: John Deutscher http://blog.johndeutscher.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-115 John Deutscher Sun, 25 Oct 2009 01:02:37 +0000 http://johndeutscher.wordpress.com/2009/02/18/smpte-12m-timecode-support-for-silverlight/#comment-115 John, I have not done any profiling of that method myself, but that sounds about right. For most of the apps that I have used the TimeCode class in I have found that 200ms updates is just fine for refreshing the UI text of the timecode as it it ticking along. I'm not sure about your specific use case, but I can't seem to get my brain to even read the frames as they are ticking along that quickly anyways. I would not bother trying to update the UI for every frame unless you have some really specific need to be that accurate (although you will likely be more constrained by the speed of the user that is interacting with your app). John,
I have not done any profiling of that method myself, but that sounds about right. For most of the apps that I have used the TimeCode class in I have found that 200ms updates is just fine for refreshing the UI text of the timecode as it it ticking along. I’m not sure about your specific use case, but I can’t seem to get my brain to even read the frames as they are ticking along that quickly anyways.
I would not bother trying to update the UI for every frame unless you have some really specific need to be that accurate (although you will likely be more constrained by the speed of the user that is interacting with your app).

]]>