About half of the time that I hit "stop" and close the player on a valid AVI, it seg faults.
MPlayer doesn't have a "stop". Perhaps you're talking about gmplayer or some other front-end?
If I try to play corrupted AVI files (which it should choke on), it seg faults (which it should not do, as that indicates a failure in bounds checking that could be very dangerous if viewing untrusted content).
Nobody in their right mind would have MPlayer running as root, so it's not a huge risk. Certainly, yours is a bug nobody else is seeing these days.
(I've used the Fedora and/or FreshRPMS versions only), and are thus compiled with fairly modern compiler versions
"fairly modern" doesn't mean anything. gcc 2.96 was "fairly modern" at one time. gcc 3.3 is fairly modern too, yet buggy as hell.
Also, unofficial packages have been known to have numerous problems in the past. Try the official RPMs on the website, if you don't want to compile anything.
What are the developers doing differently that seg faults are so rare for them?
Using official versions. Compiling from source themselves. Using the latest versions of the program. Not using gmplayer or any other front-end. etc.
Are they only using carefully crafted test files?
No, definately not. MPlayer has an ftp directory just for people to upload problematic files.
Are they running with some special libraries or compiler versions?
No, although avoiding libraries and compiliers with custom distro "fixes" will certainly help a lot. I know, first hand" RedHat has a history of really buggy software in their releases, libraries and compilers. gcc 2.96 was a RedHat-only phenomenon, which was derided by most of the free software world.
Is there an unreleased fix?
Quite a few in CVS, since there hasn't been an actual release since 1.0pre7 about a year ago.
So what your saying is you want cigarette style warnings on ALL product packages you buy?
No, not even remotely all products. Only those who have a serious limitation (ie. making the whole thing useless in a short period of time) and no reasonable way for the individual to fix that problem.
Blaming the users for not paying more for an extended warranty is completely ridiculous.
t is of course very difficult to figure out that it was a reply to your post (and relates to it) or, *gasp* to read the pages I pointed you at.
No, I did read through that Wikipedia link in fact. It said NOTHING ELSE on the subject, than what you posted here.
but in any application where high currents are required and weight/volume is less important a consideration then cost, lead acid is by far the best choice.
No, it's not nearly as simple as that. Lead Acid also has the distinction of dropping it's voltage as current is consumed, making it a poor choice in many applications (including starting your car, actually), it loses much more power in a no-load situation in much less time than NiCds, and it can supply far less current in low tempuratures than NiCds. Lead acid batteries also need a much smarter charger, because under or overcharging them will do permanant damage.
Even if you don't consider weight, there are many reasons to use NiCds.
i think that this is an exageration, that it will take a week to install java. two days ago i installed JDK on fedora server Core 2. btw you need much smaller JRE instead of JDK (15M vs. 45M).
I'm on FreeBSD... I have to go download package after package, clear up about 2GBs in/usr, and wait as it downloads and compiles Openmotif, Linux binary compatibility modules, etc. etc.
i think there is some misunderstanding about bouncers, because bouncers in no way are mandatory
Yes, I misunderstood, likely due to the limited info in the "About" page I had to draw on. It reads more like a thesis (bouncing from subject to subject, covering DDoS issues in detail, which I don't really care about at this point) than an introduction to the project.
Java was a natural choise to bring prove of concept fast and get feedback from the users. unfortunately the feedback remains zero.
*sigh*
Yeah, alright, I'll try it out. It make take a week before I have a jdk up and working, but oh well. I really hate Java.
among planned steps is implementation in C# (Mono) and small embeddable C/C++ agent
I'd probably have tried it before now if there was a C/C++ client. Preferably with a GUI of some kind, even some web-based interface would be okay.
But then again, Java P2P clients like Limewire/Bearshare are fairly popular, so it might just be me.
If you're really interested in getting users, why not try submitting a story to/. here?
Xine does support the "all" package of codecs - I use it!
Now you're just taking things out of context. I said (in the next sentence):
I sincerely doubt Xine supports all of those avalilable.
So, unless you've tested EVERY DLL in there, you're not proving anything.
Try doing some research before posting...
You've clearly misunderstood. I wasn't saying Xine didn't support those codecs, just providing a list you could use for comparison. I'm not about to spend an hour of research on every idiotic claim someone makes on/.
you even mention codec's which are supported by ffmpeg (e.g: libavcodec).
Umm, what? If you're trying to say that libavcodec is from the ffmpeg project, I know that quite well. MPlayer and ffmpeg are largely one-in-the-same, sharing servers and developers. In fact devs for either project have commit access to the other, by default, and most use it.
If you're trying so say something else, I completely missed it.
You're trying to take someone out of his time and apply your moral to him.
As are you. Perhaps the founding father's minds would be changed about voting independantly of political parties, if they had been born in modern times.
Unfortunately, most of us are sheep, simply following the social mores of our time with little thought other than fitting in - the Milgram experiment has proven this:
The Milgram experiment was not about social mores, but about the pursuasive effect of authorities, over your own personal objections. Really completely different issues.
As an example though, Xine uses the same codecs as mplayer, in fact you download them from the mplayer site! So stating that it supports less file formats is ludicrous!
Absolutely wrong. You have no idea what you are talking about.
First off, the "essential" codecs xine has you download are only a fraction of the codecs available in the "all" packages (you want both the Linux and Win32 ones), and I sincerely doubt Xine supports all of those avalilable. They tend to focus their efforts on the most popular, and neglect all the less common formats.
In addition, even if it did support all the binary DLLs, those are only a fraction of the codecs MPlayer supports. These include: qtx x264 xvid libavcodec real dshow/dmo win32 faad2 libmpeg2 liba52 mp3lib libtheora tremor libmad gif opendivx libdv amr_wb amr_nb xanim faac musepack libdts speex twolame toolame liblzo. And those are only the offical ones. There are a few patches floating around for other odd codecs as well.
In addition to all of this, it's not just a question of having the codecs working. In order to make any use of them, you have to be able to decode the container to read out the streams. New Quicktime/MOV atoms spring up rather frequently, and it's the MPlayer devs that figure out how to decode them, and presumably with the xine guys checking out the code somewhat later and integrating those new features into their player. I very rarely see the opposite. This usually is the big issue with new formats not working, particularly when they use codecs that are otherwise supported.
So stating that it supports less file formats is ludicrous!
Acting like you know what you're talking about is ludicrous!
Xine developers will tell you that Xine is based on a large ammount of MPlayer/ffmpeg code, and that they continue to pull updates and fixes from MPlayer.
Is it so hard for you to believe that different people can have different experiences on different hardware setups?
Yes. It makes absolutely no sense at all that MPlayer, which has been heavily optimized with hand-written assembler in speed-critical places (including imported libraries) would be slower than Xine, which has not recieved much performance tuning, and certainly doesn't have the hand-optimized code that MPlayer does.
Extrodinary claims require extrodinary proof. I'll believe it when I see someone provide detailed benchmarks with both, a copy of the sample used, and plenty of system info. It's not hard, but nobody is doing it... Presumably because they can't.
Besides that, I have no reason to trust these posts. Almost NOBODY is even posting as a logged-in user, so this could just as well be one idiot masquerading as several for all I know. None of which are spending a minute to provide real evidence.
I've only used it once in a program, and it made trivial for me to play a sound (and it accepted WAV, MP3...). ffmpeg is a much more low-level library.
Xine-lib is right in the middle. At the low-end is libavcodec, then xine-lib, then at the ultra-easy end is MPlayer in slave-mode, which is also used extensively by many programs.
So hrm.. they do have quite some disadvantages, but being unable to handle high current output is not one of them, rather the opposite actually.
"High current output" is a COMPLETELY arbitrary designation. It's only meaningful if you provide some numbers, or refering to it in COMPARISON TO SOMETHING ELSE.
The battery in my watch is good at "high current output" too...
So when Americans say "laws like this will end up with cell-phones tossed in the nearest river" - Now you know why.
The primary reason would be because he didn't bother to read the article at all, where it was clearly addressed.
Also, I happen to be an American, and in California, household hazardous waste disposal is free for individuals, although medium/large businesses are required to pay for proper disposal.
Yes, they've existed in the past, but you really won't find any for about the past decade at least.
That really wasn't the point, anyhow. This thread is about the reasons for using cadmium (hence the portable drill reference), and lead acid batteries certainly don't provide anywhere near the high current output that cadmium does, so it's not even applicable.
Yeah, but at worst they'd dump them in a landfill, and you'd be no worse off.
But really, it's much, much easier to catch companies than individuals. A small company from around here was just recently caught dumping hazardous waste down the sewers...
WHAT THE FUCK DOES SOME STUPID SLASHDOT UID HAVE TO DO WITH THE VERACITY OF ANYTHING?
If he had posted any evidence to back-up his claims, it wouldn't have mattered at all.
However, in the case of bald-faced assertions that go against all logic, with no evidence, the UID and lack of karma bonus will usually tell you whether or not you're just seeing some 13 year old who doesn't know what he's talking about, some troll with a nice new account, etc.
Fucked-up people like you have turned/. into a cesspit.
Looking through your comment history, it looks like you might actually hold that distinction.
and this is exactly how data transfer layer works in my Rody project. google Rodi P2P
Yes, I keep hearing about Rodi, and then I go to the website and read that part about requiring Java, "bouncers" being trusted to handle all data, and I run like hell in the other direction...
I've always wanted an OS that loaded drivers for every single peripheral ever made just in case I ever plugged one of them in.
Although they are part of the kernel, they really aren't loaded, in the Linux sense of the term.
That's one of the main reasons why compiling your own kernel in Linux is a day-to-day thing, while it's almost never done in the BSD world, despite it being quicker, simpler, etc.
But on OpenBSD it would get fixed a lot more quicky because everyone would potentially be vulnerable.
No, that's just crap, and you have no idea what you're talking about.
And thank God they have avoided crazy and buggy hacks like loadable modules and only loading drivers you actually need.
Although you're trying to flame, you're absolutely right. Loadable modules are a massive security hole, as well as being buggy, a huge hassle, etc.
I'm switching to BSD immediately because I am always moving my HDD from one machine to another and having my soundcard work automatically when I do that is a major plus.
Removable hard drives are wonderful. IDE, Firewire, USB2, etc. I move harddrives around constantly, and having to manually reconfigure everything is a really massive hassle, and seriously buggy with the unstable and bloated Linux tools that try to fake the real PnP support the BSDs have had from the beginning.
But hey, I don't expect you to understand. I know brain-cells don't grow on trees, and some have far more than others...
Of which, ALL li-ion batteries carry a shelf-life of 18 months so no fsking wonder they stopped working. Anything else is gravy.
I don't know where this bullshit comes from. I've got LiIon batteries from nearly A DECADE ago which are still working perfectly.
People are fond of saying that LiIon batteries lose 50% of their capacity each year, ignoring the facts around that statistic, which says that only happens if they are stored at their maximum charge level over that time. If you have a smart charger, which keeps them at around 80%, they should last for many years, with only a slight decrease in capacity over time.
If people are too cheap to spend $60 protection more on a $300+ purchase it's their own damn fault imo.
No. Not when it's well known the limited life-span of the batteries, the fact they aren't user replaceable, and yet Apple didn't provide any "downer" info about this fact on the package.
NiCd don't last nearly as long and have a lower energy density.
No, actually they DO last nearly as long. The best NiCds were at about a 25% disadvantage to the best NiMH batteries when I last checked, Besides that, NiCds have the advantage of being far lighter than NiMH or Lead Acid, and somewhat lighter than LiION, which can be a real advantage in vehicles.
NiMH do not contain cadmium and are capable of also delivering high amounts of current.
They've been working very hard to get NiMH to provide high current, but it's still not as powerful. NiCds can deliver their full current in a very short period of time, making them preferred for high-loads.
In fact, all of the rechargable AA batteries I see in the stores for cameras and whatnot are now NiMH instead of NiCD.
I believe that's mainly to do with the fact that NiMH don't naturally lose their charge as quickly as NiCd, as well as issues with memory effects.
if you try to overcharge them, then the excess energy simply goes into separating the water in the electrolyte into hydrogen and oxygen.
That's completely wrong. Overcharging lead-acid batteries will seriously damage them.
I generally like lead acid too, but they do have several disadvantages, and it doesn't look like it will take long before something else will surpass lead acid in price, while not having as many disadvantages (tempurature, natural discharge rate, unstable voltage, etc).
Slashdot Mirror
MPlayer doesn't have a "stop". Perhaps you're talking about gmplayer or some other front-end?
Nobody in their right mind would have MPlayer running as root, so it's not a huge risk. Certainly, yours is a bug nobody else is seeing these days.
"fairly modern" doesn't mean anything. gcc 2.96 was "fairly modern" at one time. gcc 3.3 is fairly modern too, yet buggy as hell.
Also, unofficial packages have been known to have numerous problems in the past. Try the official RPMs on the website, if you don't want to compile anything.
Using official versions. Compiling from source themselves. Using the latest versions of the program. Not using gmplayer or any other front-end. etc.
No, definately not. MPlayer has an ftp directory just for people to upload problematic files.
No, although avoiding libraries and compiliers with custom distro "fixes" will certainly help a lot. I know, first hand" RedHat has a history of really buggy software in their releases, libraries and compilers. gcc 2.96 was a RedHat-only phenomenon, which was derided by most of the free software world.
Quite a few in CVS, since there hasn't been an actual release since 1.0pre7 about a year ago.
No, not even remotely all products. Only those who have a serious limitation (ie. making the whole thing useless in a short period of time) and no reasonable way for the individual to fix that problem.
Blaming the users for not paying more for an extended warranty is completely ridiculous.
No, I did read through that Wikipedia link in fact. It said NOTHING ELSE on the subject, than what you posted here.
No, it's not nearly as simple as that. Lead Acid also has the distinction of dropping it's voltage as current is consumed, making it a poor choice in many applications (including starting your car, actually), it loses much more power in a no-load situation in much less time than NiCds, and it can supply far less current in low tempuratures than NiCds. Lead acid batteries also need a much smarter charger, because under or overcharging them will do permanant damage.
Even if you don't consider weight, there are many reasons to use NiCds.
I'm on FreeBSD... I have to go download package after package, clear up about 2GBs in
Going into day 2 now...
Yes, I misunderstood, likely due to the limited info in the "About" page I had to draw on. It reads more like a thesis (bouncing from subject to subject, covering DDoS issues in detail, which I don't really care about at this point) than an introduction to the project.
*sigh*
Yeah, alright, I'll try it out. It make take a week before I have a jdk up and working, but oh well. I really hate Java.
I'd probably have tried it before now if there was a C/C++ client. Preferably with a GUI of some kind, even some web-based interface would be okay.
But then again, Java P2P clients like Limewire/Bearshare are fairly popular, so it might just be me.
If you're really interested in getting users, why not try submitting a story to
Now you're just taking things out of context. I said (in the next sentence):
I sincerely doubt Xine supports all of those avalilable.
So, unless you've tested EVERY DLL in there, you're not proving anything.
You've clearly misunderstood. I wasn't saying Xine didn't support those codecs, just providing a list you could use for comparison. I'm not about to spend an hour of research on every idiotic claim someone makes on
Umm, what? If you're trying to say that libavcodec is from the ffmpeg project, I know that quite well. MPlayer and ffmpeg are largely one-in-the-same, sharing servers and developers. In fact devs for either project have commit access to the other, by default, and most use it.
If you're trying so say something else, I completely missed it.
As are you. Perhaps the founding father's minds would be changed about voting independantly of political parties, if they had been born in modern times.
The Milgram experiment was not about social mores, but about the pursuasive effect of authorities, over your own personal objections. Really completely different issues.
Absolutely wrong. You have no idea what you are talking about.
First off, the "essential" codecs xine has you download are only a fraction of the codecs available in the "all" packages (you want both the Linux and Win32 ones), and I sincerely doubt Xine supports all of those avalilable. They tend to focus their efforts on the most popular, and neglect all the less common formats.
In addition, even if it did support all the binary DLLs, those are only a fraction of the codecs MPlayer supports. These include: qtx x264 xvid libavcodec real dshow/dmo win32 faad2 libmpeg2 liba52 mp3lib libtheora tremor libmad gif opendivx libdv amr_wb amr_nb xanim faac musepack libdts speex twolame toolame liblzo. And those are only the offical ones. There are a few patches floating around for other odd codecs as well.
In addition to all of this, it's not just a question of having the codecs working. In order to make any use of them, you have to be able to decode the container to read out the streams. New Quicktime/MOV atoms spring up rather frequently, and it's the MPlayer devs that figure out how to decode them, and presumably with the xine guys checking out the code somewhat later and integrating those new features into their player. I very rarely see the opposite. This usually is the big issue with new formats not working, particularly when they use codecs that are otherwise supported.
Acting like you know what you're talking about is ludicrous!
Xine developers will tell you that Xine is based on a large ammount of MPlayer/ffmpeg code, and that they continue to pull updates and fixes from MPlayer.
Depends on your time-zone. Right now, it's still the 4th around the Pacific.
"It's a trap!"
Agreed. I'd pay extra if there was a menu option that would skip over the Ewoks entirely...
Not to mention the original scrolling text in the theatrical release, and opening scene.
Yes. It makes absolutely no sense at all that MPlayer, which has been heavily optimized with hand-written assembler in speed-critical places (including imported libraries) would be slower than Xine, which has not recieved much performance tuning, and certainly doesn't have the hand-optimized code that MPlayer does.
Extrodinary claims require extrodinary proof. I'll believe it when I see someone provide detailed benchmarks with both, a copy of the sample used, and plenty of system info. It's not hard, but nobody is doing it... Presumably because they can't.
Besides that, I have no reason to trust these posts. Almost NOBODY is even posting as a logged-in user, so this could just as well be one idiot masquerading as several for all I know. None of which are spending a minute to provide real evidence.
Xine-lib is right in the middle. At the low-end is libavcodec, then xine-lib, then at the ultra-easy end is MPlayer in slave-mode, which is also used extensively by many programs.
"High current output" is a COMPLETELY arbitrary designation. It's only meaningful if you provide some numbers, or refering to it in COMPARISON TO SOMETHING ELSE.
The battery in my watch is good at "high current output" too...
The primary reason would be because he didn't bother to read the article at all, where it was clearly addressed.
Also, I happen to be an American, and in California, household hazardous waste disposal is free for individuals, although medium/large businesses are required to pay for proper disposal.
Yes, they've existed in the past, but you really won't find any for about the past decade at least.
That really wasn't the point, anyhow. This thread is about the reasons for using cadmium (hence the portable drill reference), and lead acid batteries certainly don't provide anywhere near the high current output that cadmium does, so it's not even applicable.
Yeah, but at worst they'd dump them in a landfill, and you'd be no worse off.
But really, it's much, much easier to catch companies than individuals. A small company from around here was just recently caught dumping hazardous waste down the sewers...
If he had posted any evidence to back-up his claims, it wouldn't have mattered at all.
However, in the case of bald-faced assertions that go against all logic, with no evidence, the UID and lack of karma bonus will usually tell you whether or not you're just seeing some 13 year old who doesn't know what he's talking about, some troll with a nice new account, etc.
Looking through your comment history, it looks like you might actually hold that distinction.
Maybe because everything I've said is factually correct, and you're just trolling for Xine...
Feel free to try and dispute any of the facts above, rather than just bitching and whining.
And? Doesn't make that one any less ironic.
Yes, I keep hearing about Rodi, and then I go to the website and read that part about requiring Java, "bouncers" being trusted to handle all data, and I run like hell in the other direction...
Although they are part of the kernel, they really aren't loaded, in the Linux sense of the term.
That's one of the main reasons why compiling your own kernel in Linux is a day-to-day thing, while it's almost never done in the BSD world, despite it being quicker, simpler, etc.
No, that's just crap, and you have no idea what you're talking about.
Although you're trying to flame, you're absolutely right. Loadable modules are a massive security hole, as well as being buggy, a huge hassle, etc.
Removable hard drives are wonderful. IDE, Firewire, USB2, etc. I move harddrives around constantly, and having to manually reconfigure everything is a really massive hassle, and seriously buggy with the unstable and bloated Linux tools that try to fake the real PnP support the BSDs have had from the beginning.
But hey, I don't expect you to understand. I know brain-cells don't grow on trees, and some have far more than others...
I don't know where this bullshit comes from. I've got LiIon batteries from nearly A DECADE ago which are still working perfectly.
People are fond of saying that LiIon batteries lose 50% of their capacity each year, ignoring the facts around that statistic, which says that only happens if they are stored at their maximum charge level over that time. If you have a smart charger, which keeps them at around 80%, they should last for many years, with only a slight decrease in capacity over time.
No. Not when it's well known the limited life-span of the batteries, the fact they aren't user replaceable, and yet Apple didn't provide any "downer" info about this fact on the package.
No, actually they DO last nearly as long. The best NiCds were at about a 25% disadvantage to the best NiMH batteries when I last checked, Besides that, NiCds have the advantage of being far lighter than NiMH or Lead Acid, and somewhat lighter than LiION, which can be a real advantage in vehicles.
They've been working very hard to get NiMH to provide high current, but it's still not as powerful. NiCds can deliver their full current in a very short period of time, making them preferred for high-loads.
I believe that's mainly to do with the fact that NiMH don't naturally lose their charge as quickly as NiCd, as well as issues with memory effects.
That's completely wrong. Overcharging lead-acid batteries will seriously damage them.
I generally like lead acid too, but they do have several disadvantages, and it doesn't look like it will take long before something else will surpass lead acid in price, while not having as many disadvantages (tempurature, natural discharge rate, unstable voltage, etc).