Comment: Re:That. Stop Doing That. (Score 2) 304
Comment: It appears ... (Score 1) 487
Comment: Re:That is not encouraging (Score 1) 326
I can't think of anyone in the current crop of "stars" who could replace Ford's character.
Perhaps you have forgotton Keanu? Pllenty of experience with horrble & unwanted sequels.
Comment: Re:Well it can't be any worse than "After Earth" (Score 1) 326
Comment: Re: This is horrible (Score 1) 375
right Nyder?
What a great concept, a
Comment: Re:Surprise is that this doesn't happen already (Score 1) 443
Comment: Re:SmartOS! (Score 1) 191
Comment: Re:..but it's the same for everyone (Score 1) 335
Comment: Re:not so simple... Re:I should hope so (Score 1) 279
Comment: Re:It's my party and no one else is invited (Score 1) 212
what would you have the author of the software do?
What any competent maintainer would do. determine the parameter(s) value that induces the fault and code a workaround that wards that function call from those values, throw an assertion to get a better handle on what the root cause is, which would probably help the FFMPEG track down the issue if it is in their code. Its as likely that an unitialized value in the calling code is the culprit as something in FFMPEG internals. Grat rule of thumb, initalice EVERY variable when you declare it, let the compiler optimize it out as needed. turn on the uninitialized variable compiler warning explicitly. Dont rely on the default
Comment: Re:Is Apple being compensated? (Score 1) 239
silicone within the device.
hipster geek paradise, an iDevice with DD boobies.
Comment: Re:i know real reason (Score 1) 347
There is no posh
or Ginger or Sporty. If you meant polish, I think we can safely assume it was exhausted on all the prior turds.
Comment: Re:WAKE ME WHEN IT IS 8.0 !! (Score 4, Funny) 112
What about Bob?
Im SAILING!!!!!