Sonar 8.5 Producer - Is This a Bug?

I'm sure your aware that 8.5 is long gone and no longer supported. You might be the last one on earth using it. Don't get me wrong, it's great software but most all of us have moved on and how things worked in 8.5 is soon forgotten by all the wonderful helpers here. I still have it installed on my DAW computer and If I get a chance tomorrow I'll see If I can duplicate your issue. 

Annabelle,
 
I’m not sure what sight-impaired assistance features are available for the current Sonar products. However, while you continue to research those possibilities, you might want to look into Reaper. I’ve provided some links below, all but one from this year (2016), that would suggest that current versions of Reaper continue to be supported by developers of sight-impaired assistance software.
 
Just as current Sonar products are, in many ways, light years ahead of Producer 8.5, so too are current Reaper versions, in many ways, light years ahead of Producer 8.5. I currently have Sonar Producer 8.5, Sonar Producer X1, Sonar Platinum Lifetime, and Reaper. They all work. But, for sight-impaired people, Reaper may be the most modern option.
 
Great thing is, you can try it for free while you continue to work with Sonar.
 
Here are the links -
 
https://blog.bryansmart.com/
 
https://www.coolblindtech.com/reaper-on-windows-episode-1-general-introduction-why-reaper-is-awesome/
 
http://godigitalqld.dsiti.qld.gov.au/JamieTeh/stories/making-audio-production-more-accessible-to-the-blind1
 
http://forum.cockos.com/showthread.php?t=175681&highlight=screen+reader
 
http://forum.cockos.com/showthread.php?t=175583&highlight=screen+reader
 
The last link is actually a report of someone having an issue with a screen reader on Mac OS with Reaper. So, obviously, all is not perfect. I would still suggest checking it out.
 
Good luck.

Annabelle

Earwax
Annabelle,
 
I’m not sure what sight-impaired assistance features are available for the current Sonar products. However, while you continue to research those possibilities, you might want to look into Reaper. I’ve provided some links below, all but one from this year (2016), that would suggest that current versions of Reaper continue to be supported by developers of sight-impaired assistance software.
 
Just as current Sonar products are, in many ways, light years ahead of Producer 8.5, so too are current Reaper versions, in many ways, light years ahead of Producer 8.5. I currently have Sonar Producer 8.5, Sonar Producer X1, Sonar Platinum Lifetime, and Reaper. They all work. But, for sight-impaired people, Reaper may be the most modern option.
 
Great thing is, you can try it for free while you continue to work with Sonar.
 
Here are the links -
 
https://blog.bryansmart.com/
 
https://www.coolblindtech.com/reaper-on-windows-episode-1-general-introduction-why-reaper-is-awesome/
 
http://godigitalqld.dsiti.qld.gov.au/JamieTeh/stories/making-audio-production-more-accessible-to-the-blind1
 
http://forum.cockos.com/showthread.php?t=175681&highlight=screen+reader
 
http://forum.cockos.com/showthread.php?t=175583&highlight=screen+reader
 
The last link is actually a report of someone having an issue with a screen reader on Mac OS with Reaper. So, obviously, all is not perfect. I would still suggest checking it out.
 
Good luck.

Since you say you have Sonar 8.5 Producer Edition, would you please be so kind as to try and test the hotkeys in fade mode that I've mentioned, and see if it works for you?

good question. im not sure why he took all that time promoting Reaper when it would have taken 3 minutes to try and repro her problem. I know some people who are very happy with Sonar 8.5. yes it is dated but why have to re learn the wheel switching to Reaper when you could still use Sonar 8.5 ?
 
I know this is possibly the 4th time you have created a thread with the same question. My only advise is, I would check in preferences for a setting under fade clips. cant remember to be honest.
I was under the impression that JAWS still worked even in Sonar X2.
See here: SONAR and screen readers for vision impaired users.
 -------------------------------------------------------------------------------------------------------------
SONAR and screen readers for vision impaired users
SONAR has a special Accessibility Mode which can be helpful for vision impaired users when working with screen readers (Window-Eyes, JAWS, etc.). The Accessibility Mode is enabled by adding a key to the Windows Registry (WARNING: only do this if you are comfortable with editing the Windows registry; you may want to back up the registry first), and allows screen readers to receive various information from SONAR that may otherwise not be displayed on the screen (names, values, etc.).
The key is:
HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\X2
 
The Value is:
AccessibilityMode
It is a DWORD. Value can be 0, 1, 2 or 3:
0 - no accessibility (default)
1 - put the access string in the Track view's caption
2 - put the access string in the CWACCESS window
3 - put the access string in the CWACCESS window and make this window visible
---------------------------------------------------------------------------------------------------------------

I believe Windows 10 can read a screen for vision impaired users. I don't believe it only works with Sonar 8.5. 

Annabelle

SquireBum
Annabelle,
  I ran my old version of SONAR 8.5 and tested fade-in and fade-out for both snap to grid functionality and audible effect.  Everything worked on my system as expected, but I don't use any type of screen reader, such as JAWS, on my system.
 
Hope this helps,
Ron
 

Did the Numpad Plus and Numpad Minus keys work in Enhanced Clips mode to increase and decrease the fadeout?
By the way, I have Windows 7, not Windows 10. Mine is also 64 bit version.

