Jump to content

azslow3

Members
  • Content Count

    334
  • Joined

  • Last visited

Posts posted by azslow3


  1. General channel message is:

    F0 00 00 66 <dev id> 20 <chan> <mode> F7

    • <dev id> "17" for C4
    • <chan> is (if I read the source right) 0...31 for C4
    • <mode> can be 0, 2, 4 or 6. (4/6 - display peak hold, 2/6 - LCD bar graph, whatever that means...). "01" you see for MCU will not work.

    After mode is set, you use:

    [D<row>] [<chan><level>] (2 bytes)

    So "D0 05" means "row 0, chan 0, level 5". For C4 there will be more, like "D1 52" for "row 1, channel 5, level 2)

     


  2. Unlike for original Logic Control (almost MCU Pro),  I have not seen C4 documentation. So the source code is good source...

    Check MackieControlLCDDisplay.cpp, especially SetMeterMode (and called from it SendMeterModeSelect).

    What you mention (0x21) is "Global meter mode" (which declare "vertical" or not). I guess you need channel meter mode (0x20) with proper parameters.


  3. 4 hours ago, Michal Ochedowski said:

    I can't believe that such an advanced DAW doesn't allow a function, which to this day I took for granted. Chaining a few MIDI effects together and being sure that data will be transferred from one to another. Really disappointing.  

    Can you believe such common format as VST no longer allows you to process all MIDI "as is"? You still can process some MIDI messages, but far from all (and everything except Notes is transferred rather tricky way). That is VST3... Note that no new developers are allowed to created VST2 (not possible to sign the license).

    Cakewalk still support DX MFX only, but curiously that can be an advantage in not so distinct future. At least everyone can write DXes without rather "fancy" VST3 license. F.e. everyone who has signed it agree to switch to ANY next format, so VST3.10, VST4, VST5 within fixed time period... Steinberg has learned that declaring VST2 "obsolete" many years ago  does not prevent this format is still in use. So they have decided to solve the problem in advance...

    • Like 1

  4. 7 hours ago, msmcleod said:

    This is the key statement. 

    Anything your create yourself using Cakewalk by BandLab is yours.

    Strictly speaking not everything. 

    Audio and MIDI output created by using Cakewalk is yours, as long as used audio and MIDI material allows that (f.e. mentioned in the license terms to use provided by BandLab content). With that output types user is free to do anything he/she wants.

    Which rights user has for other "outputs" is unclear. At the end of Sonar I have opened a question about user rights over Sonar Projects. User is allowed to use these projects with Sonar (and now Cakewalk, since BandLab has bought rights for Sonar). And user has all rights for the "output" of own projects (mentioned audio and MIDI). What else is allowed to do with these files is not well defined. For myself I came to the conclusion I can use all the information I put into project myself the way I want (f.e. automations, tracks layout, tempo map, etc.). Legal background and related precedents exist in EU. But that is probably not the case f.e. in US.
    Here the evil is in formats: common audio and MIDI formats are open, plug-ins presets standard file formats are property of plug-in format creator (so not particular DAW), text based project formats are also open in general (at least the text related to the user activity can be legally extracted). Cakewalk projects have binary proprietary format (fortunately not encrypted, breaking any encryption is prohibited even in EU).


  5. Please note that:

    • I do not think there are any presets for MMcL (nor original Cakewalk) Mackie control surface plug-in.
    • 'Configure layout' is to set relative physical position for several Mackie devices (f.e. left-to-right MCU+XT+XT vs XT+MCU+XT and so on). Related information is displayed on devices, not on computer monitor.

  6. 6 hours ago, razor7music said:

    So, Editor 5 still $99

    Yup... and Studio €150. While all changes are on Assistant  "level". Version 4 had good cross-grate sales, while quite some features for Studio. Version 5 has  no new editor/studio features  and no sales. Better voice processing is a good thing, but too expensive for noobs like me (just because I like multi-track, so upgraded to Studio before).

    • Thanks 1

  7. I remember up to Melodyne 4 there was clear table with versions comparison. I can not find it for 5.

    I mean they want more for Studio -> Studio then for Editor -> Editor, while I have not found  "Studio only" marks in changes. Sure, I can just demo and check myself...

    EDIT: the table is still there, in "What can Melodyne do?" So all "New" features are in Assistant


  8. You know that Roland has sold Cakewalk, right? And shortly after that Roland has "discontinued" related hardware, including $5k VS-700 (no official Windows 10 drivers).

    You can try to ask for "DAW CTRL" MIDI protocol documentation. Some companies just make that open (Novation, Ableton, etc.), some give it to developers only (NI), but other keep it "secret" (for no apparent reason). That is most realistic way to make transport (and other controls) working with Cakewalk (and most other DAWs).

    FA-x keyboards could be set to Mackie mode, so at least basic transport works. For Fantom Roland mention nothing in that direction in the documentation.


  9. 1 hour ago, Jim Roseberry said:

    You can hear that tiny fan ramping up with CPU usage.  It's high-pitched and annoying.

    ...

    TDP is 125w (about the edge of large/quality air-cooling).

     

    Sorry of off-topic... I have high-pitch noise from my Z390. Not from fan (I have not found any), but still annoying (from googling that is common). And I wish my TDP 95W CPU consumed that 95W by default. My (middle size) air cooler was unable to keep CPU any cool when I was running my fist PRIME95 test... I was disappointed (by the cooler), till I have found that CPU power consumption is over 200W (with all BIOS "defaults").
    I mean it seems like "TDP" has no meaning these days (my 9900K consumes from 10W to 250W at its own will, till limited explicitly).


  10. MPK261 is a flexible device. You can configure what and how each control sends. There are predefined presets for different DAWs, controls are set to send different messages in each of these presets.

    For ACT MIDI configure (or find existing configuration) all controls for sending CC messages. For buttons use "momentary" mode. You can use "relative" mode for knobs, but you need to set parameters properly in ACT MIDI then (in addition to control learning), also they can appear "too slow" for you in that mode.

    ACT MIDI and Generic Surface do not show messages they receive. You can "record" controllers as normal MIDI clip and then check the recording in Events List mode. You can also use MIDI-OX (with Cakewalk stopped) or AZ Controller (inside Cakewalk) to monitor incoming messages "real time".


  11. 5 hours ago, QuestorCP said:

    Are there any controlling surfaces that really integrate to CbB, or is this really smoking dope?

    I have mentioned the whole known set of "supported" keyboard controllers: Roland A and Nektar Impact. Both are limited as hardware (f.e. no encoders) but the integration was provided by the companies. I write "was", Roland is no longer affiliated with Cakewalk and all Nektar's powerful controllers do not support Cakewalk.

    But MPK261 is not a bad choice for controlling Cakewalk. It has capable hardware. The only problem the solution is DIY. So you will need to invest a bit of time to make it work. Depending from what you are ready to sacrifice:

    • you want transport buttons and 24 tracks (with ABC keyboard banks) Volume+Pan+One switch per strip (Mute OR Solo OR Arm, etc): setup Generic surface plug-in.
    • you want overlay the right part section (8 encoders + 8 faders + 8 buttons, NO transport, NO ABC banks) for mixing, controlling plug-ins and executing commands: setup ACT MIDI plug-in.
    • you want all controls, overlay functionality, LED feedback: you will need AZ Controller.

    First two options you can get up and running within an hour. Set MPK261 to Bitwig mode and follow Cakewalk PDF I have mentioned.

    For the third option you start with mentioned preset, that should work out of the box. To extend it or change the functionality you will need to spend significant time (days or even weeks) and without background in programming I would not recommend diving into complex modifications.


  12. Original documentation describes both plug-ins (pages 1215-1228): https://bandlab.github.io/cakewalk/docs/Cakewalk Reference Guide.pdf

    If in addition you want to know how all that works: http://www.azslow.com/index.php/topic,107.0.html

    Well... MPK261 does not "fit" into standard plug-ins functionality. M-Audio support some DAWs, but Cakewalk is not in the list (not a surprise, only Roland and some Naktar keyboards are Cakewalk aware).

    You can  start with: http://www.azslow.com/index.php/topic,393.0.html
    as stated in that post, I do not remember which MPK261 mode should be used. If not Bitwig, that should be some other standard preset. And  I do not remember what this preset does nor which MIDI IO should be set. But it definitively recognize ABC banks and most controls do something useful 🙂

    General installation you can find in "Manuals" section / Videos linked on top.

    (the preset was created long time ago and remotely... I have never touched real MPK261)


  13. Great work! Special thanks for detailed information concerning fader calibration. I have made my preset strictly "remotely" (not seeing/touching the device), so I was not aware such problem exists

    The only general suggesting about functionality: original Mackie was using "direct" API for controlling plug-ins, there was no ProChannel but (fixed positioned) "effects". Cakewalk has switched to ACT mapping approach at VS-700 (and other Roland surfaces) time. There was nasty bug in maps saving for several years, but last Platinum and CbB do not have it. I mean uniform way to control Synth/FX/ProChannel and standard control learning procedure is better (AutoMap, NKS and VIP use the same idea for controlling).


  14. 3 hours ago, Tommy Byrnes said:

    So, I'll take your advice and re-sit and re-thermal paste first, then replace the liquid cooler...

    It sounds more an more you simply have a problem with cooling. To rule out  audio interfaces, Cakewalk, etc., you can try to run PRIME95 (I guess your system will shutdown within several seconds...). But better follow the advise from Slartabartfast, before doing any future tests.

    "Low multicore load" normally consumes less power then one core doing the whole job. That is why you could observe some difference after "balancing" the load using Cakewalk settings. But that is not a solution for your problem.


  15. 11 hours ago, Tommy Byrnes said:

    Thanks, Azlow. I don't think I"ve had any major plugin changes. A few new ones from Plugin Alliance and one from FabFilter, neither of which have caused issues in the past.  The temp starts to spike as soon as I open CbB.

    "Open CbB" is too complex operation for computer, to get reasonable advise you need to localize the source:

    1. Open CbB with EMPTY project. Turn off audio engine. Minimize it to the tray. Any CPU use from it?
    2. Step by step, checking significant CPU load increase:
      1. Maximize CbB
      2. Add several audio tracks without plug-ins, up to your usual number of tracks in the project
      3. Start audio engine (if not started by tracks)
      4. Add some audio clips
      5. Start playback
      6. Add plug-ins
      7. Load your usual project

    Once you notice CPU load, independent on which step, try minimize CbB and then change audio device to build-in.

    That should point which part of the system/CbB triggers high temperature: plug-in(s), graphics, audio interface.

    Sorry for repeat, but from all your previous observations it seems like your system is "fine tuned" for low multi-core load only. I mean if full powered single core overheat, full powered all cores will switch your system off instantly. Can you run PRIME95 for a half an hour? I guess not, and that is looking for troubles.

    FX-8350 is an "old world" AMD CPU. Every surface micrometer has to carry the heat out from TDP 125W to keep "max temp" under 61C. May be it is time to re-mount the cooling head. For comparison: modern AMD CPUs have TDP 105W (real ~150W) and "max temp" 95C. That is obviously way simpler to keep under control.

    My own system is Intel based, ~40C idle. It runs ~70C when "test loaded" under TDP (95W), I can keep it under 85C with power limit 170W. Without limits it can consume up to 250W and my "small" air cooler is unable to deal with that (I have only one case fan). All that without any "manual overclocking", modern CPUs overclock themselves by default...


  16. Is that happens with or without plug-ins? Can it be you had some changes in plug-ins you use (updates or simply changing settings)? As correctly was mentioned by Oleg, CPU consumes different power based on activity. In my case (i9), "100%" CPU tests can consume from around 90 up to 250W (if not limited...), depending from what these tests do.

    Since you mention some interference with graphics, check/update your graphic card driver. F.e.  graphics can switch into "software" mode with bad drivers.

    In any case, if your system can hit thermal limit something is designed/set/assembled incorrectly or broken. No software activity should be able to overheat correctly build system.

    • Great Idea 1

  17. As long as you wrap plug-ins in question into NKS, I think you can control parameters using Komplete Kontrol native methods. If I remember correctly, there is still no "deep integration" for these keyboards into Cakewalk (so there will be no "automatic track following"), but it should work for the purpose.

    In MIDI mode you can use Cakewalk feature called "ACT" ("Plug-in dynamic mapping"). It is available in "ACT MIDI" and "Generic Surface". "ACT" term is also used for surface API in general, so a bit confusing (but "ACT" button on top of plug-ins is for "Plug-in dynamic mapping"). You can easily find many guides in the Internet (and that feature is described in the standard documentation). Plug-in dynamic mapping works for any plug-in in focus (FX, Synth, ProChannel).

    Finally you can use ACT map in AZ Controller.

    You will find many posts that "ACT does not work", "my mappings are not remembered", etc. But that is more for older versions of Cakewalk (there was one nasty bug for several years). And you can move to the "safe side" by using "AZ ACT Fix" (usable with all surface plug-ins) in case you still hit some problems with mappings (or just for convenience... there is no build-in feature to "clean" automatically created and hardly unusable maps, with that utility you can clean, reorganize, backup and one click restore).

    • Like 1

  18. They are remembering current strips. Let say you are working with several not consequent tracks and need to switch between them. You  can temporary reorder them, but that can be annoying. With F buttons you can remember up to 4 strips and switch with one button press. Note that strips can be tracks and buses.

    That was default behavior in the original plug-in, not my idea. I have just reproduced it in the preset.

    • Thanks 1

  19. Track/buses should switch by pressing left encoder (in plug-in/EQ mode works with Shift only, in all other modes with and without shift). That is mentioned in the documentation (and differences list for the preset).

    F1-F8 have "default" behavior from the documentation (save/recall current strip). F1-F4 are recall, F5-F8 (so F1-F4 with Shift) are save. 

    • Thanks 1

  20. 2 hours ago, Steve Owen said:

     Hopefully the SL will be supported soon and in particular the 'In Control' feature - which works like a dream with Ableton.

    msmcleod still updating MCU and partially HUI compatibility.

    Except for Softube Console 1, I can not remember any new device got Cakewalk support from Cakewalk or device producer last 5 (or even more) years.

    That is about the hope it "will be supported soon"...

    Novation is publishing all technical documentation (not many companies do). Cakewalk has public surface API (not many DAWs have that). So THEORETICALLY anyone can write reasonable integration (including LEDs, display, colors and device specific controls).

    In practice only several new devices got reasonable integration, using AZ Controller platform. But that is DIY solution. Not many people was ready to invest significant time and effort to create deep integration. I have written the platform and created several big presets. But I no longer ready to create presets for devices I do not have.


  21. Crashed DAW just because of some MIDI device internal mode is not expected result. It can be you have some "MIDI loop" inside your project, during surface (and other MIDI devices) setup it is better have black project loaded (without any MIDI tracks). Other reason can be some Control Surfaces in Cakewalk preferences (Cakewalk tend to mess with MIDI IO assignments when new devices are added). Finally "starting from scratch" is also an option, after cleaning all MIDI devices in Windows Device Manager and removing Cakewalk MIDI related INI files.

    But in case you prefer out of the box solutions, I agree that FaderPort V2 is not the device to use with Cakewalk. At least till someone make working preset and write/record installation instructions.


  22. Classic had specialized plug-in for Cakewalk. V2 does not have such plug-in and it can not mimic Classic.

    There is no published preset for V2 (at least I have not seen it), but in case you put V2 into some "native" mode (so its controls just send what user is doing, without attempt to be "smart"), you can MIDI re-learn the preset for Classic using V2. That should work, except feedback (Classic designers have made a... mistake... so feedback to buttons does not match commands from these buttons. I think "Use Ctrl" instead of exact MIDI messages in the Feedback section should work for V2.)

    So, definitively manageable (with device in hands) but a bit of DIY. If you have no time nor willing to invest it, I can not help.

×
×
  • Create New...