a workaround for the chopper crash -ACID Product Family

Subject:a workaround for the chopper crash Posted by: CDM Date:8/30/2002 4:38:49 PM From Frank Shotwell: Thanks to everyone who has posted details on this Chopper/Beatmapper/Track-props crash. I just found the bug, and a workaround. The bug is in our new list-based-preview code. It crashes when our preview engine (Chopper/Beatmapper/Track Properties playback) tries to 'stop' if the explorer window isn't open. There are two simple workarounds. 1) Leave the explorer window open. Hit Alt+1 to open it, and then you can tuck it behind one of the other 'views' as a tab, if you don't want to burn screen real estate with it. or 2) Turn off the list-based-preview feature. You first need to make sure the Explorer window is visible, or you'll crash disabling the pref. Go into Options->Preferences->Other-> and uncheck "Enable multiple-selection preview in Explorer window". With this turned off, you should be able to avoid the crash whether the Explorer window is open or not. Very sorry about the inconvenience this bug has caused, and thanks again to all who helped us find it.

From Frank Shotwell:

Thanks to everyone who has posted details on this Chopper/Beatmapper/Track-props crash. I just found the bug, and a workaround.

The bug is in our new list-based-preview code. It crashes when our preview engine (Chopper/Beatmapper/Track Properties playback) tries to 'stop' if the explorer window isn't open.

There are two simple workarounds.

1) Leave the explorer window open. Hit Alt+1 to open it, and then you can tuck it behind one of the other 'views' as a tab, if you don't want to burn screen real estate with it.

or

2) Turn off the list-based-preview feature. You first need to make sure the Explorer window is visible, or you'll crash disabling the pref. Go into Options->Preferences->Other-> and uncheck "Enable multiple-selection preview in Explorer window". With this turned off, you should be able to avoid the crash whether the Explorer window is open or not.

Very sorry about the inconvenience this bug has caused, and thanks again to all who helped us find it.