Jump to content

William W. Saunders, Jr.

Members
  • Posts

    144
  • Joined

  • Last visited

Posts posted by William W. Saunders, Jr.

  1. This suggestion is a simple fix and excuse me if you have already tried it.  See if the automation envelopes are still there.  If not, go back to your last saved version before the problem and copy just the envelopes you are missing (set Now to 1:01.01, select/highlight the whole track or bus then "Copy Special" from the Edit Menu, selecting only "Track/Bus automation" with the check boxes).  Then "Paste Special" into the version you have the problem on, again using the check boxes to select only "Track/Bus automation".  But when pasting, make sure you also select the correct track, "blend old and new" and "Paste into existing clips."  Also make sure you paste at the beginning of the track/bus - 1:01.01.

    If the envelopes are still there but the track/bus is not responding to them, make sure to enable read automation - highlight the R.

    • Like 1
  2. On 11/16/2021 at 9:19 PM, scook said:

    The item circled in yellow is just an example of a file name generated by the entry immediately above it.

    Given multiple files may be created on export, no attempt is made to show exactly what file(s) are created by the export process.

     

    Got it.  Thanks.  When I saw that I just got frustrated and manually named the track - never bothering to actually try the export until recently.

  3. Hi Folks,

    Whenever I try to export a mix using the tag “{trackname},” I always get the name of the first track in the project, never the track I am exporting (which is always the last track). 

    If I try to export it using the tag “{clipname},”  I always get the name “. wav”   In both instances, the track and clip names are the same.

    I’m attaching a couple of screenshots that show this. I only want track 42 and it is the only one selected and solo'd, with all others being unselected and muted. 

    Is anybody else having the same problem?  What am I missing here? 

    Thanks,

    Bill Saunders

     

    Track Name.PNG

    Clip Name.PNG

  4. I have had this happen often with Kontakt instruments.  I have solved it by being sure no controllers are mapped to "expression" in the instrument's settings.  If MIDI CC controller 11 is mapped to expression and I don't have any CC 11 events in the track, the instrument goes silent because it needs that input.   If you do want to use expression, then keep it mapped and be sure to input the controller value(s) you want.

    Another thing that is helpful is to look at your event list for the MIDI track and see if there are any MIDI modulators showing up that might be affecting volume - not just #7.  Again, it depends how those modulators are mapped in the instrument's interface.  A track that plays fine with one cello VST may be silent if you use another cello that is a differently mapped.

    Good luck.

    • Great Idea 1
  5. Funny, I just today reinstalled a slimmed 32-bit Ver. 8.5 from my OG CD's - only to use that DSP FX stereo chorus.  I copied my bass track to and fro for processing from CWBL - WITH BOTH OPEN AT THE SAME TIME.  

    Like the Cactus Flower says, it's super simple and CWBL is so solid and immunized.  It will seamlessly open any and all of my Cakewalk  *.bun,  *.wrk  and *.cwp files back to 1996, including all of these in the screenshot below.  But I always keep the original versions (don't save over) to harvest organs from.  And never save a CWBL project with an older version.

    I truly believe there is a warp in the fundamental digital universe that allows us to keep using this constantly evolving and updating WunderMuzikMaker for FRICKIN' FREE.  I mean, I bought my 'lifetime version' well before the last Sonar Platinum, but I never expected those old 12-Toners to last as long as I have.  Thanks Meng, BandLab, Morten and the rest of youze guys.   Truly an immaculate reincarnation. 

    Aloha

    2025641571_OldProjects.thumb.PNG.8595c6b1ff73452c1b4e6ae012584456.PNG

  6. I only normalize a final mix (to -1 dB) before exporting, and then send it out through my mastering software in the FX bin.  I started doing this after reading a post or article by Craig Anderton which (as best as I can recall) suggested doing this.  I've found that normalizing tracks before mixing is counterproductive.

  7. Hi Theme-Heads,

     

    I find that is hard to see the waveforms in an audio clip when I select an automation lane to view.  The duck-poop foreground color and the similarly-valued grey background are hard to distinguish.  I'd like to have more contrast between clip background and foreground in those situations, but I can't find a way to edit them in the Theme Editor or in Preferences>Colors.  Does anyone know where to find and how to change those color defaults?

    Thanks,

    Bill

  8. <<<To me that sounds impossible.  I think you need  Cakewalk support on this one. This sounds like corruption. >>>

     

    There's been a lot of that going around, but there is an update due in Washington next month which may get rid of some of it.  Probably not all.

    • Like 1
  9. On 11/15/2020 at 7:11 AM, tparker24 said:

    There are also several other items involved, like: clip FX,   Key+, Vel+,  and the  new articulations maps. 

    It would be very helpful to have a signal flow diagram to show the paths and the interactions.

    Ahh, I hadn't considered that since I haven't been using those.

  10. MIDI just goes one place - to the output(s) you assign it to.  Its simply digital instructions to your MIDI devices, soft-synths and MIDI-automatable units.  It doesn't get amplified or processed or messed with unless you have MIDI FX in your FX bin,  in which case it make a pit stop there and is tweaked before heading to your output.  Otherwise it doesn't go through any gain staging, busses or other manipulation.

×
×
  • Create New...