I'm going to repeat myself and suggest we keep expectations low for X1b. This is only a point release, or actually not even that, and 'features' will most likely be a low priority for this release with bugs and workability taking top priority.

So if you're hoping for a fully customizable Control Bar or drag and drop TO the browser or any other 'feature' improvement you may be sadly disappointed.

But then again what would this forum be without a few hundred 'X1b sucks' threads?

I missed this thread... and started a similar thread.

Anyways, I would have posted here if I had seen it first....

OH I soooooooo Hope I can use X1b in a productive manner!!! without futzin around with why dosen't this work, Why did I just lose audio.. Why dose everything else work but this program. Why why why did I buy this aggravating update so early during its beta Time .. From the day it was release to x1b it should of been called a public beta/Bug tracker. 

It seems that Zyler updates that sticky occasionally (like 4 min ago), so it might be worthwhile for us to review that sticky daily.

Zyler,
Thanks for posting the update status. I have to admit the more time went by without any definitive word on the forthcoming update, the more I stewed about it and the more disatisfied I became. But after seeing the update status this morning, I feel much better knowing exactly what is being addressed, and approximately when it will be released.
 
I have seen a few threads in this forum requesting exactly this kind of dialog and I think it's a great idea. I hope that you intend to continue this from here on out, not just for the X1b release.
 
IMHO, S1 and PT9 are a couple of HUGE paradigm shifts in the DAW industry. If Cakewalk and other developers want to retain or increase their market share, they are going to have to step up their game considerably. I want to see Cakewalk do just that. After all, Sonar is the horse I bet on and I don't want to see it fade into DAW obscurity with less development resources caused by less sales revenue, caused by inferior product, caused by less developement resources, caused by less revenue caused by............
 
It's a snowballing downward spiral and it's nothing that you don't already know. I'll just appeal to you for the sake of Cakewalk and your customers, please fix ALL known bugs before even attempting to develope the next iteration of Sonar, and please continue to provide short term road maps for these fixes.
 
 

yorolpal


Well, this looks like a list of "issues" that were "fixed".  Certainly.  Very good.  But I don't see any of the major problems with X1 as regards usability and features taken away or user preferences that are now absent addressed in this list.  Hopefully they will be there as "new" (old) features.

Hi OlPal...

Yeah... that struck me too... Lots of little fixes and of course all welcome, but not a single issue that's of heated debate... Let's hope this is a VERY partial list...

Keni

I'm glad to get some information out to you all!
It seemed like a better course of action than sitting on it until everything was cleaned up.

But yes, just to be clear - that is a partial list, not even half of the things already implemented.

All issues are stored in a particular format here that we use to tag, link, and otherwise track progress of coding.  I have to go through the data in order to clean it up into a format that makes sense.

That list will end up in the X1b sticky thread and ultimately the Readme.
I hope that helps!

Scott Lee


"I'm going to repeat myself and suggest we keep expectations low for X1b. This is only a point release"

This is a shame. Sonar X1b should have been the Sonar released on December 8th. Consider when X1b is released we will be 3 months into the development cycle moving towards the next paid version (usually released oct-dec every year). A lot of us cant use the software, we now have less time to actually "use" what we paid for initially.

I believe it would be good faith for Cakewalk to really nail this version before even considering a Sonar X2. Make it stable, listen to the user base, fix old school bugs. This would ensure the future credibility of the company and software.

Best,

Your quote was from a user, not Cakewalk staff. As per Zyler's sticky, we're addressing new and old bugs alike. We've got several fixes for AudioSnap, V-Vocal, etc., some of which deal with bugs that go back several versions. And we're also working on new bugs introduced in X1 as well as polishing features, etc.

I'm glad to get some information out to you all! It seemed like a better course of action than sitting on it until everything was cleaned up.

Yes, communication soothes the savage beasts and is much appreciated.

Seth Perlstein [Cakewalk
]
Your quote was from a user, not Cakewalk staff. As per Zyler's sticky, we're addressing new and old bugs alike. We've got several fixes for AudioSnap, V-Vocal, etc., some of which deal with bugs that go back several versions. And we're also working on new bugs introduced in X1 as well as polishing features, etc.  

You just keep 'em comin. Get the house all tidy and ship shape and then start levelling the big stuff on us. I'm assuming the X1 roadmap has plans for big features as the next couple of years roll by.

Is learning to read on the list anywhere?

FastBikerBoy


Is learning to read on the list anywhere?

Not yet, but it should be.

Oh, and how about fixing the bug where I make crappy music and spend all my time in my underpants writing missives to the forum about how much better other software is? When is that bug getting fixed? Because until then I'm gonna use (every other DAW available) but spend all my time on the SONAR forum writing about how much it sux.

Seth Perlstein [Cakewalk
]

FastBikerBoy


Is learning to read on the list anywhere?

Not yet, but it should be.

+10
 

Here's my order of importance to the listed updates (as if anyone cares)...



Fixed a crash that could occur when closing a project.
Fixed a crash that could occur when deleting automation data.
Fixed a crash that could occur when scrolling.
Fixed an issue causing the Track View to suddenly scroll.
Fixed a potential crash that could occur when changing time durations of a V-Vocal clip.
Fixed a potential crash that could occur when removing a V-Vocal clip.
Fixed a potential crash that could occur when adjusting a V-Vocal clip.
Addressed an error with looping V-Vocal clips.
Included several general stability improvements when working with V-Vocal.
D key now minimizes and restores the MultiDock when it is floating.
Fixed an issue preventing effects plug-ins from remaining docked in the MultiDock.
Fixed an issue with recording from multiple MIDI controllers simultaneously.
Fixed a layout issue in the Volume module of the Console View.
It is now possible to open the Clip Properties panel of the Inspector by double-clicking a Clip.
Fixed an issue in the PRV causing 'Grid Resolution > Follow Snap Settings' to be unavailable.
Fixed AudioSnap quantize.
AudioSnap Set Project Tempo from Clip is now functioning.
Big Time color will now persist properly.
Fixed an issue causing Track Templates to load without folders and other data.
Fixed various capitalization inconsistencies between parameter names
“Allow Only One Open Project at a Time” setting now works correctly.
Fixed an issue causing the original BPM of Groove clips to not show in the Clip Properties panel.
Fixed an issue causing 'Preview at Host Tempo' to not work properly with REX and Acidized wav files.
Accessibility: Now able to bring focus to right side of Inspector using a PC keyboard.
Accessibility: Various strings updated.
Fixed an issue where ASIO devices could be lost.
Fixed an issue where Groove Clip looping of a MIDI clip could cause Inspector fields to disappear.
Fixed an issue with key-bindings and no project open.
Fixed an issue preventing Freeze commands from being key bindable.
Fixed an issue where Follow Transport enabled in the Matrix View would disable bounce and export commands.
Fixed an issue with Snap when Musical settings are disabled.
Fixed an issue causing MDI windows to block Multidock hitzone.
Fixed an issue causing FX chain to move position when Properties page is open and the FX chain is bypassed.