MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information.

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Reggae:_MorphOS_multimedia_framework",
        "continue": "gapcontinue||"
    },
    "query": {
        "pages": {
            "23": {
                "pageid": 23,
                "ns": 0,
                "title": "ReTooled",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "===Warning===\nThis page is a \"works in progress\" page.  It is used to write, edit, erase, and start over in a sandbox style to develop other pages that site administrators do not want to go missing during a major edit.  If you find yourself on this page, and are not part of a major editing process, you might consider hitting the '''back''' button on your browser.\n----\n\n===Fonts and Browsers===\nby DoctorMorbiusFP\n\n== Birth Of A Tutorial ==\nThe early ideas concerning this article arose when I decided to replicate on Amiga browsers an useful feature of Firefox. Assume that, surfing the web, you reach a page where current fonts are so small or so big that you cannot read the HTML page in a convenient way. With Firefox you can press and hold the <CTRL> key and turn the mousewheel (or press a number of times the <+> or <-> keys): these actions enlarge/decrease all the fonts in a proportional way, until font sizes are optimized for your sight (<CTRL><0> resets the default sizes). The concept behind this feature requires that three conditions are satisfied: \n\n# The browser should be properly configured for using efficiently all the available fonts. \n# The OS should be able to support vector fonts at their full potential. \n# Suitable vector fonts (TrueType fonts) should be available and installed. \nThese conditions usually are not completely satisfied in Amiga-like environments: \n\n# Amiga browsers are not up-to-date and are provided with very poor font configurations. These browsers should be properly configured by the user, otherwise they are not able to use fonts at their best. Unfortunately, most people does not know the procedure for setting font management of their browsers in the correct way. \n# AmigaOS 3.x never supported natively TrueType fonts. MorphOS has such a support, but new TrueType fonts become usable only after their installation, and most people does not know in which way this may be done on their Pegasos. \n# MorphOS provides some preinstalled TrueType fonts, and these could also be suitable for a browser. However, an optimal display of web pages requires the so-called webfonts, but most people either ignore their existence or does not know where they can be obtained legally and for free. \n\nIn this article I will try to address all these issues. \n\nThe above-mentioned hotkey feature of Firefox is now available for AWeb by inserting an ARexx program in the Plugins directory and creating new buttons in the GUI. The pictures reported below in the [[#Examples|Examples]] subsection will show you explicitly what is possible to do with this plugin. Actually you gain much more than what is shown, because all the special settings available in the font preference window of Firefox are cloned within the plugin and become usable in AWeb. Complete details are available in the section [http://www.morphzone.org/extra/FontAndBrowsers/06_AWebEnhancement.html AWeb Enhancement]. \n\nI also provide a solution for the browser problem mentioned in the previous item '''1'''. The [http://www.morphzone.org/extra/FontAndBrowsers/03_AmigaBrowsers.html Amiga Browsers] section of this article explains a few basic properties of HTML font management and the minimal approach required for optimising the behaviour of any Amiga browser. Furthermore, the [http://www.morphzone.org/extra/FontAndBrowsers/05_CloningFirefoxWebfonts.html Cloning Firefox Webfonts] section describes extensively more advanced ways for optimisation, based on manual insertion of webfonts in the settings of any Amiga browser. Again, AWeb users are privileged because all these optimisations and settings are automatically made by a suitable ARexx configuration program. \n\nWell, I created my ARexx programs first for AWeb because it is my preferred browser: I was lucky and had success. Unfortunately I cannot provide similar programs for IBrowse or Voyager, because I had technical problems with these programs (complete details on this failure are given in the last paragraph of this [http://www.morphzone.org/extra/FontAndBrowsers/05_CloningFirefoxWebfonts.html#Firefox subsection]). \n\nYou can set the webfonts in your browser, but of course they will be used only if the relevant TrueType fonts are installed in your system. The installation of TrueType fonts was originally described in an article available for classic Amigas and ttf.library. Since no similar tutorials existed for MorphOS and its freetype.library and ft2.library, I decided that another section of this article should be dedicated to this subject: [http://www.morphzone.org/extra/FontAndBrowsers/04_InstallationOfTrueTypeFonts.html Installation Of TrueType Fonts]. There, I explain the basic installation procedure of these fonts on Pegasos/MorphOS for pedestrians. So even the previous item '''2''' is solved. \n\nAfter I wrote this section, I thought that unskilled people maybe want to understand what features are relevant for optimal use of generic fonts (possibly even in wordprocessors and DTP programs). This requires the knowledge of a few basic typographical properties of bitmap fonts and vector fonts. So I feel forced to write another section on this subject, [http://www.morphzone.org/extra/FontAndBrowsers/02_TheNatureOfFonts.html The Nature Of Fonts], where also the history of webfonts is described, as well as the place where webfonts are still freely available in a perfectly legal way. This provides a solution for the problem mentioned in the previous item '''3'''. \n\nIn conclusion, if you look at the contents displayed on the left side of this web page, you will see that this tutorial was written from the end to the beginning. I hope that, reading it in the forward direction, you will find it at least as useful as it seemed to my backward-oriented mind... \n\n\n== Examples ==\nMaybe a few example pictures will be more claryfying than all the words above. \n\n{|\n\n  \n|This is a Firefox window grabbed on a PC.  \n|-\n\n  \n|This is a window of AWeb running out of the box (just after extraction from an old MAX distribution archive) with its default fonts. The HTML source is the same as above!  \n|-\n\n  \n|And this is a window of AWeb after Dr. Morbius' cure described in this article. Please compare with the previous Firefox window...  \n|-\n|Of course, the same cure also works with IBrowse...  \n\n  \n|-\n|...and Voyager.  \n\n  \n|}Below you can see AWeb and its new exclusive dynamic management of font sizes. \n\n{|\n\n\n|These fonts can be obtained by those of the former AWeb picture, on the fly, if the user clicks one time on the '''Enlarge''' button visible in the AWeb GUI. Further clicks give further size increases.  \n|-\n\n  \n|These fonts can be obtained by clicking on the '''HugeFonts''' button visible in the AWeb GUI. This set of maximal sizes may also be reached by clicking enough times on the '''Enlarge''' button described above.  \n|-\n\n  \n|Smaller fonts can be obtained, on the fly, if the user clicks one time on the '''Reduce''' button visible in the AWeb GUI. Further clicks give further size decreases, until the minimal set of sizes is reached. This set of minimal sizes, shown in the figure, can be reached directly by clicking on the '''TinyFonts''' button. \n|}"
                    }
                ]
            },
            "268": {
                "pageid": 268,
                "ns": 0,
                "title": "Recording an LP with Audio Evolution 4",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "''Author: Kelly Samel (realstar@shaw.ca)''\n\n== Tutorial for Audio Evolution 4 - Recording a vinyl LP into your computer ==\n\n\nIf your like me you have a nice collection of vinyl LPs that you like to listen to but sometimes the portability of having mp3 files is also a\ngood thing. The answer is to digitize your vinyl collection and put the songs on your computer. So here is an explanation of my method for\ndoing so using Audio Evolution 4.0.23.\n\n== Things You Will Need ==\n\n\n# A turntable<br />\n# A stand alone phono preamp or amplifier/receiver with phono inputs<br />\n# A stereo RCA to 3.5mm mini jack adaptor<br />\n# An RCA extension audio cable long enough to reach your computer<br />\n# A copy of AudioEvolution 4 software for MorphOS, Amiga OS 4 or AROS<br />\n\n\n\n[[File:ae4_turntable.png|alt=Turntable]]\n[[File:ae4_phonostage.png|alt=Phono stage]]\n[[File:ae4_adaptor.png|alt=3.5mm adaptor]]\n[[File:ae4_rcacable.png|alt=rca cable]]\n[[File:ae4_receiver.png|alt=Receiver]]\n[[File:ae4_audioevolution.png|alt=Audio Evolution 4]]\n\n== Getting Started ==\n\n\nFirst thing is to make sure your turntable is connected to your phono stage/amplifier correctly.\nAlso ensure it is setup correctly with a good stylus and some clean records to play. If you are\nusing a receiver or integrated amp then you need an RCA audio extension cable plugged into the\nTAPE REC OUT jacks on the back of the unit. (this may vary by model) If you have a stand alone\nphono preamp then plug your audio cord directly into the output jacks on that. In either case your\naudio output cable should then be connected to the 3.5mm mini jack adaptor. Next you need to\nfind the line in jack on the back of your computer. This is usually colored blue. Plug the 3.5mm\nmini plug into this port. OK. Everything is now connected to start recording audio into your\ncomputer.\n\n[[File:ae4_linein.png|alt=LineIn]]\n[[File:ae4_taperec.png|alt=TapeRec]]\n\n== Launching the Software ==\n\n[[File:SelectAudioMode.png|alt=Select Audio Mode|right|frame|Select an audio mode]]\n\n[[File:ae_soundio.png|alt=Soundio window|right|frame|Make sure you are recording from line in]]\n\n=== Select an audio mode  ===\nStart Audio Evolution 4 software and select an approprate screenmode. When it asks what audio mode\nyou want to use select the appropriate option for your machine. If you have an external soundblaster card\nfor instance then \"EMU10kx HiFi 16 bit stereo++\" would be correct. A Pegasos computer using internal audio\nwould use \"Pegasos: HiFi 16 bit stereo++\". I would suggest 44100 as the sampling rate as this matches CD audio\nquality and will translate well to the MP3 format.\n\n=== Start a new project ===\nNow select Start a new project and give your project a name in the filerequestor. Keep in mind that your\nproject location is where all recorded audio samples will reside so make sure you have at least a couple GB\nof free space.\n\n=== Set audio card input source ===\nUnder (menu item: Options->Soundcard in/out) make sure input is set to line in.\nNow is also a good time to save your preferences. (menu item: File->Save preferences)\n\n[[File:ae4_welcome.png|alt=Welcome window|none|frame|Start a new project]]\n\n== Preparing to Record ==\n\n=== Find the control window ===\nNext step is to find the Control window. This is often hidden beneath the Time Line Display window\nwhen you first start the application so use the depth gadgets to reveal it.\n\n[[File:ae4_control.png|alt=Control window]]\n\n=== Testing the input ===\nNow press the red record icon to open the recording panel. Click the check box next to the Left and Right\ninput levels to begin monitoring the input. Now put an LP on your turntable and start playing the record.\nYou should be able to see the colored level meters moving back and forth. This indicates the strength of\nthe audio signals your computer is receiving. If the meters are moving then the audio from your turntable\nis coming in fine and you are nearly ready to record.\n\n[[File:ae4_record.png|alt=Record window]]\n\n=== Setting correct gain ===\nIf the L/R levels appear too low you may have to increase the gain setting. I found a gain setting around\n15 to be good for most of my recordings. The correct value will vary a little depending on your equipment\nand the record you are playing. You want to keep the level meters in the upper green area with only the very\nloudest parts of the recording just peaking into the red area. This will give you a good balance of volume and\npreserve the dynamic range of the recording. Do not record with the signal constantly going into the red as\nyou will be effectively clipping off and losing a lot of audio information that you want to preserve.\n\n\n== Recording the Audio ==\n\n=== Time to record ===\nIf everything checks out up to this point then get your tonearm cued up at the beginning of the A side of the\nrecord and press the red 'rec' gadget. Now you will notice your hard drive LED flashing as well as the virtual\nHD LED in the recording window. This means that audio is being saved onto to your hard drive. You can now\nlower the tonearm down at the lead in groove and start sending audio data to the software. Once you reach the\nend of the LP side you can press the stop gadget to stop recording and save your sample. When the requestor\nasks if you want to keep the sample select 'okay' and give it an appropriate filename.\n\n== Editing the audio waveform ==\n\n=== Getting ready to edit ===\nAt this point we will begin to break up the large audio stream into the individual music tracks that make up\nthe album side. You need to close the recording panel to continue. The rest of the work will mostly be done\nin the Time Line Display.\n\n=== Viewing and playing back the audio waveform ===\nAfter recording you will see a visual representation of the audio you\njust recorded in the timeline display. \n\n\n[[File:ae4_timeline.png|600px]]\n\n\nFirst its a good idea to expand the track display until you can see the track\nwe are working on better.\n\n[[File:ae4_expandtrack.png|alt=Expand track icons|none|frame|Expand tracks]]\n\n\nAlso adjust the zoom level so that you can see the silent gaps between the\nsongs better. Generally a zoom level of 8 or so is ideal. \n\n[[File:ae4_zoom.png|alt=Zoom bar|none|frame|Zoom level]]\n\n\nThe scroll bar at the bottom of the window is used to scroll left/right\nthrough the audio data currently displayed.\n\n[[File:ae4_scrollbar.png|alt=ScrollBar|none|frame|Scroll bar]]\n\n\nYou can listen to any part of the waveform by clicking on the play icon\nwithin the control window or by pressing the space bar. Pressing the\nstop icon or space bar again will halt playback.\n\n[[File:ae4_play.png|alt=Play icon|none|frame|Play]]\n\n\nSet your starting playback position by clicking the timing ruler\njust above the waveform display. You can also click and drag the green\ntime marker for fine adjustment of your current playing position.\n\n[[File:ae4_timemarker.png|alt=Time marker|none|frame|Marker]]\n\n=== Trimming lead in and lead out===\n\n[[File:ae4_split.png|alt=Split file tool|frame|left|Split mode]]\n\n[[File:ae4_grabmove.png|alt=Grab move tool|frame|left|Grab / move mode]]\n\nFirst thing we need to do is trim off the empty lead in area at the beginning\nof our LP side. So we need to find out where the first song starts by\nlooking at the waveform visually and by listening. We then want to seperate\nthis lead-in area from the actual start of the first song. We will use the split\ntool to achieve this\n\nPut the editor into split mode by clicking on the split icon. Now as\nyou hover the mouse pointer over the waveform display you will\nsee a dotted line that demonstrates where a split can be made. \n\nLine up the dotted line just before the start of the first song and click once.\nChange the edit mode back to grab/move before continuing just so you\ndon't accidentally make more splits by clicking on the waveform again.\n\n[[File:ae4_splitmarker.png|alt=Split marker dotted line]]\n\n\nNow you may notice that we have two pieces of audio data sitting next to each\nother at the split point. Each section of audio data is labeled. One section to the\nleft and one section to the right of where the split point was made. You can\nselect the section containing the empty lead in by clicking on it once. Pressing the delete key on your\nkeyboard or right clicking and selecting \"Remove\" from the popup menu will delete the section.\nPresto it's gone and we are left with only the part we wanted to keep. You can now scroll to the\nend of the audio data and using a similar process remove the empty lead out section at the end of the LP.\n\n=== Breaking up the audio tracks ===\nAt this point we have the complete audio from our first LP side with the lead in and lead out\ntrimmed off. Next we want to split this one big waveform into individual song tracks. This is\neasily achieved by finding the silent gaps between each song both visually and by listening\nand then making a split just before the start of each song. You should end up with several\nsplit sections beside each other, one for each song.\n\n[[File:ae4_splittrack.png|alt=Split tracks example]]\n\n=== Saving the audio tracks ===\n\nNow that all of the songs have been split up into individual audio sections we can\ngo ahead and start to save them out to disk as AIFF samples. Select the song you want to save\nout by clicking directly on the section containing it and then right click and select \"Save To Disk\" from\nthe popup menu. Do this for each song and give the tracks meaningful file names.  Congratulations you\nhave now recorded, trimmed and saved out all of the songs from one side of an LP. Now you can repeat\nthis prodedure for Side B.\n\n=== Converting to MP3 files ===\n\nSo next thing you are asking is how am I going to make these into\nMP3 files. I suggest the freeware program CodeAudio (formerly named:TheMpegEncGUI)\nin conjunction with the lame mp3 encoder. You can specify a list of input files where you can\nselect the AIFF files that you previously saved to disk and then you can batch encode the lot\nof them in one fell swoop. I suggest using joint stereo 256Kbps and high quality (-h) mode\nfor good quality MP3 playback.\n\n== Links ==\nAudio Evolution 4 http://www.audio-evolution.com <br/>\nOnyx Soft Code Audio http://www.onyxsoft.se/codeaudio.html <br/>\nLame MP3 encoder http://aminet.net/mus/misc/lame-morphos.lha"
                    }
                ]
            }
        }
    }
}