Robert Bone

Anything from Craig is a bargain at any price.

Perhaps USB Selective Suspend got reset to on, under Advanced Power Plan option. Also, check Power Management on connected devices.

YAY YAY YAY - Vlada - you have THE most amazing luck at discovering the strangest errors ever. Glad you are back in business. I may not solve much for you, but years back, when we built your new computer (back then), I made you a promise that I would always help you, the best I could. Folks are only as good as their word, and as long as I am on this planet, I will do my best to honor that promise to you. ROCK ON! (I have ZERO idea why what you did fixed anything, but who's counting?)

I hope this path is fruitful. Best wishes for a good outcome.

Sorry - didn't catch the XF, rather than XS, in my typing. You can see the associated driver file paths and names, if you go to Windows Device Manager, and double click on the current driver in the Sound, Video, and Game Controllers category, to bring up the driver Properties, then click on Driver, and then Driver Details, to see the full path to the driver(s) for that device. Then, you can navigate to that location, and copy those files off to somewhere else. Some folks rename them. That way, you can always restore them or rename them back to their original name(s), if you had renamed them. Bob Bone

I always just use 'V' to toggle on/off the video display. Bob Bone

Might want to edit your 1st post's subject to show "Solved". Helps others skip reading trying to help, for them to know this is figured out. Bob Bone

Good idea to edit the 1st post, subject line, to add "Solved"

Assume you did this after factory reset: Connect via USB Connect the Motif XF to your computer via USB. Set the Motif XF to MIDI IN/OUT = USB Press [UTILITY] Press [F5] CONTROL Press [SF2] MIDI Set MIDI IN/OUT = USB Press [STORE] to write this to your Flash ROM And, this appears to be latest driver, for 64-bit Windows: https://usa.yamaha.com/support/updates/umd_win64_kbd.html

You can copy/rename old driver first, as a precaution. Don't know if compatibility-mode available in Properties for a driver_ might be worth checking out, as well. Bob Bone

THANKS, LARRY! It instantly brought me back to the days after my 1st divorce, when my entire rack was filled with nothing but spacers, like my bank account.... That sound - the lonely and haunting sound of nothing.... PERFECT recreation! I downloaded the documentation PDF, and it was a file of zero length - VERY quick read, got me up to speed on the plugin, in no time at all. Bob Bone

Hey, Vlada - do you possibly have either a different host (alternate DAW, for example), or alternate computer, or even just some stand-alone synth, where you can see if the Yamaha is able to generate and/or respond to midi, outside of CbB? Just trying to isolate where the issue is - is it with the Yamaha itself? With CbB?, Possibly with Windows? If you download and use Midi Ox, is midi activity being detected by Windows? (Midi Ox will show you any midi messages coming across in Windows - handy free little utility - download it at: http://www.midiox.com/ and the download link is towards the bottom of the page - the link is yellow). Any chance you were naughty this year, and Santa is giving you a midi lump of coal? Bob Bone

Hi Vlada - In the steps you listed, in testing my theory - You did not indicate you had added the Yamaha back as a midi device, after you had removed it and restarted. Because you had removed it and saved with it removed, you need to add it back in, in order for it to be usable. Bob Bone

From the documentation: Recycle Plug-In Windows. By default, Cakewalk recycles the currently-open plug-in window when you open a new plug-in UI, and all previously open plug-in windows are closed. This prevents Cakewalk from being filled with numerous open plug-in windows, and you don’t have to manually close plug-in windows that are no longer needed. If you prefer to always open a separate window for each plug-in, clear the Recycle Plug-In Windows check box. To toggle the current behavior, hold down the CTRL key when you open a plug-in UI: If Recycle Plug-In Windows is enabled when you hold down the CTRL key to open a plug-in, all other open plug-in widows also become pinned. If Recycle Plug-In Windows is disabled when you hold down the CTRL key to open a plug-in, all other open plug-in widows close, and the new plug-in window is unpinned. You can also pin individual plug-in windows so they remain open when you open another plug-in window. To do so, click the Pin Plug-In Window button on the plug-in property page. Pinning windows is the only way you can have multiple plug-in windows open simultaneously. Note: Plug-ins that are docked in the MultiDock are not affected by the Recycle Plug-In Windows setting. Docked plug-ins are automatically pinned and cannot be unpinned. To dock a plug-in window, hold down the CTRL key and drag the window to the MultiDock. Note: Plug-in window recycling is disabled when loading projects, which ensures that projects open with all previously open windows. Bob Bone

Hi, Vlada - I have downloaded some software code from Microsoft, and elsewhere, with which I intend to build a little utility to try to address the issues I was describing earlier in this post, but it will take me some number of days to do the research, coding, testing, etc., of that. In the meantime, when time permits, I do look forward to your trying my suggested set of steps, to see if indeed you are dealing with what I call the "Windows internal reassignment of USB device to port mapping" issue. (I might think of a better term for the issue at some point). Anyways, I hope if you are experiencing this issue, that following the steps I had posted fixes the issue - even if just temporarily. Bob Bone

If you click on the question mark in the upper right of the window, it opens up a panel where you can adjust all kinds of things. Edited - @Canopus has it right. I was in the doctor's office when I first posted, and my memory was a bit foggy. Sorry about that. Bob Bone

Could be their servers are getting hammered on the holidays - it took me several hours to be able to download the free plugin from NI this year, but it eventually worked. Bob Bone

Vlada - I believe when the midi devices are removed from Preferences, those changes Applied, then save and close and reopen, CbB picks up the new internal identifier for the midi controller, so when you then add that keyboard back into the Midi Devices, and hit Apply, it has the proper identifier associated with the keyboard - in its new port location (internally), and that should make it work, IF the issues are from the internal reassignment I am speculating is causing your issues. I am eating lunch, followed by a nap, and then I will begin using a couple of utilities I downloaded, one from Microsoft, and another from a developer, that lets me inspect detailed info on what USB devices are connected, and which ones are in which ports, etc..... I am in search of a PERMANENT solution to the issue of internal reassignment of USB devices / ports, so that this issue can get resolved whenever it pops up. I will let you know how my efforts go, as I too have this issue, and as a developer myself, I cannot stand when stupid coding logic messes up my day. Bob Bone

I suspect that since Vlada had indicated gear had moved from one location to another, that perhaps the USB cables didn't end up connected to the same devices/ports. Could be wrong - just think that is my best guess on what is happening. Bob Bone

1) Possibly mismatch on midi channels, between the keyboard and the track? 2) While the above may be the cause, I think the following is my guess for most likely scenario: If using USB cable to connect external keyboard or controller, if any of the plugged in USB cables - to the computer - have moved to a different port - (and it does not even have to be the XS that got plugged into a different USB port - could be any of the devices plugged into any of the USB ports on the computer), so for some @$(*@$&(*@$&& reason, Windows reassigns its own internal table of what is plugged into what, and Sonar or now CbB, can show the device names as being valid declared and selected as active devices in Preferences > Midi > Devices, but underneath - internally - that device had been given a new connection identifier by Windows, and you would never know it by just looking at it. SOOOOOOOOOO - you can try to get everything plugged back into the ports, the exact same way they were before, and that should clear up the issue, OR you can: Load up your project, and go into Preferences > MIDI > Devices, and remove the check box for the XS, then click Apply, save the project, close the project, open it again, then check the box again for the XS as a MIDI Device, and click Apply. IF the above is why it was not playing, then these steps should result in it properly playing again. Please note - I am NOT an expert on the internals of this situation - I just (and most of us) have learned the hard way, that moving ANY USB devices to different ports makes for unwanted chaos with external midi keyboards/controllers being able to be properly recognized in projects where those devices were present but subsequently managed to get internally reassigned by Windows. Additionally, I have been dealing with this ^&)@&)*&@& situation myself, for about a month, and I have not yet figured out how to stop this from having the same issue, over and over, even though no cables have been moved after an initial movement of a different device caused the issue a first time. In other words, I KEEP having to do that same process, of removing my midi controller as a midi device, saving the project, reopening it, and adding the controller back in as a midi device and saving the project. Every single time I open the project again, I have to go through this. Driving me NUTS. SO - even though I cannot offer you a permanent solution, at this time, IF this is what is causing your issue, then at least by doing the above steps, as I explained in the 2nd paragraph above, hopefully you can at least be able to again use the XS. Please note: If you go into Windows Device Manager (right-click on the WIndows Start Button and click on Device Manager), you can view the presence of what I call Ghosted USB devices, by going to View, and clicking on Show Hidden Devices, and then expanding the device category Sound, Video, and Game Controllers. Any devices that are listed, that are lighter in color - like a pasty white or grey, those are for devices that are there but that had gotten internally reassigned. So, if my controller shows up twice, once nice and dark (and active if you look at properties for it), and has a 2nd, or 3rd, or 4th, additional entry that only shows up when I have the Show Hidden Devices option selected under View, those additional entries indicate that those are not current driver entries, and it is a confirmation that somehow, a USB device ended up in a different USB port, and it caused an internal reassignment. I usually remove those Ghost entries, by uninstalling them, as they are no longer what is being used. Maybe there is some kind of way to get this all sorted out once and for all, and if anyone knows the secret to that, PLEASE PLEASE PLEASE jump in and enlighten me, because thus far, I have been unable to figure out how to do it. Bob Bone

Hey I may have missed seeing it - when does this super deal expire, for grabbing the whole set of samples? Will it still be available come this upcoming Monday? Thanks, Bob Bone

I found this one, 64-bit: https://freepiano.tiwb.com/en/ Will try it out in a bit. Thanks again for you guys jumping in to help me out Bob Bone

Thanks - I am looking at a 64-bit plugin on KVR. I will still let tech support know of the error in their auto-sizing logic, in case they want to fix it, now that folks the world over are starting to snag giant HDTV's at remarkable prices. I saw a 55" Ultra High-Def HDTV from Samsung (I think) for less than $300. a 4k Smart TV with a built-in HDR, for less than $300 - wow. Anyways - I will see what I can find that will work. I figure a good 2 days of testing out all of the new plugins, and sounds, etc.... so this will be well worth it. Bob Bone

That also seems to run stand-alone fashion - I will give it a whirl, in any case. Bob Bone

64-bit?