Friday, 31 August 2012

Troubles in Getting My Voice Heard by My MacBook

Reported Incident Severity Level: MINOR

I am using an early version of Intel-based MacBook. It has a built-in microphone and a webcam suitable for video chat. It also has a headphone jack and an audio input port.

At the online course of the university I took last year required a Skype interview as part of its end of the course test. The lecturer recommended to use a headset instead of the built-in mic and speaker while communication over Skype and I purchased one. During the interview, the lecturer told me that the mic of headset didn't seem working so well but we managed to complete it. I have not been used the headset since then. So I forgot about it.

Recently, I found something was wrong when I tried to record my song in DTM software using the mic of the headset. When I looked into the screen the sound level bar responded but once I sit back in the chair and started singing the bar didn't pick up any signal.

I believed the mic input should be switched from built-in one to headset one, but it was not true. After searched around over the net, I learned that my MacBook's audio input port can't supply power to the headset mic. It is a plain line-in audio port. What I had been thinking as the voice through the headset mic was actually the sound picked by the built-in mic.

I have an old small battery powered mixer which has a plug-in power mic port. So I connected it between the mic jack of the headset and the Mac's line-in port. Then I tested. Still the headset mic didn't work. I thought the mixer was broken and purchased a tiny USB headset adaptor.

It was after I connected the headset to the adopter, I noticed the mic switch of the headset had not turned on. I still need the mixer anyway as MacBook doesn't have a plug-in power mic port but I didn't have to buy the USB headset adaptor.

Actual Incident Severity Level: MODERATE
Root Cause: lack of knowledge/insufficient prior check

Wednesday, 29 August 2012

The First Fire Drill in the New Office Location

Reported Incident Severity Level: MINOR

Yesterday, we had the first fire drill since our department was moved into the current building. I have been the unit fire warden for the department for years. So I had been familiar with the procedures of fire evacuation processes.

But, as it turned out, it was with the previous building, but not with the current one.

Of course, I went though the emergency information kit on the day we moved. However, the familiarity with the same procedures in old situations somehow prevented me from fully understanding those in the new circumstances.

Fortunately, I could pick up what I had missed out through physically moving about and identifying every bits and pieces of the procedures in the first drill. We are now better prepared, I hope. I thought such an on-site practice is vital to shake off the false assumption that everything would be the same as the situations we had been accustomed to but actually already changed in some ways.

Actual Incident Severity Level: SERIOUS
Root Cause: inappropriate application of old experience to new circumstances

Tuesday, 28 August 2012

Blog Title Changed

Reported Incident Severity Level: SERIOUS

As a job, I am dealing with medical errors by maintaining records of them and reporting to the people concerned. My own personality is quite fit for this job, not because I am a perfect person without errors, but because I have learned in a very hard way that human errors are inevitable - including mine.

After some inactive blogging months, it came to my mind that it would be useful for me, and maybe for some of the people out there, if I record my funny mistakes in the daily life and the lessons learned from them.

That is why now this blog has the new title, description and address with a new format.

Actual Incident Severity Level: MINOR
Root Cause: a change of minds