Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by chuckebaby

  1. Not much you can do with a sample that comes in at -10 lufs (unless its being used for EDM, Techno, etc.). You can clip gain the samples to -3 TP (which will also decrease the lufs value) but the LRA (Loudness Range) will not change.

    Seeing a bit more of this lately with people downloading free beats YouTube and layering vocal tracks on top of them. some of mastering engineer friends have asked me the best way to deal with it. There simply isn't much you can do in terms of gain reduction. you might as well throw your limiter in the trash for that session.


  2. I like this idea.

    Objective- I find moving automation nodes to be some of the most difficult work.  Unless you are zoomed in full scale and have a track fully expanded it is nearly impossible to make pin point accurate on node placements. 

    Non objective- If we find ourselves needing to place nodes in the perfect spot down to the precise element of a fraction of a millisecond, the problem is us really. Sometimes we need to just call it a day and throw a node in there. Its not going to make a lot of difference between a millisecond.

    However, i like the idea. Good stuff.

  3. 8 hours ago, Starship Krupa said:

    To elaborate, plug-ins "expose" various parameters to the host (Cakewalk). Mostly this is used for automation. In Cakewalk, we can also access them via the Plug-In Chain feature.

    Unfortunately, to my knowledge, there is no standard assignment for these parameters like there is for MIDI CC's. The plug-in reports them to the host with their full names (whatever the plug-in developer wants to call them) and then the host displays those.

    Of course, with plug-ins that don't have a Wet/Dry control in the UI, it's not likely that they will have them available as parameters, either.

    To do this outside the plug-in is a matter of creating a parallel routing path. To see how to do that with the existing program, look up tutorials on "New York compression" or just parallel plug-in routing. That's the way to do it while you're waiting for CbB to get the feature.

    you are correct, FX chains can and do control parameters, but unless every manufacturer assigns the same wet/dry parameters to each plug in or somehow has a code name to interact with the learn function, its just a mixed bowl of salad. 

  4. 10 hours ago, sjoens said:

    I know I'm alone on this but...

    I was hoping to use alt code symbols in track titles like arrows: "▼" (alt+31) & "▲" (alt+30).

    They can be typed in but don't remain after saving & closing the project.

    Open the saved project and there's a "?" where the symbol was.

    Am I doing something wrong or can we not use special characters?

    The problem isn't really within cakewalk but more windows itself.

    Windows does not allow certain special characters to be used in file names and once a track is stored within the project folder, files are listed by track names.

    I could be slightly wrong here, but i dont think i am.

  5. Using Windows 10 ? try WASAPI exclusive for your driver mode.

    Once i read, plug and play, no drivers need for any product, i run. All good products create their own drivers and keep them updated. Companies that don't do that, often reply on ASIO4ALL or onboard WASAPI. More or less because they don't want to be bothered or responsible for having to pay a software development vendor to keep up with their product.

  6. Now that LUFS has become the industry standard for streaming content, Cakewalk would really benefit from adding in a professional built in meter.

    I know this thread is about VU meters but I'm strictly talking about a hybrid meter that could be designed by Cakewalk for use in the mixing/mastering stages. Giving readings for Peak/RMS, LUFS, The K-system and VU. 

    Personally i use Youlean for all my mastering work.  

    • Like 3

  7. there are so many questions here im not sure where to begin except to say, check out the manual and watch some videos. I went from Pro audio 9 to Sonar 7 and then 8, 8.5 then X1 was the big change, it was a whole new design it took me a while to figure out what was what but once i did, the work flow is 10 times easier then it was back then.

    • Like 1
    • Great Idea 1

  8. I believe this is the limitation of the mackie. you must have stereo outputs 1+2 together and routed directly to 1 stereo track.

    I have a Mackie Pro FX 12 I used to use for drum monitoring and it has the same USB option (stereo output L/R only) through USB.


  9. 3 hours ago, scook said:

    In the tool tip for the - in the lane header.

    And that is what the - on the lane header does. It removes the lane. It does not remove the automation envelope.

    Above, I provided a link to the documentation on deleting automation envelopes.

    It doesnt say.. Remove lane though does it ?

    i thought the tool tip said Automation lane ON / Automation lane OFF

    I suppose i could see this as confusing, i always just took it as the lane was either open/on or closed/off.

  10. Im not sure if this will work or not... but you could make a copy of the file... Change the EXT of the file name from.WRK to.CWP.

    As i said, im not even sure it will work but if it is an extension issue, this might solve it. As i said though.. make a back up so you dont mess with the original /wrk file.

  • Create New...