Vastman

aghschwabe
 
 
 
It updated fine (and no problems with the update itself). Just borked audio on some plugs and my sustain pedal is out of commission...which is enough problems for one day. I've rolled back to the "J" update so I can get this project done (though manually inputting the sustain pedal is going to suck).
 
In other words: one problem at a time. ;-)
 
ps: for the time that I had Kingston installed, I definitely saw the improved speed...but it's not worth the cost of a reliably functioning DAW.

Maybe I'm in a mood but it's frustrating when people appear out of no where, with zero other posts, DON'T POST THEIR SYSTEM SPECS in their sig like we repeatedly encourage, and use vague language like "Just borked audio on some plugs" OY! Wastes good peoples time...
 
FWIW, I've had Iris2 for awhile but hadn't gotten round to installing it.  I just did, to check the crashing issue you posted about elsewhere.  First, I rolled back to "J" land, then installed Iris2 and all the additional content, added Iris2 to a song I'm working with, which has over 100 tracks of audio, synths, kontakt/falcon/omnisphere2 tracks, lot of Albion One... a song already beginning to stress my pretty robust system.   
 
I verified Iris worked fine...at least the vst3 version...I use vst3 whereever possible, and also wanted to test the bakers new vst3 work.   Iris itself was kinda boring but....  I saved the song, and reupdated to "K" land.  Brought up the song with the iris track... played fine.  Added another vst3 instance of iris.... recorded/played back fine...
 
Don't know if you're using vst3, but from here it works fine.
 
FWIW, if ur using vst2, try vst3.

Maybe they have only one post because how they use Splat has worked for there needs and now it doesn't just because the backers changed something and messed up something for therm. IMO!   

ampfixer

southpaw3473
Well, I've updated to Kingston and my VST Scan # is 5.4.1.0!! I've been having some new clicking issues with a couple of plugins-McDSP seems to be a culprit. Wonder if all this is related.

I'm not certain, but I'm pretty sure that's the correct number of the VST scan prg. I'm sure it will be clarified in a few days. As long as things are working I won't sweat the details .

I wonder how many people here are using copyright protected images as their avatars? :)

Anderton
It seems the biggest problems with updates occur with third-party plug-ins, especially when there's an upgrade to a new version of VST (as happened with Kingston). I remember when the rolling updates concept was first discussed, much of the talk about rollback revolved around making this easy because of the expectation that people would run into incompatibilities with certain plug-ins.
 
If you look at Apple, another company that essentially does rolling updates with iOS, you'll find that after the iOS update there are a flurry of updates from third-party apps running under iOS to maintain compatibility. Similarly, I think it was Noel who said in another post that plug-ins are a "moving target." I don't know enough about code to know why some plug-ins "break" while others don't, but at least any issues do seem to get resolved eventually.

So there are issues with this version!!! The bakers NEED to email the people that DON"T live here and let them know! BE4 they have to record someone and nothing is working and they loose a pile of cash! 

Dave000
 
So there are issues with this version!!! The bakers NEED to email the people that DON"T live here and let them know! BE4 they have to record someone and nothing is working and they loose a pile of cash! 

Professionals know to TEST new versions BEFORE they bring in clients for a session. Some even have separate systems specifically for testing such things before installing on their main rigs.
 
It's moot anyway because if you end up with a problem you just have to rollback to whatever version you were using before. It's not a big deal unless you go WAY out of your way to make it one.
 
But you know all that... and are just making a big deal out of it because... "reasons".
 
Good call trolling a stickie thread that's unlikely to get locked though.

Beepster
Professionals know to TEST new versions BEFORE they bring in clients for a session. Some even have separate systems specifically for testing such things before installing on their main rigs.
 
It's moot anyway because if you end up with a problem you just have to rollback to whatever version you were using before. It's not a big deal unless you go WAY out of your way to make it one.

I think 'pros' would prefer scheduled stability releases with regression soon after, so they know when to upgrade without beta testing. Rolling back is out of the frying pan into the fire quite often (without having to look for it). Classic example of this right now is the Z3TA+2 update. I wasted a few hours testing, adopted it as good and then found out via forums member that presets get garbled with existing projects. Now I (and probably most of us) need to dump it. So now I need to uninstall and install again Z3TA+2, the old version that suffers from stuck loops etc. This I suppose is entirely my fault?? I didn't test it properly as a beta tester? But if I knew a stability release was on it's way soon afterwards I might have not wasted my time. Regardless glad z3ta+2 is getting fixes thankyou cakewalk. Again stressing I'm not disagreeing with monthly release schedule.

...and I don't want to associate myself with Dave above until he makes calm points with evidence to back himself up. Prefer sensible discussions (well ever hopeful).

Doktor Avalanche

Beepster
Professionals know to TEST new versions BEFORE they bring in clients for a session. Some even have separate systems specifically for testing such things before installing on their main rigs.
 
It's moot anyway because if you end up with a problem you just have to rollback to whatever version you were using before. It's not a big deal unless you go WAY out of your way to make it one.

I think 'pros' would prefer scheduled stability releases with regression soon after, so they know when to upgrade without beta testing. Rolling back is out of the frying pan into the fire quite often (without having to look for it). Classic example of this right now is the Z3TA+2 update. I wasted a few hours testing, adopted it as good and then found out via forums member that presets get garbled with existing projects. Now I (and probably most of us) need to dump it. So now I need to uninstall and install again Z3TA+2, the old version that suffers from stuck loops etc. This I suppose is entirely my fault?? I didn't test it properly as a beta tester? But if I knew a stability release was on it's way soon afterwards I might have not wasted my time. Regardless glad z3ta+2 is getting fixes thankyou cakewalk. Again stressing I'm not disagreeing with monthly release schedule.

