Jump to content

Starship Krupa

Members
  • Content Count

    2,419
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Starship Krupa

  1. That is weird with a beard. The only thing that comes to mind is that somewhere along the way, the noise you're hearing is 180 degrees out of phase on each side. When you center both, it gets cancelled. I don't know where along the chain this could be coming from, but hit the big button to disable all FX and see if it still happens. If it does, examine the audio file(s) to see if the distortion is present on each side. Maybe load the audio file up in an audio editor like Audacity or whatever you have. This will tell you whether the distortion is baked into the recording. You can also try pulling down left and right one at a time in the Hardware section of Cakewalk's console and see if the distortion appears.
  2. Since you've accomplished the task of getting everything hooked up and Cakewalk receiving MIDI information, you probably do just need to set the output of the MIDI track to the synth and all will be well. One thing to look out for: if you've followed John's instructions and still can't hear anything, make sure you don't have the MIDI track solo'd by itself, because that will mute all other tracks including the one with SI Electric Piano on it. Cakewalk usually links solo and mute between MIDI and instrument tracks, but it's possible to override it. Just mind your solos and mutes and you'll be fine.
  3. I don't know exactly what's happening here; worst case scenario is that a user waits longer than 6 months to run the program, then has to run BandLab Assistant to re-validate. Cakewalk does that every 6 months to renew the license subscription. Otherwise, it doesn't demand anything. You may get a notice that there's an update available, which, since the developers are working hard at improving the program, happens often. Installing the updates is optional. They always have plenty of fixes and other improvements, so I always update, but I'm not forced to. The biggest hassle I've run into is that BandLab Assistant (which is developed by a group different from Cakewalk itself) fails on updating itself, so I have to go to BandLab's site and download the latest version. That's a pain, but a trivial one. Sometimes I have to enter my username and password once or twice to get BandLab Assistant re-installed, but this was also true for Cakewalk Control Center, the old download-and-validate program. So at the most, there should be "sign in," and maybe "download," and "run BandLab Assistant," but no "re-enable this, re-enable that, download this and that....and so-on." It literally does validate your license and then "leave it alone" for 6 months at a time. If you re-validate at any point, the clock starts over. The latest version of Cakewalk doesn't even need BA to validate the license (only to install Cakewalk and update it), so all of that is history. If anything other than what I describe is happening on your system, there's a problem that's not part of the usual experience, so if so, post more details and we can figure out what you need to do to avoid this in the future and get straight to work. Cakewalk by BandLab is so far ahead of where SONAR was 3 years ago, it's very much worth sorting it out.
  4. Wow, those are some nasty symptoms. Now that I think of it, I wonder if this is the cause of an odd issue I've run into a couple of times. If it happens again, I'll make a note of whether the project was using A|A|S Player. (The specs of my main DAW are in my sig, but I also sometimes copy projects to my aging laptop for mixing. It's maxed out to 8 Gig RAM and "hot-rodded" when I swapped a quad core i7 in place of its original dual core i5 and swapped the spinny drive for a 250G SSD. After 3 years of BandLab ownership, Cakewalk has gotten so stable that I have had projects open, forgotten about them, had my computer go into full sleep, wake it back up and Cakewalk is still open and runs happily. I don't know about anyone else, but for me, this is a HUGE improvement over the last version of SONAR.) A couple of times now I've had a project open on the notebook, gone away and left it, come back and had a pop-up from Cakewalk saying that it can't write to the disk. Checking the disk, it's been at zero free space, when usually it's about 50G free. Exiting Cakewalk and then checking, the disk was back to its usual free space. This is a classic symptom of a memory leak; the program uses more and more memory, the system increases the size of the swap file to accommodate it until there's just no more room. Either that or it had to create a hibernation file that was enormous, or both. Given your issue, it could be the same thing but with a slower onset, maybe because on my system, the transport wasn't running. Anyway, since A|A|S seem to be dragging on getting back to you, it could be that in the wake of the v. 3 updates they're busy working on fixing a bug or bugs and Eric just has no news for you. Not all companies are forthcoming enough to say "it's a known issue, our developers are working on it." To help figure this out there are a couple more things you can try (and so will I). First, take a look in Resource Monitor and see if you can see specifically what process(es) are eating up your RAM. If you're not familiar, you open Resource Monitor from a link at the bottom of Task Manager's Performance screen. It shows what's using up CPU and RAM in greater detail. I've suspected memory leaks in the past with A|A|S Player, but never pinned it down, because my usual trick of limiting the number of voices seemed to cure it. They love to put loooooooooong release tails on those patches, which causes the player to quickly stack 'em up. Second, if you have another audio program you can try the plug-ins in, it would be helpful to see whether your A|A|S synths have trouble with them. I think Ableton Live! Lite is still available for free, also Mixcraft and REAPER have free trials. If they choke Ableton, then for sure there's a problem there. I've posted elsewhere about the (sometimes significant) sonic differences between the earlier sound packs and the ones "remastered" for v. 3. Have you also updated your sound packs along with the synths? Who knows, there could be some issue with using v. 2 sound packs with v. 3 synths.
  5. I'm a user of the Session versions and Swatches/Player with about 20 sound packs. No trouble here, except that they're a touch more resource-hungry, which I help by restricting the number of voices to 4. A|A|S have an enthusiastic following here on the forum, so it would surprise me if the issues you are seeing are common. I mentioned resources, is your system powerful enough? 8 Gigs of RAM minimum? Quad core of some kind?
  6. Also, I notice that @abacab seems to have a couple of Gigs in "unused plug-ins" folders. That seems....wasteful, if they're actually not being used?
  7. Not long ago A|A|S came out with major updates to Chromophone, Ultra Analog, String Studio, and A|A|S Player/Swatches (what you use to play sound packs if you don't have the aforementioned synths). Version 3. I noticed at the time that they mention in the sound pack blurbs that the ones derived from those instruments have been "remastered" for version 3. I did some side-by-side listening tests with A|A|S player, and yes, the sounds were "bigger," even in just Player. I recommended re-downloading whatever sound packs you may have to take advantage of this. Upon further listening, I noticed that some of the sounds were not only bigger, but have changed tonally, to the point where I feel I can't fully trust my use of them in pre-version 3 projects. Not that I'm going to switch to another sound, but that I might have to do a bit of tweaking in order to make sure the sounds still sit where I want them in the mix. tl/dr: If you've updated your A|A|S sound packs since the v. 3 release and have projects that use those sounds, pay close attention to make sure that your A|A|S hasn't gotten too big for the mix. Easy enough to tweak with something like Sidewidener and maybe your favorite EQ.
  8. I'm cross-posting this to Instruments and Effects. Not long ago A|A|S came out with major updates to Chromophone, Ultra Analog, String Studio, and A|A|S Player/Swatches (what you use to play sound packs if you don't have the aforementioned synths). Version 3. I noticed at the time that they mention in the sound pack blurbs that the ones derived from those instruments have been "remastered" for version 3. I did some side-by-side listening tests with A|A|S player, and yes, the sounds were "bigger," even in just Player. Upon further listening, I noticed that some of the sounds were not only bigger, but have changed tonally, to the point where I feel I can't fully trust my use of them in pre-version 3 projects. Not that I'm going to switch to another sound, but that I might have to do a bit of tweaking in order to make sure the sounds still sit where I want them in the mix. tl/dr: If you've updated your A|A|S sound packs since the v. 3 release and have projects that use those sounds, pay close attention to make sure that your A|A|S hasn't gotten too big for the mix. Easy enough to tweak with something like Sidewidener and maybe your favorite EQ.
  9. I wrote up a tutorial (with manufacturer-specific examples) on how to de-crapify your drive of spurious plug-in versions. Of course, I didn't catch everything that those wily manufacturers strew around, so others have chimed in. I may have missed an A|A|S or two, as it later occurred to me to do a search from the top level of my C drive for "AAS Player" and I found a 16th copy. Unbelievable. 16 useless copies flung all over the place every time I install a sound pack. Yes, for sure, Avid and Digidesign (which is where RTAS versions go, because the world needs RTAS, doesn't it?), especially after an iZotope installation/update. I think the canonical path for AAX is C:\Program Files\Commmon Files\Avid. I suspect that this is driven by suggestions from their tech support staff on how to reduce calls. It's easy enough to decline AAX, forget one has done so, then install Pro Tools First and wonder why the plug-ins don't show up. Then it's "how do I get them to show up in Pro Tools?" over and over again. This is Meldaproduction's rationale for still forcing installation of 32-bit versions (although they now allow you to install only VST3's, which is a great improvement). Especially weird in Vojtech's case because Meldaproduction's stuff (outside of the FreeFX Bundle) is decidedly not aimed at people unfamiliar in the ways of plug-ins. He's crusty enough to say screw it, we're not answering another support question from someone who fires up an antique program to work on an old project and forgot they excluded 32-bit versions or expects a reverse BitBridge.
  10. All now hail the almighty Ctrl-Alt-F, which zooms your project to fit horizontally without zooming it vertically. Introduced in the latest drop.
  11. That's a description of an effect. Maybe it's just a poor choice of category titles, but "Musical Instrument Software," sounds like software that is used as a musical instrument. The category right before it was Musical Instrument Hardware, a Moog was chosen. They had two categories for Signal Processing Software, isn't Melodyne more of that? Their categories need to be updated, I think. There's a single category for Workstation Technology/Recording Devices, which I guess covers DAW's because UAD LUNA was chosen. That leaves out so many other things. How about Recording and Mixing software, or Music Production Software? They have separate categories for Large and Small Format hardware consoles. Is that a hot market right now? And a 50-year Anniversary re-issue of a valve stadium rock bass amp won a technical achievement award? The SVT was a great achievement....in 1970. In 2020 a 300W tube bass amp with an 8 driver cabinet is kind of the opposite of a technical achievement. The big achievement would be finding a dependable source of 6C4 tubes. Or a vehicle capable of carrying it to gigs.
  12. Great to see Antonakis come out with another one. RealSpread was an early hit in the Favorite Freeware FX thread.
  13. Same. Is it worth the download if I already have other orchestral libraries like VSCO? Orchestral sounds are a background thing for me.
  14. That's easily done. After you install Theme Editor, there's a collection of custom faders in C:\Cakewalk Content\Cakewalk Themes\Theme Editor Toolkit including these.
  15. Updated with new Selection Module art and a few other small odds and ends.
  16. Whoever referred to the default behavior as "destructive" knew what they were saying. Yes, please, do not destroy my MIDI clips!
  17. Contact Cakewalk by BandLab support. Also better to post issues in the main forum, not the UI Themes forum. Good luck, mate.
  18. Thank you much for clarifying this. I have a LOT of their lower-tier software, the kind of stuff you get in bundles or BOGO's and I wouldn't want to do anything that might dissuade them from participating in those programs. I've written them, to praise the product and to make a plea that they add some choices to that installer of theirs that spews 15(!) unwanted copies of AAS Player.dll/aax/vst/RTAS around my drive every time I install a sound pack. (I have a folder on my desktop called "AAS Wipe" that contains shortcuts to each of the places their installer puts the program where I don't want it)
  19. Glad you're back up and running. I was thinking we'd be watching the financial news for a sudden surge in audio software sales revenues.
  20. Thinking about springing for the $17 tier even though I have all of these packs except Plastic Pop. I have an older version of Entangled Species and I know they've updated the Chromophone engine since then, to its betterment. 4 new packs and one update for $17 isn't too bad assuming that they're okay with trading in dupes. I'd prefer to know that that's a standard policy. I'm sure manufacturers prefer people going to them if they want a different product rather than hawking license transfers on the cheap to fund it, and this way of handling that is preferable to the transfer penalties charged by other companies. Worst case I'd wind up with Plastic Pop and an upgrade to Entangled Species for my $17.
  21. I support this, especially the date added part. I try out a LOT of plug-ins, nearly every freeware one that comes along gets installed and fiddled with a bit, and they can get installed into non-intuitive categories. Also, the display name might differ somewhat from the name of the plug-in. No matter what manufacturer actually coded it, if they sell it through PluginAlliance it will show up with PA as the mfr., so that can confuse things, too. Not under Unfiltered Audio, but Plugin Alliance. While we're at it, I'll feature creep it to drag and drop organization in the Browser, please? I forget that this doesn't work and keep half-consciously trying it.
  22. Okay, hooray, everybody, as of this Early Access drop, there is now a command for horizontal-only resizing to fit the project width. Look for Zoom To Fit Project Horizontally. They did a fantastic job of implementing it, it does the same thing whether you are zoomed out to kingdom come or zoomed in to little bitty ticks. There's no default key binding, so you'll have to do your own or put it on the Custom Module. Mine's on the "." key because it was the most convenient unused key. Not precisely the lasso zoom that @Keni was asking for, but I think it will be a MAJOR convenience.
  23. Clip outlines in the PRV are not a big deal for me, but it did have me puzzled that Tungsten wasn't showing them. The tint that tracks take on when they are armed for recording is something I'm interested in because I like to reduce ambiguity, and the shift to a slight dusty rose tint doesn't really stand out enough.
  24. As the author of a Tungsten-based theme, I'm kind of puzzled about how in PRV, the only themes where I can notice the effect of View/Show Clip Outlines are the lighter ones. Mercury, MIL-SPEC Alpha, other lighter themes both show the clip outlines as an overlay. There seems to be some way to set this, as I see that Flat White Matcha and MIL-SPEC Alpha differ slightly, but I can't find it in TE or TYLIP. Also, in PRV, when a track is armed for recording, the view background and clip take on a pinkish hue. This seems to be universal, in every theme I can find, but has anyone figured out how to change it?
  25. I finally fully grasped how routing works in TAL Vocoder-II, so posting it here as a public service. The basic concept of a vocoder is that you're using one audio signal to modulate another. It's a form of sidechaining, you have one audio source and you're using another one to affect it. The audio signal being affected is the "carrier" and the one affecting it is the "modulator." Many vocoders, including hardware ones, include simple internal synths to use as a carrier. TV-II has one, but may be used in a way where you may disable the internal synth and feed it both audio signals. My initial confusion with TV-II was that in order to use it with its internal synth, you set it up backward from the usual sidechain arrangement. The plug-in is installed on the modulator track, not the track actually being modulated. That was the biggest thing to get my head around. There are two ways to use it. 1. You want to use its internal synth (as the "carrier") with other audio controlling it (as the "modulator," traditionally a vocal). This is fine for the bread-and-butter Tupac/Daft Punk effect where you want a "robot voice." 2. You want to feed it carrier from your own synth track, and another audio track as modulator. This was my ultimate goal with a vocoder, because I want to use breathier pads for the synth input than the TAL Vocoder's simple internal synth is capable of. More Kraftwerk "Autobahn" than Tupac "California." We'll begin with case 1. Start with a MIDI track with the notes you want to send the synth, and an audio track you want to use to modulate it (usually a vocal). Insert TV-II as an effect on the audio (modulator) track. In the plug-in UI, at the top, click on the VST3 button and enable MIDI input. Go to the MIDI track and set its output to TAL Vocoder. That's it. Now, you'll have to fiddle with the controls in the plug-in, adjust the synth to get a sound you like, etc., but the routing will be set up. (The confusing part here is that you're inserting the plug-in on the modulator track, not the carrier. That's what I mean by backward.) For case 2., you'll be using a stereo bus. You will be sending audio only, not MIDI, to the plug-in. Create a stereo bus. Name it "Vocoder." Insert TV-II as an effect on the bus. Click the button in the plug-in UI that's labeled "Input Mode On." In the audio/synth tracks you wish to use, create sends to "TAL-Vocoder-2." Set the sends to Pre-Fader. Pan the send on the track you wish to use as the "carrier" to hard left. Pan the send from the "modulator" to hard right. To mute the dry sound from the carrier and modulator, just pull their faders down. If you want some dry sound, bring them up There are alternate ways to accomplish case 2, but this is the easiest I've found. Send a nice hot signal from the modulator to the right input of TV-11 and again, do some fiddling with the vocoder controls. The internal synth is inactive in this mode, so leave it alone. General tips for vocoding: on your modulator track (usually voice) fire up a good 1176 emulation, set it to 12:1 and smash the snot out of the signal before sending it to the vocoder. Also, if using a vocal, a tuning correction/pitch changing plug-in can add another dimension. I use Meldaproduction MAutoPitch on the "Man To Woman" setting to bring my voice up (for the AIR Talkie Walkie sound), and set it so that it "glitches" a little bit. Feed the vocoder a nice, hot modulator signal.
×
×
  • Create New...