![]() |
|
![]() |
This section describes Main Page features not dealt with elsewhere.
CONTENTS
COMMON FUNCTIONS
Three buttons on the Main Page give quick access to "context" menus for common information and editing functions:
![]()
- INFO: various file-information functions, including File Properties, Level, Analysis windows.
- LEVEL: presets for normalisation, gain and phase-inversion (parameter values are built-in).
- EDIT: cut and paste functions, simple mixing, Split and Interleave channels.
You can left or right-click the menu item; if you right-click, the selection is made when you release the button over the item.
FILE FUNCTIONS
There is also a pop-up "context" menu for common File functions: right click the mouse over a "neutral" part of the Main Page to gain access to these, including the RECENT FILES list. The ESC key can be used to cancel the pop-up menu.
IMPORTING MARKERS
The use of MARKERS to play or process part of a file has been described previously. (See the sections MARKERS and PROCESS SEGMENT.)
Under OPTIONS | SETTINGS | Settings tab, you can set the path to an external soundfile editor (e.g. Audacity). If this is one of the following, then Markers saved to file in that editor can be imported using the menu item Markers | Load Markers File:
- AUDACITY:
In Audacity, click on the wave display where the marker is required and select Tracks | Add Label at Selection (or Ctrl+B).
Repeat to add other markers.
Save to file: File | Export Labels. using the default name labels.txt.
- VIEWSF (CDP program):
In Viewsf, zoom in and click on a precise point, zoom out and select Add Marker.
Repeat to add other markers.
Save to file using the default name marks.dat .
Soundshaper initially looks for the exported external file in [User-Folder]\MARKERS.
The external editor is launched from the menu item Tools | External Soundfile Editor (shortcut F2), or by clicking the external editor icon in the toolbar:
![]()
TIMES FILE
Several CDP processes use a Times file, either as a single list of times, or as FROM TO pairs. The processes concerned are listed in the Appendix (TIMESFILE PROCESSES). For each process, you are asked if you want to save a times file from Markers. You may sometimes wish to CANCEL to set up the Markers and then re-select the process. The appropriate file is then saved to and retrieved from the folder [User-Folder \ [Process name].
To set specific marker times from the display in the Soundfile Player, drag the Left Loop Point to the desired position and click the LoopPt button to add the time to the Markers list; alternatively use the Play-position slider to move the Play cursor, then hit F3.
You can also save the current Markers to a generic Times file: see menu Markers | Save Markers to Times file (Shortcut: CTRL+T). This saves FROM TO pairs from the current Markers. For example, if the first four Marker values are 0, 0.092880, 0.406349, 0.743039, then a paired-times file will begin:
0 0.092880 0.092880 0.406349 0.406349 0.743039The Times file is saved to a standard file [User-Folder]\Timesfile.txt, overwriting this as necessary.
In general, where CDP requires pairs of FROM-TO times, the "TO" must be followed by a "FROM" that is slightly later (e.g. there should not be two values of 0.092880; the second could be 0.092881). You should therefore expect to edit the Timesfile, when recalled on a Parameter Page.
To save a single list of times, use menu Markers | Save Markers As.
Save to [User-Folder]\MARKERS\times.txt, or preferably to a name associated with the process or soundfile involved, or your project.
USING SOUNDSHAPER WITH AN AUDIO EDITOR (Tools Menu)
Although Soundshaper has a built-in editor, it can also be integrated with most audio editors, e.g. to run VST plugins. You can either:
- Send the contents of any cell to an audio editor (or other external audio program),
or- Work from the editor and send some or all of the sound to Soundshaper for processing.
FROM SOUNDSHAPER TO EDITOR AND BACK
- Select your favourite editor in Options | Settings | Settings-tab | Soundfile Viewer.
- Create a dummy cell, following the one you've just processed (Menu: Patch | Add Null Cell )
- Send the contents of the dummy cell (soundfile only) to the editor by clicking the external editor icon in the toolbar, or hit F2.
Alternatively, you can set up any audio program as a "Favourite" (File | Favorites | Select Favorite Program) and send the current cell's soundfile (only) to the program via Tools | Favorites plus select the external program in the menu.- Process the imported sound in the editor
- Export it from the editor (see below), normally to the SAME soundfile name (the NULL cell).
- Continue on to the next process in Soundshaper.
FROM EDITOR TO SOUNDSHAPER AND BACK
In the Editor:
- Highlight the portion you want to process.
- Export the selection to a file (see below). Leave the selected portion highlighted.
Exporting the selection:
Audacity File | Export Selection Wavosaur File | Export Selection Nero Edit | Copy to File Wavelab File | Save special | Export Selection Wavepad Edit | Save selected region Waveflow File | Export Selection In Soundshaper:
- Open the file, e.g. by drag and drop.
- Run the process then save the final cell (should be a soundfile) to a file (click on Save icon).
Back in the Editor:
- Open the processed file, select the whole contents (usually CTRL+A) and copy to clipboard (CTRL+C).
- Click on the original file's window (not on the sound-display) and delete the originally selected portion (usually DELETE key or CTRL+DELETE).
- Paste in the processed contents from the clipboard (CTRL+V).
If you don't like the result:
- CTRL+Z: undo the paste operation
and- CTRL+Z: undo the deletion (restore the original).
FAVOURITES: LAUNCH EXTERNAL PROGRAMS
You can launch up to ten external programs of your own choice from the menu: Tools | FAVOURITES. The items are populated from a Favourites File a simple textfile, in which each item occupies two lines:
- Menu Title: the program name as you want it to appear in Soundshaper's Menu (for example: Doubler).
- Program path\filename: the program's folder (directory) followed by its file name ( .exe or .bat)
(for example: C:\CDP\batchfiles\Doubler.bat).The default Favourites File Favorites.txt located in [User-Folder]\FAVORITES\Favorites.txt, is loaded automatically into the Tools | Favourites menu when Soundshaper starts up.
(The file is supplied upopulated, for you to fill it with your ten most favourite programs.)Click on the menu item to launch the external program. Alternatively, the keyboard shortcuts ALT+ F9-12 and Shift+Ctrl+ F9-F12 are reserved for launching Favourites 1-4 and 5-8 respectively. The current cell's soundfile is sent as an Infile to the external program, together with any parameters you enter in the dialog box. Highlight an empty cell first if you don't want to send a file to the program.
To add applications to a Favorites list:
- Select Menu: File | FAVORITES | Select Favorite Program (or CTRL+ALT+F10).
- Browse to find the program's .exe file and select this. Or select a Batch file (.bat).
- A dialog asks you to choose whether to add the program to the list, or replace the list's top item (the ALT+F9 slot).
- The programs is added to the current Favorites list (Favorites.txt or one you have loaded).
The dialog warns that the file itself has not been saved (updated).
- To save a Favorites file Menu: File | FAVORITES | Save Favorites File (or Shift+ALT+F11).
- To load a Favorites file Menu: File | FAVORITES | Load Favorites File (or CTRL+ALT+F11).
You can have as many Favorites files as you like, provided each contains no more than ten items.You can also edit a Favorites file in a text editor such as Notepad, or load it into Soundshaper's REPORT WINDOW (DRAG+DROP onto the Main Page, or File | REPORT WINDOW | Load Textfile... (Ctrl+Alt+F12). Editing the Favorites-file text is currently the only way to delete an item from the list.
EXTERNAL PROCESSING
If you are intending to process the sound in the external program, you should first create a NULL cell, which is a dummy process (a copy in the next cell) Menu: Patch | Add Null cell / External Process (or Ctrl+ #). This creates a soundfile which can safely be altered and overwritten by the external program, without affecting files associated with any other cells.
At present, you cannot launch a CDP process (.exe) directly via this mechanism, because the CDP suite is made up of command-line programs, which must be run in a console window. You can, however, launch Windows' CMD.exe, from which CDP commands can be run.
OTHER TOOLS (Tools Menu)
PAPLAY / PVPLAY
The CDP programs PAPLAY for soundfiles and PVPLAY for soundfiles and spectral files can be used in preference to the Soundfile Player.
Both are available in the TOOLS menu, with full parameters. This route might be necessary if you are using a specific soundcard (see Appendix: SOUNDCARDS). You can view the current audio outputs in Options | Show Audio Output Devices, which displays the output numbers used by CDP.
RECORDING SOUNDFILES
To record a soundfile via your soundcard, click on the RECORD button in the Transport:
, or select Tools | RecSF (or F11). The CDP program RECSF is used for this operation. Use Ctrl+C to terminate recording, unless a fixed time has been set. The recorded soundfile is (optionally) loaded into the source cell of the current patch row, which should be empty.
On the Parameter Page, give an Outfile name and/or choose an output folder: the default anme is recsf.wav. Choose a name starting with a tilde character (~), in the TEMP.OUTFILES folder, if you want Soundshaper to erase the file when you exit.
Note: if you want to use a specific Input Device (other than the soundcard selected in Windows' Control Panel), you will have to find its Device number by typing recsf in a Console Window set up for CDP commands.
MIDI To SEQUENCE
MIDI to SEQ (Alt+F5) takes a standard MIDI file and translates it into CDP's Sequencer format (CDP: sequence2) of Sound No, Time, Pitch, Level, Duration. The procedure uses the public-domain program mf2t, updated by CDP. The output textfile has the suffix .seq. (mf2t is supplied with Soundshaper and must reside in [Soundshaper-folder]\BIN.)
BREAK-EDIT
BREAKEDIT (Alt+F6), CDP's breakfile editor, is similar to Soundshaper's Graph-Edit, but with some other facilities, such as Logarithmic and Exponential (convex) curves. For BRKEDIT, which processes breakpoint files, first load the file into the SPARE FILE slot.
PITCH CALCULATOR
The PITCH CALCULATOR (Alt+F7) is a simple convertor between Frequency (in Hz) and Pitch (as MIDI).
This is supplied with Soundshaper and must reside in [Soundshaper-folder]\BIN.WINDOWS CALCULATOR
CALCULATOR (Alt+F8): a link to the Windows calculator. Or you can click on the Calc button on the Toolbar
![]()
GRAINMILL
GRAINMILL is a standalone version of GRAIN (Menu: Soundfiles | Grain | Grain ), with some altered parameter names. To integrate GRAINMILL with Soundshaper, first create a NULL cell, as outlined above.
USER BATCH SCRIPTS
Soundshaper can now run user-written "batch" scripts and integrate the results within the patch system:
Select Tools | Run User-Batch script (Alt+B)Batch scripts consist of a series of command lines (such as CDP statements), saved as a text file with the suffix .bat. When run within a console window, the whole series is run sequentially.
Two good resources for learning about batch scripts are found at tutorialspoint.com and ss64.com.To integrate a batch script within the patchgrid, Soundshaper must be able to pass an input file to the script from the current patch cell and similarly receive an output file from the script. There is no provision yet for different channel-counts or for second inputs.
When calling a Batch script, Soundshaper assigns the variables %inf% to the current cell file (the input) and %outf% to that of the next cell (the output), both using the SET command. SET uses simple text substitution: e.g. if %inf% has been set to ~A_0.wav, then any use of %inf% in the script is substituted by ~A_0.wav. The in/out file types are assumed to be .wav.
Your script should therefore refer to %inf% for the initial input file and %outf% for the final output file, as in this example:
:: OctaveDoubler - echo the input an 8ve lower and mix copysfx %inf% ~U_0.wav pvoc anal 1 ~U_0.wav ~U_1.ana -c1024 -o3 repitch transpose 1 ~U_1.ana ~U_2.ana 0.5 pvoc synth ~U_2.ana ~U_3.wav submix merge ~U_3.wav ~U_0.wav ~U_4.wav copysfx ~U_4.wav %outf% echo ----- CDP FINISHED -----When run, Soundshaper adds the necessary PATH statements etc. The final line "CDP FINISHED" should be included to tell Soundshaper that the script has been run.
Note that this script uses the imaginary patch row U that is beyond the current 16-row patchgrid limit of A-P. (Use of rows Y and Z is not recommended, as these are reserved for future use internally.) There is no need to use this system for naming files, however. Any filenames can be used; those without paths will be output to the TEMP. OUTFILES folder where the script is run. Filenames in that folder beginning with the tilde prefix (~), such as ~U_0.wav are deleted when the patch is cleared or Soundshaper is closed.
The batch file can be located anywhere, but if it uses data files these must all be in a folder of the same name (e.g. Batches\myfile.bat would have its data files in the subfolder Batches\myfile\ ). Both the batch file and any associated subfolder are copied to the TEMP. OUTFILES folder before being run.
If you wish to save the output to another folder, add a statement like
copysfx ~U_4.wav C:\Batches\doubler.wavYou might also delete all of the internal files at the end of the script, with a statment like
erase ~U*.wavCSOUND SCRIPTS
You can now run Csound scripts from within Soundshaper and combine them in patches with CDP processes. Before doing so:
- Install Csound on your system.
- Check Option 7 "Run Csound Scripts".
If Soundshaper cannot find Csound.exe, a File Dialog will open for you to select it manually.- Visit the Settings Page and save the settings to your Soundshaper.cfg file. The setting tells Soundshaper to find and set the path for CSOUND whenever Soundshaper starts.
To run a Csound script, select Tools | Run Csound script, and in the submenu choose one of:
- Synth for a synthesis script with no soundfile input
- With 1 input file for a script with one soundfile input
- With >1 input for a script with two or more soundfile inputs
- Paulstretch for the built-in extreme time-stretching opcode
For the Synth option, the current patch cell should be a source cell (column 0), as output will be directed there (like other synthesis functions). For the other options, the current cell should normally be a soundfile (except for "NONE" below).
For the third option a script with more than one input the standard ADD INPUT selector will pop up for you to select either the appropriate patchgrid cells, or select the file(s) from a folder. (Note that Infile2 will be copied to the patchgrid.)
For one of the first three options, a File Dialog will direct you to select your script file either a unified format .csd file or an .orc file (from the older .orc/.sco format); the latter triggers a selector for the corresponding .sco file of the same or a different name.
As with Batch scripts, the selected Csound script is copied to the TEMP. OUTFILES folder where the script is run.
Output files
The opcode outs (and its variants) is typically used for output. In the case of a .csd file, an output file can be specified in the <CsOptions> section.
Soundshaper recognises the special filename csout.wav:
-o csout.wav -WComment out any real-time output:
; -odacSoundshaper will then copy csout.wav to the output cell. (For synthesis, this is the currently selected source cell.)
Alternatively, especially in the older .orc and .sco format, the output file might be written to the default file test.wav. If csout.wav does not exist, Soundshaper looks instead for test.wav and copies this to the output cell.Input files
Although Csound is mostly known as a synthesizer, it can also process input sounds. For sound input, Csound scripts typically use the opcodes soundin or diskin, or they may use an opcode like loscil, which reads function tables created with GEN01 or ftgen. The input soundfile(s) may be specified by name in the opcode statement or in the score section (or .sco file). A typical reference is just a filename, e.g."fox.wav". Input files are typically in the same folder as the script, though a path can be included.
With such variety, it is not practical for Soundshaper to analyse the Csound script to find its input files. Instead, we need to identify these from a number of possibilities. A pop-up window allows you to select one of several options for the main input filename and any secondary inputs:
![]()
- CSIN: the infile (e.g. ~A_0.wav) is copied to the file csin.wav and secondary inputs likewise to csin2.wav, csin3.wav, etc. The script's main input is called "csin.wav", any further inputs being "csin2.wav", "csin3.wav". etc.
- SOUNDIN: the infile(s) is/are copied to file(s) called soundin.1 [, soundin.2, soundin3, etc.].
The opcode soundin often expects files of these names. This option is for scripts that use these filenames.
- SOURCE for source cells only. The main soundfile has been loaded to a source cell (column 0), which you want to process.
Optionally choose infiles 2,3... likewise to source cells. When the ADD INPUT selector pops up, select either the appropriate patchgrid cells, or you can choose the files at that point (by drag and drop or via the File Selector).
Soundshaper copies the source filenames to the TEMP. OUTFILES folder, so that the Csound script can find them there.
The script in this case refers to specific named files. For example:The Csound script refers to the file "fox.wav". You select a sound of this name for cell A_0 and choose SOURCE.
Soundshaper copies ~A_0.wav to "fox.wav" in a separate subfolder within the TEMP. OUTFILES folder (\~A_1 - as ~A_1 is the output cell).
The script then runs with its expected sound "fox.wav".Note that the script doesn't care what the sound "fox.wav" actually is. You could re-name a drum sound "fox.wav" and the script would run with that.
- SAVED: same as SOURCE, but Infile1 uses a saved version of the infile cell. For example:
The Infile cell is "~A_1.wav", which has also been saved to "fox.wav", because that is the input filename used in the script.
Soundshaper copies ~A_1.wav to "fox.wav" in a separate subfolder within TEMP. OUTFILES (\~A_2 in this example).
As with SOURCE, this may or may not be the actual sound expected in the script.In this case, the script refers to some filename which only you know. You have saved the current cell (the one to be processed) to this name, within the TEMP. OUTFILES folder and without a tilde prefix (unless that is the name in your script). For secondary inputs, choose these files from their source folder(s), so that Soundshaper can make copies to the TEMP. one.
- NONE: none of the above. For example, the script refers to "fox.wav" and "kickroll.wav". Copy these manually to the TEMP. OUTFILES folder. Also copy the .csd file (or .orc/.sco) to the top level of \TEMP and the script will run, but should be treated as a synthesis script, with output to a source cell. If the current cell is not a source one, a warning is given.
This is rather a poor choice. The patch can be saved and re-run, but the infiles must be left in \TEMP. A sub-patch (patch run in a cell) is not possible.
Csound Script with supplied soundfiles
To run a script that has one or more supplied soundfiles in the same folder as the script, which is very common:
- Select an empty source cell
- Load (one of) the script's soundfile(s) from the script folder
- Select Run CSound script with one or >1 infile, as appropriate
- Choose SOURCE from the pop-up options
- Select any secondary soundfiles from the script folder, when ADD INPUT appears.
Click the Add Infiles OK button.- Choose the Csound script from the script folder.
Paulstretch
The final menu choice for Csound is Paulstretch, a spectral process devised by Nasca Octavian Paul for extreme time-stretching and partially implemented as a Csound opcode (from Csound 6.07).
This opcode is fully integrated into Soundshaper: the source cell and parameter values are set as for CDP processes and Soundshaper writes a customised Csound script, instead of a CDP one.
(It is hoped this may provide a template for many future implementations of Csound scripts.)
HELP
QUICK HELP
Selecting Help | Quick Help (or F1) on the Main Page or a Parameter Page activates a pop-up description of the process or function, with parameter usage and notes relevant to Soundshaper. Quick Help opens in its own resizeable window, which is closed with the ESC key or a button at the top of the window. On the Main Page, choosing the Quick Help option enables the pop-up window to open when you select a process, without obligation to run it. You can then choose to proceed or Cancel. Hit F1 again to de-activate the feature.
CDP REFERENCE DOCUMENTATION
There are several links to the CDP documentation. This is normally located in [CDP-Folder]\Docs, but you can set it on the Settings Page (Folders Tab).
MAIN PAGE: Help | CDP Help (or Alt+F1) brings up the CDP Main Index (\Docs\html\ccdpndex.htm) in your browser.
The current CDP function name is displayed at the right of the Status Panel (if Option 4 Show Hints has been checked). Clicking on this panel brings up the appropriate CDP Help section.
PARAMETER PAGES: Select Help | CDP Help (or Alt+F1) or click on the CDP-function Panel (bottom right-hand corner) to bring up the appropriate CDP Help section.
ONLINE HELP: If Option 12 Online CDP Help has been checked on the Main Page and you have an online connection, selecting CDP Help brings up the Reference Documentation for the current process. Failing this, the stored documentation should come up (though this currently goes only as far as the relevant HTML page and you need to select the process yourself from the index).
SOUNDSHAPER HELP
You can access this manual from within Soundshaper. Soundshaper expects it to be located in:
[CDP DOCS]\SOUNDSHAPER\.The [CDP DOCS] folder is normally [CDP-Folder]\Docs, but you can set it on the Settings Page (Folders Tab).
MAIN PAGE: select Help | Soundshaper Help (or Shift+Ctrl+F1).
PARAMETER PAGES: Selecting Help | Help (or SHIFT+Ctrl+F1 also links to this Manual. Some versions of Soundshaper may bring up a Soundshaper-oriented CDP-Reference for the process if one is available.
HISTORY
Soundshaper maintains a History of your processes and prompts you to save this when you exit the program.
The following is a typical example of a History record:
****** SOUNDSHAPER HISTORY 2016-05-05 10:22:12 ****** ----------------------------------------------------- Cell : A_0 File In : apianos.wav File Out: ~A_0.wav Length : 4.000000 Channels: 2 CDP Prog: copysfx Params : NONE ----------------------------------------------------- Cell : A_1 Process : STACK File In : ~A_0.wav File Out: ~A_1.wav Length : 8.724082 Channels: 2 CDP Prog: modify stack Params : -1.5 10 1.0 0 1.0 1 TRANSPOSE: -1.5 COUNT: 10 LEAN: 1.0 ATTACK TIME: 0 GAIN: 1.0 PROPN: 1 ----------------------------------------------------- Cell : A_2 Process : BLUR File In : ~A_1.wav File Out: ~A_2_c1.ana Length : 8.748118 Channels: 2 CDP Prog: blur blur Params : 40 WINDOWS: 40 ----------------------------------------------------- Cell : A_3 Process : FORCELEVEL File In : ~A_2_c1.ana File Out: ~A_3.wav Length : 8.745215 Channels: 2 CDP Prog: modify loudness 4 Params : -l0.707946The files are text files (.hst) prefaced with the date, as year-month-day, e.g. 2016-05-05.hst. These are stored by default in [User-Folder]\HISTORY, which is created for you, though they can of course be saved anywhere and given any name. If you have more than one session in a day, it is helpful to name the files differently, e.g. 2016-05-05a.hst and 2016-05-05b.hst, as saving overwrites any previous file of the same name. (It can be useful to save a temporary record to a name like !now.hst.)
You can save the History at any time using the Save History button on the Toolbar:
or File | Save History (or CTRL+H).
The File | HISTORY submenu also offers:
- Show History: the selected file is displayed in the Report Window.
- Clear History: the current History record is erased this is what Soundshaper has accumulated so far in the current session, irrespective of whether it has been saved to file or not.
Originally, the History saved complete CDP command lines; this is no longer possible, as the current command lines make use of variables which would be meaningless to the reader. The CDP program/mode and assembled parameter string are still recorded, however.
Soundshaper has no facility to translate the History record back into a usable process chain: this is accomplished by saving and loading Patches, which are complete re-usable records of each processing sequence. Patches can be saved without sources, to make storage less cumbersome. (At present, a re-run patch is not added to the History.)
AUDIO DEVICES
For sound playback, the recommended setting (in SETTINGS) is MediaPlayer/WaveMapper. This directs the Player to whatever soundcard you have nominated in Windows' Control Panel as the default for sound playback. Other soundcards may not be available to the Player, and this may result in PAPLAY / PVPLAY being used instead.
OPTIONS | Show Audio Output Devices lists the available sound outputs in the Report Window, with the numbers used by CDP for PAPLAY / PVPLAY. These output numbers could be used when playing files via either program, with full parameters.
OPTIONS | Update Audio Devices can be used to refresh the list of available Audio Devices, as required. They are also updated when you visit the Settings page.
THEMES
Soundshaper has a new default theme, or "skin". Soundshaper supports a number of 3rd-party skins from Alphaskins. The skins are stored in Soundshaper's subfolder \Skins. The default (pre-selected) theme is called Office2007 Black; the previous default theme Pulsar is still available.
The choice of themes has been reduced in Soundshaper 6 to eliminate some that are not very effective. The remaining ones are:
- DARK: Office2007 Black (new default), Cold (darker background), Nautilus, WMP2008, TV-b (less effective)
- MEDIUM: Pulsar (former default), Dark Glass (not that dark), Gray Plastic
- LIGHT: MacMetal, XPSilver, Elegant, Next Alpha.
To change the Theme, click on File | THEME and select one of the items from the "Skins" folder. You can also set the Theme to be applied when Soundshaper starts. See the Settings page: Settings tab | Change Skin.
RETURN to top of page |