Michael Elliott

Is there a lock symbol on the clips? If so, the Lock Data function may be turned on for them. You can select them, right click on them, and turn that off.

On my ancient SONAR, it's all stored in the programdata folder: C:\ProgramData\Cakewalk\Studio Instruments\SI-Bass Guitar\Patterns

Just curious--what do these look like? (not a problem I've run into yet) EDIT: Nevermind, as I was typing it up (distracted in the middly by JellyBean wanting to play), the screenshot above got posted. :oops:

BTW, depending on what options exist in newer versions of the plugin manager, you may have to select the option to rescan existing plugins for it to check to see if they're still there. If it's not even checking for that, it isn't likely to remove entries for missing ones. FWIW, I despise that category 3 type--I don't want anything on the system other than the actual programs that are doing the work I need done. Anything else is just one more layer of crap to break and keep me from using the things that do my work, and one more layer of crap between me and getting them to work again. Same thing with "authorization" and "licensing" programs. If plugins or software has those, then regardless of how "good" they are, or cost (even "free"), they're not worth the heartache they're going to cause me at some point, if not immediately. I have not had *any* program using one of those schemes that did not have a serious problem at some point, causing me hours, days, or weeks of grief trying to get it fixed, usually with little or no help from the company that supplied it or made it--and for some of them that were no longer around, it wasn't even possible to fix, especially the ones that require their servers to be working and accessible to even use the program. So...I pass on all of those. Just give me files I can unzip into place and run directly, or stick in my VST/etc folders to be scanned, etc., and I'll be much much happier.

What driver are the other working programs using? What are their settings? Do any of them have exclusive access to the driver(s), and if so are any of them running (even as "inactive" TSRs) while using CbB? That could prevent CbB from accessing the drivers to get sound in or out. Are any of the drivers set to allow exclusive access in the Windows sound control panel? You might disable that if so, and see if it makes a differenc.e Keep in mind that ASIO, per Steinberg's limitations, can only use a single audio device at a time, so if you have separate in and out devices, you can only use one of them at a time in any program that is set to use ASIO. To use separate devices for in and out, you will have to use one of the other driver modes, to allow you to select multiple devices at once. If you are unable to select multiples, then first uncheck both inputs and outputs for the current driver(s). Then you can try selecting multiples; if there are any that won't let you do that, it means those drivers are written in some way that prevents access to them while the others are being accessed, which you'd probably have to take up with the hardware manufacturer. Regarding the crashes, I would guess that you have a driver called ASIO4ALL installed. It isn't a "real" ASIO driver, and is known to cause various problems. Uninstalling that completely may fix the ASIO issue, if you have a real ASIO driver to select instead. (many devices do not, and use ASIO4ALL as a "wrapper" to talk to their *real* driver...but the way ASIO4ALL works is talking to *all* audio drivers on the system, which isn't helpful when trying to access a single device, and is part of the problem).

What plugins (synths) have you already used, and what tech issues did you run across with them? (this may give us a level of experience to start the help with) FWIW, I use audio phrases and loops in my projects on http://amberwolf.bandcamp.com (some of the most recent of which have some similarity to the styles of the artists you mention) to give me the "world" sounds I'm after, since these also give me the playing style and expertise of those instrument-players (whcih I don't have and will certainly never have time to learn for all of these :lol: ). Most of mine have been the free packs from various places like Ghosthack, Cymatics, Black Octopus, etc., but I've bought a few on the holiday sales for very cheap (90%+ off!) that have enough more to be worth it, many variations, and of course I can cut, chop, stretch, squish, retune, etc., any of them. I do this partly to save frustrations with "tech issues" (including authorization and licensing-server failures, and all that stuff), and though it does place limits on what I can do with the stuff I have that would be lessened if they were the instruments instead, that has made me learn some other things and make some stuff I wouldnt' have otherwise even tried. It also gives me access to vocals, since even if I could sing (see Back to the World for an example of that problem), I don't have the right kind of voice to make any of the sounds I want.

.

It should be essentially the size of your RAM, since your entire RAM state needs to fit into it, and it has to ensure there is always enough reserved space for this to happen without any intervention (user or otherwise).

Something like this almost happened with the original ATX way way back when; I don't recall why it went the other way. At some point, to make certain kinds of advances, one has to break legacy-compatibility. I dislike it even more than the next person 😉 but that's just the way things are. You can only "hack" so many things onto something else before some kind of major revamp of the system becomes necessary to improve it. There are good technical reasons to avoid wires whenever possible: --radiated noise / RFI. Shielded wires can help with this, but it increases their cost and complexity. Changing currents in the supply wires create changing radiated noise, which can be made worse by faulty / insufficient caps on the devices to filter the induced noise from operating the fast-switching high-current devices around the board(s). --every connection between any one thing and another is a potential failure point, and every one adds resistance. Eliminating the cabling eliminates every connection between the wires and their contacts at each end, and the wires themselves, reducing down to just the contacts in the inter-board connectors, and the PCB traces, and the solder connections between those, all of which would exist in either case. Then there's the cost of making the wiring harness and qc'ing it, and connecting it to the boards. Then the cost of replacing hardware that is damaged / destroyed by incorrect wiring in the harness itself, or mis-assembled connectors, or user-error.

If you don't mind another program running, you can use Herman Seib's VSTHost to pass midi to/from the Kronos port. It's not *totally* straightforward, but once you figure out the necessary routing, and save *all* the possible ways there are to save the setup from it, it can recall automatically when started, and you should be able to set it up to start with windows so you don't have to remember it. Side benefit is it also is a VST host, so you can use it to host external plugins or synths if you have any need for that.

It may not even be a preset--it might be an option, or a global effect, that is meant to help emulate some analog property.

The first thing I tend to think of whenever I see your username is "epic trigga". No idea what it would mean, but...there it is. FWIW, I started with used well-worn analog tape decks (open reel 1/4"), in the 80s, with "toy" keyboards and such (sometimes opening up the backs of the keybaords to touch different parts of the PCB to make it make noises other than those intended; I didn't know enough electronics to actually modify stuff, but I knew from accidents with radios that this could happen with audio circuits and fingers). In the (early 90s? late 80s? whenever the a500 was first available used) I went to the amiga and Trax (which sucked) and Bars&Pipes (which was great), but by the mid-90s was forced to a Windows machine, and picked Cakewalk v3 because it was easier and more intuitive to use than the other one that was on Synthony's demo computers (Cubase? dont' remember), and just about everything could be done with a keyboard with only a few things being easier with a mouse, whcih made everything faster to do. Been using CW, then CWPA, SONAR, and Project5 since then. (still ahve the others but the older SONAR is what I'm still using--I'd consider the newer SONAR if it weren't subscription-only, and had a permanent *completely offline* license system like the old one, so that once activated, I'd just be able to keep using it just like it was right then forever, and if I had to reinstall (on any machine) I just use the same key as that one, so I could still use it no matter what happens to Bandlab/etc, just as the Bakers made sure we could do with the old SONARs). I'm a bit better at the production side of things nowadays, but I'm not sure that my actual music is any better than it was then. (still have boxes of probably unplayable reels and cassettes, and a few DATs I wish I had a machine to play; if there was a mostly-automated way to get those into the computer and onto Soundclick I'd stick it all up there for "posterity"...or maybe archive.org would be a better place).

What other plugins and instruments are on all the tracks and buses feeding that one? Some plugins generate noise as part of their function; it may be so low you can't even hear it but still be able to see it in an analyzer view. Is input echo on for any track? General input noise can also do that.

If it's a ground loop issue, then a workaround is to get one of those old adapters for plugging a grounded device into a two-prong outlet. You're suposed to then run the wire from the adapter to a ground somewhere else, but in your case you can't do that because it will cause the hum. The ground is a safety feature to prevent electrical shock. I expect that you probably won't have an issue with that, but you should be aware that without a ground the risk exists if certain types of failures happen inside the power supply. Like this kind of thing https://www.amazon.com/JACKYLED-Listed-Grounding-Adapter-2-pack/dp/B06XTHWYPK though I don't know anything about that specific one (I have a couple ancient ones kept in a drawer for various things, including stuff like this). If you have a multimeter, you can test if the HA-adapter connects the neutral of the ac side to the - side of the dc out; this could cause the hum. Can't do much about it beside replacing it with a different one that doesn't do that.

.

Welcome--I know your name from somewhere...did you used to frequent the old newsgroup ages back?

.

Just to be sure, is that really only 2gig, or 2terabyte?

What do the midi tracks feed? if it's external hardware gear, or external software, you would have to record those as audio tracks within the program with the midi tracks first, and then you can export those. If it's internal software (vst, etc) then the other advice already give on this thread should work.

.

.

Is this the device you are playing back from? https://www.roland.com/us/products/mobile_studio_canvas/ or are you only using the built in sound on the laptop? Meaning, where are your speakers / headphones plugged into to listen to the music? If you are listening to the music via the laptop speakers or headphone connector, then exactly how do you have the system wired to get the sound from the SC50 into those? What specific procedure, step by step, did you use on the older versions? Which steps are unavailable on the version you are using now? Was the system wired exactly the same way then as now? If not, what specifically was changed? Does it still work correctly on your older version?

Do the laptop ac adapter and the new item ac adapter have grounding plugs? If not, it isn't an outlet-caused "ground loop". If one or both has no ground pin on the ac adapter, then do they both have polarized plugs? (and if they have detachable cords, on *both* ends of the ac cords to the adapters)? (so that they can only be connected to the AC source in one way) If it's possible to plug one in either way, try it the other way. Some devices are not "isolated", and use the neutral side as ground, *and* connect that internally to the negative rail of the DC output, which can cause problems of various kinds. If the plug is not polarized, it can also lead to worse hum when the neutral-wired side of the system is connected to the hot side of the outlet. (this "shouldn't" matter, electrically, but it often does). Does it happen when the laptop is not connected to it's ac adapter, or when the new item is not connected to it's ac adapter (assuming it can operate without it, some can and some can't)? If it stops when one of them is not connected to teh outlet, then it's likely that one or both have the neutral connected to the DC side ground, and it's allowing AC noise to pass thru into the ground. Since it didn't happen until you added the new item, it's probably the new item's adapter causing the problem. Since the new item doesn't cause the problem under every test condition so far, it's unlikely that the new item has bad or insufficient capacitors allowing AC noise to pass thru to the DC side, but it could still be that, and a replacement ac adapter that's functioning correctly would fix this issue. Alternately, if you are electrically-DIY-capable, you can wire up a battery power source for the new item, using an old unused ac adapter's cord that has the same plug as the new item to connect the battery(ies) to the device instead of the actual ac adapter. That eliminates all possible issues with the ac adapter (grounding, faulty caps, etc).

Thanks! It's rather out of my usual methods, so it (and my last few most recent tracks) are quite the experiment for me.

.