a few definitions of ''shame''

1)dishonor: bring shame or dishonor upon; "he dishonored his family by committing a serious crime"
2)a painful emotion resulting from an awareness of inadequacy or guilt
3)the ridiculous list of bug fixes for sonar 5.01 (a.k.a cakewalk v.15.01), a so called ''pro audio'' aplication:


* Clip envelope editing anomalies, which could occur when 1) creating a clip envelope in a project that had tempo changes, and 2) the clip was positioned after the tempo change and 3) the Now time was over the clip and 4) new nodes were created before the Now time.
* The Mute tool would sometimes mute the wrong clip due to mouse clicks being incorrectly treated as drags.
* The Mute tool could mute the wrong part of a clip if the project contained tempo changes.
* When punch recording, newly recorded clips were 3dB too loud if the panning law was set to -3dB.
* Envelope jump shapes were not rendered properly when sent to VST’s.
* Wrapped VST’s could occasionally be saved with different CLSID’s on different machines, resulting in a “missing plug-in” error message.
* The Go-Previous Measure command would not move the Now time earlier than the current measure.
* When deleting a dotted line envelope—such as a Mute envelope—could leave the group “latched” in an undesirable state. For instance, a track could remain muted even if a Mute envelope was deleted.
* The Edit-Split… command would sometimes not work properly when selecting “Split Repeatedly”.
* Jump envelopes did not take effect when the Now Time was moved during playback.
* Muting a cropped clip with the Mute tool could prevent the clip from being included when exporting or bouncing the clip.
* "Transmit MMC" option in Options | Project | MIDI Out did not work.
* It could be difficult to select steep envelope shapes.
* Quick Groups did not work properly for Send controls on buses.
* Redundant automation was recorded during punch recording when two or more controls were grouped.
* If a V-Vocal clip was created from a partial clip selection, the V-Vocal clip volume would be reduced if the track’s Volume Trim was not set to 0dB.
* In the localized versions of SONAR, decimal values were displayed using a comma in the Process-Audio-Gain, Process-Audio-Normalize, and Process-Audio-Remove DC Offset dialogs.
* Audio Projects could produce a buzzing noise after playing a MIDI project in which the Now Time was moved during playback.
* Confidence recording could display incorrect waveform preview when moving Now time during punch recording.
* Crash with UAD v4.0 CS-1 plug-ins. Loading presets/banks saved from earlier UAD versions could crash the Cakewalk VST adapter.
* Presets/banks saved from earlier UAD plug-in versions could cause a crash when loaded into UAD v4.0 CS-1 plug-ins.
* Deleting a Send control performed several document modifications. It now only adds a single entry to the Undo history.
* All “Load Track Icon” commands are now labeled “Load Track Icon…” to indicate a dialog will open.
* Custom track icons were not loaded when opening a project template via the File-New command.
* Opening a tabbed effect property page could result in a crash when the project was closed.
* Inserting a track template that contained a soft synth in a Bus FX bin could result in a crash if the Undo History was cleared or the project was closed.
* The Clips pane did not shade if a Bus was Muted/Soloed from the Track Inspector or Console view.
* A crash could occur when generating a long waveform preview while playing back a surround project.
* Adjusting track properties, such as mute/solo/arm, did not mark a project as dirty (modified, but unsaved).
* Changing a MIDI track’s output would not mark the project as dirty.
* Changing ‘Snap to Scale’ Root Note or Scale value did not mark the project as dirty.
* Adjusting ‘Show Automated Mute’ from the Track Menu did not mark the project as dirty.
* Changing various In-line PRV parameters from the Track menu did not mark the project as dirty.
* Adding/deleting/modifying lyrics in the Lyrics view did not mark the project as dirty.
* Hiding/showing tracks in the Console view did not mark the project as dirty.
* If the Mackie Control control surface plug-in was enabled, simply loading a project would mark it as dirty.
* Inserting a track template that contained a tempo-synced effect (such as SpectraFX), then undoing the operation and inserting a different track template could result in a crash.
* CPU meter was reporting incorrect values.
* Tempo changes could cause automation envelopes to not be rendered correctly.
* A V-Vocal clip’s Bypass state was not persisted properly with the project.
* V-Vocal clips would not render correctly after undoing a Freeze operation.
* New peak markers could appear in the wrong location if the Now time was manually changed during playback and the meter peaks were reset.
* Bus peak markers could appear in the wrong position when adjusting levels during looping.
* On a bus strip, if you set output, reassigned a send, or created a new send to a "new" bus, a crash could occur if the new bus was somehow routed to the default bus.
* A muted/soloed layer could become stuck in that mode after performing the Compact Layers command.
* When there is only a single layer, the per-layer mute and solo buttons are no longer displayed.
* Resizing a tabbed Loop Construction view could result in undesirable graphic artifacts.
* Drag&drop of track templates resulted in various unexpected behavior: dragging into empty workspace didn’t work; dragging track templates to empty project made the template load without custom track icons; dragging templates in bypassed the Insert-Insert From Track Template-Import Filter settings; some track templates created extra tracks that didn't exist in the template; some track could be missing when dragging multi-track templates.
* Scrubbing audio at high latency setting and with ‘64-bit Double Precision Engine’ enabled could result in a crash.
* If ‘64-bit Double Precision Engine’ was enabled, audio of mixed bit depths could not be exported.
* Repeatedly opening the Colors dialog and changing settings could cause SONAR to become sluggish.
* Drawing of vertical rules could be slow in large projects that were zoomed out.
* Help-SONAR on the Web would go to the SONAR 4 Owner’s page instead of the SONAR 5 Owner’s page.
* Waveform preview “overs” would not always remain visible under certain situations.
* Waveform preview on a synth track that was assigned to a surround bus would not remain visible after stopping playback.
* Drag&drop of partial clip selection would create linked clip effects.
* Copying (Ctrl+drag) a partially-selected V-Vocal clip is no longer allowed.
* Deleting clip effects during playback could result in momentary CPU spike.
* MIDI key bindings would fail to work when toolbar tooltips were displayed.
* A crash could occur when attempting to play back a project using a sample rate that is unsupported by the audio hardware.
* The Track-Sort command did not work correctly.
* Missing key binding for View-Track View.
* Go-Previous Marker did not work during playback.
* Go-Previous Marker was available during recording.
* The Step Record window could display an incorrect custom tick value.
* The ‘Custom Tick Step’ edit box was always disabled when initially opening the Step Record window.
* Track icons could be drawn incorrectly in the Track Inspector if the Console view was configured to show small icons while the Track Inspector was configured to show large icons.
* After changing the Now time during playback, plug-in automation would only update correctly when envelope nodes were intersected.
* sfz could crash when starting playback if End = -1.
* When using tabbed views, the current tab view was not persisted in projects.
* Under certain circumstances, waveform previews could result in a flat line.
* If the BounceBufSizeMsec= variable had been changed in AUD.INI, bouncing down audio could result in the Mixing Latency setting being changed.
* Changing the master bus interleave (mono/stereo), could result in the bus getting out of sync.
* Folder composite clips were not always drawn correctly depending on zoom level, often making it appear there are multiple composite clips while there is really only a single composite clip.
* If a folder composite clip spanned multiple display pages, and had "child" clips that started in the offscreen page, the child clips didn't get selected when clicking the composite clip.
* In the Piano Roll view and In-line PRV, hiding notes (uncheck “Show Notes”) would leave velocity tails that were un-editable. Hiding notes now also hides velocity tails.
* Inserting a Pitch Wheel, Velocity, or Aftertouch envelope on a MIDI track would cause the envelope to insert with an incorrect default value.
* Changing the Now time to earlier than the Loop Start time during playback could cause envelopes to not render correctly.
* If many views were tabbed, clicking on the rightmost tab would not scroll any additional tabs into view.
* The ‘Load Track Icon’ command would not always default to the correct folder if a custom folder was specific in Options-Global-Folders.
* Using a mouse wheel to scroll a tabbed Synth Rack view would also cause the Track View to scroll.
* The “Hidden” indicator in a Track Folder would not update if a track was hidden by the Hide Track menu command instead of the Track Manager.
* Inserting a track template would cause the current Track view tab (All, Mix, FX, or I/O) to always revert back to the All tab.
* Lasso selection would sometimes not work correctly if there was only one track in the project.
* In a Track Folder, the Archive button would not refresh properly to indicate if all or only some tracks within the folder were archived.
* The Quantize MFX would not apply the default settings.
* Moving a delay-compensated effect from a track FX bin to a bus FX bin during playback could cause audio to drift out of sync.
* Inserting a delay-compensated mono effect in a bus stereo FX bin could cause audio to drift out of sync.
* Cyclone DXi would sometimes have outside graphics bleeding through it.
* Looping a project while displaying waveform previews could cause SONAR to become sluggish.
* Generative MFX plug-ins, such as Session Drummer, would still play even after the MIDI track was archived.
* Slip-editing or fading a single clip could also affect other partially-selected clips.
* If an effect’s property page was tabbed, but not the current tab, double-clicking the effect in an FX bin would make the tabbed effect property page visible, but the tab itself would not change.
* Clicking directly below the Strip Select (Quick Group) triangle in a track/bus header strip would cause the strip to be selected instead of the track/bus.
* Copying and pasting a MIDI clip would sometimes result in a clip that was slightly longer than the original clip.
* “Link to Now Time” is now enabled by default in the Step Record window.
* When the Track Inspector displayed a main out, the “Link Faders” button would momentarily disappear when adjusting a Send or EQ in the Track Inspector.
* Pressing the ‘C’ key to enable the Split tool did not immediately update the mouse cursor.
* Copying and pasting data on multiple MIDI tracks using “Replace Old with New” instead of “Blend Old and New” would only work on consecutive tracks. If there was any break between the source tracks, data that was pasted after the break would be blended instead of replaced.
* Events in partially selected clips that were outside the selection time range would be ignored during export. This was not a problem for MIDI and audio events, but if the time range spanned an envelope jump shape--such as a Mute envelope--the envelope could be rendered in an undesirable state (off instead of on, and vice versa).
* If the Track view was maximized, the resize handle was still visible in the lower right corner.
* The red “overs” displayed in waveform previews would not always display properly when zooming and scrolling the Clips pane.
* If multiple tracks were displayed in a tabbed Staff view, the displayed tracks would not be persisted by the Staff view when saving the project.
* Confidence recording (waveform preview) would not work if you punched in on-the-fly.
* The VST Configuration Wizard's 'Folder defaults' options were not persisted.
* Window layouts did not work properly if multiple views were tabbed.
* Improved responsiveness of zooming in the Piano Roll view and Tempo view.
* When editing controller data on a multi-clip MIDI track, holding down the Shift key to draw a straight line could cause data to be deleted after the line.
* When the Console View was floating and had focus, pressing "M" multiple times would open multiple instances of the Track Manager dialog.
* Performing a lot of drag or nudge edits that overwrote the Undo History could result in a crash.
* Under rare circumstances, audio clips would not draw properly if the CPU load was high.
* 32-bit PCM ACIDized wave files created in Sony Sound Forge or Sony ACID could take a long time to import.
* Using the Navigator view to resize a Track view that contained several minimized track folders could result in a lockup.
* Copying and pasting an audio clip that had been cropped in the Loop Construction view could result in the pasted clip being offset by the crop duration.
* Clicking the 'Maximize/Restore the Tabbed View' button did not automatically give the tabbed view focus.
* It was sometimes difficult to move the vertical Track view splitter bar since the hit spot was only 1 pixel wide.
* Moving an imported Groove clip to an earlier location could cause the Groove clip to unroll.
* A crash could occur if you immediately right-clicked in the Track view after opening SONAR while the template menu was still busy initializing.
* Saving (overwriting) a CWB file multiple times could cause the file sizes to increase exponentially each time, until running out of disk space.
* Distorted audio could occur after freezing a ReWired instance of Project5 version 2 if the Project5 GUI was still open.
* Under rare circumstances, SONAR could become unresponsive after a while if ‘Use Multiprocessing Engine' was enabled (Options-Audio-Advanced).

