mettelus

Yes. When you open the PRV, it lives in the Multidock, which can then be undocked and moved to a second screen. The link above explains how to undock it.

As someone who doesn't really own much orchestral content, this was a good opportunity for me to jump into something of much better quality. I may also not use it a great deal, but it is significantly deeper in content than I was expecting. I have never been a huge fan of Kontakt's GUI, but quickly forgot what player I was using once I jumped into the library. It is definitely a nice library, and since I have nothing to really compare it too, I won't have anything to complain about. ?

Due to common components between programs, it is recommended to install them chronologically. Also bear in mind that CbB is 64-bit, so getting too attached to "older" may be a frustrating or even futile venture, depending on what plugins you are focused on. When I built this machine up, I installed everything from Cakwalk Command Center, then CbB. If you want V-Vocal, I would do that first, then CCC, then CbB.

You may also have core parking enabled, which is a Windows thing. I just tried a quick Google search for disabling core parking and am coming up with Registry changes to achieve it. I forget offhand how to access that in Windows 10 without having to drill into the registry (some are not comfortable with editing the registry). Since you are on a laptop, that update may very well have enabled core parking on you. Core parking allows cores to drop to a 0% use state, which will be counterproductive for DAW use... BUT you also never want to run as a DAW unless plugged in (another reason it is used is to conserve power). *If* you are comfortable editing the registry, you can Google "how to disable core parking in windows 10" and the first video that pops up shows this and the key to search for.

I went back through my email to find this, and I actually backed all the way out to MixControl v3.4. Tech support sent me a direct link to their cloudfront storage for 3.4, which is still valid, but I cannot remember if the PRO 40 and PRO 24 were apples-to-apples (but believe they were, HOWEVER, mine is first gen). Check with them on this first... Tom Harrington was the one who finally resolved this for me. Below is the email from 6/13/2018. Be sure to validate the compatability and back out of the current installation before installing a different version. "I believe the issue you are describing may also be resolved by cycling clock source and sample rate as well as firewire buffer size. To my knowledge this is present on Windows as well as Mac. You cna resolve this by using 3.4. I think the reason 3.4 did not work for you is not firmware relate dbut is in fact related too the driver. Please follow the steps in this article to fully remove 3.7: Uninstalling Scarlett MixControl from a PC And then install 3.4: https://d2zjg0qo565n2.cloudfront.net/sites/default/files/focusrite/downloads/20454/saffire-mixcontrol-3.4.exe Best regards, Tom Harrington // Focusrite Technical Support Engineer"

Windows Task Manager is looking at the system level, and CPU 0 is the "workhorse" of any Windows system, since every system has a Core 0. IIRC, Cakewalk was change a long time ago so that the CPU usage reflects only what Cakewalk is using, so that should be balanced fairly well... however, not all VST(i)s can be shifted from Core 0. If the system loads Core 0 with that project running in Windows Task Manager, you may want to try dissecting that project by first doing a "Save As..." to a new name (be sure to do this step so you have the original project intact), then removing VST(i)s and/or archiving tracks from the copy to find the CPU-hungry ones. Unfortunately, there is no definitive list of these, and no way to monitor them from within Cakewalk, but I believe that was a feature request long ago on the old forum. *If* you get into a situation where you need to bake-in VSTis, the "Save As..." feature works well, allowing you to bounce to track(s) and archive the original tracks so that you can work with only audio for the ones that are completed. The original project files should be small (sans unbounced Melodyne edits), which will let you back out of an archiving situation cleanly (there have been reports of un-archived tracks losing settings in the past, so play that one safe). Since I mentioned Melodyne... also check if you have unbounced Melodyne edits (project file size being in the MB+ range).

Open Console View and check the Master buss for PC channel and FX. If all sound is gone with FX enabled, it would seem you have an FX on a buss (if you created any), or on the Master itself.

Updates can re-enable things that were previously disabled, and the Wdf01000.sys issue is commonly linked to "Automatic Network Discovery" which basically pings for Wi-Fi devices in range every 3-4 seconds. There is no reason to have that enabled... if you want to connect something, it is safer to manually search for it and connect it. To disable, go into "Control Panel->Network and Internet->Network and Sharing Center->Advanced sharing settings" (on Win10) and select "Turn off network discovery" in both the Private and Public sections. This does not disable the network from functioning, but disables it from constantly pinging.

For your Saffire, I had an almost identical issue when switching to Win10 with my Saffire PRO 24 DSP, and solved it by rolling the MixControl back to version 3.6. I was incorrectly led to believe that a firmware update required version 3.7, but then couldn't get rid of it. On Win10, not only must MixControl be uninstalled as a program, but is also must be removed in the Device Manager (since it is seen as the driver there). At that point the older version of MixControl could be installed.

Glad you found it. The "Enhancements" tab was 5th tab I couldn't remember... it is not present on my Win10 machine, and I do not miss it.

The ADSR Sample Manager post is already halfway down page 2 because Larry floods this forums with deal posts. ? If I don't chime in on something as it flies by, it'll scoot off the radar so fast that I forget to find it again later.

