Try Shotwell, it's still yound, but seems to have entered a development spurt and is adding (useful!) features rapidly. If you don't shoot raw 0.5 should do just about anything f-spot did, with the addition of auto generated events.
Re:The features I'm still waiting for...
on
Gnome 2.30 Released
·
· Score: 1
F-Spot is slow...
Worse, if let it, it eats metadata at night; I'm referring to the madness they do with time zone conversion. Even if you convince it to leave your pictures alone it will still fuck with how time is displayed...
There is nothing wrong with a config database, it's just that the Windows Registry isn't one. It's a catch all, store anything under the sun database.
Re:The Benefits of Moving Backward
on
Gnome 2.30 Released
·
· Score: 3, Interesting
I strongly preferred the spatial back in the day, because the browser mode was next to useless. The breadcrumbs convinced me to switch back, but it took a while for browser mode to actually become better, instead of just being familiar to Windows Explorer users.
Fundamentally you don't have the right to demand somebody else work for you for free.
Demanding work for free would be slavery. A copy of the end result of some work is not the work itself, but please go on ignoring this "purely semantic" difference...
Bullying and police involvement have basically nothing in common. I mean who would call the police because I got blackboard erase cloths thrown at me on a regular basis?
I hit it while trying to prevent users from deleting a specific file without breaking everyones links.
An edge case is when Excel drops some rows from a drop down filter in a huge file or writes two megabytes of junk in the middle of a table and the computer grinds to a halt while scrolling over that place (never found a solution for the first one, second one required resaving with Openoffice...) This one, on the other hand, is hit by enough people for Microsoft to have a support article and a suggested workaround.
In the end, edge case or not, Microsoft controls the whole stack, but the only solution they have after several years is to add yet another Microsoft product into the stack.
He claims that Theora is more comparable to MJPEG, then H.264. I ask for a comparison demonstrating this, as in, the fact that Theora and MJPEG are comparable. You link to a H.264 vs Theora comparison and act all smug that H.264 came ahead, even if I never disputed it would. What?
With that out of the way, why should a take a comparison that encodes from a H.264 source and gives different frames for comparison without explaining why? And, heck, at least use x264, no need to handicap H.264.
You might have missed that whole embedded device playback debate, so if you want to impress me with H.264 results (I'm quite familiar with them however, it's good), link to something that uses baseline profile as that's what people will have to use in HTML5 for it to play on the iPhones of this world.
Baseline H.264 is much simpler than Theora. Comparing baseline H.264 to full-fledged Theora is utterly unfair.
Not according to the x.264 guys, they say Baseline trounces Theora and Xiph says Theora is less computationally intense then Baseline. If you are going to argue with them then a simple statement is not enough.
Incidentally it is also the only fair comparison in context of HTML5, because H.264 is always praised for it's embedded support. Guess what, most of the embedded H.264 decoders are Baseline only. If we are to compare Theora to anything, but baseline, then people should shut up about embedded penetration being the holy grail.
Since when is an order of magnitude difference required?
Every time someone brings phrases like "horrid" and "light-years behind" into the discussion.
2X - 4X is realistic, and means a huge difference in file sizes, and required bandwidth.
2x - 4x hasn't been demonstrated for generally used bitrates, to the best of my knowledge. Feel free to link me up.
For high quality, it's MORE THAN AN ORDER OF MAGNITUDE difference. Theora can't do high quality at ANY bitrate, so the bitrate difference is actually INFINITE.
That's a bold claim, let's start simple. Define "high quality" in quantifiable terms, then we'll see if you can present proof.
The fact that you're calling me a "fanboy" for telling the truth, based on my years of codec development, just demonstrates that YOU are the one who has a problem with the truth.
Years of codec development or not, keep your statements this side of the stratosphere. "Light years" might be appropriate between MJPEG and a modern codec, not between a modern codec and a state of the art codec.
Because there clearly aren't any things that sit between "less then 30 minutes" and writing. Would you like some sauce with the huge middle you ate?
This is generally true, but much less so in Europe then America. ISPs just might be forced to provide what they advertise over there.
You are completely right, we all should have just given up on PNG and switched to JPEG 2000.
I don't believe that justification and explanation have become synonyms quite yet.
Just don't expect any of that to run on your iPad after modification...
Try Shotwell, it's still yound, but seems to have entered a development spurt and is adding (useful!) features rapidly. If you don't shoot raw 0.5 should do just about anything f-spot did, with the addition of auto generated events.
Worse, if let it, it eats metadata at night; I'm referring to the madness they do with time zone conversion. Even if you convince it to leave your pictures alone it will still fuck with how time is displayed...
Thankfully not only is it not part of Gnome, but a good alternative seems to finally be getting of the ground.
In the keyboard shortcuts, bound to ctrl+alt+tab by default. Now let me get out of the way of your rant.
There is nothing wrong with a config database, it's just that the Windows Registry isn't one. It's a catch all, store anything under the sun database.
I strongly preferred the spatial back in the day, because the browser mode was next to useless. The breadcrumbs convinced me to switch back, but it took a while for browser mode to actually become better, instead of just being familiar to Windows Explorer users.
Are you the economy?
Just to clarify. You don't think that irrational market behavior and asymmetric information are serious problems for a market?
So why don't you complain at Ramze, that his criticism of the USSR lays with the corrupt, authoritarian government?
Demanding work for free would be slavery. A copy of the end result of some work is not the work itself, but please go on ignoring this "purely semantic" difference...
It's perfectly possible to both think that copyright, as it stands, is out of whack and not pirate...
How about you put in a pla^HFaraday cage in your house instead?
Because the only thing that a fight settles is who can win that fight.
Bullying and police involvement have basically nothing in common. I mean who would call the police because I got blackboard erase cloths thrown at me on a regular basis?
Almost certainly because you weren't involved in it and turned a blind eye.
Yes, the culture is even better at ignoring the problem.
You're assuming an empty can...
I hit it while trying to prevent users from deleting a specific file without breaking everyones links.
An edge case is when Excel drops some rows from a drop down filter in a huge file or writes two megabytes of junk in the middle of a table and the computer grinds to a halt while scrolling over that place (never found a solution for the first one, second one required resaving with Openoffice...) This one, on the other hand, is hit by enough people for Microsoft to have a support article and a suggested workaround.
In the end, edge case or not, Microsoft controls the whole stack, but the only solution they have after several years is to add yet another Microsoft product into the stack.
He claims that Theora is more comparable to MJPEG, then H.264. I ask for a comparison demonstrating this, as in, the fact that Theora and MJPEG are comparable. You link to a H.264 vs Theora comparison and act all smug that H.264 came ahead, even if I never disputed it would. What?
With that out of the way, why should a take a comparison that encodes from a H.264 source and gives different frames for comparison without explaining why? And, heck, at least use x264, no need to handicap H.264.
You might have missed that whole embedded device playback debate, so if you want to impress me with H.264 results (I'm quite familiar with them however, it's good), link to something that uses baseline profile as that's what people will have to use in HTML5 for it to play on the iPhones of this world.
Facts are not things you state, it's things you show. Show us how Theora stacks up to MJPEG instead of implying that they are basically the same.
Not according to the x.264 guys, they say Baseline trounces Theora and Xiph says Theora is less computationally intense then Baseline. If you are going to argue with them then a simple statement is not enough.
Incidentally it is also the only fair comparison in context of HTML5, because H.264 is always praised for it's embedded support. Guess what, most of the embedded H.264 decoders are Baseline only. If we are to compare Theora to anything, but baseline, then people should shut up about embedded penetration being the holy grail.
Every time someone brings phrases like "horrid" and "light-years behind" into the discussion.
2x - 4x hasn't been demonstrated for generally used bitrates, to the best of my knowledge. Feel free to link me up. For high quality, it's MORE THAN AN ORDER OF MAGNITUDE difference. Theora can't do high quality at ANY bitrate, so the bitrate difference is actually INFINITE.
That's a bold claim, let's start simple. Define "high quality" in quantifiable terms, then we'll see if you can present proof.
Years of codec development or not, keep your statements this side of the stratosphere. "Light years" might be appropriate between MJPEG and a modern codec, not between a modern codec and a state of the art codec.
Can you back that up with some numbers (that aren't made up on the spot)?