Shame means not owning up to your own shortcomings and making amends. There is no shame in fixing bugs. I'm proud we fixed as many as we did. Other vendors won't even tell you where the bones are buried, let alone fix them, let alone enumerate the ones that were found.

ORIGINAL: Ron Kuper [Cakewalk]

Shame means not owning up to your own shortcomings and making amends. There is no shame in fixing bugs. I'm proud we fixed as many as we did. Other vendors won't even tell you where the bones are buried, let alone fix them, let alone enumerate the ones that were found.

Amen - good preaching Mr. Kuper -

Flawed humans want perfection from others and forget their own imperfections. In my family we call this being "derpis"!

Mr. Kuper I think you folks do a wonderful job - I've never had any issues with Cakewalk or Sonar - granted I'm a hobbyist at best but mercy, I work in a big programming shop and I understand what it takes to put out applications. Though I don't program myself but I help support them once they go out.

I stand amazed!

Great work - keep it up

Now that I have your attention Ron, are there any new development regarding the issues UAD-1's users are having with Sonar?

are there any new development regarding the issues UAD-1's users are having with Sonar?

I run three (3) UAD-1 cards with Sonar 5.01 every day for hours on end, what issues are you having ?? Most of the so called "issues" I see reported are user "issues", ie.. not understanding how to configure their systems or having systems (motherboards, chipsets, etc..) that have conflicts with the UAD1 card, this is not a Sonar problem. Please be specific...WHAT ISSUES do you have ??

