Weekly Edition
Return to the Distributions page
| |||||||||||||
|
| |||||||||||||
Pushing ahead (Grand Fallacy)
Paul Frields notes in his
weblog that Fedora 12 will have a shorter schedule. "We had so many features in the Fedora 11 release, some of them particularly extensive and complex, that we drove a slightly longer release cycle. To make up for that longer cycle, the Fedora 12 cycle is somewhat shorter. That truncation returns us to release dates close to the May Day/Halloween calendar we originally set up back around the Fedora 7 time frame."
(Log in to post comments)
Pushing ahead (Grand Fallacy) Posted Jul 7, 2009 19:40 UTC (Tue) by briangmaddox (subscriber, #39279) [Link]
Now if only they'd quit their pattern of taking options away (ie, letting me select my PCM channel for volume control instead of Master since my laptop is a bit odd). It's one thing to simplify, another to have 14 page long threads in a forum basically telling users to get lost :(
Pushing ahead (Grand Fallacy) Posted Jul 7, 2009 19:56 UTC (Tue) by rahulsundaram (subscriber, #21946) [Link]
Oversimplification of what happened but the issue you cite is being fixed in
the Fedora 12
https://fedoraproject.org/wiki/Features/VolumeControlCont...
This isn't a Fedora specific change but one that is part of upstream GNOME
Pushing ahead (Grand Fallacy) Posted Jul 7, 2009 21:09 UTC (Tue) by briangmaddox (subscriber, #39279) [Link]
Actually when I was on Mandriva I didn't have the problem. I could specify the control channel. My concern in moving to Fedora wasn't that it was an upstream change as much as an extreme stubbornness in recognizing that sometimes you can go too far in dumbing things down.
Pushing ahead (Grand Fallacy) Posted Jul 8, 2009 4:58 UTC (Wed) by rahulsundaram (subscriber, #21946) [Link]
Other distributions would get it by their next releases. If you read the original feature page I think it was recognized that it wouldn't cover all the use cases yet. That's why the old gst-mixer was also installed by default and now those issues are being fixed in the subsequent release.
Pushing ahead (Grand Fallacy) Posted Jul 8, 2009 7:36 UTC (Wed) by jengelh (subscriber, #33263) [Link]
Don't worry about Master or PCM. Before long, Pulseaudio will offer you only one fscking control anyway.
Pushing ahead (Grand Fallacy) Posted Jul 8, 2009 18:13 UTC (Wed) by nix (subscriber, #2304) [Link]
Isn't one control *per stream* enough for you?!
Pushing ahead (Grand Fallacy) Posted Jul 8, 2009 19:11 UTC (Wed) by jengelh (subscriber, #33263) [Link]
I was talking about the surprise you get when running alsamixer and only see one control when one expected to the global controls.
One per stream? That's insane. And brings another problem: volume. If you run `mplayer -ao jack`, you cannot use mplayer's volume controls meaningfully because ao_jack already outputs at 100%. This also happened with -ao esd, and affects about all output modules whose mixer does not directly map to the global mixer settings.
Pushing ahead (Grand Fallacy) Posted Jul 8, 2009 22:00 UTC (Wed) by nix (subscriber, #2304) [Link]
Aha. You miss the neat part.
There's one volume per stream *internally*, but externally this is exposed
There are still things to solve (plug in your bluetooth headphones and
Pushing ahead (Grand Fallacy) Posted Jul 8, 2009 22:09 UTC (Wed) by jengelh (subscriber, #33263) [Link]
Well, the departure from the global-only scheme is plain confusing. I can imagine user reports about "I can't hear anything" turning out to be related just because of the per-client volume level. The problem is that when alsamixer is "just another client" when people used it for global volume control forever and it is as I hear in irc "but there's just one control" then that's a halfbaked job.
Pushing ahead (Grand Fallacy) Posted Jul 8, 2009 22:57 UTC (Wed) by nix (subscriber, #2304) [Link]
Well, alsamixer always adjusts the hardware volume, doesn't it? It might
adjust a hardware volume that PA doesn't touch, in which case it will affect all stream volumes, or it might adjust one that PA is touching, in which case it probably won't last long (I'm not sure what PA does if something else fiddles with the hardware volume while it's running: maybe it notices, I'm not sure).
Pushing ahead (Grand Fallacy) Posted Jul 9, 2009 11:33 UTC (Thu) by cladisch (✭ supporter ✭, #50193) [Link]
> Well, alsamixer always adjusts the hardware volume, doesn't it?
Wenn called without options, alsamixer adjusts the controls of
|
|
||||||||||||