What makes MP3s any less lossless than CDA. Its another format and thats it. As a musician (and more to the point, an engineer and tech for real musicians), I don't think I've recorded anything in the last 2 years where the master wasn't at 24bit 96Khz...that means any CD ya listen to is VERY lossy.
Yes, CDs are lossy. However, MP3's are much more so. CDs use 16bit/44.1KHz audio, but so do MP3's (I'm aware it's possible to use other datarates, but it's very rare). When the MP3 is made from the (already lossy) CD, it discards 9/10 of the data. That's what makes MP3's lossier (is that a word?) than CDs.
I want lossless formats for my music not for quality purposes (I can't distinguish between CD, 192kbps MP3, and 128kpbs AAC/Vorbis), but for freedom purposes. If you recieve music as a WMA (DRM'd or not), and you want to put in on an iPod, you have to transcode it to MP3. That's quality loss. If you burn it to an audio CD and then later rerip and reencode that CD (say you lost the original file), then that reencoding is a quality loss. The losses from reencoding/transcoding can be quite noticable, especially with more than one generation. A lossless original gives you the freedom to do what you want with the music you bought.
Correct tagging does not seem to be a common practice on file sharing networks
It can be, if you know how to find it. Most higher-class sharing systems (suprnova/bittorrent, directconnect, soulseek, etc.) have files that are almost exclusively well-tagged. Even with lower-class systems like KaZaA, you just have to search for the album you want in the "album" field, and the only results that will show are the well-tagged ones (or so I've heard).
Why do you insist on trolling every single KDE topic with this complaint though?
He wasn't trolling, he was asking a simple question. I wondered the same thing, and I'm sure many others did too. No one has implied here that the QT licensing scheme is in any way bad. Stop overreacting.
I believe it means that a Shoutcast client can access an Icecast server as if it were a Shoutcast server. Icecast has potentially lower bandwidth usage, since it supports Vorbis. Otherwise, I've never noticed much of a difference (I've never used either of them for anything serious).
While I agree that TI calculators are ridiculously overpriced (although that's because that's what the market will bear), the TI-83+SE actually has 1.5MB of ROM, much more than the TI-83+'s 160KB. Of course, short of ebooks (which are only really usable on the 89 and 92), there's no real use for all that space.
Megahertz-wise, yes. Mathematically, the 86 can solve polynomials and systems of linear equations, convert between units, and a few other nice things, as well as having a much nicer screen.
there were a few people who made the point that this is yet another reinvention of a wheel that's been invented correctly multiple times, except Gnome is about 5 years behind the curve... and ya know what? They're right. It is.
This problem has not been "solved". There is no one solution. There are many different ways to do it, and it's not always clear which is the best. If you read the article, there are a few innovative ideas coming out of this. Solutions are available for most GUI problems, but that doesn't mean they've been "solved".
Ok, so the point of this exercise is the "new API". Outstanding. How long will this one last? I'll wager between 3-6 months before the almighty API designers get bored with their "new API" and decide to reinvent it again. I doubt it took that long to abandon the one this API is replacing.
The current API has been in place for more than 5 years. It was a little cumbersome, but it worked and the dialog itself was extremely usable when you learned about its tab completion (it wasn't very intuitive, however).
us people who use gtk+ apps sans gnome will be screwed.
Even if GTK did switch to gconf, it wouldn't matter that much. GConf is tiny, and many GTK apps require it anyway. That said, GTK currently uses flat text files for all configuration, and I don't think that'll change just because of this fileselector.
Get in trouble. Long, laborious litigation. What was solved? Nothing. Consumers don't have more rights. It's still a pain in the ass to decode DVDs, and now he's on a bunch of corporate sharks' bad sides.
It was impossible before to play DVDs on Linux, or to rip them and make backups for your own purposes. Now, it's possible (although dubiously legal in the US). That's what was solved.
Slashdot Mirror
Because it's a better player, and there's no reason I shouldn't be able to use the music that I bought with it.
Yes, CDs are lossy. However, MP3's are much more so. CDs use 16bit/44.1KHz audio, but so do MP3's (I'm aware it's possible to use other datarates, but it's very rare). When the MP3 is made from the (already lossy) CD, it discards 9/10 of the data. That's what makes MP3's lossier (is that a word?) than CDs.
I want lossless formats for my music not for quality purposes (I can't distinguish between CD, 192kbps MP3, and 128kpbs AAC/Vorbis), but for freedom purposes. If you recieve music as a WMA (DRM'd or not), and you want to put in on an iPod, you have to transcode it to MP3. That's quality loss. If you burn it to an audio CD and then later rerip and reencode that CD (say you lost the original file), then that reencoding is a quality loss. The losses from reencoding/transcoding can be quite noticable, especially with more than one generation. A lossless original gives you the freedom to do what you want with the music you bought.
It can be, if you know how to find it. Most higher-class sharing systems (suprnova/bittorrent, directconnect, soulseek, etc.) have files that are almost exclusively well-tagged. Even with lower-class systems like KaZaA, you just have to search for the album you want in the "album" field, and the only results that will show are the well-tagged ones (or so I've heard).
You could give your money to a local provider.
This is a different question than the standard "can I use Qt in my closed-source app?", so it's not redundant.
The same OO.o integration work has been done with GTK+.
Epiphany, the official GNOME browser, also supports session management and has a very well-done bookmark system.
He wasn't trolling, he was asking a simple question. I wondered the same thing, and I'm sure many others did too. No one has implied here that the QT licensing scheme is in any way bad. Stop overreacting.
That's not xmms in the screenshot, it's beep, an XMMS fork ported to GTK2 and Pango/Freetype font rendering.
I believe it means that a Shoutcast client can access an Icecast server as if it were a Shoutcast server. Icecast has potentially lower bandwidth usage, since it supports Vorbis. Otherwise, I've never noticed much of a difference (I've never used either of them for anything serious).
Knock yourself out.
Grand Theft Auto: Sin City. Where's the redundancy in that name? It's not like it'd be "Vice City: Sin City" or something stupid like that.
So it blocks Pink Floyd's "Money", not once, but twice? I wonder how that's managed...
While I agree that TI calculators are ridiculously overpriced (although that's because that's what the market will bear), the TI-83+SE actually has 1.5MB of ROM, much more than the TI-83+'s 160KB. Of course, short of ebooks (which are only really usable on the 89 and 92), there's no real use for all that space.
Megahertz-wise, yes. Mathematically, the 86 can solve polynomials and systems of linear equations, convert between units, and a few other nice things, as well as having a much nicer screen.
For most people, anything added since 1.2 is a new thing.
Dude, chill. It's just a mockup.
Have you tried GIMP 1.3/2.0? The UI is much more flexible and usable - you can dock windows to each other and do all sorts or cool stuff.
I take it you're a big assembler fan?
I would, but it's already been done.
Windows fileselectors are resizable, at least under 2000 and XP.
This problem has not been "solved". There is no one solution. There are many different ways to do it, and it's not always clear which is the best. If you read the article, there are a few innovative ideas coming out of this. Solutions are available for most GUI problems, but that doesn't mean they've been "solved".
Ok, so the point of this exercise is the "new API". Outstanding. How long will this one last? I'll wager between 3-6 months before the almighty API designers get bored with their "new API" and decide to reinvent it again. I doubt it took that long to abandon the one this API is replacing.
The current API has been in place for more than 5 years. It was a little cumbersome, but it worked and the dialog itself was extremely usable when you learned about its tab completion (it wasn't very intuitive, however).
Even if GTK did switch to gconf, it wouldn't matter that much. GConf is tiny, and many GTK apps require it anyway. That said, GTK currently uses flat text files for all configuration, and I don't think that'll change just because of this fileselector.
It was impossible before to play DVDs on Linux, or to rip them and make backups for your own purposes. Now, it's possible (although dubiously legal in the US). That's what was solved.
No. At least, not as yet.