ORIGINAL: JohnIsa

Please. how long has it been since ''amends'' have been promised for simple basic issues like ''non gaping audio engine'', and the painfull UAD1's issues... You've got such a great app as far as ease of use and intuitivity. why are such huge issues still not addressed?

I have no gapping problems at all with Sonar 4.0.4 or 5.0.x in my new DAW (Athlon 64 3200+, nothing out of this world). I use lots of softsynths and effects and the CPU usage seldom goes over 80%. I can keep editing stuff, adding and deleting plugins, change views, all with no gaps at 5 ms latency.

Of course, that doesn't mean there may not be a problem with Sonar. But you having those problems doesn't mean there *is* a problem with Sonar, either.

ORIGINAL: JohnIsa

1)dishonor: bring shame or dishonor upon; "he dishonored his family by committing a serious crime"
2)a painful emotion resulting from an awareness of inadequacy or guilt
3)the ridiculous list of bug fixes for sonar 5.01 (a.k.a cakewalk v.15.01), a so called ''pro audio'' aplication

I don't like replying to troll posts, but this one takes the cake. (Pun intended).

I feel obliged to reply just to let Greg, Ron and all the other people at Cakewalk,
know that people like you are in the minority....Cakewalk is , by far, the most open,
honest, helpful and obliging audio software company on the planet bar none.