I just tried Enhanced keyboard editing mode in both SONAR 8.5 and SONAR Platinum 2016.10.  Fade in and fade out do not follow Snap to Grid.  Cropping does follow Snap to Grid.  Both SONAR versions function the same way on my system.
 
Hope this helps,
Ron

Annabelle

SquireBum

Annabelle

SquireBum
Annabelle,
  I ran my old version of SONAR 8.5 and tested fade-in and fade-out for both snap to grid functionality and audible effect.  Everything worked on my system as expected, but I don't use any type of screen reader, such as JAWS, on my system.
 
Hope this helps,
Ron
 

Did the Numpad Plus and Numpad Minus keys work in Enhanced Clips mode to increase and decrease the fadeout?
By the way, I have Windows 7, not Windows 10. Mine is also 64 bit version.

I just tried Enhanced keyboard editing mode in both SONAR 8.5 and SONAR Platinum 2016.10.  Fade in and fade out do not follow Snap to Grid.  Cropping does follow Snap to Grid.  Both SONAR versions function the same way on my system.
 
Hope this helps,
Ron

Did you get the same results I did? In other words, were you able to hear the results of a fade-in, but not hear the results of a fade-out? If that is the case, is there a bugfix for this problem I have?

if it is some sort of bug, there will never be a fix for it. there were no updates for 8.5 and it's 5 versions old.

Annabelle

SquireBum

Annabelle

SquireBum
Annabelle,
  I ran my old version of SONAR 8.5 and tested fade-in and fade-out for both snap to grid functionality and audible effect.  Everything worked on my system as expected, but I don't use any type of screen reader, such as JAWS, on my system.
 
Hope this helps,
Ron
 

Did the Numpad Plus and Numpad Minus keys work in Enhanced Clips mode to increase and decrease the fadeout?
By the way, I have Windows 7, not Windows 10. Mine is also 64 bit version.

I just tried Enhanced keyboard editing mode in both SONAR 8.5 and SONAR Platinum 2016.10.  Fade in and fade out do not follow Snap to Grid.  Cropping does follow Snap to Grid.  Both SONAR versions function the same way on my system.
 
Hope this helps,
Ron

Did you get the same results I did? In other words, were you able to hear the results of a fade-in, but not hear the results of a fade-out? If that is the case, is there a bugfix for this problem I have?

 
Annabelle,

I tried fade in and fade out using the Numpad plus and minus keys.  I was able to hear the results of the fade in and fade out.  The fade out seemed more subtle than the fade in, but I tested it on a guitar audio clip, which has a strong starting transient that will be most affected by a fade in.  Guitar notes naturally fade, which gave the impression of a more subtle fade out.  The fade out was definitely working, because the clip ended with an audible pop when the fade out was not active.
 
Just my opinion, but I always consider clip fade in and fade out as a tool to eliminate clicks and pops caused when slicing clips.  The length of a fade is usually measured in milliseconds.  I don't believe clip fades were intended to be used for whole track or song fades.  For track or song fades, I think a volume automation envelope on a track or bus is a far superior tool.  Volume automation allows a fade to occur over several measures if that is what you desire.
 
The bottom line is that I don't think you are encountering a bug.
 
Hope this helps,
Ron

tlw
The perception of a fade out or in is greatly affected by the "shape" of the fade curve.

A straight line (a linear fade) is perceived as gaining most of it's volume very near the start of the fade if it's a fade in and retaining most of its volume until very near the end if it's a fade out.

A fade in that gains most volume change towards the end of the fade in or loses most at the start by using a curve that's more logarithmic sounds smoother and more natural. For whatever reason, that's how we perceive it. I don't know if it's possible for you to control the fade curves or not, but if you're cuttently using straight-line linear fades (the default) and can change that try using fade-ins that start slowly and gather speed and fade-outs that do the reverse.

Is there a specific button I can press to go to a submenu that will allow me to change the fade curve that will affect the fade-out via the plus and minus numpad keys? For example, I press Numpad * as a keyboard equivalent to a right-mouse-click, and depending on where I am in Sonar, it will take me to a context menu that has a set of choices dealing with a certain parameter. An example of that would be, if I'm on a clip that has a fade-in at the start, or in this case, a fade-out near the end, even though JAWS won't report that, I press the Numpad * key, and I'm supposed to land on a context menue that lists choices of three fade types, "Linear", "Fast Curve", and "Slow Curve". However, since I believe that the fade parameter is a graphic of a triangle, which is clearly an image, JAWS doesn't exactly see what it is, but yet there's some way that it recognizes that I have pointed the "JAWS Cursor", which is different from the regular "PC Cursor", to the start of where the fade-out should begin. So if a "Linear" fade is a straight line, how would I describe a "Fast Curve" and a "Slow Curve"? Would they be like wavy lines? Or maybe diagonal lines?

Cactus Music
Sorry I didn't get a chance over the weekend, but I just fired up Sonar 8.5 Pro and tried your fade outs and I have no problem at all making any type I desire.  So sorry there is no bug at all. 
The icons will show for the choices they look like a 45 degree angle for linear and then a slope with a dip for fast and a slope with a bump for slow. I'd post the picture but I know that's not going to help you. 

I tried putting accessibility mode on in the registry keys, but I'm not sure if that really did anything. Maybe if you send me an email, I can share with you an example project where I'm having trouble with fade-outs.