Jump to content

msmcleod

Staff
  • Content Count

    3,082
  • Joined

  • Last visited

  • Days Won

    22

msmcleod last won the day on January 16

msmcleod had the most liked content!

Community Reputation

2,057 Excellent

9 Followers

About msmcleod

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you want events to be copied as well you need to have the "Select Events with Sections" checked, or selected within the select module: When this is checked, click the section toggles between selecting the section with and without events. Before you execute Duplicate, check the events are actually selected:
  2. This is something that is on our "to do" list, but for the time being what I do is store the following in separate folders for each configuration: Cakewalk.ini (general cakewalk settings) TTSSeq.ini (MIDI device settings) Aud.ini (Audio device settings) If you're using a control surface, also copy ctrlsurface.dat Before starting Cakewalk, I just copy the relevant set files to %APPDATA%\Cakewalk\Cakewalk Core As @Promidi has said, you could create a batch file to do this for you. One thing I would add though, it's important that: - You always use the same USB ports - If possible, start up your machine with all the relevant devices connected so that they're always picked up by Windows in the same order
  3. Cakewalk should work with any controller that offers Mackie MCU emulation, however unless it specifically offers a SONAR or Cakewalk mode, some of the buttons may not do the same thing as what is labelled on the unit. There's usually overlays you can get that will show the correct button mapping for Cakewalk. In saying that, Faders, Pan and Transport control & Jog Wheel should all work fine regardless. Also, if you're using a unit that doesn't specifically support SONAR/Cakewalk, you'll probably need to check the "Disable Handshake" option within the Mackie Control properties dialog within Cakewalk.
  4. Some plugins simply do not work well with up-sampling. In particular, most 32 bit bridged plugins end up playing twice the pitch... I suspect a similar thing is happening with H-Delay.
  5. FWIW I really wouldn't recommend the Realtek ASIO drivers (unless they've been updated/overhauled recently). I had no end of problems with sluggish UI and hangs using it on one of my laptops (it's a pretty high end i9 laptop too). Switching to WASAPI solved all my issues.
  6. I quite often use virtual instruments for writing, then re-record with real instruments; the exception being drums, as I've only got an electronic kit, and perhaps acoustic "strummed" guitars, cos... well, they sound a whole lot better than my £300 acoustic does! But the beauty of instruments like NI Session Guitarist/UJAM Virtual Guitarist is that they provide some interesting riffs I wouldn't normally come up with. That's not to say I always keep the riffs as they are, but they're a great starting place for getting the creative juices going. In some cases though, they're bang on the money and I'm happy to use them as is.
  7. Yes, the chips are the same - just incompatible code. I think the PWM chips are actually the same too, but there's no way to change the code on them. FWIW I found the upgrade pretty straightforward. I got the updated IC's from here: https://www.ebay.co.uk/usr/knight-commerce?_trksid=p2047675.l2559
  8. Yes, that makes total sense.
  9. I used WDM mode with my two DS2416 cards for nearly 20 years. It worked perfectly.... actually it still does work perfectly on my Win 7 32 bit boot. The downside was plugin latency (esp. VSTi's), but then with dynamics/eq on every channel, plus 4 fx processors, I hardly used plugins at all in those days.
  10. Unfortunately, you not only need to buy the new v3.0 chip, you also need to buy new PWM chips as well, as the major change in the v3.0 firmware was how it deals with the fader calibration/sensing (the two PWM chips control the motorised faders). Unless you've got faders that are buzzing/unable to stay in the same location, there's really no need to upgrade to v3. There's no new functionality other than how it handles the faders. I would however recommend upgrading to v2.1.2 via Sysex. IIRC v2.1.0 was incredibly sluggish. https://supportloudtech.netx.net/loud-public/#category/11397
  11. This is absolutely correct. Workspaces are for limiting/removing areas of functionality so you can focus on a particular workflow task. The idea being, that if the various modules / menu functions you don't need are hidden, it's easier to find the functions you do need. Workspaces are global settings which are completely project independent. It's up to you whether the workspace overrides the project layout or not. Screensets are project specific, and are for providing different layouts within that project. I tend to use my own project templates so that the screensets are at least similar between projects.
  12. FWIW my Windows 7 machine works absolutely fine with the latest CbB. The link you've posted saying Edge isn't supported by Windows 7 is over three years old. The Edge browser was included in one of the final Windows 7 updates just before update support stopped. It's running fine on my Windows 7 machine. The CbB installer gives a clear warning at the start of the installation that Windows 7 is no longer supported. All that means is we don't test it any more. I've not found any problems running CbB on Windows 7.
  13. Ah... this is a slightly different issue.... You've probably got things set up like this: If it's set to Master, channel 1, then changes to the master volume in CbB end up changing the Left Master output fader of your audio interface. You don't want this. Set it to this: This tells CbB / MackieControl to use the First Bus for the master fader, which is usually the Master Bus. If you're getting random signals from the Mackie on the master fader, inserting a dummy bus before the master bus will mean that it'll control that bus instead (which will do nothing, since nothing will be sent to it).
  14. I've got an almost identical setup to you (i.e. old grey MCU/ XT / C4, with the MCU + extender upgraded to 3.0.0 / PWM to 3.5.0) - I'm also running through a MidiTech (it's the 8x8 tho). I'm not having any issues with mine. I'm assuming this happens with every project, and you've tried it with a blank project with no VSTi's present (and also without MidiOX running) ? If this is the case, it sounds like a hardware problem with the MCU. Each PWM chip controls 4 faders, so the two PWM faders control faders 1 - 4, and 5 - 8. I'm not sure what is used for controlling or sensing the master fader. The first thing I'd try, is to switch the MCU off and just use the XT & C4. If the problem is no longer happening, you know its coming from the MCU. Also double check everything else in your setup. I'm running in MME mode for MIDI as UWP gives me issues with other MIDI interfaces. You could also try an earlier version of CbB, or even Sonar Platinum to see if this makes any difference. The MackieControl.dll hasn't changed in a while, but the automation in CbB was overhauled for 2021.01 - so it might be worth ruling that out. Given that I'm not seeing this issue though, I'm doubtful this would make a difference. In the meantime, the only other thing I can suggest is to leave the master fader disconnected, and insert a new "dummy" bus before the master bus. This way it won't be controlling anything that could be affecting your sound. The only other solution would be to get a used MCU from eBay... but be 100% certain it is actually the MCU first. FWIW, there's a MCU main board on eBay at the moment for £45 : https://www.ebay.co.uk/itm/283941583200 - you'll need to check with the seller that it's definitely an original grey MCU rather than an MCU Pro tho, although from the looks of it (v3.0.2 PWM chips) it's probably an original MCU.
  15. Are you using a workspace? If you are, it's probably applying the workspace after importing the screenset.
×
×
  • Create New...