I wonder if you realise how stupid this makes you seem to people who really know
what is really happening here?

For my money you just created a new definition for "pathetic".

So if you're so down on SONAR...what DAW software do you reccomend?

( I realise you probably won't reply....most trolls run and hide as soon as they're done)

There is no shame in honesty and hard effort. Failing at idealistic perfection is not shameful...it is human. And each one of us fails in that regard.

It's not fact that we fail at perfection that is important...it's HOW we fail that defines our integrity and dignity.

The only dishonor here is that which JohnIsa's puerile attempt at insult brings upon himself.

Kudos to Cakewalk. I continue to be impressed by your candor and willingness to listen.

Go through a list of bugs for Win XP fixed in service packs 1 and 2 sometime. I read an article where Windows XP Beta 02 had 106,500 bugs. Yet I still use Windows everyday to run SONAR and all kinds of other things just like thousands of other people around the world.

All the whiners need to shut up and make music! (in a cover my butt move, I exclude from this statement all people with a legitimate complaint)

I'm happy with Cakewalk and the support they provide.

Funny how negative posts like this almost always come from a "New Member".

ORIGINAL: JohnIsa

1)dishonor: bring shame or dishonor upon; "he dishonored his family by committing a serious crime"
2)a painful emotion resulting from an awareness of inadequacy or guilt
3)the ridiculous list of bug fixes for sonar 5.01 (a.k.a cakewalk v.15.01), a so called ''pro audio'' aplication:


