Jump to content

Bob Greene

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

1 Neutral
  1. I appreciate everyone's input on this topic. I always find these inputs useful. I hope to hear from each of you in the future.... and Tim Smith, I extra appreciate your mix of the Celtic music, which is one of my favorite styles. You have a good ear and talent. Hope to hear more of your material. Thanx again everyone.
  2. I am from the old school of engineers when everything was tape, etc. During this era, there was a problem called 'crosstalk' that would invade your mix if the heads were not aligned correctly... it is when one track bleeds over into the track beside it. This is not supposed to happen in the digital realm, but.... I was doing a setup for a mixdown, setting up a kick>bass gtr 'duck' compressor to make the drums a bit more aggressive beside the bass. I set up my sends on the kick, snare, and HiHat tracks going to the sidechain on the bass compressor at the appropriate levels and noticed that during a part where I had enveloped the drums out at a certain point for the bass to ride with a keyboard part, that the drums were still peaking through onto the bass track. This confused me as digital should have no crosstalk. I began sorting out the 'equal likelihood division' troubleshooting and realized that it was coming from the drum sends that were set on 'pre' to the sidechain bass duck compressor. Then I realized that it must be the attack time as it was set to less than 0.4 msec, so I raised the attack time to 0.7 and this stopped the crosstalk of the drum peaks through the bass track. No matter how many years you have produced material, there is no end to the learning... AIN'T IT GREAT!! Hope this helps someone else in our little world of sound. If you have a similar experience that might help us, please don't be ashamed to let the rest of us in on it. I'm sure many of us could use your knowledge. Have a great day!!! Windows 10 Pro, 64bit, HP Z420 Workstation, Intel Xeon CPU E5-2690 v2 @ 3.00GHz 3001 Mhz, 10 Cores, 20 Logical, 32 Gb RAM KomaTosa Records Staff Donalsonville, GA
  3. TVR Productions, I had the same problem, as the M1 is one of my favorite softsynth plugs. The way I stopped this problem: I went to my PLUGINS Cakewalk folder, cut the Korg folder and placed it outside anywhere Cakewalk would NOT look for plugins. I then restarted Cakewalk and let it tell me that the M1 plugin was not available and ok'd it. Once the project opened, I opened another instance of the M1. , then I took all the MIDI data that had been written for the M1 and put it in the new M1 folder and latched it to the new M1. Then I deleted the old M1 instance. I closed the project and Cakewalk all the way out. Then I replaced the Korg folder back into the plugins folder of cakewalk. I then fired Cakewalk and the projects in question and they now worked fine with all my presets that I had saved beforehand. I re-added M1 on several projects, as I use it a lot, before I put the Korg folder back into the plugins cakewalk folder. So, if you have several projects with the M1 , make sure you fix everyone of them before replacing the plugins back in, as I did. Otherwise, you will be repeating these steps needlessly multiple times... lol . If this for some reason doesn't work for you, please let me know. I will try to help you as much as I can. Windows 10 Pro, 64bit, HP Z420 Workstation, Intel Xeon CPU E5-2690 v2 @ 3.00GHz 3001 Mhz, 10 Cores, 20 Logical, 32 Gb RAM
×
×
  • Create New...