Amberwolf

That means the plugin is not properly installed, and would need to be reinstalled to fix the problem. If you don't have the installer, and it is the DXi version, you might be able to manually re-register the plugin using regsvr32. I don't recall the procedure, but googling that phrase should find instructions.

.

Wierd, the above is "Hidden - This content must be approved before it can be edited." I don't even have any links in it? This forum is so wierd (it doesn't even have a "roll eyes" emoticon)

At the moment, there's no worry about the suno site taking away money; their agreement expressly forbids it's usage for that: they don't say if that's true of the other tiers or not; they are not expressly called out in that agreement in this way. they also repeat this more than once: However, their site does not allow you to create your own independent account there, unless you use your phone number. To create an account without a phone number, you must use one of your existing accounts with some other service, linking these things together. Anyone that doesn't want to do this, or does not have one of these other services, can't use suno.

Something I used to call "programmer syndrome" but is better called "engineer syndrome": almost always, the developer of a product (physical or digital) only ever sees it from the inside, and they don't actually look at the things in the way they are used by their intended userbase. When that userbase responds by telling them how it ought to work to do the required job, the developer typically refuses to change it and sometimes explodes at the user, completely missing the whole point of the product, which is to be used by the user, and thus must do things the way the *user* wants them done, not the way the dev thinks they should be done. Often the problem is only a UI issue--the under-the-hood stuff works fine, but is not user-accessible in a useful way, or in a user-friendly or workflow-friendly way. These issues usually get the hardest pushback from the dev, which is the most ridiculous part of it, since the dev should be making the User Interface for the user, not for themselves...but they make it the way the program internally works, not the way the user needs to access those features. I have almost never been able to get this across to devs. The Bakers here have been the most responsive of all of the devs I've ever worked with, but even they have this syndrome now and then, prioritizing program design and operation over user interface and user-experience like any other dev. Sometimes it is because a dev thinks they know how a feature should be used...but it doesn't matter what they think--what matters is what the *user* wants to do with the program and they way they need to do that, *especially* with art creation, as an artist is not going to do things in some programmatical way, in most cases. Each one has a way that works for their art, and the program must be adapted or adaptable to that, which is one reason presets and other UI customizability is so very important. There are many such improvements in customizability in Sonar / etc., though from the posts I see around here some of them could stand some improvement in user-awareness-functionality, and in control accessibility / state-visibility. It's not easy to make a UI at all, much less one that does all the things a complex program (like Sonar) can, and it's impossible to make a single UI that does everything every user needs it to in the way the user needs it to...so complete customizability is essential for such complex programs. Customizability is even harder to create flawlessly than a fixed UI...so anyone attempting to do it at all gets my congratulations and eternal thanks, even while I goad them on to continuous further improvements. But when a program (or device) foists a UI on user, especially an artist, it is at best unhelpful, and usually actively prevents a user from doing the things they want to do. As much as I dislike most of the current usages of AI, I can't wait until AI is advanced enough to alter existing programs for me tell it to create the UI I need, as I need it. Or even just to create a UI "over the top" of the program, so that when I need to do something, it lets me tell it what controls I need, and what information I need displayed, and then I tell it what to do with those and it makes me the UI I need to see for the stuff I am doing at that time, and refine it as I go.

Guess that's why it's free, doesn't have the most basic of functions. Or conversely, it doesn't save presets because it's a free version of something else? (or is going to be? I don't know this developer or their products)

You could record the metronome sound in a track, trim it, and export the clip, put it in Sonar's metronome folder...

Names are probably the only thing I'm pretty good at. (the songs hardly even get listened to, and almost never more than partway thru, so I imagine they can't be as good as the names). Ditto.

The specific error would be more helpful in resolving your problem, as the description you give is similar to another error that means something is not installed, but not the same and so probably doesn't mean that. It also doesn't say what specifically is missing, making it even more difficult to help you find/fix it.

I've never had the full version of SD, just the Lite that came with some version of SONAR. What is it that doesn't happen as expected when you set it up in the current version of Sonar?

Seems pretty useless to have something you can alter settings in but not save presets for, so I'd guess there must be a way. If not, you might want to ask them why such a basic function would be left out. But they might be like BabyAudio, where they don't think users should be allowed to have fine control over their plugins, and don't let you change most parameters, it's all buried "under the hood" so that some potentially really useful plugins are just left as useless garbage for anyone that wants that control and isn't just a "preset pusher".

I would guess (without having tested this) that you'd probably have to have the CC data (or whatever it is you want to overwrite) on a separate track from the MIDI notes and other data, so that overwrite mode won't destroy any other data in that section.

FWIW, speaking voices generally use a fairly narrow range, around 2khz to 4khz, for their primary information content. Most of the time you can automate a simple EQ with a single band and adjustable Q factor on hte soundtrack track or bus to "duck" the soundtrack in that frequency band during the sections the narrator is speaking, and gradually go back to normal when they're not. There are other frequencies down around 80–200hz and/or 160–260hz depending on the speaker that can conflict, too, but they don't usually cause problems understanding the speech. (the actual frequency range varies based on the speaker, but quite often the "telephone" setting in an EQ will have a useful range already in it, you just have to flip the gains on the bands so that it is ducking that range and leaving the rest alone, instead of ducking the rest and leaving just that). Or even less complex, you can use a simple compressor like the Core compressor in Duck mode on the soundtrack track or bus, with it's sidechain input fed from the vocal bus, to automatically reduce the gain of the sountrack whenever the narrator is speaking. With this, the only parts you usually have to adjust are the attack / decay and the gain. This is much simpler than analysing the tracks to find their conflicts, and generally works perfectly well.

