Cakewalk - Console View Resources
Some customers have reported difficulties using the Console view with a project that contains a large number of tracks. Cakewalk has confirmed this problem can occur and is investigating this further. Meanwhile, if you encounter this problem, try to reduce the number of tracks. For example, if the project contains Muted or Archived tracks, try deleting those from the copy of the project with which you want to use the Console view.
Console View and Aux Sends
The Console view supports a special CAKEWALK.INI setting:
[Console View]
TileConsoleAuxSends=<1 or 0, default=1>
When set to 0, the send knobs and enable buttons for an audio module are lined up top to bottom and do not wrap. Tiling occurs when you have more than 4 aux sends configured). This option is useful if you prefer to use more vertical space in the console than horizontal.
Note: This variable is useful if you use any of the Session 8 templates, since the Console view in these templates are configured to show 5 aux sends.
Enable Read and Write Caching
Please keep in mind that the Enable Read Caching and Enable Write Caching options in Tools-Audio Options-Advanced will not take effect until you exit and restart Pro Audio.
Session 8 StudioWare™ Panels
The Session 8 StudioWare™ panels that were included with Pro Audio 6.0 have been removed. The Session 8 panels are obsolete now that the new Console view has been added. The only limitation is that the Console view cannot control the Input/Return section on the Session 8. To control the Input/Return section, please use the supplied Session 8 Internal Mix template (File-New-Session 8 Internal Mix).
Dump Request Macros
When you press the Receive button in the Sysx window, you may pick from a list of Dump Request Macros. These are short System Exclusive messages sent to a synthesizer to make it dump (send back) System Exclusive data. DRMs are defined in your CAKEWALK.INI file in the [Dump Request Macros] section. You may add your own DRMs or modify the ones that we have provided. Use the Windows Linux - vi to edit the file.
Please note that many DRMs have been donated by customers who are using the particular equipment. In some cases we have not been able to test those DRMs because we do not have access to that equipment. We are redistributing such DRMs on an as-is basis.
Real-time Effects and Processor Speed
To properly use real-time effects in the Console view, you need a computer with a Pentium 120 MHz or faster processor. Even with such a powerful CPU, there is a limit on the number of effects you can use simultaneously. Furthermore, different types of effects are "more expensive" in terms of how much CPU they consume. For example, Reverb is relatively expensive, whereas the 2-band EQ effect is relatively inexpensive.
A good strategy is to use an expensive effect like Reverb in an Effects Loop (Aux section in the Console view)). That way, you can have several audio tracks share one effect. You can then individually adjust each track’s send and return levels.
Finally, no matter how slow your CPU is, you can always use any effect by applying it to the audio as an off-line edit command. See the "Editing Audio" chapter in the User’s Guide for more information on these commands.
Full MMC Auto Punch
Auto Punch works for all MMC devices that support on-the-fly recording. (In past versions of Pro Audio, Auto Punch was restricted to only those devices that supported the MMC Event command.)
If all MMC features work except for Auto Punch record mode, your equipment probably doesn't support the MMC Event command. (Consult with the manufacturer if you aren't sure.) You can overcome this limitation by adding the following line to the Options section of your TTSSEQ.INI file, which can be found in your Cakewalk Pro Audio directory:
[Options]
MMCUseEvent=0Make sure you restart Pro Audio for the new setting to take effect. This mode causes Pro Audio to send MMC commands to perform automated punches during recording. This method is less precise than use of pre-programmed events, so only use this setting if necessary.
Managing Chord Libraries
The Chord Properties dialog box has in Import button that allows an existing chord library to be merged into your current chord library. This is especially useful when you install a new version of Pro Audio, but you've added chords of your own to the chord library that you don't want to lose.
The Pro Audio installation process will never overwrite the existing chord library, which is in file CHORDS.LIW; it will copy the new chord library to CHORDNEW.LIW if CHORDS.LIW already exists. You can then use the Chord dialog Import button to import the new chords from CHORDNEW.LIW without losing your own chords. The Import function checks each chord carefully to avoid creating duplicates.
Due to the large number of chords in the standard chord library, the Import function may take a long time to complete. If you are sure that you never added chords of your own to the library, then you can simply copy CHORDNEW.LIW to CHORDS.LIW to get the new library.
Panic (Reset) Strength
The Reset command (Realtime-Reset and Transport toolbar) stops playback and turns off any "stuck notes". There are two ways a MIDI note can be turned off: By a note-off message or by MIDI controller number 123 ("all notes off"). By default, Reset uses controller 123 only.
This may be insufficient for some older synthesizers. If so, set PanicStrength=1 in the [WINCAKE] section of CAKEWALK.INI. To do so, you may use Tools-Initialization Files. Reset will send a note-off message for every note on every channel of every port. This makes Reset much slower but will resolve the problem.
The following describes in detail which events Pro Audio transmits for both Reset options:
PanicStrength=0
Pro Audio sends:
Event: Value: Channel: Port:
Pitch Wheel 0 1-16 All
Controller 1 0 1-16 AllController 7 127 1-16 All
Controller 10 64 1-16 All
Controller 64 0 1-16 All
Controller 66 0 1-16 All
Controller 67 0 1-16 All
Controller 121 0 1-16 All
Controller 123 0 1-16 All
PanicStrength=1 (this method takes longer, as it send a Note Off message for every pitch on every channel on all ports; the first method only sends a single "All notes off" message (controller 123), which some older equipment don't respond to properly)
Pro Audio sends:
Event: Value: Channel: Port:
Note Off C#5-G9 1-16 All
Pitch Wheel 0 1-16 All
Controller 1 0 1-16 All
Controller 7 127 1-16 All
Controller 10 64 1-16 All
Controller 64 0 1-16 All
Controller 66 0 1-16 All
Controller 67 0 1-16 All
Controller 121 0 1-16 All
Controller 123 0 1-16 All
Lyrics View and Special Keys
The shortcut keys for starting and stopping playback (SPACEBAR, P), recording (R), and rewinding (W), do not work in the Lyrics or CAL view, since these keys are used instead to type lyrics or CAL commands. When the Lyrics or CAL view is the active window, use the buttons in the Transport toolbar to start, stop, record, and rewind.
Sample StudioWare™ Panels
Cakewalk Pro Audio comes with sample StudioWare™ panels. Some of these are available by choosing File-Open, selecting StudioWare in the Files of Type list, then double-clicking on the desired StudioWare™ icon. Others are included within template (.TPL) files. Cakewalk Pro Audio 8.0 ships with these StudioWare™ panels:
Panel: Format:
AWE .CakewalkStudioWare
EMU Orbit .CakewalkStudioWare
General MIDI .CakewalkStudioWare
Mackie OTTO 1604 .CakewalkStudioWare and .TPL
MMC (A generic Panel
for products that support
MIDI Machine Control) .CakewalkStudioWare
Novation BassStation BS-1 .CakewalkStudioWare
Novation BassStation Rack BSR-1 .CakewalkStudioWare
Novation DrumStationRack DRM-1 .CakewalkStudioWare
Novation SuperBassStation SBR-1 .CakewalkStudioWare
Roland GS .CakewalkStudioWare
Roland JV-2080 Effect .CakewalkStudioWare
Roland JV-2080 EFX #1-#25 .CakewalkStudioWare
Roland JV-2080 EFX #26-#40 .CakewalkStudioWare
Roland JV-2080 Patch .CakewalkStudioWare and .TPL
Roland SC-88Pro EFX #1-#34 .CakewalkStudioWare and .TPL
Roland SC-88Pro EFX #35-#64 .CakewalkStudioWare and .TPL
Roland UA-100 Compact Effects #1-#34.CakewalkStudioWare and .TPL
Roland UA-100 Compact Effects #35-#64.CakewalkStudioWare and .TPL
Roland UA-100 Full Effects .CakewalkStudioWare and .TPL
Roland UA-100 Mixer .CakewalkStudioWare
Roland UA-100 Utility Split Events .CakewalkStudioWare
Roland UA-100 VT-X .CakewalkStudioWare and .TPL
Roland VS-880 .CakewalkStudioWare
Session 8 Input/Return section .TPL (Session 8 Internal Mix)
Tascam RC-808 .CakewalkStudioWare
Yamaha 03D .CakewalkStudioWare and .TPL
Yamaha ProMix 01 .CakewalkStudioWare and .TPL
Bug fixes in Pro Audio 8.01
The following is a list of bugs and other issues that have been addressed since version 8.00:
Exporting audio to a .WAV file with the Tools-Export Audio command would double the file size.
When loading projects that were created in Pro Audio 7 and earlier into Pro Audio 8.00, audio event velocities were not mapped properly. In Pro Audio 8.01, velocities are no longer migrated, they are retained, and now act as an additional gain factor on top of whatever envelopes may already exist in the audio.
If the Tools-Global-Options-MIDI-Prepare Using [500] Millisecond Buffers setting was left at its default value of 500 milliseconds, then notes could drop out during playback on tracks that had a Time+ setting of greater or equal to "1".
If the Stereo Reverb audio effect was inserted as a Master effect, opening and re-opening its property page could crash Pro Audio 8.00.
Audio effects would slow down the system during silent passages in a project.
Lasso zooming down vertically causes Track pane and Clips pane to get out of sync (the Track pane cells and the clips in the Clips pane would not align properly).
Combining overlapping 24-bit audio events in the Audio view introduces distortion.
In Pro Audio 8.00, it was not possible to import the audio stream from a video file when working with 24-bit projects.
24-bit audio was corrupted upon Export to Audio (the resulting .WAV file would distort).
It was not possible to use the Tools-Export Video to AVI command when working with 24-bit projects.
It was not possible to copy and paste 24-bit audio between two 24-bit projects.
The Parametric EQ audio effect would lose its settings when closed and re-opened by double-clicking the effect bar in the Console view.
Archived tracks would stream (silent) data in Pro Audio 8.00. This means that archiving audio tracks would not improve system performance.
Using the piano key pane in the Piano Roll view to select notes by pitch caused the focus to stay there. This meant that you could not use the DELETE key to delete the selected note events.
When using multiple sound cards in Pro Audio 8.00, any effects that were patched in an Aux bus would not be applied when using the Tools-Mixdown Audio command.
The Left/Right arrow keys could not be used to scroll horizontally in the Piano Roll view.
Archiving an audio track that was using an Aux send, could cause silent playback or a crash.
When working with volume and pan envelopes, the Node Properties dialog now only displays the timeline in samples. This is because currently envelope nodes are relative only to the clip and not the sequence, thus other timeline modes are useless for this type of node.
Digital Audio Labs (DAL) online Help for the V8 incorrectly referred to the Soundscape HDR1.
Online Help for Tools-Audio Options did not list several new settings. This Help section has now been updated to reflect all audio option settings.
Certain CAL Track Function references opened the wrong online Help topic.
The "i" hot key was used twice in the Clips Pane inspector menu.
Changes to the Tools-Global-Options-MIDI-Prepare Using [500] Millisecond Buffers setting did not appear to "stick" between sessions until playback was initiated.
It was not possible to drag a volume or pan envelope node in the Audio view when at a vertical zoom level of 60% or greater.
A Playlist did not use the MIDI Echo settings of the currently playing project; it used the MIDI Echo settings for the next project in the Playlist.
If the Scrub tool was selected in the Audio view, moving the anchor point for an event that did not begin at time 1:1:0 could crash Pro Audio 8.00.
Dragging a volume envelope could cause audio popping.
Note durations could not be set in the Staff view by using the numeric keypad (although you could use the QWERTY keyboard).
Only the first 32 characters of an audio event’s name were displayed correctly. Any remaining characters were displayed as garbage.
Lasso zooming while holding the Shift or Ctrl keys could cause the measure numbers in the time ruler to disappear.
Vertical lasso zoom past the length of track could cause a crash.
CFX (mono) audio effects would remain in track inserts after unsuccessfully dragging them to an AUX bus (mono effects cannot be used in an Aux bus). The effect would appear to be removed from the track insert, but the effect would be applied during playback, and would also be displayed if you closed and re-opened the Console view.
Dragging a clip down to another track that was initially not visible (only visible after vertically scrolling the Clips pane), would not redraw the screen, and the clip would end up on the wrong track.
Forwarding to the end (Go to End) of the currently playing project in a Playlist could cause a crash.
Scrubbing in the Audio view with high zoom levels could lead to a crash if a video file was loaded.
Dragging and dropping events vertically, then scrolling, could cause the time ruler bar to disappear.
When sending real-time input to the Arpeggiator MIDI effect, the echoed MIDI data would be transmitted on the wrong channel.
Dragging the Arpeggiator MIDI effect’s ‘Lowest Note’ slider during playback could cause a crash.
If a video file was loaded, arming a track for recording could cause the video to roll.
When applying an audio effect as an offline command, only the first clip would be processed if ‘Create a Send Submix’ was selected in the Mixing tab.
The default Arpeggiator MIDI effect settings have been replaced with more useful and appropriate default settings.
If a MIDI effect was applied to one of a few LINKED clips, the associated clips would be moved incorrectly.
The Metronome could drift away from MIDI tracks during looping playback.
When using the Session 8 hardware, patching effects in the Console view, then trying to close the Console view, would lead to a crash.
Lasso selecting events could cause a crash if looping was enabled and the Staff view was open.
If the Overwrite record mode was selected, Pro Audio would cause an application error if you used any keyboard accelerator keys (spacebar, etc.) during a count-in.
Lasso zooming past the end of a track could cause a crash.
If the anchor point had been moved, an audio event would not move to the proper location when changing the Time setting in the audio event Properties dialog.
When applying volume and pan envelopes, there is some additional overhead during playback. This is necessary in order to process the envelopes with better than sample accuracy. In Pro Audio 8.00, the additional overhead would be applied to all the audio events, even if just a single audio event used a volume or pan envelope. In Pro Audio 8.01 playback is more efficient, as any additional overhead only applies to audio events with non-linear envelopes. Audio events with a straight envelope line, or no envelope at all, will result in more efficient playback.
Patch Caching would send incorrect data to certain sound card drivers.
Patching multiple Master effects in the Console view, then opening and re-opening the effect property pages could cause Pro Audio to crash.
There was a small resource leak when repeatedly scrubbing in the Audio view while a video file was loaded.
Se você possui programas ou arquivos interessantes envie-nos!
sergio@sheffield.com.br
