mettelus

Melda's installer does allow the option to install VST3 only (so you can re-install them and check only the "VST3" option); but I am in a weird situation that Adobe Audtion 4 only uses 32-bit VST2s. To that end, I just submitted a Feature Request to Melda to add a 32-bit/64-bit option to their installer. For me, this would allow installing 32-bit VST2s (CbB would not see them since they are outside the scan path), and 64-bit VST3s. From CbB's perspective, similar could be achieved with a Feature Request to exclude select VST paths (i.e., subfolders), since Melda installs them by default to a subfolder at the VST2 path location(s).

Yeah, the jack grips the plugs better for sure (5 contact points versus 2), but is not that tight. The sleeve also has tigher tolerances and seems longer, so you cannot just jam a plug in it and hope for the best (it has to lined up fairly well). However, this might be a concern if the jack is mounted to plastic or if the plate isn't on a rigid surface, so that is something to keep in mind. This is also for something that would get motion or tension on the cable, so would be overkill on static equipment that never gets a cable pulled. The one niggle I do have with it is that the nut size is just slightly bigger than the one I took out, so I cannot use the old ones as a spacer. I had the old jack double-nutted to make it perfectly flush to the mounting plate, but this new one sticks out 1/8". It didn't come with a second nut to use under the mounting plate. I only got one jack, so not sure if this was a packaging error.

Now I know why dance music makes me want to wet myself!

This little beauty is worth an honorable mention, since it is cheap, incredibly effective, and properly engineered. "Traditional" output jacks consist of contacts at the sleeve insert, and a single prong to engage the tip such as this one. The issue with this design in that weakening of the prong and/or tension on the cord can result in intermittent loss of contact. After experiencing this last weekend (on a 35 year old guitar jack) and a little searching, I found this guy which came yesterday. I am not sure exactly when these hit the market, since they are "patent pending," but both the tip and sleeve are gripped by two prongs inside the jack cavity. These actually snap into place with some force, so will not let go or lose contact (without intent) in most cases. They also come in long barrel and stereo versions, so they have more applications than just for guitar. Even testing an Xvive U2 wireless transmitter, the fob on that requires a little force to even spin it in the jack. I wanted to pass this along to folks who might be interested. For $6.80 (eBay was cheapest) and a couple of solder joints, this is an impressive "upgrade" for any instrument needing love on the output jack(s).

Do a quick check of the scan folders in X1. Does CbB have them all listed the same? It may be a simple path issue, but I do not have UAD to check where they are installed.

Adobe is riddled with ping-backs to multiple servers, and intercepting them all creates an ever-changing landscape. Staying offline is counter-productive for some apps, since that is where they have most use, or what they are for in the first place. Having said that, throwing litigation threats at people is sort of just that... Adobe wouldn't recover legal fees from individual users, but maybe from companies. One nicety of Win 10 is that the OS itself shouldn't lock-out the CS6 (or below) apps in the foreseeable future. The amount of features added in the past 6 years hasn't been enough to even consider jumping on the CC bandwagon for me. If someone makes revenue from them, that is a different story that would take more consideration. The timing of the announcement in the OP also coincides with Adobe doubling the CC price of those apps (the most popular subscription), so it comes across that they are testing how far they can push it.

Exactly....there are no moving parts...so there are no worries with just setting them in there. That's exactly what I do...so, unless you are OCD about them being mounted, there really is no need. +1, Samsung's don't come with any mounting brackets, so my 850 is sitting on the bay floor as well.

^^ Hardcore right/wrong assessments of tool usage tend to miss the mark, but it does bring light to "studio" versus "live." No one will care how the end product was made (DAW, tools, overdubbing, etc.); but when live, those that rely on "studio tools" stick out much more prominently.

I am not sure if the stars are only personally viewable or aggregated... but regardless of this, there is no way to sort this forum by any topic rating, which is what is required to be useful to end users. Even using the "custom view" there is no entry for "topic rating" or similar. I just went back to check the old forum's Feature Request subforum, and the ability to sort by rating has also been removed. Many people have contributed a lot of very thought-out requests over the past several years, but even with prompting users for input, many of these have been purposefully buried over time. Although it is great to prompt users for input; if there is no follow through, it simply wastes people's time and effort.

I didn't even realize that "file" was there... the Spitfire Audio app install defaults to my main user directory (C:\Users\[username]) and I just left it there. After launching Kontakt to add the library, that prompted Native Access to launch so I could register the S/N, and then prompted me to locate the library for Kontakt. I never copied/moved it anywhere, just mapped it to where it was installed. I am not sure if this is what you are asking though? What an odd file name to have in the main directory though.

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).