Here is the link that was inadvertently deactivated from my Reply identified above as Reply #69.
The original upload of this video occurred on November 29, 2013, as required by the CFSAC's requirement for receipt of pre-recorded video submissions for their December 10 - 11, 2013. This was my first attempt at pre-recording any video and then uploading it to a YouTube Channel. I followed the directions that the CFSAC published for pre-recorded testimony. On the Monday following the Nov. 29th deadline for submitting pre-recorded testimony, I contacted the CFSAC's third party contractor to confirm that my pre-recorded video testimony had been received and it met the requirements for use at the CFSAC meeting. I was told that the recording was acceptable and it would be presented at the meeting.
On Friday of that week (Dec. 6th), I was contacted in the afternoon by the CFSAC's third party contractor informing me that they were having a problem with the audio recording on my video. They were unable to determine why it was now not working properly, but they wanted me to know that they would still play the video at the meeting, but there would be no sound.
Yes, you heard that correctly they would play the video with my lips moving, but there would be no sound. I will let you imagine how I might have responded to this information.
Anyhow, after some arm twisting, arrangements were made to allow me to phone in my testimony in place of playing my pre-recorded testimony without sound. The compromise I reached with the CFSAC representative was that I would be called at a specific time on Thursday, December 11th, prior to when I would be leaving Washington D.C. to fly home. As seemed to be the theme of my trip to Washington, apparently events at the CFSAC meeting delayed my phone testimony from happening at the time I had been slotted to testify. Approximately two hours after the agreed upon time that I would phone in my testimony, I received a call from the CFSAC committee while riding in the back seat of a taxi on the way to the airport. All I heard when I picked up my phone was that the CFSAC committee was calling and they were ready for me to provide my testimony. Talk about being caught off guard, I had no notes to read from and the only thing on my mind was how I was going to get all the luggage I brought with me from the taxi to the terminal without any curbside assistance available due to construction going on in the area. What happened after that is somewhat of a blur.
It is my understanding that I did present some type of testimony via the phone on December 11, 2013, but I really don't know what I said or if it made any sense to anyone listening in to the meeting. I am still awaiting the HHS to publish the recording from this meeting, which I assume will include my phone in testimony. Part of me is a bit fearful to hear what I said from the backseat of a cab, but the other half of me thinks this could be quite entertaining when put in context of the situation I was dealing with. So for now I will just re-post my pre-recorded testimony submitted, but not played at the Dec. 10 - 11, 2013 CFSAC meeting. If this recording is played on a device other than an Apple product (desktop computer, laptop, iPad or iPhone) there appears to be an issue with the audio volume. To date the HHS has not been able to figure out how their instructions to upload pre-recorded testimony via YouTube can be tweaked so that different types of recording devices uploaded to Youtube will play without audio issues. Perhaps this was just an issue that resulted because of the recording equipment I was using (iPhone), but I have put in writing to the HHS that I hope they will solve this problem for future CFSAC meetings. I would hate to see the pre-recorded testimony option go away just because there is a tech issue that has not yet been addressed.
To those who have made comments on my YouTube channel that the date shown that my video testimony was uploaded somehow shows that this testimony was not timely submitted to the CFSAC committee, your assumption would be incorrect. Please understand that this video has been taken down and uploaded multiple times since December while people with much more tech knowledge than me, try to figure out if I can fix the audio problem on my end or it needs a fix by some other tech wizard. So far, we have not had any success in figuring out how to solve this problem.
Wally