cannot render file??

[complich8]

err, is it possible that your download of the files you're trying to play hasn't completed?

Presumably you're downloading from batches, what does the file list for your client say? What client are you using?

[naruto=pwnage]

just recently, yesterday actually. I started using BitComet. I originally was using azureus. but it was using to much RAM for my liking so I decided to start using BitComet and try it out. I know for a fact the files I'm trying to play have both downloaded completely since it says beside them 100%. also VlC seems to be unable to play these files. I have not yetredownloaded CCCP but I will in a minute and I'll edit to tell you all how it went and if all my stupid problems have ended.


EDIT: dammitalltohell. the files STILL won't work. and yet, the first two do. grr..

[complich8]

I recommend another client switch, this time to utorrent.

As for the current problem, maybe just wait until the batch completes?

"Can't render file" (as opposed to something like "can't locate decompressor") usually indicates that the file looks like nonsense to the player. Which could mean that the client just hasn't gotten around to rearranging the pieces it downloaded into a coherent file yet.

Generally, a media player's approach to rendering a file is something like this:
step 1: determine the container type (ie: use the file extension, or mime/magic data). Errors here would be something like "unsupported file type" or "unknown file format". If you try to open an mkv without an mkv-handler installed, for example, you'd probably hit this. Codec packs usually fix these things, by bundling those container handlers.
step 2: open the file. Errors here would be "access denied" "unable to open file" or the like, indicating that the file is locked or you don't have permissions to open it. Things that will hold locks on files include other media players, torrent clients, and sometimes explorer itself. Sysinternals process explorer can be helpful in finding what is holding file locks.
step 3: parse the container for streams and formats. At this point, if the file is unparseable, it'll give you render failures, "failed to render file" for example.
step 4: find decoders. This is where you'd get "can't locate appropriate decompressor" sort of errors. That's the sort of thing goes away when you've got an appropriate codec or playback filter registered.
step 5: set up render filters and start playback. This is where you'd get runtime errors -- corrupted frames, invalid data in streams, etc...

This sounds to me like in your case, it's failing at step 3. Meaning the client isn't holding the locks anymore, but the data doesn't make sense to it.

[Kraco]

step 4: find decoders. This is where you'd get "can't locate appropriate decompressor" sort of errors. That's the sort of thing goes away when you've got an appropriate codec or playback filter registered.

There aren't always any visible error messages here. The file might play, but with no video or with no audio. This happens sometimes when a subber group by accident uses some strange encoding or setting.

[complich8]

quite true. Depends on the player and its settings too, though.

[naruto=pwnage]

HALLE FREAKIN' LUJA!!! IT WORKS!!
somethiing must have happened while downloading on BitComet but it works now. thanks for reccomending uTorrent good advice many thanks!
peace

[Munsu]

I guess it's what I said, BitComet was probably still using the file...

When you click on the batch torrent and see the files in BitComet you'll notice that some finished files are still on "Write and Read" status.