Nice list. Good job. It's gratifying to know far Calewalk has come.

Anderton

200bpm
Looks very legit.  Why does the blog say "making Music on PC or MAC".  Do they have a Mac version coming?

I wish! Sorry, no...this refers to the iOS products as well as the cross-platform instruments like Rapture and effects like the CA-2A. I do tell people that one of the best Windows machines is a Mac running Boot Camp, but Cakewalk doesn't like me to talk about that because they don't want to have to deal with SONAR tech support on a Mac - like how people can access their Mac data under Boot Camp (they can't, they have to use something like Parallels).
 
I really doubt that SONAR will ever appear on the Mac...it's been in deep with Windows for so long I think there's probably no turning back. Whenever I ask Andrew Rossa about a Mac version he says "there are no plans at this time," but I don't think the "at this time" is a dodge that means there's something planned for the future. I think there really are no plans.

Hi Craig...

I agree... I love running on the Mac hardware... But personally I'm very happy to run win7Pro under Bootcamp as I don't particularly like the Mac OS... So I don't have any Mac data I need to reach... I just ignore the Mac drive... Nice having dual Xeon Quad cores! ;-) (soon to be dual Xeon 6cores as well as 64G of RAM)... Now I just need gas to run it! ;-)

As to the bug lust itself, there are so many things both new and fixed that I will be busy examining and learning them for quite some time I'm sure! As with many items they will be very appreciated once used to them such as the different ways of opening plugins....

Thanks!
Keni

Nice job with all the enhancements! I particularly noticed the fix for the audio dropout while generating waveform images during playback in large, high sample rate projects. I put a little video on Youtube to show the fix.
 
http://youtu.be/LlpqyubWJLo
 
--Bill
 

BillThompson
Nice job with all the enhancements! I particularly noticed the fix for the audio dropout while generating waveform images during playback in large, high sample rate projects. I put a little video on Youtube to show the fix.
 
http://youtu.be/LlpqyubWJLo
 
--Bill
 

I watched your video. This is one if the weirdest things I've seen in a DAW. Despite the so-called improvements, the whole Sonar graphical methodology looks extremely disconcerting to me. Is this normal Sonar behaviour? I've never seen such a thing. Does Sonar always take time to update the Waveform like this even though the previous interference has been resolved?? I say again, I've never ever seen such a thing in a DAW before. Someone pease tell me if this is normal for Sonar?

I hadn't noticed this issue until I did projects with lots of data at high sample rates. Basically the fix is prioritizing audio playback over waveform generation.

Maybe.

Drone7
I watched your video. This is one if the weirdest things I've seen in a DAW. Despite the so-called improvements, the whole Sonar graphical methodology looks extremely disconcerting to me. Is this normal Sonar behaviour? I've never seen such a thing. Does Sonar always take time to update the Waveform like this even though the previous interference has been resolved?? I say again, I've never ever seen such a thing in a DAW before. Someone pease tell me if this is normal for Sonar?
 
In my books, I would deem lots of data as a session running 21 realtime softsynths, 10 stereo tracks of audio at 24bit 96khz plus 90 realtime effects plugins, 7 tracks playing-back samples. Would such a session cause this behavior in Sonar with the following PC specs... Haswell Quad Core i7, 16 gig Ram, 2 gig dedicated graphics card, SSD.

 
Weird in what way? Maybe you didn't understand what his video was demonstrating. He is loading a huge high sample rate audio project where the wave pictures have not been yet cached. In *any* DAW when you load such a project it needs to literally read every sample of audio to determine how waveforms have to be displayed. You can try it for yourself - import a large number of big wave files (a few hours in duration preferably) into any daw and you will see it trying to render the waveforms.
 
Also your scenario listed does not constitute any significant disk load. We are talking about a disk streaming optimization here so we need a ton of wave files not synths. So your scenario wouldn't be relevant.
 
I assume Bill's test is similar but what I did was load an audio project at 96K with about 15 GB of audio. When that is done SONAR literally has to process 15 GB of audio data before all pictures are rendered. This process is done in parallel as a background task. In fact many DAW's don't even parallelize this so it would be much slower than SONAR.
In earlier versions this parallel task could interfere with playback causing dropouts. The new design removes this limitation. 
 
When I tested this even a blazing fast Haswell E with 16 cores would drop out. With the new system fix even a slow system is able to handle the workload and wont drop out. Even though most users aren't loading 15 GB audio projects the fix will make their system more resilient to dropouts under disk load. I see this as a huge improvement...

Whoa

John T

Noel Borthwick [Cakewalk]
Even though most users aren't loading 15 GB audio projects the fix will make their system more resilient to dropouts under disk load. I see this as a huge improvement...

I'm currently working on a 40gb project, and this has been a godsend.

Whoa thats big! Are you noticing an improvement? I bet X3 would be more dropout prone esp pics were generating.
An easy way to test if you don't mind the wait for pictures to regen is to press CTRL-A then right click and open "associated audio files". Then click recompute pictures. Then while its doing that press play - in prior versions you would most likely drop out pretty quickly.
Of course this is a worst case scenario since normally you would have all the pictures precomputed - but you get the picture :) Although even when the pix are available there were still potential disk contentions when seeking the timeline or zooming in a lot, that would be resolved by this fix. It just makes the system more solid.

Does anyone know about that screen jumping thing I was talking about? I dug up the original thread where it was confirmed.
 
Recipe 1)
 
http://forum.cakewalk.com/FindPost/3048475
 
Recipe 2)
 
http://forum.cakewalk.com/FindPost/3048496
 
Confirmation by Dan Cate...
 
http://forum.cakewalk.com/FindPost/3048505
 
Confirmation by CakeAlex...
 
http://forum.cakewalk.com/FindPost/3048604
 
Sorry to belabor this but it's one of the very few things that consistently irks me in X3. Very distracting. If it's been fixed, awesome. If not I'll submit an official report so hopefully it will be fixed before I get a chance to upgrade (probably this summer).
 
Just if anyone (Baker's or users) has a chance to check it out.
 
Thanks.

CakeAlexS
Just to add to Noels workload I've PM'd him a project to test if possible... Things must be busy...!

For the screen jumping? Nah, you must mean for something I missed upthread. It's pretty easy to reproduce and I'm not sure why I haven't seen more reports about it. I guess maybe I work in a weird way or something.

Cool. Still hoping someone can test that in Platinum.
 
 

@ drone 7 - sorry if I am being ignorant or intrusive, but what version of Sonar do you own, please?

I've not had chance to test my 40 gig monster today. If anyone's curious, though, it is an odd one.
 
Did a three day job recording an entirely improvisational noise rock band. Came out of it with about 6 hours of 24 tracks at 44.1/24. I record to an old (but awesome) Fostex HDD recorder and then import into Sonar later when I'm doing band stuff.
 
So I'm initially working on a project containing the whole six hours, and planning to chop pieces out for later proper mixing and editing.
 
As you can likely imagine, it varies wildly across those six hours, so there's a fairly short limit on how long it's worth keeping a common base mix for all of it. But for now, that's what I've got to work with. And to blow some smoke up Sonar's ass, I was impressed with the extent to which it's just worked like it was a regular three minute song.

Yo Keni
 
Your avatar is like freakin me out, and stuff.
 
Add some hair, lose the orange, or color the stash.
 
At least for the forums.

Drone7

Anderton
I hadn't noticed this issue until I did projects with lots of data at high sample rates.

A little bit ambiguous.. "lots of data". I know what you mean, but could you give me an example of what constitutes "lots of data" from Sonar's perspective?

In my case, 6 GB of audio files running in the same project at 96/24.