Jump to content

Robert Bone

Members
  • Content Count

    1,221
  • Joined

  • Last visited

Everything posted by Robert Bone

  1. Hi - was there any specific error message? Was a mini-dump produced? What version of the Nectar plugin are you using? VST2 or VST3 (if available) Bob Bone
  2. By the way - I can take the ASIO Buffer Size all the way down to 32 samples, which results in about 1.6 millisecond latency - WAY kewl. Not sure if my friend is going to get his laptop and interface back....... well, the interface, anyways (kidding - besides I have a UAD Arrow Thunderbolt 3 interface for my laptop, but WOW is that Quantum 2626 T3 NICE too) Bob Bone
  3. Hi - I just ran into this, helping a friend who just bought a new Intel-based laptop with a Thunderbolt 3 port, and a brand-spanking new Presonus Quantum 2626 Thunderbolt 3 audio interface (BEAUTIFUL, and a beast). Anyways, he reported to me hearing pretty evident pops and crackles for anything running through the Quantum 2626 headphones, so after trying a few obvious things, effects, latency, ASIO Buffer Size, etc., I had him run both the laptop and the interface up to me, so I could take a better look into things, and work through Sweetwater tech support, on his behalf, if needed. SO - after confirming the rather horrendous pops and crackles for myself, I did some digging, and found a promising article on the Presonus web site, which is at the following link: Presonus article on Quantum series interface pops and crackles Sure enough, when I followed the steps in the above article, downloading the little freeware utility program, and disabling a couple C-State Idle settings, and applying the changes, the pops and crackles instantly went away, so I consider the issue resolved and that should be that. I just thought I would post the issue and its solution here, in case anybody else had purchased one of the Presonus Quantum series Thunderbolt interfaces. (the new 2626 is brand new and really just starting to ship, as of 2 weeks ago). The article was from 2019, so may apply to earlier Quantum series audio interface models. Hope this helps someone else, too Bob Bone
  4. Could Windows have hijacked the audio interface ASIO drivers? That happens sometimes, where Windows automatically assigns an audio interface's ASIO drivers as the default sound device for Windows, for playing of Windows sounds, and Windows Media Player, and YouTube videos, etc.. I always go into Control Panel > Hardware and Sound > Manage Audio Devices, and disable any and all devices shown for my audio interface, under both the Playback, and Recording tabs. That stops Windows from hijacking the audio interface's ASIO drivers, as I only want Cakewalk, or other stand-alone instrument software, to have access to my audio interface.
  5. Thanks - sorry - I have been helping someone for 5 hours, thus far, (configuring laptop remotely, and dealing with audio interface drivers and such, NOT any trauma from Cakewalk by Bandlab on that system), and was hoping you could dig that thread up and help out, because I am currently tearing my hair out on this other set of trauma. TRULY appreciate your help, Bob Bone
  6. Kewl beans, your having sent the dump file to Noel. Also - yeah - for some of the bundled plugins that came with Sonar, you can indeed use those in Cakewalk, but only if Sonar is also installed alongside Cakewalk - like Dimension Pro, Session Drummer 3, etc.., Sonar is not so huge, that if you like those old Sonar plugins that are not present in Cakewalk by Bandlab - go ahead and install Sonar, however you might then want to also temporarily uninstall Cakewalk by Bandlab and then install it again, as that would be the natural order of how they would have been installed had you not uninstalled Sonar. They modified VstScan.exe for example, and you would get the new updated one with Cakewalk, but if you install Sonar over the top, without installing Cakewalk by Bandlab again, then I believe the VstScan.exe version would be the Sonar version. Small things like that. Perhaps someone like @scook, or someone else, could offer some wisdom on installation order. And, the above only matters if you are interested in using some of those Sonar-only plugins that are not present in Cakewalk by Bandlab, so if not interested in those plugins, just ignore my thoughts above. Bob Bone
  7. I ran into the duplicate ID situation 3 years back, when I bought two identical midi controllers, and couldn't properly control the 2nd one. Called Sweetwater and they then additionally involved the maker of the midi controllers, and none of them had ever considered that someone might try to use 2 identical controllers - turns out that that broadcast ID info the midi controllers send out, cannot be manupilated, so Sweetwater swapped out 1 of the controllers for one from a different company. Worked out fine - AND I got an extra bag of candy out of the deal, as Sweetwater includes a little bag of candy in every box of music gear they ship. Bob Bone
  8. I am not sure what info is needed to keep things connected or to be reconnect. I think it is because of the internal way Windows keeps track of which device is plugged into what port, some kind of numbered identifier, I think, because Cakewalk does not know which port a device is plugged into, all it knows is a device is present, so if the port changes, Cakewalk doesn't know if the connecting USB port is the same or not. I dunno. I will shoot an email to Noel or someone else, and ask what info the have available about USB-connected devices and about the ports, and I will ask for details on what they have been trying to get from Microsoft - I will post back when I get a reply, and try to dig up whatever info it is that Cakewalk needs. Maybe if I dig into whatever it is they say they need and don't have, I can help find something out. Bob Bone
  9. It's OK - the internet won't run out of ink anytime soon, so all is well. Perhaps seeing a similar report of the issue of the Bandlab update failures will help draw attention to it, that leads to a resolution - ya never know...... Hopefully, you are all set now, by going to grab the newest version straight from the web site, and just manually running it to install the updated version. Bob Bone
  10. That makes sense, as such a process as defrag would wreak havoc on any streaming audio, such as what Cakewalk does. Post back if you have continued weirdness since making that change. Bob Bone
  11. I have a curious question - you mentioned uninstalling Sonar recently. If you have Sonar installed alongside Cakewalk by Bandlab, then you can use any bundled plugins that came with whatever Sonar version you have, in Cakewalk. MANY folks (myself included) have Sonar installed with Cakewalk by Bandlab and they live happily alongside each other - and having continued access to the bundled plugins that came with Sonar Platinum, for me, is a wonderful thing. Dimension Pro, Rapture Pro, and others.......all work fine in Cakewalk by Bandlab, because they see that Sonar is installed, and that satisfies their authorization mechanisms, and allows them to work in CbB. SO - just curious on why you would have uninstalled Sonar. Bob Bone
  12. Please send the dump to supprt@cakewalk.com and they can see if that is an issue within Cakewalk. You might also want to make sure your Windows Update maintenance is all up to date - sometimes, even with automatic updates set, some maintenance requires explicit clicking by the user, on the Install Updates, for some of the maintenance to be applied. Go into Windows Update (for Win 10 go to Start button > Settings > Updates and Security > and that will get you into Windows Update. Once there, look under the Check for Updates button, and any optional maintenance that requires you to actually explicitly click on the Install Updates to get it applie should be shown there. IF there is such maintenance to apply, and it might require a subsequent restart or update and restart, then get back into Windows Update one additional time, and even if it says you are up to date on updates, there might have been further updates to apply, that had to wait until THAT set of updates was applied, so c;ocl on Check for Updates one additional time, to make sure there weren't additional updates to apply. This is because Windows Update didn't actually check for updates on its own, after you had applied that last set of maintenance, and that is why the clicking one more time on Check for Updates helps make sure there are not any additional ones needing to be applied. One for thing to check - that error, which is an Access Violation, can also happen if one or more dependencies are in the code, and require one or more of the Microsoft Visual C++ Runtime Redistributable libraries and that/those library or libraries are not installed on your computer. Those libraries are not a part of normal Windows Update maintenance, but can be needed by programs written in C++, and if a particular coding call only got exercised once your project got to some particular size, for whatever reason, if the code made a runtime call to one of the functions that is from a missing runtime library, well, that can produce an Access Violation. SO - in addition to making sure your Windows Update maintenance is all caught up, I suggest you also download and install, directly from Microsoft, the 15-20 Microsoft Visual C++ Runtime Redistributable libraries. They can all be installed, and they released the series of them, going back to the early 2000's, so there are a few of them, and that is just how it works - where programs can have dependency requirements for any one of those particular libraries, which is why installing all of them is a good thing to do. I have them all installed on all 3 of my music production computers, and have installed them on every other computer I have built for my other music production minded folks. I put together a post in the forums, with a list of all of the download links - again directly from Microsoft, of the complete set of these runtime libraries, and they are ordered from oldest to newest, so you can just start at the top of the list and work your way down. Please note that even though you are running a 64-bit Windows, you still need to install both the x64-bit versions as well as the x32-bit versions - both sets are needed, even though you wouldn't think so. Any questions, please post back. Still, send the dump to the Cakewalk folks at the above email address for support, and install any missing Windows Update maintenance, and also download and install the runtime libraries as noted above, and see if that fixes your crash issue. Installing those libraries will not do anything adverse - those libraries just need to be installed to be there if any programs require routines that only can be found in one of them. These being installed may also prevent additional crashing from apps and/or plugins that have those library dependencies, so it is a good idea to install them, in any case. Here is the link to the forum post I refer to, with the download links to the runtime libraries: Forum Post with Microsoft Visual C++ Runtime Redistributable library download links Bob Bone
  13. By the way - even though I have the USB Selective Suspend parameter disable, in my custom power plan, sometimes, regardless, specially after those big cumulative updates to Windows, I sometimes go back in and check, and find that, somehow, the Power Management tabs for some of the USB hubs are checked back on - to allow Windows to turn off USB devices connected to that hub. Pisses me off, that this occasionally happens, but sometimes it does - so I suggest folks take a look at the propeties dialogs for the various USB hubs, after those major updates, just to make sure Windows hasn't sneaked those paramaters under Power Management, back on. Bob Bone
  14. I agree - as I understand it, Microsoft never built a means of retrieving some set of information needed to be properly able to do that - I have, on a couple of occasions, tried to look into any programmatic way to find out what devices are connected to which ports, and came up empty - I did so early this morning, and went into a whole bunch of the fields you can select on Device Details of the Properties dialog for my USB-connected audio interface, just as an example, because I do not currently have a midi controller connected, because I am moving stuff around. Anyways, I also went into the Registry, looking at the Device Parameters, and other places, trying to figure out any way to get enough information to be able to write some sort of utility program to ferret out the info - and still, I have not yet found anywhere I can get that information. I am just not good enough at Microsoft Windows 10 internals to figure it out, though I WILL keep trying. IF I can figure out a way to programmatically get the info, I will create a litle utility to display everything, and I will, of course, pass that along to the Bakers. VERY frustrating - ALWAYS has been like that, and I KNOW that the Bakers have approached Microsoft with the issue, on more than one occasion, and never were able to get Microsoft to do anything whatsoever about any of it. The Bakers have been frustrated with this issue for many, many, years. I will continue my quest, because SOMEWHERE, buried in Windows, that information must exist, so perhaps there is a way to do the digging to find it, and that is what I will continue to pursue. Apologies for my Windows internal skills not being better - am workingh on it. I have built some little utility programs for myself, going all the way back to 32-bit XP Pro, but most of my programming languages and experience (38 years) was on mainframe systems, (COBOL, Assembler, DB2, CICS, was a DBA, etc..). Most of my PC-level coding has been in C#, which is fine, but I do not yet know all the routines and API calls to easily know where to go look for the info - I am working to correct that, because it will help me when I want to write utilities or whatever. I WILL get there, because I am also stubborn. Bob Bone
  15. I think I will fire off a couple of emails, to Overloud and Native Instruments, support, to get their thoughts and recommendations. When I get responses, I will post them here, in case anyone is interested. Bob Bone
  16. Thanks - that is about how I figured it. So, I guess I will audition presets, or build them, as they are, and then if I decide to track with one, I will for now do the individual component-level gain staging, and save off that preset, hopefully into a bank or category, that contains all the other presets I did the gain staging for. Then again, at some point, I might just cave, and do a gain plugin reduction after the amp sim. I will see how it goes, over time. Fortunately, as primarily a keyboard player, though I do also play guitar, this issue won't likely crop up too often. Bob Bone
  17. OK - so I am looking for guidance from folks who have delved into dealing with gain staging between the different effects and the amps used in amp sims presets, such as from TH3 and Guitar Rig 5 Pro. Almost every preset I check, in either of those two amp sims, and indeed any amp sims I have, jack up the signal by anywhere from 8 to 10 dB at their output. While the easy fix is to reduce the output volume, either in the amp sim, or by inserting a gain plugin after the amp sim, in the FX bin, that ignores what should be gain stage points between each of the effects in the amp sims preset - chorus, delay, distortion, amp, reverb, whatever. Before I adjusted any of the input gains and output volumes, between the effects for a given preset chain, I looked at how these levels were, compared with the input gain of -18 dBFS going into the preset, and they were all over the place, with the output volumes from any of the effects adding several decibals to the signal, before feeding the next effect, so that by the end of the chain, there were usually about 10 decibals added. Each of those components in an amp sims preset have an input gain, and an output volume, and my understanding is that many of these effects are designed with a 'sweet spot', which as I understand it, tends to be at the -18 dBFS mark. Further, it is my understanding that any and all effects should really be 'gain/volume neutral', where their processing output should not be higher or lower than their input, so that with the effect(s) on or off, the output levels should be the same as what their input gain levels were at - that -18 dBFS sweet spot. SO - why aren't the hundreds, or thousands, of presets that come with these commercial amp sims, set up to honor the above? Also, what are considered 'best practices' for dealing with the out of whack levels most, if not all, of those presets have? What do YOU folks do with the above? I would also like to point out that many of the knobs for output levels, do not pop up any actual dB level when hovering over them, and some don't even bother to tell you how much change is occurring when you drag them up or down, they are just knobs that respond to dragging the mouse, but they leave me in the dark for how much change is actually occurring. Further, often - for a given preset - the output level knob of the amp sim often doesn't have enough range to properly compensate for how much volume was added above the target of -18 dBFS, so I have to reduce gain beyond the amp sim plugin - which seems pretty silly to have to do. I know that if I just turn down the output volume of the amp sim, no matter what is going on between the individual effects for a given preset, but that seems to me to not be operating with the 'best' quality of sound that can be produced, as compared to going through the hassle of adjusting gain/volume between all of the components, etc..... By the way, at the moment, when I settle on whatever combo of effects, or on a given preset, in ony of the amp sims, I currently start off with just the leftmost effect in the chain turned on, and then adjust the output level to meet my target of around -18 dBFS, and then turn on the next effect in the chain and repeat, etc., until I work through the whole chain. That way, at the end of it all, I am 'gain/volume' neutral. I have no idea if there is a better way to approach it - but it does seem to work between each effect, to do it that way. This would be similar to having a series of effects outside the amp sims, in the FX bin, and if doing that, I would approach it in the same manner, between each effect, to maintain neutrality.... SO - thanks for any guidance with the above. I am a keyboard player, but would indeed like to create the best quality sound in any of my projects, for any guitar tracks that use amp sims. This should be an interesting discussion - hopefully I am not just off in left field with the above. Bob Bone
  18. The Cakewalk folder in the Roaming folder above, contains some files for Cakewalk\Core, so I went ahead and added it to the Avast Exceptions, though it is not a bottleneck if I had not done that. But, I figured why not, and added it. If you open File Explorer, and enter the following (just copy and paste it into File Explorer: %appdata%\Cakewalk You can look at the files and folders within - the Cakewalk Core folder has some misc files, and the drum maps. Again, skipping that entry in your exceptions/exclusions paths of your antivirus won't really slow things down any. I just had a 'why not?' moment when I added it to my Avast exceptions. Really, your sample libraries, Cakewalk Content, and Cakewalk Projects, and the paths to your VST2 plugins and the C:\Program Files\Common Files\VST3 are your biggest bang for the buck, for having the antivirus software skip scanning files accessed/written/manipulated. And, it is not anything to do with the Bandlab Assistant that I have those paths skipped by Avast. Those paths are there because they are accessed by Cakewalk, so Cakewalk performs better by not having extra overhead from the antivirus program. Bob Bone
  19. In Cakewalk, when you insert a bus, you can choose either a stereo bus or a surround bus. Bob Bone
  20. I was not classifying my request as a bug fix - for the record - it does seem that as I had noted, Cubase on a Mac was what my friend had used to create the midi files he sent me, and it apparently did export those files with the .midi extension. I would point out that Cakewalk is currently inconsistent with handling files of type *.midi, as when I double-click such a file, it opens with Cakewalk, and Cakewalk does process the file properly and set it up ready to play with TTS-1, however Cakewalk does not show those files in either the File > Open dialog box, or in the File > Import > MIDI dialog box, or by default in the Media Browser. I have the current workaround of renaming those *.midi files to *.mid, so my request is certainly not earth-shattering, nor stopping me in my tracks, should you guys elect to skip this one. I just thought that since at least one established, and widely-used music production program does create files with that extension, and since to the best of my awareness, the implementation of adding that extension to the filters in the dialog boxes wouldn't need any additional logic, that perhaps you guys would be OK with adding it. Here is a screen shot from the Cubase export for midi files, showing their default extension in this pic, as "Untitled.midi"
  21. If you download the Native Instruments free "Komplete Start", it comes with several of the synth engines, and Guitar Rig 5 Player, which has a tuner in it that I like, but as noted, lots of other free ones out there. (The Komplete Start bundle has a free Kontakt Player - and a set of sample-based instruments, along with a 'lite' version of Reaktor - Reaktor Player, and I forget what else, but for free, you would get the tuner from Guitar Rig 5 Player, and the other components too, so not a bad deal - hard to beat free). And that free bundle from MeldaProduction is amazing - very high quality in all of their components - they also make other non-free components, that are worth checking out. Bob Bone
×
×
  • Create New...