abacab

46 minutes ago, Rod L. Short said:

Is there any way to get my old Sonar Platinum back??

Cakewalk Command Center. Same as it ever was...

23 minutes ago, Larry Jones said:

Where do I look to find out which releases are which, and when a targeted release turns into a broad release?

I don't have a handy link to that specific info, as that appears it is always a moving target. There are a few blogs that cover that info as it becomes available. But here is some related info.

I believe you can set Windows 10 Pro to defer until the semi-annual channel (broad release) is available.

Windows lifecycle fact sheet

https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet

Search product lifecycle

https://support.microsoft.com/en-us/lifecycle/search?alpha=windows 10

Quick guide to Windows as a service

https://docs.microsoft.com/en-us/windows/deployment/update/waas-quick-start

The Matrix is a workaround for looping a clip along with your project as you have described.

But a couple of other methods just popped into my head.

1. You didn't mention what instrument you were using for the ambient synth sound. But if it is actually a synthesizer maybe you could adjust the ADSR envelope for a continuous sustain, until a note off message is received by MIDI. You had mentioned it was fading by bar 4, and that is most likely due to the envelope in the synth. Now if it is a sample based synth, you are limited by the real length of the sample used, and it cannot be extended  indefinitely on playback with only an envelope.

2. Otherwise,   you could record a sample of the ambient synth playback into an audio track. Then  you could import that audio clip into a sampler. In the sampler, set the loop point and use that to repeat the part you want as long as the note is held. Use the sampler plugin in place of the synth with the ambient patch. If you are careful with the zero crossing at the loop point, you should be able to eliminate glitching as it loops.

https://www.tx16wx.com/

29 minutes ago, kitekrazy said:

 There's always hope MS will mess that up too.   I think I'd rather go back to buying an OS and getting services packs.  The DAW user is never 100% safe from the evoling OS in the Windows and Mac world.

You could always spend your life forever tweaking Linux hoping to get a stable functioning DAW out of that instead! 

1 minute ago, kitekrazy said:

 Some truth there and this time they didn't mess up my home network requiring a roll back.   One system jumped from 1709 to 1809.

 Only XLN and recently Audiomodern Riffer had issues.  At least XLN you don't have to contact support. If it were other software it be days reauthorizing crap.  Software with no machine limits don't seem to be bothered.

That's a big +1 for my iLok License Manager protected plugins. Same for Waves!

They take a Windows update in stride, and keep on rockin!

20 minutes ago, kitekrazy said:

Just a reminder that they haven't a clue how to protect your authorizations from Windows upgrades.

Or maybe MS just doesn't know how to upgrade Windows without changing the PC hardware ID?

I just launched Command Center and these loop libraries are still showing up for me:

Big Fish

Loopmasters

Sample Magix

X-Mix

However the Big Fish libraries are the only ones that will download and re-install OK.  Just tested a re-install with Big Fish Urban Loop Collection.

I just get a "did not complete" error for Loopmasters, etc. when I try to install them.

7 hours ago, sealesb said:

Sorry I think we need to clarify this, "and has nothing to do with the user ID". Lets leave the Microsoft updates out of  the equation for the moment because we know they can cause this type off issue as abacab correctly stated. Changing from a Microsoft account to a local account most certainly can cause this issue of plugins needing to be registered again also and it all depends on whether you installed your VSTs under a Microsoft account or a local account in the first place I think! It is to do with permissions.... a mind boggling Windows invention.

Note this: A day or two after the latest update, switching from  a Microsoft account to a local account disabled our copy of Addictive Drums instantly on the studio PC along with a couple of Izotope plugins. Just re register them and we were fine. These same plugins worked fine after the update with us. It was changing to local account which de-registered them.

So all we were offering here was another reason for plugins needing to be registered again. It seems Windows update caused the original problem for dotonemanband and that's fine as he has it sorted now. But.....what we found was another reason for this issue and it should not be so easily dismissed, with all due respect to those who have posted on this, as it may sort the issue for other people. After all we are trying help people sort problems and all "cures" should be taken into account.

 

The topic at the top of the page is "Windows update changes". and the OP had stated that he had just updated prior to their  trouble with authorization.

The context of my statement here was meant to be taken in relation to the current thread, not as some global rule.

I was not dismissing your suggestion,  but it didn't directly relate to the OP's stated issue.

Your observation is interesting, and that info will certainly  be useful in a broader context for troubleshooting plugin authorization issues. But I truly doubt that many folks are frequently switching back and forth between local and Microsoft accounts.  Although, as you have obviously experienced, it can happen.

All good here with the update!

I believe Meng even made a comment somewhere over on the old forum, that there are no current plans for further developing scripting in the new Cakewalk.

8 hours ago, John said:

I have always updated going back to the DOS days. With Windows 10 Pro I seek out updates and am happy to get them. I look at is as Windows being constantly improved and made better. Bugs are address. New features are added. Soon we will be getting a huge increase in how many plugins can be loaded. 

For more information on this read this FLS Slot Limit Increase.

 I find with every update Windows gets better. Problems get resolved and useful features are added. The notion that these updates are intrusive or a burden I find untrue. Staying current is a good thing to do. Freezing ones OS so that it becomes out of date makes it harder for developers to update their applications to take advantage the new  abilities of the OS.  MS tries to keep as much compatibility as is possible. But there is a limit to how this will impact future improvements and greater security.  We are not paying for all these updates so I can't see a downside. 

While it is generally good to be up to date with quality and security updates, Microsoft QA testing has been lacking with Windows 10 feature updates in the semi-annual channel (Targeted) major version updates.