I keep forgetting that exists, since it's design is nothing useful to me....so I didn't even think of it when I replied. My apologies to the OP if Bandlab (vs Cakewalk by Bandlab) is what you are referring to, in which case my instructions would be useless.

I might be misrembering, but I think Next has it's own format, or can open the new shared format that Sonar saves in. To open .CWP files from CbB, I believe you must use Sonar. If this is the case, then once open in Sonar, you could then resave as a new file using the new shared format with Next.

.

Something I discovered a long time ago is that, "impossibly", wires just "go bad" all the time, even just sitting there, never moving, no vibration, etc. When I'm troubleshooting something, in any technology, one of the first things I do if I have spare cables, wires, etc., is to swap them out. If it's intermittent, and the wiring is not just a pluggable cable, I'll move it around especially near where it exits or enters a device...and usually I'll find the problem there. There are reasons these failures happen, but...still....

AFAICR there is an option in settings for this? If it is a periodic silence, it's probably a plugin that has lost it's authorization or isn't working right; many "demo" versions use periodic silences (usually of random duration and event time) to encourage purchase. Regarding TTS1, if you had it installed on the system, it should still work in Sonar. (unless you uninstalled whichever program had installed it and uninstalled TTS1 with it). There is also at least one thread around here for TTS1 explaining how to get it back, though I don't know if the procedure still works or if it's universal. I don't have a link so you'll need to poke around for it.

Does it send CCs for the controls on it you want to use for this? Which volume envelope do you want to record? If it's the CC7 envelope in a midi track, then if it sends CC7 that's easy. If it's something else, like the track volume automation envelope itself on a synth or audio track, then you may have to set it up as a control surface. Azslow probably has something to do this with, but I haven't experimented with his stuff yet (I should, he's brilliant). A few years ago I used some generic thing I found cheap on ebay used, "Worlde Panda Mini 25-Key Portable USB Keyboard Drum Pad MIDI Electric Controller" the older model of this https://www.amazon.com/Worlde-Portable-Keyboard-Controller-Colorful/dp/B079FGP3BH?th=1 and between using it's software to define notes / ccs for the controls and the control surface "learn" stuff in SONAR, I managed to get it to control a few things. Took a few hours to figure out, but was easy enough once I got the idea. I'd still be using it for that cuz it was really handy, but it's electronics are pretty shitty, and all the pots (slider or knob) are really jittery and "gappy', tending to jump around in values or skip whole groups of values. It's worse the faster you move them, and the jumps aren't in the same place everytime, so it's not the pots it's the stuff that reads and processes them. (I could've replaced the pots easy enough, so of course it couldn't be that).

FWIW, instead of exporting, if you just want a MIDI clip "as-is" you can ctrl-drag it out to a Windows Explorer window with the folder of your choice. This copies just that clip. If you have a bunch of clips to do this for, select them all and drag them out, and you'll get one file per clip. Doing this creates filenames with "the project name , track name (clip number).mid". If you need an entire track's worth of clips as a single file, just bounce it to a clip, and then ctrl-drag taht clip out. (you can then undo the BtC if you like). If the clips don't start where you want them to, you can drag the clip out to that point...but...whatever you do, it will still require a midi event of some kind at the start of where you want the clips (and the same for the end of the clips).

That's a PEBKAC issue. That's a hardware problem.

Hmm.....lemme see....I completely missed that big gigantic orange bar at the top of that page, which clearly shows that I've used up all the space. Guess I'll go delete some older stuff. Thanks. :sheepish grin:

Ok, I split the most recent one out to it's own thread here: I guess if it gets replies, I'll split all the others out to their own threads too.

That's what I thought I remembered it being...but it's not that for me. 😕 I must be missing something obvious somehow, whcih isn't all that surprising. (I was just trying to attach the cover art in the latest Drywater Mars (Part 5) thread...)

This one is almost completely different from the others in the Drywater, Mars series; I left a couple of bits of sound here and there, including one ending vocalization, to tie it in to the others. No huge orchestral percussion, a closer more intimate (but not really quiet) sound. Every story has it's intimate scenes; this is one between two of our hero crew, as the ship drifts in zero g on course to the station. POV outside ship, pan from station across the cold emptiness of space, turns back toward ship drifting straight towards camera, rapidly approaching the ship filling the screen until the window onto the interior is all we can see. Music pauses just for an instant as we pass thru the window into the room, where two crew are just floating into the room, one following the other. One reaches the far wall, pushes gently back, meets the other and both motions counteract and they stop, floating in the room, reaching for each other, touching each others faces, almost in wonder. POV closeups on their faces, alternating one to the other as the music swaps back and forth, this continues: Practiced nullgrav motions let them embrace, retreat, caress, clothing drifts away beyond them as you watch their emotions and sensations written across their faces, still alternating, sometimes both in view, as they rotate with the POV, all the way thru the interaction to the usual conclusion.... Not Just To Breathe With You -- Drywater, Mars Part 5 https://amberwolf.bandcamp.com/track/not-just-to-breathe-with-you-drywater-mars-part-5 (posted to a new thread out of the original based on advice from Bajan Blue)