Nah, you are good. There is always someone lurking around. There are three things to check to find your issue, but if Windows Media Player and VLC sound the same, it is probably in #1 or #2 below: Windows level - Type in "Sound" in search bar and open "Sound (Control Panel)." Select the Realtek (or whatever the default device is on the Playback tab) and "Properties." In that pop-up, go to the "Spatial Sound" tab at the top and make sure that it is set to off. Also, on the "Advanced" tab, set the default format to something reasonable (I use 24-bit, 44100 Hz (Studio Quality)), and check that both "Exclusive Mode" options at the bottom are unchecked. I seem to remember Win7 had a 5th tab at the top, and think it was for Dolby FX, which you would also want off if it is there. Basically, check all of the tabs in that pop up for any audio effects. Realtek - There is a version of Realtek HD Audio Manager (or some such) that I *think* could also be accessed via the "Configure" button on the Sound (Control Panel) -> Playback tab after selecting the Realtek. If you have that installed, it should come up typing "Realtek" into the Windows search box. This is not on my Win10 machine, but if you can access that (have it installed), I know there were also things like "Speaker fill" (essentially fake surround sound), and the Dolby FX there (playback environments like "Bathroom" and such). Disable those if you can access. VLC (this is most likely not your issue, since you get the same results on VLC and WMP) - For VLC specifically, the mixer stuff is in the "Tools->Effects and Filters" if you open the application (I opened it without launching a media file). Go through each tab of the "Audio Effects" and make sure that none are enabled. Check those first and see if that helps, and can go from there. #1 and #2 above are the ones that will affect you at a system level.

Reminds me of when something fails on you repeatedly until you try to show it off to a spectator... as soon as you grab someone to "come look at this," it then works without issues.

Good point, my apologies. Trying to up the ante only undermines your request. Plus, I broke the unwritten "3 posts before derailment rule"... two faux pas in one go! (Ouch)

Good plug for an "Arranger Track" (and all the associated Ripple Delete drag/drop goodies). I would much rather read what the section is in nice bold colored sections with big text, and when moved have it look identical. When moving things with markers, the markers themselves could either mask or be masked by the adjacent sections (and marker text is rather small).

I have mentioned this a few times and not seen it refuted yet, but some issues that seem to be off by 1 come across as indexing errors to me. Depending how encountered errors are resolved, and indexing error could default itself to reset whatever it is trying to instantiate.

Which driver mode and buffer size are you using? Driver mode and sample size can also be playing into this. If using Windows audio/Direct Sound/MME, low buffer sizes can insert hums, a little higher will insert pops/clicks, and higher (256+) are where VSTis begin to playback correctly. Some need up to 8K depending on the VSTi and driver mode used.

I may be oversimplifying this, but historically MIDI notes on the first beat were prone to be missed. As a result, many users start songs on bar 2 (or 3). Because that first bar is empty, there is nothing stopping you from partially filling it. Yes, there will be that blank space at the beginning, but you can set the now time there, or jump around the project via markers (need to assign keyboard shortcuts, but they are available).

Do you have a music shop near you that you can try things hands on? That would be ideal, even if a day trip, since there is so much variation between keyboards/controllers that come down to personal preference. I do not own the Modx6, but it seems it has a good deal of sound editting internally, so is hard to imagine running out of sounds. Plus it will double as a controller (there are free VSTis to play with if you look around). When you do buy something (whatever you end up choosing), be sure it is from a place with a liberal return policy. Just in case you change your mind after you get to truly use it, you will want the ability to adjust as painlessly as possible.

Therein lies the issue. Windows Media Player has a truckload of sound enhancements internal to the program. All media players have some sort of mixer to my knowledge, so in addition to Windows itself, each program would need to be checked. The export from Cakewalk will reflect the options of the export dialog, so if a media player sounds differently, check the settings for any mixers or sound enhancements. Based on your issue, it seems they are engaged in your media player.

Check your Realtek quick... "Sound" in Control Panel... then select the Realtek and "Properties." In that pop-up, go to the "Spatial Sound" tab at the top and make sure that it is set to off. Windows has internal FX chains (basically) that are accessible to programs that will color the sound coming out of the system. Some programs also have these internally (I believe VLC does), so you can also check them there... mixers, ambient environment, speaker fill, and other DSP effects. You want to check that those are all either zeroed out, or off. Bear in mind, that someone listening to your music is doing so in their own environment; so even though you may have them off, they may have them on.

The concept is interesting, but it seems to negate the rest of the signal chain. I have never been a fan of active electronics (but also not sure what that battery is for) in a guitar, but admit I like switches, and one set of pickups that are clean with proper dynamics can be sculpted during processing into most anything. I never saw the initial mention on these, but checked prices... New are $4000, used $1500, and seemed to be a lot of used ones about. The price difference doesn't make sense to me.

+1 to the above, 700 tracks is a lot and I presume that also includes a fair number of VSTis. I would recommend saving the folders mentioned above as track templates, then inserting them strategically into blank projects (by synth is a logical approach). Massive project templates can cause undue strain on a system, so it is better to use track templates as building blocks, then bounce and archive as needed for system performance. Also bear in mind that all VSTis are not scripted the same way, and consume resources differently. No DAW can control this; it is up to the user. Even the most powerful system will fall to its knees if loaded with enough "CPU hogs."

Max, that recipe would be worth shooting Noel a PM about. To my knowledge there has never been a recipe to reproduce this issue, but a recipe to prevent it might be just as helpful.

Right click the MIDI file and choose "Open with..." and then Cakewalk. This will import the tempo map, and if no MIDI output is assigned in Cakewalk preferences also insert TTS-1 and route the channels. Importing a MIDI file inside Cakewalk will strip off this data. I am not sure if the tempo information can be copied directly between projects though, so hopefully someone will chime in to that specifically.