* Clip envelope editing anomalies, which could occur when 1) creating a clip envelope in a project that had tempo changes, and 2) the clip was positioned after the tempo change and 3) the Now time was over the clip and 4) new nodes were created before the Now time.
* The Mute tool would sometimes mute the wrong clip due to mouse clicks being incorrectly treated as drags.
* The Mute tool could mute the wrong part of a clip if the project contained tempo changes.
* When punch recording, newly recorded clips were 3dB too loud if the panning law was set to -3dB.
* Envelope jump shapes were not rendered properly when sent to VST’s.
* Wrapped VST’s could occasionally be saved with different CLSID’s on different machines, resulting in a “missing plug-in” error message.
* The Go-Previous Measure command would not move the Now time earlier than the current measure.
* When deleting a dotted line envelope—such as a Mute envelope—could leave the group “latched” in an undesirable state. For instance, a track could remain muted even if a Mute envelope was deleted.
* The Edit-Split… command would sometimes not work properly when selecting “Split Repeatedly”.
* Jump envelopes did not take effect when the Now Time was moved during playback.
* Muting a cropped clip with the Mute tool could prevent the clip from being included when exporting or bouncing the clip.
* "Transmit MMC" option in Options | Project | MIDI Out did not work.
* It could be difficult to select steep envelope shapes.
* Quick Groups did not work properly for Send controls on buses.
* Redundant automation was recorded during punch recording when two or more controls were grouped.
* If a V-Vocal clip was created from a partial clip selection, the V-Vocal clip volume would be reduced if the track’s Volume Trim was not set to 0dB.
* In the localized versions of SONAR, decimal values were displayed using a comma in the Process-Audio-Gain, Process-Audio-Normalize, and Process-Audio-Remove DC Offset dialogs.
* Audio Projects could produce a buzzing noise after playing a MIDI project in which the Now Time was moved during playback.
* Confidence recording could display incorrect waveform preview when moving Now time during punch recording.
* Crash with UAD v4.0 CS-1 plug-ins. Loading presets/banks saved from earlier UAD versions could crash the Cakewalk VST adapter.
* Presets/banks saved from earlier UAD plug-in versions could cause a crash when loaded into UAD v4.0 CS-1 plug-ins.
* Deleting a Send control performed several document modifications. It now only adds a single entry to the Undo history.
* All “Load Track Icon” commands are now labeled “Load Track Icon…” to indicate a dialog will open.
* Custom track icons were not loaded when opening a project template via the File-New command.
* Opening a tabbed effect property page could result in a crash when the project was closed.
* Inserting a track template that contained a soft synth in a Bus FX bin could result in a crash if the Undo History was cleared or the project was closed.
* The Clips pane did not shade if a Bus was Muted/Soloed from the Track Inspector or Console view.
* A crash could occur when generating a long waveform preview while playing back a surround project.
* Adjusting track properties, such as mute/solo/arm, did not mark a project as dirty (modified, but unsaved).
* Changing a MIDI track’s output would not mark the project as dirty.
* Changing ‘Snap to Scale’ Root Note or Scale value did not mark the project as dirty.
* Adjusting ‘Show Automated Mute’ from the Track Menu did not mark the project as dirty.
* Changing various In-line PRV parameters from the Track menu did not mark the project as dirty.
* Adding/deleting/modifying lyrics in the Lyrics view did not mark the project as dirty.
* Hiding/showing tracks in the Console view did not mark the project as dirty.
* If the Mackie Control control surface plug-in was enabled, simply loading a project would mark it as dirty.
* Inserting a track template that contained a tempo-synced effect (such as SpectraFX), then undoing the operation and inserting a different track template could result in a crash.
* CPU meter was reporting incorrect values.
* Tempo changes could cause automation envelopes to not be rendered correctly.
* A V-Vocal clip’s Bypass state was not persisted properly with the project.
* V-Vocal clips would not render correctly after undoing a Freeze operation.
* New peak markers could appear in the wrong location if the Now time was manually changed during playback and the meter peaks were reset.
* Bus peak markers could appear in the wrong position when adjusting levels during looping.
* On a bus strip, if you set output, reassigned a send, or created a new send to a "new" bus, a crash could occur if the new bus was somehow routed to the default bus.
* A muted/soloed layer could become stuck in that mode after performing the Compact Layers command.
* When there is only a single layer, the per-layer mute and solo buttons are no longer displayed.
* Resizing a tabbed Loop Construction view could result in undesirable graphic artifacts.
* Drag&drop of track templates resulted in various unexpected behavior: dragging into empty workspace didn’t work; dragging track templates to empty project made the template load without custom track icons; dragging templates in bypassed the Insert-Insert From Track Template-Import Filter settings; some track templates created extra tracks that didn't exist in the template; some track could be missing when dragging multi-track templates.
* Scrubbing audio at high latency setting and with ‘64-bit Double Precision Engine’ enabled could result in a crash.
* If ‘64-bit Double Precision Engine’ was enabled, audio of mixed bit depths could not be exported.
* Repeatedly opening the Colors dialog and changing settings could cause SONAR to become sluggish.
* Drawing of vertical rules could be slow in large projects that were zoomed out.
* Help-SONAR on the Web would go to the SONAR 4 Owner’s page instead of the SONAR 5 Owner’s page.
* Waveform preview “overs” would not always remain visible under certain situations.
* Waveform preview on a synth track that was assigned to a surround bus would not remain visible after stopping playback.
* Drag&drop of partial clip selection would create linked clip effects.
* Copying (Ctrl+drag) a partially-selected V-Vocal clip is no longer allowed.
* Deleting clip effects during playback could result in momentary CPU spike.
* MIDI key bindings would fail to work when toolbar tooltips were displayed.
* A crash could occur when attempting to play back a project using a sample rate that is unsupported by the audio hardware.
* The Track-Sort command did not work correctly.
* Missing key binding for View-Track View.
* Go-Previous Marker did not work during playback.
* Go-Previous Marker was available during recording.
* The Step Record window could display an incorrect custom tick value.
* The ‘Custom Tick Step’ edit box was always disabled when initially opening the Step Record window.
* Track icons could be drawn incorrectly in the Track Inspector if the Console view was configured to show small icons while the Track Inspector was configured to show large icons.
* After changing the Now time during playback, plug-in automation would only update correctly when envelope nodes were intersected.
* sfz could crash when starting playback if End = -1.
* When using tabbed views, the current tab view was not persisted in projects.
* Under certain circumstances, waveform previews could result in a flat line.
* If the BounceBufSizeMsec= variable had been changed in AUD.INI, bouncing down audio could result in the Mixing Latency setting being changed.
* Changing the master bus interleave (mono/stereo), could result in the bus getting out of sync.
* Folder composite clips were not always drawn correctly depending on zoom level, often making it appear there are multiple composite clips while there is really only a single composite clip.
* If a folder composite clip spanned multiple display pages, and had "child" clips that started in the offscreen page, the child clips didn't get selected when clicking the composite clip.
* In the Piano Roll view and In-line PRV, hiding notes (uncheck “Show Notes”) would leave velocity tails that were un-editable. Hiding notes now also hides velocity tails.
* Inserting a Pitch Wheel, Velocity, or Aftertouch envelope on a MIDI track would cause the envelope to insert with an incorrect default value.
* Changing the Now time to earlier than the Loop Start time during playback could cause envelopes to not render correctly.
* If many views were tabbed, clicking on the rightmost tab would not scroll any additional tabs into view.
* The ‘Load Track Icon’ command would not always default to the correct folder if a custom folder was specific in Options-Global-Folders.
* Using a mouse wheel to scroll a tabbed Synth Rack view would also cause the Track View to scroll.
* The “Hidden” indicator in a Track Folder would not update if a track was hidden by the Hide Track menu command instead of the Track Manager.
* Inserting a track template would cause the current Track view tab (All, Mix, FX, or I/O) to always revert back to the All tab.
* Lasso selection would sometimes not work correctly if there was only one track in the project.
* In a Track Folder, the Archive button would not refresh properly to indicate if all or only some tracks within the folder were archived.
* The Quantize MFX would not apply the default settings.
* Moving a delay-compensated effect from a track FX bin to a bus FX bin during playback could cause audio to drift out of sync.
* Inserting a delay-compensated mono effect in a bus stereo FX bin could cause audio to drift out of sync.
* Cyclone DXi would sometimes have outside graphics bleeding through it.
* Looping a project while displaying waveform previews could cause SONAR to become sluggish.
* Generative MFX plug-ins, such as Session Drummer, would still play even after the MIDI track was archived.
* Slip-editing or fading a single clip could also affect other partially-selected clips.
* If an effect’s property page was tabbed, but not the current tab, double-clicking the effect in an FX bin would make the tabbed effect property page visible, but the tab itself would not change.
* Clicking directly below the Strip Select (Quick Group) triangle in a track/bus header strip would cause the strip to be selected instead of the track/bus.
* Copying and pasting a MIDI clip would sometimes result in a clip that was slightly longer than the original clip.
* “Link to Now Time” is now enabled by default in the Step Record window.
* When the Track Inspector displayed a main out, the “Link Faders” button would momentarily disappear when adjusting a Send or EQ in the Track Inspector.
* Pressing the ‘C’ key to enable the Split tool did not immediately update the mouse cursor.
* Copying and pasting data on multiple MIDI tracks using “Replace Old with New” instead of “Blend Old and New” would only work on consecutive tracks. If there was any break between the source tracks, data that was pasted after the break would be blended instead of replaced.
* Events in partially selected clips that were outside the selection time range would be ignored during export. This was not a problem for MIDI and audio events, but if the time range spanned an envelope jump shape--such as a Mute envelope--the envelope could be rendered in an undesirable state (off instead of on, and vice versa).
* If the Track view was maximized, the resize handle was still visible in the lower right corner.
* The red “overs” displayed in waveform previews would not always display properly when zooming and scrolling the Clips pane.
* If multiple tracks were displayed in a tabbed Staff view, the displayed tracks would not be persisted by the Staff view when saving the project.
* Confidence recording (waveform preview) would not work if you punched in on-the-fly.
* The VST Configuration Wizard's 'Folder defaults' options were not persisted.
* Window layouts did not work properly if multiple views were tabbed.
* Improved responsiveness of zooming in the Piano Roll view and Tempo view.
* When editing controller data on a multi-clip MIDI track, holding down the Shift key to draw a straight line could cause data to be deleted after the line.
* When the Console View was floating and had focus, pressing "M" multiple times would open multiple instances of the Track Manager dialog.
* Performing a lot of drag or nudge edits that overwrote the Undo History could result in a crash.
* Under rare circumstances, audio clips would not draw properly if the CPU load was high.
* 32-bit PCM ACIDized wave files created in Sony Sound Forge or Sony ACID could take a long time to import.
* Using the Navigator view to resize a Track view that contained several minimized track folders could result in a lockup.
* Copying and pasting an audio clip that had been cropped in the Loop Construction view could result in the pasted clip being offset by the crop duration.
* Clicking the 'Maximize/Restore the Tabbed View' button did not automatically give the tabbed view focus.
* It was sometimes difficult to move the vertical Track view splitter bar since the hit spot was only 1 pixel wide.
* Moving an imported Groove clip to an earlier location could cause the Groove clip to unroll.
* A crash could occur if you immediately right-clicked in the Track view after opening SONAR while the template menu was still busy initializing.
* Saving (overwriting) a CWB file multiple times could cause the file sizes to increase exponentially each time, until running out of disk space.
* Distorted audio could occur after freezing a ReWired instance of Project5 version 2 if the Project5 GUI was still open.
* Under rare circumstances, SONAR could become unresponsive after a while if ‘Use Multiprocessing Engine' was enabled (Options-Audio-Advanced).

