I apologise for the show arriving so late, Britain decided to come back from holiday and break their computers so I was busy all week. Said holiday period also meant that news was thin so Me, Thom, Tess and David discuss Snow Leopard, the EULA issue and then proceed to the issue of cloud computing, what constitutes ‘user-friendly’ and whether Linux really is easier or more difficult to use than Windows or Mac. Due to some recording issues, sound levels are not perfect and I hope to resolve that next week.
Download .mp3 |
Subscribe in iTunes |
Subscribe RSS
This was the first OSNews podcast I listened.
It was okay.
I listened to most of them and this one was really great.
A lot of real wisdom ( only because I agree with nearly everything that was said .. about EULAs, copyright, defaults, desktops, clouds and appliances etc)
I especially liked Krocs comments about IEs wizard and PCs being protoboards.
Keep up the good work.
PS. David was muted for a minute .. did he put the micro where light is a scarce resource? People on the internet are into some kinky shit ..
Unfortunately two conversations in the show were lost due to some recording issues and I had to cut-and-shut the audio. The quiet sections for David are where some of that happened.
As for a good kde distro kroc i would recommend you try mandriva 2010 beta 1. It is really nice.
Or Pardus, even if the repos are quite bare.
when you came to the conclusion that all OSs are complicatet you missed a chance to praise beos
..how many people will listen to this podcast on a device that will have to be rewinded to skip to an earlier time on the podcast..
i am asking because the lady kept saying “rewind the podcast” and i keep seeing a person listening to this podcast with a walkman or on one of those old redios that uses a cassette tape
This is the first OSNews podcast I’m listening to and I have a request – please normalize the volume of panelists, otherwise it’s very uncomfortable to having to adjust volume depending on who currently speaks.
Listen to e.g. Stack Overflow podcast to see/hear how it should be done properly.
Seconded. Do real levelling. It’s really annoying if you’re listeing to it with headphones.
And while you’re at it get a Deesser to get rid of the sharp s-sounds. http://en.wikipedia.org/wiki/De-essing
We’re doing this on the cheap, and it’s not that I can’t spend money on the solution (better Mic &c.), it‘s just that I don’t know how. Next week I’m going to attempt changing recording method which may provide better levelling (and less crashes). In GarageBand I adjust the separate stream’s volume but it still varies greatly along the length of the podcast.
My time is becoming more limited to spend on the edit so I’m looking for solutions that drastically reduce the time it takes to produce a podcast and keeps the quality to an acceptable level but I admit that I know *nothing* about proper audio recording and equipment.
You can vary the volume of the stream as the podcast goes on in garageband. Click on the downward arrow underneath the track’s name and you’ll see a little flat graph representing volume underneath the track. You can click and create different volume levels at different points on the track to fix the varying levels on each track.
I’m aware of that and do use it where possible, but it is far too time consuming. I can’t spend four hours or more doing an edit having to monitor and modify the sound levels over an hour or two show. The more adjustments I have to make, the less regular the show will be. I need to be able to have the show edited and published in under two hours.
i don’t know if i miss something but what happen with the embed player in the web ?
Since there was no clear divide of topics and I was late with the show already, I couldn’t provide a time-index. This meant there wasn’t anything to note in the body of the article and so I crammed everything into the teaser; the teaser section doesn’t support the embedded player shortcode, and I felt that people could easily play the MP3 in the background anyhow by opening the MP3 link in a new tab, that way if you clicked to comment on the article, it wouldn’t stop the audio.
Not only KDE does this, Mozilla does this too, just have a look at their design contents, Mozilla labs, etc.
They always mention wonderful screenshots of KDE desktops on Planet KDE, then when I go there the only screenshots I see are rather plain ones with maybe just a launched added.