Tom Riggs
If it is not recording sustain pedal at all check in the preferences under midi playback and recording to make sure that the to record controller is turned on.

HUZZUH! I found a solution!
 
First, thanks for the input everyone. The controllers were definitely on. It's was like Sonar saw the cc64 changes (as evidenced by the MIDI in/out monitor in the toolbar), but chose to ignore them.
 
I was working the problem with Synthmaster 2.7 - and as I was noodling with a pad, I could hear clicking when I pressed or released the sustain pedal.
 
I immediately loaded and switched to Serum. If you've never used Serum, apart from being sounding beautiful (if CPU heavy) it has a brilliant interface - you can see any changes that are happening. I loaded another pad in Serum...and lo...the sustain pedal now changed the resonance...yes, the little control knob was flipping back and forth. I opened up the ACT controller and there was the answer: the pedal was mapped as a switch (S7). W. T. H.?
 
I reloaded my keyboard profile (Akai MPK88) and voila...I have a sustain again.
 
Thanks for your patience and input everyone.

Hi Everyone SOMETHING IS VERY WRONG
 
Loaded my project which has loads and loads of tracks including Sylenth and the db meter sky rockets to maximum on sylenth and master ,
 
Reverting back to JP has fixed this problem > none of the previous updates every did this .
 
I uninstalled kingston re downloaded it and the same thing UNUSABLE For current project Major problems WITH VST Sylenth and who knows what else
 
ANYONE ELSE ?????
 
 

Yes, I've already read that Sylenth1 doesn't work in Kingston.

I've noticed Kingston spreads the workflow more evenly to different CPU's/threads with Steven Slate Digital plugins. They used to pile mostly on thread #0 earlier.
 
Am I just imagining things?

Jyri T.
I've noticed Kingston spreads the workflow more evenly to different CPU's/threads with Steven Slate Digital plugins. They used to pile mostly on thread #0 earlier.
 
Am I just imagining things?

Nope, check page #5 of the Kingston ezine release under "streaming" (I'd post a link, but I don't think it'd show since I haven't posted enough.) Along with the JP optimizations, the added ones in Kingston were bound to show a noticable improvement in lower CPU load and improved thread management.

yoosookim
Has anyone tried Sylenth1 with this yet? I get incredibly loud white noise in the left channel and heavily distorted playback in the right channel. I tried other VSTs, and those work fine. Very frustrating and unfortunate as I use Sylenth pretty regularly.

I have exactly the same problem yoosookim. I found the only work around to be record and edit the midi track for Sylenth as usual, then activate record on the Sylenth output and record the midi playback realtime. A bit slower than fastbounce but works perfectly. Pretty glad we recently got that feature as I too use Sylenth often.

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.

A good friend of mine writes plugins. His take on the plugin problem is that often in the development cycles the programmer/devs come to a point where they can take a shortcut or do everything by the book. The ones who take a shortcut because "we don't use that," or "our users don't use that," often leave gaps in code - where the DAW is expecting one thing, the VST just tries to skip it. Consequences vary, but he says "the ghost in the machine" (unforseen, or unintended new issues/relationships in code) are always an issue - but good coding practice can avoid a myriad of problems.
 
Which makes me wonder if some of the Kingston optimizations weren't actually shortcuts that are now the root of unexpected problems. By which I mean, the shortcuts/optimizations in Kingston may be perfectly good...now we're just being introduced to otherwise dormant shortcuts the VST devs took. *shrug*
 
I had some weirdness with Kingston, but I've now got it narrowed down to just one misbehaving plugin - the VST2 version makes noise, but the VST3 version is fine.
 
All that said, the speed increases are impressive. CW seems to be getting everything right...Kingston is hopefully just a minor bump in the road.
 
My only aggravation in all this is that CW drops a huge update the day before Thanksgiving, and then close shop for the long weekend. I wouldn't want to see their inboxes/trouble tickets/voicemails on Monday. ;-)
 
(And Happy Thanksgiving)

This is what may be happening in some plugins not working scenarios.


In this order:
a) Before Ipswitch Sonar was not processing mono interleave correctly with VST3 plugins.
b) Various plugins had code to work around that issue (a), or somehow their code managed to bypass the problem.
c) Ipswitch fixes the mono interleave issue.
d) This breaks plugins that had that workaround code (b).

Now plugins need to be fixed to strip out that workaround code (b).
OR maybe there is a regression bug with (c). Who knows... Cakewalk can confirm.
 
I mention mono-interleave because cakewalk has mentioned that before as a possible problem.
 
Cheers...

For some reason I have an old version of VST scan in the Kingston download package. In JP it was 5.9.0.40 but with Kingston it has changed to 5.3.0, an older package. It seems to my tiny brain that this older scan version doesn't like Kingston. I just installed 1 new plug and the VST scan said 88 removed and 66 added. Nonsense.
 
Noel and co. know that something's going on and I'm sure that it will get sorted after the US holiday. FIve stars for the Cake crew because even at this time of family and celebration they've been sending me pm's about the issue and I can't ask for better care than that.