If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
"Bill in Co" wrote in
m: The very few (so-called) "file repair" apps I've tried haven't worked yet on a corrupted file, so who knows. I think that makes sense, as it would be infinitely harder to fix (reconstruct) a corrupt video file (or an exe file, for that matter!!), than something as simple as a text (or even doc) file, for that matter. Doesn't bother me that much, if a frame is borked, the error only persists till the next keyframe anyway. |
#12
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
"Bill in Co" wrote in
m: That videohelp site has version histories for lots of files on its site, so you may find something in that regard. Here is the ffdshow link, and on it you'll find the changelogs for ffdshow. http://www.videohelp.com/tools/ffdshow Large log! Not all that useful though. For example: 1668 Introducing Layer for Unicode on Windows 9x. trunk : re-enable Windows 9x support. beta4 branch is updated at the same time. Not sure what version is meant by 1668, nor is there any word of when 9x support stopped, but it certainly did, and was not logged as such. The aspect ratio thing is very unclear from that log, but it is clear that they revisit the issue a lot so they do intend to keep it accessible to us, from what I can see. It also seems that they try to keep the size down to around 5 MB for much of the development, so bloat is presumably reigned in. There are curious hints like 'removed references to WAVpack from web stuff' or some such. Very cryptic. Not sure why WAVpack wasn't to their liking, but perhaps it has to do with being closed source despite free to use. Anyone know which latest FFDshow reliably works on W9X? I doubt there's a definitive answer, if the makers never logged any discontinuation, so personal accounts of success will be all we have. I don't mind trying FFdshow but I'll find it easier to take seriously if I don't have to blunder about for months trying everything they ever released, in an effort to get satisfaction. Yes, I know about the philosopher Jagger, but the philosopher House says work smart, not hard... |
#13
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
Lostgallifreyan wrote:
"Bill in Co" wrote in m: The very few (so-called) "file repair" apps I've tried haven't worked yet on a corrupted file, so who knows. I think that makes sense, as it would be infinitely harder to fix (reconstruct) a corrupt video file (or an exe file, for that matter!!), than something as simple as a text (or even doc) file, for that matter. Doesn't bother me that much, if a frame is borked, the error only persists till the next keyframe anyway. Well, as far as these video file "repair" utilities are concerned, this is assuming they can actually read the file in correctly and in sequence, and detect the sequential frame boundaries properly as it does so. I'm not sure that's possible. If it is, then I could see how this could work. But if a file is truly corrupted (say like the power went out as it was being written to disk, or something even worse), is that really possible? Or does the file instead just appear as a random sequence of bits and bytes to the file utility? Maybe it depends critically on what kind of file it was in the first place as to whether or not it's even possible at all to recover it. |
#14
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
Lostgallifreyan wrote:
"Bill in Co" wrote in m: That videohelp site has version histories for lots of files on its site, so you may find something in that regard. Here is the ffdshow link, and on it you'll find the changelogs for ffdshow. http://www.videohelp.com/tools/ffdshow Large log! Not all that useful though. For example: 1668 Introducing Layer for Unicode on Windows 9x. trunk : re-enable Windows 9x support. beta4 branch is updated at the same time. Not sure what version is meant by 1668, nor is there any word of when 9x support stopped, but it certainly did, and was not logged as such. The aspect ratio thing is very unclear from that log, but it is clear that they revisit the issue a lot so they do intend to keep it accessible to us, from what I can see. It also seems that they try to keep the size down to around 5 MB for much of the development, so bloat is presumably reigned in. There are curious hints like 'removed references to WAVpack from web stuff' or some such. Very cryptic. Not sure why WAVpack wasn't to their liking, but perhaps it has to do with being closed source despite free to use. Anyone know which latest FFDshow reliably works on W9X? I doubt there's a definitive answer, if the makers never logged any discontinuation, so personal accounts of success will be all we have. I don't mind trying FFdshow but I'll find it easier to take seriously if I don't have to blunder about for months trying everything they ever released, in an effort to get satisfaction. Yes, I know about the philosopher Jagger, but the philosopher House says work smart, not hard... I don't have a definitive answer on this for you, and would be surprised if anyone here does either. :-) I guess the documentation at the videohelp site and the ffshow sites is a bit sparse. But I thought I throw these two ideas out to you: Since there were so many releases, you could probably use a divide and conquer approach, and just try out versions released in 6 month intervals, and potentially narrow it down from there. Still a bit of work, however. :-) I can tell you that on my Win98SE computer, I wasn't able to play mp4 files, so I installed a version of the K-Lite Codec Pack for Win98 last year (which installed ffdshow), and that seems to work well on my Win98 computer. The K-Lite Codec Pack version was version 345 (3.4.5.0) (for Win98), and when I select properties on its ffdshow.ax file, it shows version 1.00.3.1464, build date 05/09/2007, although the ax file date in explorer is 9/10/2007. |
#15
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
Bill in Co wrote:
The K-Lite Codec Pack version was version 345 (3.4.5.0) (for Win98), and when I select properties on its ffdshow.ax file, it shows version 1.00.3.1464, build date 05/09/2007, although the ax file date in explorer is 9/10/2007. I have version 1.0.5.2427 of ffdshow.ax, with a build-date of 05/01/2009 on the win-98 system I'm typing this post on. |
#16
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
98 Guy wrote in :
Bill in Co wrote: The K-Lite Codec Pack version was version 345 (3.4.5.0) (for Win98), and when I select properties on its ffdshow.ax file, it shows version 1.00.3.1464, build date 05/09/2007, although the ax file date in explorer is 9/10/2007. I have version 1.0.5.2427 of ffdshow.ax, with a build-date of 05/01/2009 on the win-98 system I'm typing this post on. With or without KernelEx? I'll look at that though. It may even be possible to compile ffdshow with GCC on W98, but it may be harder to figure out all the detail needed to do that, than to find a compile that already works. Bill, I found MP4 playable if I also added a MP4splitter.ax file, apparently from Gabest.org. Haven't yet got WMV working, but I do have separate codecs for that anyway. FLV would be nice... What I'm basically after now is a set-and-forget codec setup. So long as it lets me use MPC which I prefer, and will co-operate to play the formats I use, and lets me do that without having to think about it for another five years, I'll get by. It took awhile for the dust to settle in the codec wars, but it looks now like there isn't much to choose from other than finding the latest one that works. (Various reports say that stuff doesn't always stay working though, so once I have one that does, I'll stay put and live with it rather than agonise over trying to keep up with stuff I can't expect to control.) |
#17
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
"Bill in Co" wrote in
m: Maybe it depends critically on what kind of file it was in the first place as to whether or not it's even possible at all to recover it. Maybe they should be shipped with PAR2... Doesn't need a lot of that to give redundant cover, apparently. 'Broken' files may work find on another codec, too, I imagine, if they are not really broken, just misread by a decoder that can't handle something a later encoder made. I wonder if some repairs rely on reading backwards from a good key frame, if the normal forward reading got disrupted. That way a damaged keyframe might be fixed, resulting in no worse than momentary blurring. I'm ok with remaining ignorant though. Working with video technology is so timeconsuming that only specialists can expect to know enough to keep up with the changes. If I tried, I wouldn't get much else done. |
#18
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
Lostgallifreyan wrote in
: The K-Lite Codec Pack version was version 345 (3.4.5.0) (for Win98), and when I select properties on its ffdshow.ax file, it shows version 1.00.3.1464, build date 05/09/2007, although the ax file date in explorer is 9/10/2007. I have version 1.0.5.2427 of ffdshow.ax, with a build-date of 05/01/2009 on the win-98 system I'm typing this post on. I think I posted this earlier, but my version is ffdshow_rev2322_20081114_clsid.exe, somewhere between those two. I think after W9X support was dropped, it was put back, but some people chose to ignore than and compiled it on WXP, and FOR WXP, but others may have observed the intent to retain the support (last official log entry states that it was reinstated, as I quoted in a post earlier. So there may be some very recent ones that work fine, even without KernelEx to get them installed.) |
#19
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
Lostgallifreyan wrote in :
I think I posted this earlier, but my version is ffdshow_rev2322_20081114_clsid.exe, somewhere between those two. http://www.msfn.org/board/topic/1059.../page__st__322 First post there says mine is latest official build, but I doubt that, because the history file said nothing about that for 2322, and even if W9X support were dropped, it isn't the first time it was put back. All the reports of it being dropped date earlier than reports saying it works. I'm also suspicious of a pattern of version numbers that appears to have taken from some time after late 2005 (year) to progress to 2232 three years later, and 4453 as curent milestone. There are more versions of ffdshow than DAYS in those few years. No-one can nail down any kind of definitive state of release in a development like that. Even a mad CVS releasing nightly builds without a day's break in twelve years can't release as many builds as there are of ffdshow in just seven years. |
#20
|
|||
|
|||
XviD codec for W98 and Media Player Classic.
Lostgallifreyan wrote:
I have version 1.0.5.2427 of ffdshow.ax With or without KernelEx? My system(s) have Kex, but I have no idea if it's needed for that version of the K-lite codec pack. The K-lite that I have, I installed in Feb 2010. It includes mediaplayer classic (version 6.4.9.0, looks like file-date March 20 / 2006). FFDshow files seem to date mostly between nov/dec 2008 and jan 2009. Looks like I installed it from a file called klite285.exe, which I don't know off-hand where I got it from, but it looks like this link will give you a nice selection of choices: http://alteversion.de/k-lite/ |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
problem with mp3 player/windows media player | Mirey86 | General | 0 | June 3rd 08 09:13 AM |
Media Player Codec issue | Steve | Multimedia | 0 | October 11th 05 06:15 PM |
Mp3 player is not found in Windows MEdia player 8.0 | Banker | Multimedia | 1 | September 7th 05 01:09 AM |
Problem using Media Player and Zoom Player since screwing around with DivX | Mark | General | 3 | January 29th 05 03:35 PM |
Windows Media Player vs Real player | General | 1 | August 14th 04 03:01 PM |