Well, since I don’t have gigs coming up for a while, I thought I’d risk updating to the Windows 10 Fall Creators Update, and as often happens with big Windows updates, Cantabile brought up the licence dialog. However, unlike normal, it wouldn’t accept my licence key any more. I had to get in using my password. Has anyone else seen this? Should we be worried?
Neil
If you’re trying to scare me because it is so close to Halloween here in the USA, it is not working! 
I’ve always used the password, so I didn’t notice anything awkward. Everything else is working very nicely. I’m shocked! (I usually experience at least one frustrating glitch when updating - not this time!)
Terry
This happened to me after I renewed my license. I had to use my password when I tried to install the successive build. I have Windows 7 though.
Ah, that might explain why I had a dialog when starting Cantabile on my music laptop after not having used it for a long time and after putting the newest stable build on.
The strange thing was I could not cut and past my license key into it, but when I typed it in manually it worked.
Interesting, I didn’t try typing it in manually…will try that if it happens again…
Neil
Hey Neil,
Just ran some tests here on Win10 Creators (is that different to Win 10 “Fall” Creators?) and everything seemed to work just fine. I’m running Windows 10 Pro v1703 build 15063.674
When you say it wouldn’t accept your license key - do you mean you couldn’t type it in, or that it gave an error afterwards?
Brad
I mean I pasted my license key in from Evernote, as I usually do, but it gave an error saying either e-mail address or license key was invalid. Switching to password mode worked fine. I wonder if there could have been some formatting or suchlike on the clipboard from Evernote, which made the password different from if it’s typed in raw?
I did the same Windows 10 Fall Creators Update on another machine, and Cantabile let me in fine with my license key when I typed it in manually. Not sure what would have happened if I’d pasted it it as I’d done before.
Neil
That was the response I had when trying to paste my license key on the latest build, but typing it manually was fine, which surprised me.
That’s really weird - I can’t think of any reason for that (and can’t reproduce it here either).
I thought it was as well. Only other thing I can think of is that the file I put the license key into was created on a Mac ( cut and paste key from email into that file on a USB stick) so was there some funny invisible white space or something? But I’ve used this transfer method before in Cantabile…
Something else I’ve noticed, which I think started happening with the Windows 10 Fall Creators Update, is that when I start Cantabile, my MIDI devices don’t seem to be working. I have to stop/start the Cantabile audio engine to get them to work. Anyone else seeing this?
Neil
Hi - I did the Windows 10 update. Ugh. Cantabile won’t open - the windows installer opens and then gets stuck. Any ideas??
I did the update the day before a gig (!) on my Surface 3.
I made sure Cantabile loaded up and checked everything was connecting correctly.
I’m using the Novation AudioHub and it was recognised by Windows and Cantabile so I assumed all was good.
Ha!
At the gig we didn’t have a chance for a proper sound check, just a line test.
My first note of the first song and I was two octaves and a tone out of key! (If it was just two octaves I could have coped I suppose, but I can’t transpose a tone on the fly!!)
Fortunately this was a guitar heavy song so I could drop out, and I frantically played around with settings, both in Windows and Cantabile.
I knew pretty quickly what was wrong: the sample rate had changed in Windows for the interface. 96KHz instead of 44100 (or whatever it usually is).
Windows was stuck on 96 and I couldn’t change it.
I switched to the onboard audio and swapped the audio cable (a couple of nice big pops for the sound guy to puzzle over!!)
Then, while playing the next two songs with a bit of latency, I was downloading and installing drivers from the Novation website, Googling “change sample rate in Windows” and frantically pressing buttons.
The fourth song was keyboard free, so I took a closer look. Realised that I could put Cantabile into 96Khz and found Novation’s own control panel applet to do the same.
Plugged in my headphones to the Novation and tinkered about a bit - and got it to work.
I was back to normal for the fifth song.
Nothing like a bit of drama to keep the heart pumping!
Moral of the story: test, test and test again!!
I’ve been doing more testing on Windows 10 here and haven’t been able to reproduce any of the described problems. However…
After I initially updated to Win10Creators, I did have several issues with Visual Studio (yep, Microsoft’s own product) and couldn’t get it solved. The only fix in the end was a complete fresh reinstall of Windows 10 and now everything seems to be working perfectly.
I suspect the Windows upgrade process has issues.
Brad
I just restarted Cantabile without the audio engine and it started up fine so far, so fingers crossed. Thank you very much!
That makes a lot of sense. I’ve been reading about the issues some have had with this Creators update. My current studio rig had the Creators update installed from first build so it wasn’t added later via Windows update procedure. I’ve had zero issues here with this rig running Cantabile and REAPER.
Well, I went for it- we’ll see. It did at least fix my Firefox issue on that machine.