Site Map - skip to main content - dyslexic font - mobile - text - print

Hacker Public Radio

Your ideas, projects, opinions - podcasted.

New episodes Monday through Friday.


Our hosting is kindly provided by Josh from AnHonestHost.com. We would appreciate it if you could donate to help reduce his costs in funding the hosting.
He is also accepting bitcoins to 1KsxJr9HtsdaUeU7yaV9bk9bQi21UPBtUq

hpr1133 :: How I got in to Linux

Another contributor describes their Linux journey

<< First, < Previous, Latest >>

Hosted by Dick Thomas on 2012-12-05 is flagged as Explicit and is released under a CC-BY-SA license.
Listen in ogg, spx, or mp3 format. | Comments (3)

Part of the series: How I Found Linux

Started by monsterb, this series invites people to share with us how they found Linux. It has become traditional for first time hosts to share with us their journey to Linux. Indeed it has morphed to be way to share your journey in tech right up to your first contribution to HPR.

Dick Thomas (xpd259)

How I got in to Linux

Dear listeners, Today I will be briefly explaining my adventure in to tech and Linux, Starting with getting my first computer a ZX Spectrum to the current day behemoth and Debian obsession and making youtube videos for fun and to spead word of FOSS and all things Linux/BSD

Links and other things mentioned in this podcast


Comments

Subscribe to the comments RSS feed.

Comment #1 posted on 2012-12-06T16:49:12Z by pokey

Good idea

I loved the tea break with the HPR promo in the middle. It was a great idea. It reminds me of one of Klaatu's coffee breaks on Gnu World Order. I'm really sorry that it didn't execute as well as it was planned.

I'm guessing that you did that in audacity, and I'd bet that either one of two things happened. Just guesses, but:

1.) you didn't unlink the tracks before pasting it in, or

2.) you used "truncate silence" before "mix and render"

The first thing would be pretty obvious, so it probably wasn't that. The second would have removed the silence somewhere off screen if you had been zoomed in enough. If it was neither of those two things, I'd be really interested to find out what you think caused it.

For anyone using audacity, one suggestion is to use the high speed playback and listen to the whole track before your final save and export. If it's a track that you edited, then listening to it at 2X is fairly easy to do, even if you aren't used to listening to audio at that speed, because you're used to listening to that track.

Comment #2 posted on 2012-12-08T17:55:20Z by Dick Thomas

ooops

yeah, used truncate silence. tbh it was my 1st ever time installing and using audactiy so I was stumbling around lot but I will try harder next time

Comment #3 posted on 2012-12-14T12:56:01Z by pokey

Yup. Truncate silence is good, but if you're doing multi-track, then you want to truncate the silence in your source tracks before they are combined into the same project, or as the very last thing that you do before exporting, but certainly after "mix and render."

It was a good episode regardless. I'm looking forward to the next one.

Leave Comment

Note to Verbose Commenters
If you can't fit everything you want to say in the comment below then you really should record a response show instead.

Note to Spammers
All comments are moderated. All links are checked by humans. We strip out all html. Feel free to
record a show about yourself, or your industry, or any other topic we may find interesting. We also check shows for spam :).

Provide feedback
Your Name/Handle:
Title:
Comment:
Anti Spam Question: What does the P in HPR stand for ?
Are you a spammer →
Who hosted this show →
What does HPR mean to you ?