...and I don't want to associate myself with Dave above until he makes calm points with evidence to back himself up. Prefer sensible discussions (well ever hopeful).

I'm uploading a video of what I was able to record with only 2 other tracks used right now.
along with this statement :
Cakewalk Sonar Membership program.
You sign up for a FULL year of updates, patches and other stuff and at the end of the year you can pay again and keep what you have and get more updates, patches and free stuff OR you get to keep everything from the previous year NO STRINGS. Well into my Membership and it’s (for the most part) clean sailing! Now with the last update “Speedy SONAR Kingston” this is what I get recording 1 guitar track with 1 XLN drum track. Bounced or live MIDI. I have tried 16 bit 24 bit ASIO and MME 32 bit on two systems! All give the same results! The Audio is being smashed out of time.
My computer is well within system requirements when I joined the Membership program.
Is it really worth being in a Membership program if the software out grows a 6 month old system designed to work with Sonar Platinum that seems to now is obsolete?
IMO 
 

Dave000
I'm uploading a video what I was able to record with only 2 other tracks used right now.
along with this statement :Cakewalk Sonar Membership program.
You sign up for a FULL year of updates, patches and other stuff and at the end of the year you can pay again and keep what you have and get more updates, patches and free stuff OR you get to keep everything from the previous year NO STRINGS. Well into my Membership and it’s (for the most part) clean sailing! Now with the last update “Speedy SONAR Kingston” this is what I get recording 1 guitar track with 1 XLN drum track. Bounced or live MIDI. I have tried 16 bit 24 bit ASIO and MME 32 bit on two systems! All give the same results! The Audio is being smashed out of time.
My computer is well within system requirements when I joined the Membership program.
Is it really worth being in a Membership program if the software out grows a 6 month old system designed to work with Sonar Platinum that seems to now is obsolete?
IMO 
 

Dave please pull back your emotions, start a new thread. Explain the issue clearly with steps to repro. Avoiding ranting that's just not going to help you at all and in fact will simply reenforce the view here that all complaints are negative. Let's see if we can help you get to the bottom of this... If you are interested.

and let me also add that as a "Cakewalk Sonar Platinum Member" when I upgrade each month I expect things to be FIXED and not FLOPED! and to back grade to an older version would entitle me to the newer upgrade versions that work even after my 12 months is up! My last upgrade better work without NEW bug issues!  
 
Also as a member that makes me entitled to Comment on anything related to SPLAT here in this forum...  
I'm not bulling or attacking anyone.. I leave that to the peanut gallery!
 
And BTW.. I'm just a regular guy trying to record some songs and have some fun! But marketing ploys and gimmicks to keep people hooked are just not fair to anyone! 

OK I tried. I'm afraid your approach here is going to get your nowhere and just reinforce polarised and charactatured viewpoints.

Dave000

Doktor Avalanche

Beepster
Professionals know to TEST new versions BEFORE they bring in clients for a session. Some even have separate systems specifically for testing such things before installing on their main rigs.

It's moot anyway because if you end up with a problem you just have to rollback to whatever version you were using before. It's not a big deal unless you go WAY out of your way to make it one.

I think 'pros' would prefer scheduled stability releases with regression soon after, so they know when to upgrade without beta testing. Rolling back is out of the frying pan into the fire quite often (without having to look for it). Classic example of this right now is the Z3TA+2 update. I wasted a few hours testing, adopted it as good and then found out via forums member that presets get garbled with existing projects. Now I (and probably most of us) need to dump it. So now I need to uninstall and install again Z3TA+2, the old version that suffers from stuck loops etc. This I suppose is entirely my fault?? I didn't test it properly as a beta tester? But if I knew a stability release was on it's way soon afterwards I might have not wasted my time. Regardless glad z3ta+2 is getting fixes thankyou cakewalk. Again stressing I'm not disagreeing with monthly release schedule.

...and I don't want to associate myself with Dave above until he makes calm points with evidence to back himself up. Prefer sensible discussions (well ever hopeful).

I'm uploading a video of what I was able to record with only 2 other tracks used right now.
along with this statement :
Cakewalk Sonar Membership program.
You sign up for a FULL year of updates, patches and other stuff and at the end of the year you can pay again and keep what you have and get more updates, patches and free stuff OR you get to keep everything from the previous year NO STRINGS. Well into my Membership and it’s (for the most part) clean sailing! Now with the last update “Speedy SONAR Kingston” this is what I get recording 1 guitar track with 1 XLN drum track. Bounced or live MIDI. I have tried 16 bit 24 bit ASIO and MME 32 bit on two systems! All give the same results! The Audio is being smashed out of time.
My computer is well within system requirements when I joined the Membership program.
Is it really worth being in a Membership program if the software out grows a 6 month old system designed to work with Sonar Platinum that seems to now is obsolete?
IMO 
 

Dave,
 
When you tried it on two different systems did you use the same audio interface device?
 
I've had issues like this in the past after an update. What ultimately resolved it for me was to uninstall my interface's device drivers, then reboot, then reinstall them, then reboot again. Also, immediately after uninstalling the device drivers, go to device manager, show the hidden drivers, then choose to uninstall any of your audio interface drivers that show up. Seems windows will keep older versions around that might gum up the works some. After that, reboot and reinstall the drivers. May not work for you but it's certainly worth a try.
 
As far as being upset, yeah, I get that, it's frustrating. Chances are, however, that there's something wrong with your system because many folks including me are using Kingston with no issues like the ones you're experiencing. I know that's not something you want to hear, but it's important information that will help us isolate the problem. People here will be very happy to help you resolve the problem if you promise not to yell at them.
 
PS: My system is over four years old and it Sonar blazes on it, so yours should just kill.