<div class="bbWrapper"><blockquote data-attributes="" data-quote="hall" data-source="post: 1860285"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860285"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860285">hall said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Greg, remember, ignore vampz and his talk about MPEG2 vs MPEG4. Seems he really can't let it drop ... everyone did good for a few days or so on this too.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
But its a very relative point to the whole synchronization issue...<br />
<br />
denial doesn't change that.</div>
TIVO vs E*
- Thread starter Juan
- Start date
- Latest activity Latest activity:
- Replies 2K
- Views 183K
- Status
<div class="bbWrapper"><blockquote data-attributes="" data-quote="vampz26" data-source="post: 1860202"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860202"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860202">vampz26 said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Yes. One digital format. <br />
<br />
"The TV streams are converted to an Moving Pictures Experts Group (MPEG) formatted stream for internal transfer and manipulation and are parsed and separated it into video and audio components."<br />
<br />
First is was just the one, mpeg 2 available at the time this was writen, and now there are two. Both use different compression algorithms for their video and audio components, and are thus synchronized differently. This claim clearly needs to be revisited...<br />
<br />
Thanks for clarifying my point.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote> <br />
Actually they argued about MPEG-I during the trial too, so they were discussing at least two MPEG formats back then already. Adding MPEG4 on top of them will not change much.</div>
<div class="bbWrapper">Picture's elements compressed different in MPEG-4 by H.264/AVC or VC-1 algos, not the time stamps.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="Smith" data-source="post: 1860288"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860288"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860288">Smith said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Nope, doesn't required - used same PTS i.e. time-stamps format, because it doesn't compressed at all.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote> <br />
Yes that is the key term, time stamps, not I-frame.<br />
<br />
TiVo's invention is about how to parse out audio and video time stamps, then separate them, then temporarily store them, then some "source object" can "extract" them, then the video time stamps are converted into some "data stream", i.e. index table, then the index table is filled into a buffer...<br />
<br />
I mistakenly used the term "I-frame" because you began to use "I-frame" and I thought you were using "I-frame" to describe the start codes or time stamps. Now you had clarified it, let's drop the term I-frame. I-frame has nothing to do with TiVo's invention, TiVo's invention is about start codes or more appropriately time stamps.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="Smith" data-source="post: 1860288"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860288"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860288">Smith said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Nope, doesn't required - used same PTS i.e. time-stamps format, because it doesn't compressed at all.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
Excuse me? You're going to have to do better than that to refute my claim...<br />
<br />
I know for a fact that the audio/video synchronization is handled differently between mpeg2 and mpeg4 because the audio/video components THEMSELVES are handled differently. I've dabbled in code myself.<br />
<br />
Are you going to tell me, even in layman terms, that mpeg2 and mpeg4, given their significantly different compression ratios, that your one-liner makes any sense?</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="jacmyoung" data-source="post: 1860303"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860303"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860303">jacmyoung said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Actually they argued about MPEG-I during the trial too, so they were discussing at least two MPEG formats back then already. Adding MPEG4 on top of them will not change much.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
Or it changes everything.<br />
<br />
mpeg1 and mpeg2 do not differ much. mpeg4 is the juggernaut in the mix handling audio video components much differently than its predecessors.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="vampz26" data-source="post: 1860317"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860317"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860317">vampz26 said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
...I know for a fact that the audio/video synchronization is handled differently between mpeg2 and mpeg4 ...
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote> <br />
But why is audio/video sync an issue in the TiVo's patent? I don't see where it requires that audio/video sync to be a part of the invention.<br />
<br />
I do not see such requirement in the hardware claims, nor the software claims, nor the patent specification. I might have missed it. Can anyone point out where the audio/video sync is addressed?</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="jacmyoung" data-source="post: 1860312"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860312"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860312">jacmyoung said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Yes that is the key term, time stamps, not I-frame.<br />
<br />
TiVo's invention is about how to parse out audio and video time stamps, then separate them, then temporarily store them, then some "source object" can "extract" them, then the video time stamps are converted into some "data stream", i.e. index table, then the index table is filled into a buffer...<br />
<br />
I mistakenly used the term "I-frame" because you began to use "I-frame" and I thought you were using "I-frame" to describe the start codes or time stamps. Now you had clarified it, let's drop the term I-frame. I-frame has nothing to do with TiVo's invention, TiVo's invention is about start codes or more appropriately time stamps.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
What are these timestamps being calculated from and synchronized too?<br />
<br />
Certainly they would need to correspond to the format of the decoded transmission in some regard.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="jacmyoung" data-source="post: 1860327"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860327"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860327">jacmyoung said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
But why is audio/video sync an issue in the TiVo's patent? I don't see where it requires that audio/video sync to be a part of the invention.<br />
<br />
I do not see such requirement in the hardware claims, nor the software claims, nor the patent specification. I might have missed it. Can anyone point out where the audio/video sync is addressed?
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
Go back and read the thread...its been covered extensively...than you can decide what you 'choose' to accept.<br />
<br />
Its pretty scary if I can keep track of things while being banned better than the actual participants.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="vampz26" data-source="post: 1860331"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860331"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860331">vampz26 said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Go back and read the thread...its been covered extensively...than you can decide what you 'choose' to accept.<br />
<br />
Its pretty scary if I can keep track of things while being banned better than the actual participants.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote> <br />
Please, asking me to go back and read again as if I have not read this thread enough already?<img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile :)" data-smilie="1"data-shortname=":)" /><br />
<br />
The only time audio/video sync was mentioned was when Smith P. said something about audio and video needs to be in sync for playback, but not with DVR trickplays, as I have pointed out already trickplays do not involve any audio, only video.<br />
<br />
During any DVR trickplays you do not ever hear any audio, only see video. And this TiVo patent is all about DVR trickplays. If it talked about just your normal recording and playback like a VCR, the patent would never have been granted. How audio and video must sync is important for TV viewing of course, but it is not what this invention is about.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="jacmyoung" data-source="post: 1860312"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860312"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860312">jacmyoung said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Yes that is the key term, time stamps, not I-frame.<br />
<br />
TiVo's invention is about how to parse out audio and video time stamps, then separate them, then temporarily store them, then some "source object" can "extract" them, then the video time stamps are converted into some "data stream", i.e. index table, then the index table is filled into a buffer...<br />
<br />
I mistakenly used the term "I-frame" because you began to use "I-frame" and I thought you were using "I-frame" to describe the start codes or time stamps. Now you had clarified it, let's drop the term I-frame. I-frame has nothing to do with TiVo's invention, TiVo's invention is about start codes or more appropriately time stamps.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote>I have deep feeling "start code" and I-frame are interchangeable here.<br />
<br />
As to substitute I-frame by time-stamps - no that would be different component for different purpose.<br />
Time-stamps - for sync video/audio.<br />
I-frames - 'it's your stones thru swamp', ie for smooth trick play. Adding to that: you can't avoid sync during trick play - user could start watching any time during the trick functions.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="jacmyoung" data-source="post: 1860335"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860335"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860335">jacmyoung said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Please, asking me to go back and read again as if I have not read this thread enough already?<img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile :)" data-smilie="1"data-shortname=":)" /><br />
<br />
The only time audio/video sync was mentioned was when Smith P. said something about audio and video needs to be in sync for playback, but not with DVR trickplays, as I have pointed out already trickplays do not involve any audio, only video.<br />
<br />
During any DVR trickplays you do not ever hear any audio, only see video. And this TiVo patent is all about DVR trickplays. If it talked about just your normal recording and playback like a VCR, the patent would never have been granted.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
Yes, exactly...and your point?<br />
<br />
Last I checked, the audio and video still need to sync up after a trick play...</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="vampz26" data-source="post: 1860328"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860328"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860328">vampz26 said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
What are these timestamps being calculated from and synchronized too?<br />
<br />
Certainly they would need to correspond to the format of the decoded transmission in some regard.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote>It was INSERTED during recording.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="Smith" data-source="post: 1860342"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860342"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860342">Smith said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
It was INSERTED during recording.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
based on what formula?<br />
<br />
its not a random determination now, is it?</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="Smith" data-source="post: 1860337"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860337"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860337">Smith said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
I have deep feeling "start code" and I-frame are interchangeable here.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote> <br />
Not true, when TiVo talked about start codes during the trial, it was all about time stamps, which had both the audio time stamps and the video time stamps.<br />
<br />
<blockquote data-attributes="" data-quote="" data-source=""
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
As to substitute I-frame by time-stamps - no that would be different component for different purpose.<br />
Time-stamps - for sync video/audio.<br />
I-frames - 'it's your stones thru swamp', ie for smooth trick play. Adding to that: you can't avoid sync during trick play - user could start watching any time during the trick functions.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote> <br />
Audio time stamps and video time stamps may be important for audio and video sync purpose, but this invention is not about using those time stamps to sync audio and video, rather to use those time stamps, more specifically the video time stamps, to help do DVR trickplays.<br />
<br />
The fact audio and video must sync is not the invention here. In fact if this invention were about audio and video sync, it would not have been an invention. The MPEG formats were invented long ago to address the audio and video sync issue, long before this TiVo invention.</div>
<div class="bbWrapper">I'm pointing - both timestamps and I-Frame's positions are key components for produce trick play.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="jacmyoung" data-source="post: 1860351"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860351"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860351">jacmyoung said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Not true, when TiVo talked about start codes during the trial, it was all about time stamps, which had both the audio time stamps and the video time stamps.<br />
<br />
<br />
<br />
Audio time stamps and video time stamps may be important for audio and video sync purpose, but this invention is not about using those time stamps to sync audio and video, rather to use those time stamps, more specifically the video time stamps, to help do DVR trickplays.<br />
<br />
The fact audio and video must sync is not the invention here. In fact if this invention were about audio and video sync, it would not have been an invention. The MPEG formats were invented long ago to address the audio and video sync issue, long before this TiVo invention.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
Bingo<br />
<br />
Audio/Video DO need to sync up during/after trickplays regardless. That too has to be part of the invention or, as you pointed out...its not an invention...<br />
<br />
You may have within the scope of your post, exposed Tivo's patent as illegitimate exactly as Klegg and myself said it was...<br />
<br />
interesting...</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="Smith" data-source="post: 1860354"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860354"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860354">Smith said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
I'm pointing - both timestamps and I-Frame's positions are key components for produce trick play.
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
but have yet to clarify how they are calculated...</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="vampz26" data-source="post: 1860341"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860341"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860341">vampz26 said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
...Last I checked, the audio and video still need to sync up after a trick play...
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote> <br />
As I have explained, audio and video sync is important for TV viewing, but this invention is not about audio and video sync. This invention does take the advantage of the time stamps in the MPEG streams, but not for the purpose of audio and video sync, rather for DVR trickplays. So much so that the claims only talked about converting only the video time stamps, not audio time stamps.<br />
<br />
How the MPEG decoders sync the audio and video is a prior art, an invention predated this TiVo's DVR invention. TiVo could not have had a patent on the audio/video sync technology even if they had tried.</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="vampz26" data-source="post: 1860346"
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
<a href="/xen/goto/post?id=1860346"
class="bbCodeBlock-sourceJump"
rel="nofollow"
data-xf-click="attribution"
data-content-selector="#post-1860346">vampz26 said:</a>
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
based on what formula?<br />
<br />
its not a random determination now, is it?
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote>Just came from independent time generator and converted to specific format (Line22 for VCR, or PTS for digital source) and inserted during recording; all transforms/compression must preserve the time stamps - VCR or DVD or DVR will sync by those signals/stamps in case of dropping any part of the stream or during trick play.</div>
- Status