Congrats...biggest,longest post ever!!!Well done?????Now go make da music ay?,Antz

ORIGINAL: Guyunique
So just let Mr. JohnIsa be.

hehehehe Patrick... your nick in this forum is apt.
because you have a very unique viewpoint on things.

Maybe because john used the word shame in his post
you found something to identify with?

It was obviously a troll post plain and simple.

How can it possibly be shameful for Cakewalk to fix all those bugs
so quickly and then publish a list of the fixes, openly and honestly.
It would be shameful if they didn't fix them.

In the same post you've told people to stop posting what they believe,
while defending the right of the troll poster to say whatever he wants.

And trying to justify saying "bad things" about people because it
was against their ideas, not their view of products, is hypocritical,
contradictory and just plain crazy!

Freedom of speech applies to everyone mate.
Even people who disagree with your viewpoint.

Is your head screwed on backwards or something?

Hmmmm I've been holding off on SP5 until the major bugs were worked out, and I finished a project. Now I see both have happened. Time to upgrade. Thanks JohnIsa.

Dan

America is also a country of freedom

Yes, and freedom works both ways. JohnIsa is free to criticize Cakewalk, but everyone else is also free to criticize JohnIsa for criticizing Cakewalk. Now, John may criticize those who criticize him.

I must confess I haven't laughed this much in a while. Are you guys all in love with your software(s)!? You make it seem like I have insulted your girlfriend or your mother! You all should go out once in a while instead of fiercely replying to posts like mine who only serve one purpuse = Release the enormous frustration of power users who are tired of being taken for eternal beta testers.

That said, newsflash for all of you : Sonar is not a living being!! no no no kids!! and it should SERVE YOU like a SLAVE. It should obey, be responsive and strong, and able to carry heavy loads for hours on end.

Wake up.

Every upgrade Cakewalk puts out is always at the expense of some other parts of the program that worked just fine previously. There is an immense amount of threads that look like "worked fine in Sonar x.xx, what the hell happened?!".

But here's what is really frustrating. Deep inside I love this app! It's really made for creative people... It's intuitive, you can do almost everything within one window... truly an inspring environment to work in. The problem is that it's not enough to make it the workhorse that I need everyday. And god I wish it was!! Since the tech support at cakewalk have no clue how to solve my issues on their end, I have been wasting hours lately with the tech support people that handle my media-ready computer, my dsp cards and my pro soundcard... 3 out of those 3 told me the exact same thing : "maybe you should consider using another sequencer?" and "the problem is the way that Sonar handles audio".