vintagevibe
Finding a working solution would be more productive than knitting.

But as has been pointed out, finding a working solution is not possible if others don't experience the problem or can't reproduce it. If this was a common problem, I imagine there would be a lot more quite a few posts about it.

Anderton

vintagevibe
If I have to pay to get it fixed it will be just another reason to use Cubase more and avoid Sonar.  I just need to get some work done.

http://www.steinberg.net/forums/viewforum.php?f=184
 
Just sayin'...
 
And that's NOT to pick on Cubase...if you'd mentioned any DAW I could have found something equivalent.
 
Anything that runs on Windows is going to have problems and those problems are going to differ. Think the Mac will solve your problems? Here's a forum devoted to issues regarding a piece of software designed by a company to run only on their hardware...
 
http://www.logicprohelp.com/forum/viewforum.php?f=42
 
Point is you will have problems with any DAW. At some point you have to decide whether to live with them, address them...or take up knitting instead

A
Hallehlujah...I agree 100%!...That is why I like Sonar or cakewalk....It does have issues...but from the get go, once you have the OS system working properly...((if that is possible))?...You get what you need to do everything you could imagine and more!....Thanks for that CW...And I know they are trying to make the best product possible , under those confines...with out bragging too much...And most are getting things working with it...So another bravo!....
 
 I also have now bought a MAC Pro. With Logic x..Just to see what it is all about..???..So many have told me,"""" if you want to get professional results and less hair loss...Mac is the way to go """"".....I know it is not true...but for fun, let us see as witness, with the best of the best or near that so called new Mac Pro canister, I could afford to splurge on...and then we can say for sure....But I already agree with you, because I have been to those forums...Just to see what is up!.
 And pro tools...which I also have for both platforms....their forum is active with issues too!..in both camps!
 
Wink wink
..and Stienberg for me once upon a time...was also in my camp...but the outlandish coding, and pay per fixes...Is what brought them to where they are now....?...And they got bugs still also...That is why I tossed them into the Garbage....And because of their rude support at the time....I will never go back to their audio software product, even though ASIO is their baby!

Anderton

vintagevibe
Finding a working solution would be more productive than knitting.

But as has been pointed out, finding a working solution is not possible if others don't experience the problem or can't reproduce it. If this was a common problem, I imagine there would be a lot more quite a few posts about it.

So the answer to my original question is either "yes" or that there will be no fix.   Thanks for the input.

vintagevibe

Anderton

vintagevibe
Finding a working solution would be more productive than knitting.

But as has been pointed out, finding a working solution is not possible if others don't experience the problem or can't reproduce it. If this was a common problem, I imagine there would be a lot more quite a few posts about it.

So the answer to my original question is either "yes" or that there will be no fix.   Thanks for the input.

No that is not right...What is being put forward is they need more input from you, to see if it can be fixed by those who have scope into troubleshooting issues on PCs....if you do not provide them with that info...There is nothing they can do for you....So ...it is up to you, or some other with those issues to present the information needed to address it....If it is not common...And so far It is not common...might have been buggy in past builds...Could be a device conflict...?...Who knows?...with out further info...it is hidden under  something you have installed or in that setup...somewhere....Perhaps?..not saying there isn't a issue with that and your setup....But I see the other side of their need to want to help you more, by getting what they need to help you.
 
Blessings and bliss might be a resulting factor?....I know Alex is very skilled and Bob also, and there are other builders here to...of a very high order...So there is a lot of technical support Right here, in this domain.....Don't deny it...let it flow!
 
If you feel this is of some kind of sabotage tactic?....Back up or clone your existing Drive as it is, or remove ithe so called working drive, and make a fresh Drive install of Your OS...but remove the connection to internet first....And start with a new build of OS on that system for a backup...while working with the techs here or elsewhere to setup win correctly from the get go...and build slowly to install all things you need....bare basics first....And see if that helps resolve anything...then add the plug ins you want to use one by one...And see if that effects the new build....when you have time to address it.....One step at a time....or just let someone see the info of your setup....And see if it can be resolved that way.....It is completely up to you where you want to go with this.....But there are solutions to every problem or a work around....might take time....But you make the choice.
 
Be well!

Considering there don't seem to be any other reports or complaints regarding this specific issue anymore if you do not file a report to the Bakers with your specific details it is unlikely it will even be fixed in the next paid upgrade (unless by chance due to other fiddling they happen to do).
 
You know the old saying... if it ain't broke don't fix it. That can be extended to this situation by saying if they don't KNOW it's broke why/how would/could they fix it.
 
So as it is I'm gonna say the simple answer is no... it won't be "fixed" before the next upgrade and if you don't report it is unlikely to even be "fixed" WITH a paid upgrade.

vintagevibe
So the answer to my original question is either "yes" or that there will be no fix.   Thanks for the input.

You are drawing the wrong conclusion from the input I've provided.
 
The answer is "yes" if you do nothing.
 
The answer is "likely" if you can reproduce the bug so it can be examined and fixed. No one else has mentioned experiencing this problem with X3e, so it's doubtful someone else will provide steps to reproduce. System-specific solutions require the participation of the person with the system.
 
Another possible answer is "no" if some other update in your system fixes the problem due to there being an undesirable interaction with Sonar rather than a specific problem within Sonar.
 

Anderton

vintagevibe
So the answer to my original question is either "yes" or that there will be no fix.   Thanks for the input.

You are drawing the wrong conclusion from the input I've provided.
 
The answer is "yes" if you do nothing.
 
The answer is "likely" if you can reproduce the bug so it can be examined and fixed. No one else has mentioned experiencing this problem with X3e, so it's doubtful someone else will provide steps to reproduce. System-specific solutions require the participation of the person with the system.
 
