P4
P4a Screenshots of organised files and using the equipment:
This image shows me at my computer, the computer was used for the majority of the production and process of Unit 20.
We used it to:
P4c Usable Files
Most of my files were usable such as ZOOM0057 and ZOOM0065 but with editing, as most needed. However files like ZOOM0056, it was unusable, much like most vox pops, which is why I had re-recorded the three. In the end, ZOOM0070, ZOOM0071 and ZOOM0072 were the only vox pops that I was able to use due to bad sound quality in others e.g. this vox pop had lots of background noise which differs from this usable file
Here is the raw footage that contributed to my final podcast
The screenshots above are taken to show my organisation of the media files:
- I created a main file for the subject 'Media diploma 120 Hannah Diver' which will lead to the different unit folders
- The second and only folder afterwards is the Unit 20 file which is for the induction podcast unit, this folder will lead to multiple files that organizes the work even further
- The final folders put the documents, first recordings, second recordings, vox pops, and music taken from Freesound.org, this means everything is organised for myself and others who want to look, there is less confusion.
This screenshot is from the website Blogger, which we use to present our work. This image shows the layout we use to show the different aspects of the unit.
- We started out by making a Hub blog and a Unit 20 blog, which we connected together with links
- we went to layout on the settings of the Unit 20 blog
- Selected the pages setting to add more to the unit blog, organizing the different document we made into P1, P2, P3, P4 and P5
- We then posted certain documents under the different pages, much like the script and others under P1 and the recce reports under P2 also alongside a risk assessment and risk and hazards documents.
- We put the images on the blog by using screen clippings.
- To update the pages we had to make sure to press update each time to make sure we didn't loose anything
This image shows me at my computer, the computer was used for the majority of the production and process of Unit 20.
We used it to:
- Type up documents like the script, production schedule, asset checklist among others, which happened on Microsoft Word
- We transferred files between computers since we also used Macs, by using Google Drive or email.
- To keep everything organised, we created as many files as we could to keep everything separated
- We used the USB slot and a micro USB to transfer the sound files from the mic to the computer, before moving into organised files.
- We used the Adobe Audition programme to edit the podcast together with the vox pops and music
- We could obtain soundbites and music without copyright by using Freesound.org, only accessible on the internet
There are aspects of health and safety whilst using a computer such as:
- Making sure the computer screen is low enough that you don't strain your neck
- Making sure it isn't too close to your eyes as it can harm them if close enough
- Making sure that there are no faulty cables that can harm you e.g. electric shocks
- making sure the chair seat back is forward enough that you aren't leaning forward much or harming your back
- Making sure that the screen isn't too bright that it can also harm your eyes.
P4b Production process:
During the production process for the podcast in Unit 20, I wrote a script, which I tried to stick to as much as possible. I never wrote the answers for the questions I asked the two guests because I wanted to make sure they sounded natural and I wouldn't want to force words into their mouths. Thus allowing them to talk freely would allow more of a flow through out the podcast.
Other than that, I haven't strayed from changing the script.
The major process of recording was carried out with mics that could be connected to the computer with a micro USB cable. They were first turned on by holding down the slider on the right hand side of the mic, the mic is also turned off in the same way. To start recording, press the middle button with a red mark in the centre. to stop recording, simply press the same button. To test the audio, press play on the side (same side as the on/off button) it will play out of the top. To make sure the audio is good quality, hold the mic at a good distance so that the red light isn't flickering, as this means the audio is too loud. Also remember when transferring the audio, to turn off the mic before transporting files.
A muffler can be added to the top of the mic to block some sound too.
We used Blogger to post our work for our teachers to see, it is an easy way to present the work and keep everything organised. we created a main hub blog then created a second for Unit 20. On this blog we created 5 pages for different sections. On P1 we carried out a podcast analysis and took screenshots of our work for presentation. This work would include the treatment presentation, talent release forms, script, asset checklist and production schedule.
We used Adobe Audition for sound editing which allows you to do multi-track, where you can layer tracks easily. On Audition, you can raise or lower the volume, add sound effects and cut sound files together. Effects can also be added, but it can lower the quality of the podcast if they are added badly.
To put sound in the programme, go to the library section and go through files or go to file and import the sound from your files. You can add any of the sound files from your folder. There are multiple lines to layer the sound together. the sound clips can either be cut with the razor tool or by pulling the edges inwards or outwards. To loop clips, such as music then right click and press loop, you are then able to pull out the repeated music to your preference.
One of the first things we did was the production schedule so we could show when and where we would be doing things throughout the unit, we also created location recces for the college grounds and classroom. The recce ensured that we knew the safety of the location we recorded on/in and we can show whether the location was suitable or not to others. Another thing we focused on early on, was the script for the podcast. The script was created to show the areas of speech for each person; host and guests. I could highlight the names to make it clearer to those reading it off, wanting it to be as clear as possible. With the script, I made sure to include the basic structure of an intro and outro with links in-between.
During the production process for the podcast in Unit 20, I wrote a script, which I tried to stick to as much as possible. I never wrote the answers for the questions I asked the two guests because I wanted to make sure they sounded natural and I wouldn't want to force words into their mouths. Thus allowing them to talk freely would allow more of a flow through out the podcast.
Other than that, I haven't strayed from changing the script.
The major process of recording was carried out with mics that could be connected to the computer with a micro USB cable. They were first turned on by holding down the slider on the right hand side of the mic, the mic is also turned off in the same way. To start recording, press the middle button with a red mark in the centre. to stop recording, simply press the same button. To test the audio, press play on the side (same side as the on/off button) it will play out of the top. To make sure the audio is good quality, hold the mic at a good distance so that the red light isn't flickering, as this means the audio is too loud. Also remember when transferring the audio, to turn off the mic before transporting files.
A muffler can be added to the top of the mic to block some sound too.
We used Blogger to post our work for our teachers to see, it is an easy way to present the work and keep everything organised. we created a main hub blog then created a second for Unit 20. On this blog we created 5 pages for different sections. On P1 we carried out a podcast analysis and took screenshots of our work for presentation. This work would include the treatment presentation, talent release forms, script, asset checklist and production schedule.
We used Adobe Audition for sound editing which allows you to do multi-track, where you can layer tracks easily. On Audition, you can raise or lower the volume, add sound effects and cut sound files together. Effects can also be added, but it can lower the quality of the podcast if they are added badly.
To put sound in the programme, go to the library section and go through files or go to file and import the sound from your files. You can add any of the sound files from your folder. There are multiple lines to layer the sound together. the sound clips can either be cut with the razor tool or by pulling the edges inwards or outwards. To loop clips, such as music then right click and press loop, you are then able to pull out the repeated music to your preference.
One of the first things we did was the production schedule so we could show when and where we would be doing things throughout the unit, we also created location recces for the college grounds and classroom. The recce ensured that we knew the safety of the location we recorded on/in and we can show whether the location was suitable or not to others. Another thing we focused on early on, was the script for the podcast. The script was created to show the areas of speech for each person; host and guests. I could highlight the names to make it clearer to those reading it off, wanting it to be as clear as possible. With the script, I made sure to include the basic structure of an intro and outro with links in-between.
P4c Usable Files
Most of my files were usable such as ZOOM0057 and ZOOM0065 but with editing, as most needed. However files like ZOOM0056, it was unusable, much like most vox pops, which is why I had re-recorded the three. In the end, ZOOM0070, ZOOM0071 and ZOOM0072 were the only vox pops that I was able to use due to bad sound quality in others e.g. this vox pop had lots of background noise which differs from this usable file
Here is the raw footage that contributed to my final podcast








Comments
Post a Comment