• SONAR
  • All those that say that X1 has removed things that were in Sonar 8.5.3 please list them.
2010/12/24 12:33:21
John
I can't be sure but I am reading the manual and I can't find anything taken out of X1 that we had in Sonar 8.5.3. I ask this because it has been stated repeatedly that things were taken away. So what were they?
2010/12/24 12:57:53
FastBikerBoy
I don't think I've found anything actually taken out. Moved or performed in a different manner, yes. Taken away? Nothing discovered so far here. **

** Excludes anything that is a bug/oversight such as key mappings for MCU........
2010/12/24 13:04:31
cryophonik
Separate snap setting for TV and PRV.  This one is killing me and it's the only thing I've seen so far that I would consider a major shortcoming in X1.

2010/12/24 13:16:35
John
Thanks FBB. I understand that the way X1 does things is very different now and that is what prompted me to post this. Because I believe I have been misled by posters here that don't say that but instead maintain that a function or an ability is no longer in this X1 version. 

I am not talking about work flow changes but that X1 was a dumbed down version lacking many things that Sonar had. This was worrisome to me.

Yet what I am seeing over all in posts is an unfamiliarity being mistaken for no longer able to accomplish goals.

To me this idea that we would be getting a less capable Sonar then we had before is the single most irresponsible kind of posting I have ever seen. It needs to be called out if it isn't true. I wonder why anyone would want a potential X1 buyer be given this kind of information.

It is either a case of sheer ignorance or it is a deliberate tactic to undermine   the confidence with CW and its users base. Either way it needs to stop.

I suggest that people here assume that what was done in 8.5.3 is still doable in X1 but that more time is needed by them to find out how it is now done.

Here the RTFM mantra is more critical then it has ever been.
2010/12/24 13:17:27
yorolpal
+1 on separate Snap setting...why they did this is hard to fathom.  While you still can change "some" colors many are "baked" into the GUI...PLUS...where in most all previous iterations of Sonar all but a couple of colors would change instantly so you could see how they looked before committing to them, now many if not most don't change until you have closed Sonar and reopened it.  Again...hard to fathom. 
2010/12/24 13:19:13
Katie_Katie
Fair question.
 
For me, it is not that something is missing (and I don't count the Lexicon - no big deal for me), but the transparency of interaction with the user as provided across all Sonar versions until the X1.  A small example is the record button on the track.  For years I have looked for, and then clicked, the "R" button to arm a track.  It is habit, it is ingrained, "R" means "record".  Not now, it is a red dot.  The "R" does something completely different.  Will I get used to it, yes.  Does it bother me, you bet.  Others are right click menus, where is the tap tempo?, and a host of other "little things" that did not make it to this GUI as-is from the previous version(s). 
 
So to answer your question, what was removed?   Transparency of use.  But I can get past that(read:re-learn) in time, but I would have preferred plug-n-play(read:produce). 
 
2010/12/24 13:20:52
brundlefly
Why does the forum always choke on the most-difficult-to-reproduce posts?  

Here's what you get instead of my thorough listing:

 

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->  <configuration>     <system.web>         <customErrors mode="Off"/>     </system.web> </configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->  <configuration>     <system.web>         <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>     </system.web> </configuration>

2010/12/24 13:25:08
John T
Katie_Katie


Fair question.
 
For me, it is not that something is missing (and I don't count the Lexicon - no big deal for me), but the transparency of interaction with the user as provided across all Sonar versions until the X1.  A small example is the record button on the track.  For years I have looked for, and then clicked, the "R" button to arm a track.  It is habit, it is ingrained, "R" means "record".  Not now, it is a red dot.  The "R" does something completely different.  Will I get used to it, yes.  Does it bother me, you bet.  Others are right click menus, where is the tap tempo?, and a host of other "little things" that did not make it to this GUI as-is from the previous version(s). 
 
So to answer your question, what was removed?   Transparency of use.  But I can get past that(read:re-learn) in time, but I would have preferred not to so.
 
Yeah, that's my current GUI redesign objection. For example, instead of Volume and Pan symbols, we now have text saying Volume and Pan.

Neither one is better than the other, but for a long term user, the abilty to read the scheme at a glance has been given an entirely unnecessary extra bit of settle in time, and makes switching back and forth between this and previous versions (which I'm sure many of us are doing) less immediate than it could have been.

Not a major gripe, but it does seem a bit pointless and odd.


2010/12/24 13:30:32
John
Brandon if I remember correctly said those issues Ol Pal will be address in a later patch. Again though I don't see how that will effect the ability to produce a hit record. The snap to grid issue in particular may be viewed as a bug in previous versions. CW as I understand it was trying to have consistency between views.  Maybe this was a plus and something that could be reimplemented or optional.   But different snap to grids in various views seem awkward to me.


2010/12/24 13:32:21
gothic.angel
John T


Katie_Katie

 ...So to answer your question, what was removed?   Transparency of use.  But I can get past that(read:re-learn) in time, but I would have preferred not to so.

Yeah, that's my current GUI redesign objection. For example, instead of Volume and Pan symbols, we now have text saying Volume and Pan.

Neither one is better than the other, but for a long term user, the abilty to read the scheme at a glance has been given an entirely unnecessary extra bit of settle in time, and makes switching back and forth between this and previous versions (which I'm sure many of us are doing) less immediate than it could have been.

Not a major gripe, but it does seem a bit pointless and odd.





Same here...


The point being, features NOT removed, but "scattered" all around... 


far as I'm concerned:

http://forum.cakewalk.com/tm.aspx?m=2172559
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account