Another possible answer is "no" if some other update in your system fixes the problem due to there being an undesirable interaction with Sonar rather than a specific problem within Sonar.
 

 My system is freshly built with all latest drivers.  I have a degree in programming and spent 8 years doing tech support for Hewlett Packard so I'm not speaking from an uninformed perspective when I say it is most likely that this is a Sonar issue.  My steps to reproduce are to just use Sonar.  I'm am just too busy to deal with it and I've not had good experiences with cakewalk support.   The good new is I'm busy.

At least in X2, the time line is the only graphical element which is drawn differently from everything else in SONAR (for whatever reason). I have not checked with X3 yet.
 
Not every end user is able/want/will debug/trace problems. Many do not even want to report them. That is usual in computing world and I do not see any reason to react on the original post the way you do.
 
The "community" do not have the source code to check either possible cause is deductible just from the fact someone has the problem. The developers can. Only once they end nowhere,  they can kindly ask for additional  information.
 
From many other posts I know that most power users are smart and experienced. But they periodically play "fun boy" songs...

vintagevibe
 
My system is freshly built with all latest drivers.  I have a degree in programming and spent 8 years doing tech support for Hewlett Packard so I'm not speaking from an uninformed perspective when I say it is most likely that this is a Sonar issue.  M steps to reproduce are to just use Sonar.  I'm am just too busy to deal with it and I've not had good experiences with cakewalk support.   The good new is I'm busy.

Your experience has nothing to do with it. Whether you're Albert Einstein or just downloaded a Sonar trial for the first time, if you experience an issue, you experience an issue. No one doubts that. 
 
I did a search and it seems this was a major issue with X2 yet virtually non-existent with X3. However, there were several workarounds people found in X2. Apparently there was also an issue with Enable Desktop Composition having to be enabled in Windows, and making sure that process was set to Automatic for that function. Here are some others that were mentioned:
 
I got the Now Time Marker back. I am not positive as to how though. I think the issue may have been resolved when I went to Performance Options/Visual Effects box and changed the setting from "Let Windows choose what's best for my computer" to "Adjust for best appearance." [He never returned to say the problem had returned. and apparently, Adjust for Best Appearance automatically enables Desktop Composition]
 
Docking the console window will bring back the Now Time.
 
Minimize the main X2 window (the one with the Track view) then restore it, and then the Now Time marker appears, without having to save or do anything else. 
 
Grabbing the bar at the top to show/hide the track overview inspector brings it back.
 
Any resizing of the windows will bring back the line as will re-docking the floating view, so it does appear to be a graphics issue.
 
This used to happen to me occasionally. IIRC I could switch to a different screenset and back and that would fix it.
 
If your Now Time Line disappears, the solution seems to be re-docking or re-sizing any window or even changing to another screenset to get it back. AND... don't save your project with a maximized view over the main view.
 
If you press 'I' twice to close and open the inspector the timeline comes back every time
 
Of course these relate to X2, so possibly what was changed from X2 to X3 that fixed this for most people may have "broken" the workarounds. I only found one other person saying this remained a problem with X3 and he did not post a workaround. OTOH he didn't bump the thread that mentioned it or said it persisted.
 
 
Now, obviously a fix would be better but these comments may contain a clue that the Bakers might have something to go by that's more concrete than "I have a problem." If not, at least there are [supposedly] workarounds that don't require closing/opening a project or re-starting. I can't confirm any of these because without experiencing this problem (and I have Sonar running on four very different computers with very different graphics capabilities and three different operating systems) I can't try a workaround.  
 
I'd be happy to feed data to Cakewalk on anything that could provide even the slightest clue, like whether it disappears in the navigator as well. So far, these have been like UFO reports - the people who've seen them believe totally that they've seen them, but they can't provide any physical evidence for those who haven't seen them.

azslow3
Not every end user is able/want/will debug/trace problems. Many do not even want to report them. That is usual in computing world and I do not see any reason to react on the original post the way you do.
 
The "community" do not have the source code to check either possible cause is deductible just from the fact someone has the problem. The developers can. Only once they end nowhere,  they can kindly ask for additional  information.
 

i don't think anyone expects a user to debug a problem, but given that this was a major problem in X2 and a minor problem at best with X3, ANY clues would be helpful - like how often does it happen (we don't know if it's once a month or once a minute), does the now time disappear in only one view or all views, or whether any of the workarounds that worked for people with X2 solved the problem in X3. And if no workaround solved the problem, that's a clue as well. It would take but a few seconds to include that type of information in a post. For example if the OP had said "I tried all the workarounds mentioned in [linked thread that was the first hit on google] and none of them worked," then I would have known not to spend my time looking for a solution. But I looked anyway and collected them all in one place just in case he didn't try any of the solutions that worked for other people.
 
I've now seen how Cakewalk works from the inside. Not all, but the vast majority of the bug fixes in releases subsequent to X3 came from users reporting issues. Sometimes all they could give was one or two clues if they couldn't reproduce the problem, but occasinoally those were enough to solve the problem. The biggest problem is that given the lack of mentions of this with X3 and the large number of mentions with X2, the vast majority of users are not experiencing this problem. If something is specific to only a handful of systems, the lack of a fix isn't due to a desire to force people to upgrade, which the thread title seemed to imply and is the main point with which I take issue. It's due to not being able to identify the problem. In fact I fully expect the problem not to be fixed, paid upgrade or not, if someone experiencing this issue doesn't make Cakewalk aware there's a problem and provide at least one or two clues as to when it happens or what workaround fixes it...or at least how often it happens.
 
It's clear from the change in going from X2 to X3 and from X3 to X3e that with sufficient data, Cakewalk can address and improve, if not totally fix, many issues.