MS releases the newest release with a "Targeted" designation. This is generally what you will get if you do nothing to defer feature updates. This is the release that business IT teams need to pilot and test with, before they actually begin broad rollouts within their organization.

After a period of time based on business feedback and any necessary bug fixes, MS will designate the update as ready for "Broad" release, and this is when the update is "ready for business".

So depending on what you use your PC for and how critical it is for you to avoid any disruption, you may want to take a cue from the IT pros that do it for a living, and wait until the update has been fully "baked".

If it is just a hobby, and you make good backups, it is probably nothing to be too concerned about. Just be aware that you are a virtual beta tester for roughly the first 6 months of a new release, until it gets the full designation of "semi-annual channel", ready for broad deployment.

Deferring the major updates for 6 months seems reasonable to me, given these facts of how Microsoft is operating these days.

Quote

Targeted deployment refers to the phase immediately following the release of a new Windows version when it is recommended to conduct your organization's piloting process and to begin deployments to select devices, such as those with the most modern chipsets and capabilities. Surface devices make excellent candidates for these targeted deployments.

Broad deployment refers to the phase that follows targeted deployment, where your organizations' pilots and targeted deployments have provided successful feedback and Windows has been vetted for deployment to most or all of your organization's devices.[/quote]

8 hours ago, SomeGuy said:

1. Not possible on Windows Home. Can only defer (not disable) on Pro (feature updates for a year, and a month for security uodates).

Yes, you CAN disable updates for as long as you want on Pro. You just have to know where to find the policy and how to configure it.

HINT: What I am referring to isn't found in Windows update settings, where you can set the deferral. It's a specific policy found in the Group Policy Editor [Configure Automatic Updates].

I don't have Omnisphere, so can't really compare these two. But I do have Syntronik. And there is a free version of Syntronik available with 50 free presets that can give you an idea of what it is like. But with Syntronik you are just getting classic analog synth sounds. https://www.ikmultimedia.com/products/syntronik/index.php?p=versions

Syntronik is a large sample library of iconic analog synths that have been meticulously sampled to recreate the best analog sounds from vintage synths.

Omnisphere should give you access to a much broader sonic palette, including many other types of synthesis besides analog subtractive. So I can imagine that they are not even close by comparison.

Riffstation is a handy tool, and well worth the price. Grab it before is is gone!

I had originally purchased the paid version, but grabbed this one as soon as it was released as freeware. No serial required!

It should continue to function, as is until ...

I agree there's probably no point yet in tackling control surface issues as long as the basic keyboard MIDI isn't cooperating.

The intermittent nature of the problem is strange. If it was as simple as a Cakewalk setting I would expect it to either always work, or to always not work.

Definitely check out those keyboard ports that were just mentioned above, in case that is messing with Cakewalk. You might also have an internal keyboard setting for that controls which MIDI messages (keyboard or control surface) get sent to which port.  I have a Roland A-PRO keyboard that gets configured like that with two ports in Cakewalk.

Maybe another owner of your keyboard model will see this and chip in.

And if all else fails, maybe try a clean uninstall/re-install of Cakewalk? http://forum.cakewalk.com/FindPost/3802014

Good luck!

I have had this happen several times while using a local Windows 10 Pro account.

This is an issue with the computer hardware ID (fingerprint) being changed, and has nothing to do with the user ID. This makes it appear as if you are running on a different computer than that which was used to originally  authorize with.

Normally your hardware ID should only change if you have swapped some hardware, but unfortunately the major Windows feature updates do this as well.

Maybe these will help?

Moving and copying clips

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Arranging.17.html

Working with MIDI clips

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Tools.24.html

The Piano Roll view

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingMIDI.03.html

2 hours ago, Jake Diamond said:

The MOTOR appears as a MIDI Device (in Preferences) and shows up as a selection for routing in the MIDI track, but it only triggers a VSTi from time to time (I click on the track number and it sometimes works) and only records MIDI data from time to time. Then I go to another DAW and it works normally, playing and recording. It seems that the keyboard is not intermittent in any other app and I think the keyboard is working normally.

A MIDI keyboard can always be used to send MIDI notes to play virtual instruments, and record the note data into a MIDI track without issue. Just ensure that the input device is selected and recognized under MIDI device preferences and at the track input, and MIDI input echo is selected correctly.

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Playback.35.html

6 hours ago, synkrotron said:

Update:-

https://uk.pcpartpicker.com/list/z9X3J8

(budget has flexed slightly)

Wow! Just checked the pricing here in the US. It's listing at $2,176 USD for all that. Looks like a solid build! 

Virtuoso Ensembles for Kontakt Retail https://www.kirkhunterstudios.com/products/virtuoso-ensembles-kontakt-retail/

Due to popular demand, we have fully run out of Kontakt Player licenses for this title. We have decided to discontinue the Kontakt Player version due to the exorbitant costs of getting more serials from native Instruments and we are now releasing this title for Kontakt Retail.

Thanks, Everett! Good to see you around here. I discovered Fathom Pro last year, and have become a fan! Nice machine!

The Matrix view can loop clips. But the main transport will loop all tracks in the track view between the loop in/out markers. So in that context it isn't possible to loop just one track in the track view, without looping them all.

Major Windows feature updates will change your computer ID, so anything that relies on that may need to be reactivated.

I have a GTX-950 in another computer (non-DAW) that plays some older games just fine. Anything less than that will barely be better than the integrated stuff these days.

I would definitely stick to the 10XX and up series for a new GPU.