| Author |
Message |
Mac
Guest
|
 Posted:
Thu Nov 17, 2005 9:30 pm Post subject:
WME error message - any ideas? |
|
|
The encoding process was unable to keep up with the amount of supplied data
(0xC00D0BCC)
|
|
| Back to top |
|
 |
The March Hare [MVP]
Guest
|
| Posted:
Thu Nov 17, 2005 9:30 pm Post subject:
Re: WME error message - any ideas? |
|
|
On Thu, 17 Nov 2005 19:12:23 -0000, Mac wrote:
| Quote: | The encoding process was unable to keep up with the amount of supplied data
(0xC00D0BCC)
|
From Becky's [MS] post in ../SDK:
That error is NS_E_TOO_MUCH_DATA.
Whenever you get this error while writing to the network, the first thing
to
suspect is that perhaps the network isn't able to keep up with the data
that
the writer is trying to write. If you fall too far behind, that's the
error
you'll get.
If that's not the case, then there is also an obscure error that you might
be hitting, in which the indexer gets confused because there are not enough
key frames. It's unlikely that you're hitting this, but if you are, then
the
workaround would be to disable auto-indexing (you can always do indexing as
a
post-process step on the archived file later).
--
Please read this before replying:
1. Dshow & posting help: http://tmhare.mvps.org/help.htm
2. Trim & respond inline (please don't top post or snip everything)
3. Benefit others: follow up if you are helped or you found a solution |
|
| Back to top |
|
|
Mac
Guest
|
| Posted:
Fri Nov 18, 2005 1:30 am Post subject:
Re: WME error message - any ideas? |
|
|
I think I was in a low memory situation too... but only encoding - not
sending... (a pull session) Have had it a few times now though...
"The March Hare [MVP]" <phil@ndsm.maps> wrote in message
news:1h2gzg65s1kyc$.pz085cu99zce$.dlg@40tude.net...
| Quote: | On Thu, 17 Nov 2005 19:12:23 -0000, Mac wrote:
The encoding process was unable to keep up with the amount of supplied
data
(0xC00D0BCC)
From Becky's [MS] post in ../SDK:
That error is NS_E_TOO_MUCH_DATA.
Whenever you get this error while writing to the network, the first thing
to
suspect is that perhaps the network isn't able to keep up with the data
that
the writer is trying to write. If you fall too far behind, that's the
error
you'll get.
If that's not the case, then there is also an obscure error that you might
be hitting, in which the indexer gets confused because there are not
enough
key frames. It's unlikely that you're hitting this, but if you are, then
the
workaround would be to disable auto-indexing (you can always do indexing
as
a
post-process step on the archived file later).
--
Please read this before replying:
1. Dshow & posting help: http://tmhare.mvps.org/help.htm
2. Trim & respond inline (please don't top post or snip everything)
3. Benefit others: follow up if you are helped or you found a solution |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in