Jump to content

Andres Medina

Members
  • Posts

    708
  • Joined

  • Last visited

Everything posted by Andres Medina

  1. Ok, I did a few additional tests: I got the same error as yours only if I create a new audio track and that track has any instances of Console Emulators already created (I guess this happens when the default audio track is setup with this module by default) - in this case it should be definitely be a bug! If I insert a new audio track with no instances of Console Emulators and the I add those, the behavior is normal, no errors. If I delete the default instances of Console Emulators and insert new ones, the behavior, again, is normal. I think this explains why your error is not replicable by other users? Could you try and verify this?
  2. I see. I tested the same module in the tracks section of the console. It worked as expected too, using both Bus and Channel versions. Are you sure you are Ctrl+Clicking while selecting the Types? And are you sure you have all your tracks selected before doing that? I've done both mistakes before! Video 3.mp4
  3. ... you say Channel Console Emulators: in fact they should be Console Emulator BUS. You could double check this. I get the same malfunction that you describe when using the Channel version. --- The online documentation explain this: Controls There are two versions of the Console Emulator module: Console Emulator Channel. This version is designed for individual tracks. Console Emulator Bus. This version is designed for buses. It contains the same controls as the Channel version, except it does not have a Trim control. https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=ProChannel.10.html
  4. Keni, it's working fine here too... Version 2022.11 Build 021 See video. However, if I insert Console Emulator Channel Module, I get the inconsistency in the Ctrl+Slect. May be this is the culprit: you have inserted Console Emulator Channel Module instead of Console Emulator BUS Module? Video_1.mp4
  5. Yeah, it seems to be offline here too.
  6. Yes, track templates can be as large as you need, comprising several instruments and corresponding midi data, fx, etc. I use them a lot. I even created a BIG orchestra track template, with all orchestral groups already configured. It's not a project template, but a track template. Easy to add to an existing project in one go.
  7. I had a similar problem years ago, and this is what was suggested then and it worked: {in Kontakt] Click on the wrench > INSTRUMENT OPTIONS > CONTROLLER > Uncheck "Accept standard controllers for Volume and Pan" > CLOSE.
  8. I never really used the Track Manager before, and I was missing something great. In big projects, everything gets cluttered very fast. Also, I learned that if you save the Track Manager presets in a Project Template, they are part of every project created from that template. For Orchestral work it's fantastic to shift between different orchestral groups on the fly. Thanks!
  9. I think you can copy/paste the arranger track directly from one project into the other...? I've done it before using copy special - paste special.
  10. PS: There is a new Behringer driver (v 5.57.0), released in May 2023, in case any Behringer user needs to know. It is working just fine.
  11. Thanks Scook! I just found it. When I searched for other ASIO drivers, it didn't show up. I guess it's hidden somewhere! Uff!
  12. I solved it. For other users that may need this, I found this told topic that referred to deleting old drivers, using the REGEDIT. It seems that some old registry sneaked in everytime CW tried to configure ASIO. And here are the steps to edit the registry: https://helpcenter.steinberg.de/hc/en-us/articles/206633450-How-to-delete-old-ASIO-device-entries
  13. UPS! now I need some help here! I modified the AUD.INI file and made a mistake. I had to reconfigure the audio settings and now CW does not recognize my Behringer UMC404HD card, which was working just fine. I unistalled/reinstalled various Behringer driver versions, including the latest (5.57.0) and version 5.51.0 to no avail. Each time I select ASIO, it seems that the driver is recognized as a generic asio driver, and ask me to switch to WASAPI mode. I reinstalled CW (regular install). Something is wrong. Before this, ASIO was working just fine. I'd appreciate suggestions! My system is broken!
  14. UPS! now I need some help here! I modified the AUD.INI file according to instructions, and then I did reset Config to defaults (I think it was a mistake..!) I had to reconfigure the audio settings and now CW does not recognize my Behringer UMC404HD card, which was working just fine. I unistalled/reinstalled various Behringer driver versions, including the latest (5.57.0) to no avail. Each time I select ASIO, it seems that the driver is recognized as a generic asio driver, and ask me to switch to WASAPI mode. I reinstalled CW (regular install). Something is wrong. Before this, ASIO was working just fine. I'd appreciate suggestions! My system is broken!
  15. Yes, that is my method too. I though Scook instructions would spare me this step, but I work with H264 cpdecs, so...
  16. I did try this, but I can access only the trim-in and Trim-out times. Start time is greyed out...
  17. Track Automations=Envelopes When you write an automation, an envelope is created. At least here, it's working as described. Video 1.mp4
  18. Try opening the Automation Lanes. Video 1.mp4
  19. Right. I only use take lanes for recording audio. Always stay in Overwrite mode, for the reasons you say, specially midi. Never used comping recording midi. It's messy.
  20. Yes, sometimes they behave in unexpected ways! Anyway, I find them VERY useful for tracking, specially when recording talent (voices most of all), as I just arm the track and repeat over and over as many takes I want. I configure them to stack the last on top, so, in a way, the last take would be your "preferred take" in the overwriting mode. For me, the beauty of the take lanes is that I have additional takes in the background. Those have saved my day when I find out that my "preferred" take had a noise, or that a word was not clear enough. For tracking guitars, I often end up with two marked "preferred" lanes that I can copy to a different track to pan L/R. I keep record of the pre-selected takes as I go: it saves a lot of time later, and I just delete later the unusable takes. So, I end up with may be 5 good takes for a single line. I think the messy stuff is related to the use of the selecting tool. It can create a real mess. I found out that you can redo your selections from scratch by selecting the whole lane from start to the end. It clears all the messy clips. Take lanes require a different workflow approach. Yours is very straightforward! But I agree that when the lanes get messy, is a headache.
  21. I'm not really sure what are you not being able to do, but watch the videos anyway. If you think of the comp lanes as minitracks contained in a master track, that can be deleted, reordered, etc, it should not be a problem to get what you want. Remember that you must be sure that you are really selecting the right lanes or portion of lanes with the selct tool. You can even add an empty lane and move the clips of other lanes there, to create a single lane, and then delete all others. It will become a "uncomped" track. Video 1.mp4 Video 2.mp4
×
×
  • Create New...