AZSlow
AZ Controller plug-in for Cakewalk SONAR => Presets => Topic started by: Hermu on May 12, 2015, 10:42:40 AM
-
Preset for NOVATION Impulse 49/61 to use in DAW-Mode
Last Update October 15, 2017:
- additional functional improvements
- Track, Bus and ACT mode support
How to use:
1. download and install latest AZ Controller version
2. Connect NOVATION Impulse 49/61 with BasicMIDI Setup
3. Start Cakewalk and load a Project
4. use Cakewalk Plugin Manager and import "Novation Impulse 61.spp" for AZ Controller
5. configure AZ Controller and assign NOVATION Impulse 61 Input-/Outputport
6. after attached plugin "NOVATION Impulse 61" is selected and loaded, NOVATION Impulse 61 is initialised to use in DAW-Mode
the NOVATION Impulse 49/61 buttons Mixer (near the faders) and Plugin (near rotarys) are now on and can be switched on/off
if NOVATION Impulse 49/61 did not work, please check connection and port assignements.
Preset Configuration (Mixer and Transport):
Mixer=On
Plugin=On
SHIFT:
=====
[Shift]+[Track >] - Shift Mixer to next track
[Shift]+[< Track] - Shift Mixer to previous track
[Shift]+[Bank ^] - Shift Mixer to previous track -8
[Shift]+[Bank v] - Shift Mixer to next track +8
[Shift]+[Page ^] - Select next Bank 1..4
[Shift]+[Page v] - Select previous Bank 4..1
[Shift]+[Button 2] - Select Mode: Track
[Shift]+[Button 3] - Select Mode: Bus
[Shift]+[Button 4] - Select Mode: ACT
[Shift]+[<<] - Goto Previous Marker
[Shift]+[>>] - Goto Next Marker
[Shift]+[Stop] - Goto Start
[Shift]+[Play] - Set Marker, Marker can also be set during playback
Bank select:
========
[Shift]+[Page ^] - Select next Bank 1..4
[Shift]+[Page v] - Select previous Bank 4..1
Button select:
=========
Mutes/Solos button switches Mute/Solo button functionality
Bank1,2,3:
- Button: Off = Track/Bus: Mutes - ACT: actual values
- Button: On = Track/Bus: Solos - ACT: actual values
Bank4:
- Button: Off - Track/Bus: Select Track/Bus - ACT: actual values
- Button: On - Track: Rec.Arms - Bus: Solos - ACT: actual values
Mixer:
====
Fader 1..8 - Track Volume with Track Select for Track 1..8
Fader 9 - Main Volume for Stereo Master
Encoder 1..8 - Encoder Value for Track Pan, Bus Pan and ACT Values
Mute/Solo 1..8 - see Button select
9/Master - see Button select
Transport:
=======
<< - Rewind or stops playback on actual playback position
>> - Forward or stops playback on actual playback position
Stop
Play - Start/Pause playback or stops active rewind/forward and continues playback on actual position
Loop On/Off
Record
-
I've been using this with my Impulse 49, and it is REALLY nice -
Thank you for the work that must have gone into this!!
One problem I have noticed -
Whenever I use the template with Sonar, it remaps the MIDI channel of my Mod Wheel.
Instead of Channel 1, like all the other controls, it changes the mod wheel to Channel 3.
I have to do a factory reset on the Impulse 49 to get the Mod Wheel channel back to Channel 1.
I'm still very new to the AZSlow plugin, so any tips on how to address & correct this issue would be appreciated.
Thanks!
-
Hermu's preset just activate one of Impulse presets, it does not remap anything. So you can reconfigure MIDI Channel for ModWheel on Impulse itself, the change can be saved and so it will be permanent.
My answer is based on Impulse documentation and how I understand it, in case that does not work or you need more precise instructions, try to ask on Novation related forums (I think that is not DAW).
-
Appreciate the quick feedback!
Unfortunately, this issue does appear to be caused to the control surface plugin preset -
I can do a factory reset restore for all the Impulse 49 settings, and everything reverts back to MIDI Channel 1, including the Mod Wheel channel.
(I'm using the default "BasicMIDI" keyboard preset on the Impulse)
Using the same Impulse keyboard preset, if I launch Sonar without the control surface setup, everything is sending MIDI Channel 1, as expected, but of course none of the mixer functions are mapped.
Using the same Impulse preset, as soon as I enable the control surface settings using this plugin preset, all the mixer and other keyboard functions are enabled properly and transmitting MIDI Channel 1, but for some reason the template resets the Mod Wheel to MIDI Channel 3. I have to manually reset the Mod Wheel to Channel 1 - but the plugin preset sets it right back to MIDI channel 3, which definitely causes a problem when trying to use the Mod wheel with my synth plugins and external hardware.
Note that once the MIDI channel is changed by the plugin preset, and with the keyboard still at the default "BasicMIDI" preset, the Mod Wheel remains on Channel 3 even after I exit Sonar, until I manually reset the keyboard settings (i just use factory restore - quicker that way...)
I don't know if using the Impulse 49 with the Impulse 61 plugin preset might be part of the problem, but I haven't had the chance to spend much time with the plugin at this point, and am a bit of a loss a to where to look to try to figure out which settings are causing the Mod Wheel to change from MIDI channel 1 to Channel 3. So far, it appears that the Mod Wheel is the only control MIDI channel that appears to be changed by the plugin preset; all the other controls appear to be working as expected.
Appreciate the help with this!!
-
If you send me the documentation with SysEx sequences to change Mod Wheel channel (I have not found such information in the user manual), I (or you) can check where it is sent. Hermu is sending some text messages (for display), may be one of it by mistake change the channel.
-
I have found interesting thread: http://www.kvraudio.com/forum/viewtopic.php?f=259&t=422120 (http://www.kvraudio.com/forum/viewtopic.php?f=259&t=422120)
Some part is about some other script for some other DAW, but symptoms are the same: as soon as DAW connects, Mod Wheel is on channel 3. Unfortunately, there is no solution in this thread.
Other thread: http://forum.novationmusic.com/forums/impulse/impulse-61-modulation-wheel-problem (http://forum.novationmusic.com/forums/impulse/impulse-61-modulation-wheel-problem)
I do not have the device, documentation is not detailed and I have not found the protocol specification. I hope Hermu or someone else with Impulse can help or I have just missed something in google.
-
Well bummer -
I was hoping this would be a fairly quick fix. :(
Not having a usable mod wheel on my primary controller is kind of a big deal -
I'll start a template from scratch and see if I can come up with something usable ;)
Thanks for the assist, all the same!!!!
-
No need to start preset from scratch...
Open "Feedback" tab and find '_Init::Timer" (the first). Then delete 2 first actions (2 SysEx marked "Init"). Restart Impulse (so ModWhell is on channel 1). It can happened that your controls will not be assigned correctly with (impulse) preset you want to use, you can reassigned them in the "Hardware" tab.
If still no luck, try remove other "SysEx"es from the (AZ Controller) preset.
-
The only place I have found mentioning initialization SysEx is Impulse support in BitWig:
https://github.com/bitwig/novation-impulse/tree/Improvements (https://github.com/bitwig/novation-impulse/tree/Improvements), mentioned in one of the forum.
Impulse has 20 presets, but it can also have some "native" mode (just a guess, no info about that). In any case, the initialization is done with 2 sequences "6 1 1 1" and "7 19" (the rest is SysEx header for impulse). 6 and 7 are "commands" (f.e. 8 and 9 are setting the text on display). So, either "1 1 1" or "19" are real instruction to switch into particular mode.
Can you check which template is active in "normal" factory reset state and after Sonar is started with AZCtrl/Hermu preset? are these the same? If not, may be you just can adjust the channel for Mod Wheel in the Impulse preset in question (in the mentioned thread, with some firmware version, that is not possible to do after the preset is activated from computer. In this case do factory reset and without starting Sonar do the modification: switch to this Impulse preset, modify Mod wheel settings and save the preset).
-
Very strange -
Once the plugin template changes the Mod Wheel MIDI channel, the Mod Wheel is no longer accessible for editing from any of the Impulse built-in templates.
I have to perform another factory reset to recover the ability to change the Mod Wheel parameters.
Based on what little has been discussed on other forums, it appears that the Impulse does have some known strange quirks where the Mod Wheel is concerned.
I can live it for now, since I can force the Mod Wheel MIDI channel from within Sonar and Cantabile, and can do a factory reset if I need to bypass the computer and control my external synths directly.
Other than the Mod Wheel issues, your plugin solves MANY more problems than it creates, and is a huge improvement, IMHO, over the Novation Automap implementation for Sonar. Appreciate all your help!
-
Credits should go to Hermu. But may be to me as well, for patient convincing him to try my plug-in on official forum (I have got -3 votes during that discussion) :)
But have you tried to avoid one or both initialization SysExes?
-
I have a Novation Impulse 61 and have been toying with setting it up in AZSlow (right now, just doing some prelim work to see how it behaves using MIDI-OX). I think I've figured out the problem with the mod wheel (it occurs with the expression pedal and sustain pedal too).
I'd exchanged some email with Novation to try to set the pad colors, and get better control of the buttons and lights in general. In some exchanged emails, they sent me the sysex sequence that puts the Impulse into "Control" mode: F0 00 20 29 67 06 01 01 01 F7. Control mode lets you do a few things you can't normally do: you can directly read almost all the buttons. You can toggle the faders between mixer and midi mode, and read different messages off them depending on the mode; same with the rotaries. You can toggle the lights on the mute/solo buttons (but not on the mute/solo mode toggle, as far as I can tell). You can set the colors on the pads (red/green/amber, varying brightnesses, flash) when they're in Clip mode. Lots of possibilities!
It does come with a drawback - setting that mode locks the mod wheel, expression pedal, and sustain pedal to channel 3, which isn't very helpful! I think that's bug, and I've asked Novation if they know a workaround - no word yet.
However, I found a workaround. You can turn control mode back off (losing all its function, and losing any lighting you did) by sending F0 00 20 29 67 06 00 00 00 F7. (I'll just abbreviate from hereon out - incidentally the 07 19 function referenced earlier in the thread doesn't seem to do anything, and the Impulse doesn't acknowledge it as it does with the 06 01 01 01 sequence, so I don't think it's valid). But it's more granular: each byte controls a single function: it's really 06 aa bb cc. Set aa to 01 and you get full mixer/midi control of the fader section. Set bb to 01 and you get full mixer/midi/plugin control on the rotaries. Set cc to 01 to enable clip mode on the pads and set their colors. And here's the good part: the MW/EP/SP lock to channel 3 happens only if you set all three modes active. If you leave one set to 00 (say, you don't use the pads, or are happy running the faders only in midi mode) then the MW/EP/SP continue to transmit on the proper set channel, NOT on channel 3.
Waiting to hear back from Novation on whether this is fixable, but in the meantime it at least gives me a workaround to play with.
-
Yes, unlike InControl (MK2, but it is almost the same as MK1) Novation has not published AutoMap devices related specification...
Let me know in case you think I can help with something.
Note that I have a bit different approach constructing presets. You can have a look at HUI v2 preset, the idea is to define "generic" action list as a "function" for some control type/group (for example "fader") which depends from one State Set only (logically something like "strip no"). In that case once I want modify the whole group, I can modify just in one place. All final control have the list like "Set StripNo to 5. Call _fFaderActions.". All that is "functional programming" which is as old as computers, the only problem while rather simple for programmers it can look fancy for musicians. That is why I was not using that approach before, but I (and MarKo) was suffering too much from "copy/pasting" action lists. For example in Sonar it is possible to save "FX Chain" preset, which is (with presets in general) a kind of the same idea. But they are not allow to modify preset with effect in all places it is already in use, that will be just "too much programming oriented" :)
Another idea is recently added OSC related. Some phone/tablet logically (and may be physically) glued to hardware controller can add "big HD touch screen" for little money. Since it is possible to use the same preset for hardware controller and OSC, this "display" can show what is going on with controller (mode, bank, parameter names and values) along with additional controls. With (coming soon...) "ACT Fix", that can elevate controllers like Impulse up to NI NKS/Akai Advance level and a bit upper (since AZCtrl+OSC+HW controller is Sonar "native" approach unlike plug-ins only oriented other solutions). I do not have any example yet (the only published OSC preset is "stand alone"), but I have a plan to make one (MPK Mini + Android tablet).
-
Hi all, I'm trying to get my impulse 61 running. I've got it in DAW mode but have the modwheel problem. I want to try cbarn's workaround, but I have no idea how it's done. I found info on manually installing firmware on Novation's website, and downloaded MIDI-OX. It sounds like this will do what I need, yes? -Or is there an easier way?
And so, if I want to set the novation to sacrifice the pads in order to have everything else functioning correctly, I need to send this:
F0 00 20 29 67 06 01 01 00 F7 -is that correct? Do I need to do or send anything else? Or can I just send that string and everything will be awesome (except for no pads)?
FOLLOW UP: Okay, I think I've got it working, though for some reason the modwheel is now set specifically to control the fader on track 2, and if I move it while I'm in a plugin or soft synth, it STILL controls fader #2 and causes the Impulse to lose focus and stop working as a midi keyboard until I close and reopen the soft synth. ...so now I'll go find out how to remap it and hope that fixes this new problem. :)
-
Looking at the preset, I guess I understand "Mod Wheel problem" now... The problem is in the default Impulse Control mode mapping, in this mode:
Fader 2 sends "Channel 1, CC 1" messages
Encoder 2 sends "Channel 2, CC 1" messages.
But CC 1 IS "Mod Wheel" message! And so "Mod Wheel" on channels 1 and 2 are BUSY. So Novation force real ModWheel to the first free channel, so channel 3!
In case you "manage" to avoid the change of MW channel, if it sends default signal "Channel 1, CC 1", it is still mapped to the second fader. So your last update confirm my theory.
And so I see only 2 possible scenarios:
1) you are ready to accept ModWheel on channel 3. In Sonar you can force the channel in the Track settings. So only in case you want to use your hardware Synth IN PARALLEL with Sonar that can cause problems.
2) find the way to change Impulse Control mapping and force channel movement... as discussed before, not sure that is possible at all
Note that current preset put Impulse into Control mode and keep it there... Buttons "Mixer/MIDI" and "Plug-in/MIDI" are not doing anything. It is possible to switch Impulse into normal mode on Project closing or on some button press (sending 6 0 0 0). But that will not unlock Mapped in AZ Controller messages, so you will need to configure MIDI mode to send other messages. For the same reason, ModWheel should still be on channel 3. I had long time plan to enable message unlocking in AZ Controller, may be will do this soon...
-
I have started implementing "midi throw" capability in AZ Controller, so this weekend I will probably make some preset...
-
Required functionality is implemented, but I have to many questions about Impulse to modify the plug-in based on what I already know.
If you (or someone else with Impulse) have network connection from DAW computer and can install TeamView, we can organize Online session so I can check several combinations (I will remotely modify the preset and you will immediately check either it works and which side effects you observe). I think 20-40 minutes should be sufficient to answer all questions.
We can try to do the same "offline", by me writing questions / test presets there and you reporting the results. But that can take many cycles and a lot of time for me to type questions, explanations what you should try to do, etc...
If you do not like TeamView (I can understand, that is a remote control...), Skype is not optimal but still better then typing ;)
-
Aw man, I hope someone can help with that. Unfortunately I'd have to do it by email. :( Also, I'm about as clueless a noob as you could find right now, so not sure how helpful I would be. I'd be worried that user error on my part may end up confusing your efforts somehow! lol
But if no one else volunteers I'll do what I can. :)
Right now what I'm finding is that I actually have to set the impulse to send everything on channel 3 AND also set the softsynth to channel 3 for the MW to work correctly. I thought I could just set the track to receive omni, but the MW wasn't affecting the synth even though the meters show data going in until I set the synth specifically to channel 3. - EDIT: after some more testing it appears this may be an Onmisphere-specific issue (probably due to the way they've implemented multis), EWQL Play seems to work okay with just setting the track to omni and leaving the Impulse on channel 1...
-
Right now what I'm finding is that I actually have to set the impulse to send everything on channel 3 AND also set the softsynth to channel 3 for the MW to work correctly. I thought I could just set the track to receive omni, but the MW wasn't affecting the synth even though the meters show data going in until I set the synth specifically to channel 3. - EDIT: after some more testing it appears this may be an Onmisphere-specific issue (probably due to the way they've implemented multis), EWQL Play seems to work okay with just setting the track to omni and leaving the Impulse on channel 1...
Have you tried to set MIDI track to channel 1 (in the track inspector, where you have "C: None")? That converts ALL information which is sent out of the track (so, before it is entering any synth) to this channel. So MW on channel 3 also become MW on channel 1.
That approach is also rather handy for multithembral instruments (f.e. TTS-1, SampleTank, etc) since you can create several tracks with output to one synth, force each track to one specific channel and do not bother about real data channel (so you can record all tracks from one MIDI keyboard without changing its settings).
-
Also lets try to clarify things by mail. You will need no extra knowledge, just carefully follow instructions and answer on questions.
For all test, Novation should be in the mode set by unmodified latest preset (at the moment, the preset from the first post of this thread, but once we progress I will upload other test presets).
Also please use the latest AZ Controller version (0.5r1 at the moment).
The sequence:
1) open AZ Controller preferences and local "Last MIDI Event section" (near top of the window)
2) move the first fader, notice what you see as the Last MIDI Event (the information before 'value', the value will change when you move it but the rest should stay the same)
3) press "MIDI" button on the left side from faders (under "Mixer" button)
4) move the first fader again, notice what you see now
My questions:
a) "Mixer" and "Midi" buttons have leds. Is either from them lit before step (3) ? Are there any changes in these leds after you have pressed MIDI button during the step (3) ?
b) are there changes in what you have observed during steps (2) and (4) ?
-
Sorry for the delay! :-[
"Have you tried to set MIDI track to channel 1 (in the track inspector, where you have "C: None")?"
Maybe I'm misunderstanding, but that doesn't seem to work. If I set c: to channel 1 and the Impulse is NOT set to channel 1, then I get nothing. If I then set the impulse to channel 1, we're right back where we started with no modwheel.
"a) "Mixer" and "Midi" buttons have leds. Is either from them lit before step (3) ? Are there any changes in these leds after you have pressed MIDI button during the step (3) ?"
Yes, the mixer button was lit before step 3, which is how it defaults when I open SOnar. The only led change is the midi button lights up when I press it, after that the leds do not change, the midi light stays lit.
b) are there changes in what you have observed during steps (2) and (4) ?
STep 2: midi event is ch:1 cc:0
Step 4: midi event is initially ch:1 cc:33 until I start to move the fader, then it jumps to ch:1 cc:11
EDIT: Something I just noticed: during Step 4 I see the mute button led for fader 3 flickers on and off.
-
Sorry for the delay! :-[
No problem, nothing in my life depends from Impulse 61 since I do not have it ;)
"Have you tried to set MIDI track to channel 1 (in the track inspector, where you have "C: None")?"
Maybe I'm misunderstanding, but that doesn't seem to work. If I set c: to channel 1 and the Impulse is NOT set to channel 1, then I get nothing. If I then set the impulse to channel 1, we're right back where we started with no modwheel.
There is some misunderstanding... I attach a picture. So in the upper part I set the channel (on this picture "channel 4 for Sampletank") and in lower part I set input to Omni.
My MPK mini was set to channel 16, as also indicated by Sampletank till I set the channel.
So, in total I have configured Sampletank (one instance) with Drums in the channel 1, Bass in the channel 2 and Piano in the channel 4. I have created 3 MIDI tracks, routed to Sampletank, and set channels in all 3. My controller is on channel 16. As soon as I focus specific track, I can play/record particular instrument. I do not switch controller, just focus track with mouse.
If that does not work for you, there is some problem in your setup.
For the test:
5. Press "Mixer button". Do you see Last MIDI Event for it? Does LED for Mixer lit? Is LED for MIDI button still there?
6. Move fader 1 again. Is it back to ch:1 cc:0 ?
Overall questions are the following (I want you understand why I am asking all that):
* Do Mixer/MIDI buttons change what faders send ? In one direction or in both?
* Do they both also inform DAW there are operated?
* Do they also operate LEDs on there own?
-
Oh, okay, I see what I missed! Thanks for the info! WHo knows how long it would've been before I found that myself? lol (told you I was a NOOB!) :)
Step 5: if I press the mixer button after doing all the other steps, the last midi event changes to cc:34
Step 6: Yes, it changes to cc:0 when I move the fader
If I go back and forth between the mixer/midi buttons, the behavior I've described is consistent.
So yeah, it looks like the midi/mixer buttons do change what data is sent, both ways, and I'm guessing the initial cc:33/cc:34 is the DAW being informed about the button press? (I notice that when this happens it also says the value = 1 rather than 0 though it immediately changes to 0 when I start moving the fader)
-
Ok, in general that means MIDI/Mixer buttons are operating internally... I have thought I have to do this in preset. So, I do not have to ;)
While I guess channel assignment will solve your PB problem, we can assign "reset" (so disable control, return to the state the device was powered) to something. Let me know if you want that (and have an idea which button we can scarify for that).
-
INteresting... I was actually wondering about a "reset" feature because I've noticed that when I exit Sonar the Impulse stays stuck in whatever state it was left in, with messages scrolling on the little screen and any mute buttons that were engaged are still lit and unresponsive (meaning I can't toggle them off manually by pressing the button unless Sonar is running).
But it's not the end of the world. If that's something you want to add it would be appreciated, but I won't cry if you don't. ;D
For me, I could sacrifice the "roll" button, but the impulse uses it for other things than just the roll feature, so I don't know if turning it into a reset button would cause other problems, especially for those who use the finger pads (I don't).
Either way, thanks for the help, it is much appreciated! :)
-
New NOVATION Impulse 61 preset released
all infos are in my updated 1st post with new updated NOVATION Impulse 61 preset version to download.
-
THANK YOU!!! THANK YOU!!! THANK YOU!!!
I got a great deal on a used Novation Impulse 49 and have been using Cakewalk by Bandlab as it was a great free DAW. But, for the last 3 weeks, I could NOT get these two to interface correctly with each other. The Novation Automap 4 could not see the Impulse 49, and the CakeWalk ACT could not map the faders, rotary encoders or the transport controls.
AZ and Hermu, together you are the greatest!
Thank you so much, nothing else was working
J75Ogden
-
will this works with Impulse 25 ?
-
will this works with Impulse 25 ?
Original preset is oriented toward faders and buttons under faders. Since Impulse 25 has no such controls, the functionality is original preset is not practical. It has to be reconfigured to work in one strip mode (using the only fader and its button) or in 4 strip banks (4 encoders as faders, 4 as original encoders).
So short answer is no, it will not work as described out of the box.
-
thanks for replying. so how can I reprogram it ? is there a way i can learn how to manually create a preset and assign my controla to actual functions ?
-
Documentation and Tutorials explain how you can created good preset for any controller. But depending from complexity you want to achieve, be prepared to invest some time.
Without minimal background in MIDI and programming, that can be difficult.
-
Can't see anything on the Impulse or in cakewalk to show it is working.
I don't have a clue how to use this.
:'(
Is there a guide for dummies?
Or are we left to rot in the corner?
-
Have you done the installation sequence mentioned in the first post?
So AZ Controller should be installed and instantiated inside Cakewalk, pointing to Impulse MIDI IO. Preset installed and selected.
If yes, I can help to troubleshoot why it does not work. If no, write which part of the installation sequence is unclear.
-
Please stop spamming all places you can find about the topic and explain at which stage you are stuck with setup. Assuming you are not 2 years old... because in that case it will be difficult to proceed.
-
Hi,
Does this preset already have the mappings for the built in Plug-Ins?
I'm looking at the SI-Electric Piano and in AZ Controller GUI I can see in the ACT tab it looks like there are mappings but none of the Plug-In params change when I turn the rotors.
Thanks,
Kevin.
-
Hi Kevin,
AZ Controller presets do not come with plug-ins mappings. You need to "ACT learn" plug-ins you want (eventually use AZ ACT Fix utility, to backup/fix/clear/create mappings).
Usual procedure apply, as described in Cakewalk documentation. Important to set your controller (the preset) into ACT mode. You should see the mode on AZ Display (not the same as ACT tab in AZ Controller GUI, see the first post in this thread).
In short, once you switch controller to ACT mode, press "A L" button in plug-in window, move parameters in plug-in with mouse, turn/move/press corresponding controls on device (in the same sequence), press "A L" button again, confirm assignment in appeared dialog, done.
PS. Note that such way produce different result from MIDI learn inside plug-in. ACT is used to control parameters throw automations, MIDI does that throw the track MIDI input. In case of software instruments, MIDI learn sometimes is preferred way for recording performance (simper to edit in PRV to sync with modified notes). I do not think this preset supports switching controls into MIDI mode, so you will need to switch on the hardware side (so controls are sending events not defined in the preset). That is just for info, not to confuse you ;)
-
Thanks for the reply. I noticed that if I change:
Overview -> Current Software State -> Mode
From Track to ACT then controller works on the Plug-Ins (but no longer on the Mixer) based on the mappings in the ACT tab.
I guess the question now is, is there a way to toggle between Track/ACT quickly?
Thanks,
Kevin.
-
The documentation is in the first post, from Hermu. Including:
...
[Shift]+[Button 2] - Select Mode: Track
[Shift]+[Button 3] - Select Mode: Bus
[Shift]+[Button 4] - Select Mode: ACT
...
-
Thanks! I did read the whole thread a couple of times - guess I missed it - just a lot to take in :)
-
So far, so good. I just need to know where the Novation Impulse .SPP located.
Thanks!
-
You can download it from the first post in this thread. Then you have to import it using Cakewalk Plug-in Manager (from Utilities menu in Cakewalk)
-
Thanks, AZ! Went by it several times. Sorry to be such a newb :o
-
Thanks, AZ! Went by it several times. Sorry to be such a newb :o
Don't worry, I have written AZ Controller mostly because I have not understood Cakewalk documentation about control surfaces. Only after I have written "ACT MIDI explained", I have realized for my purpose Cakewalk own plug-in could be sufficient. 8)
-
I finally got this working with Cakewalk by Bandlab but there are two problems.
When I turn the Master Fader or volume slider 9 on the Impulse to minimum and turn track 1 up on the Impulse,there is still sound coming out of the right speaker,the left is muted like it should be.
Also when I move ENC 1 (pan) to the right on the Impulse and turn down slider 9 (master Fader),I still hear the right channel,it is only when the left channel is set to 0 with the master fader (Volume slider 9)set to 0 -INF that there is no sound.
Awesome utility besides those two issues.
P.S. I am using the latest beta version of AZSlow.
-
That is a combination of preset definitions (which you can change... well, with some effort ;) ) and Cakewalk long existing definitions (from Sonar, but still in CbB).
In the preset from the first post in this thread Fader 9 is controlling the first WAI Main (hardware) channel. By default, that will be left channel of the first pair of outputs of your audio interface. By default, hardware outputs are not linked in Cakewalk (there is an icon to link them), so the right channel stay untouched.
Usually Cakewalk users are not touching hardware outputs in projects, leaving them at 0dB. For the purpose of "Master" volume people use a Bus named "Master". AZ Controller supports "named strips", so the preset can be changed to control the bus "Master". But the author of this particular preset has decided to control hardware output (probably he link them). Everyone is free to have own approach 8)
-
That is a combination of preset definitions (which you can change... well, with some effort ;) ) and Cakewalk long existing definitions (from Sonar, but still in CbB).
In the preset from the first post in this thread Fader 9 is controlling the first WAI Main (hardware) channel. By default, that will be left channel of the first pair of outputs of your audio interface. By default, hardware outputs are not linked in Cakewalk (there is an icon to link them), so the right channel stay untouched.
Usually Cakewalk users are not touching hardware outputs in projects, leaving them at 0dB. For the purpose of "Master" volume people use a Bus named "Master". AZ Controller supports "named strips", so the preset can be changed to control the bus "Master". But the author of this particular preset has decided to control hardware output (probably he link them). Everyone is free to have own approach 8)
Aaah,I get you.
TY for the quick replay.
So I need to create a new software Master bus and assign split left and right channels to that bus as Channel 9 is controlling the hardware master bus.
I have an old E-MU 1212m card.
I can create an extra asio channel strip in the E-MU Patchmix and make a master bus from that.
Will the AZslow channel 9 recognise the new master bus or do I need to do some fiddling under the hood?
-
The simplest you can do is just press "Lock" button in the Main section, to lock left and right channel of E-MU output. Fader 9 continue control just left one, but since they are locked it will work as expected.
If you go "Master" bus approach, the preset has to be modified. You don't need any new strips, just create a new bus "Master", move it to the first position (in the Track view) and assign its output to your usual hardware output. Everything else should be routed to that bus.
Open AZ Controller GUI, click on "Logic" tab, select "_fFaderPar(_Ch)" in the Logic Control section, click on "_Ch:9 - WAI Master Volume" action in the list, in the Action configuration section change "Master" to "Bus" and "<First in WAI>" to "<First>".
If you don't want "Master" bus always in the first position... Click on "Options" Tab, in "Software States" section select "<New set>" (in the first drop box), type "_BusName" in the input bos right of it, press "Save". Modify "Default" in the input box to "Master" and press "Save" again. Return to the "Logic" tab and change "<First>" to "_BusName". "Master" will appear on the right (since that is the only choice).
-
You are a legend TY.
I tried the first approach ,I did not need to add a Master Bus in the track view,the master Bus is first in my console view but changing those parameters fixed the pan and balance issues.
Thank you very much.
-
Getting problems with the Mod Wheel and Sustain pedal playing on midi Channel 3 instead of 1 with this latest preset and last release AZ Slow.
-
Do you mean it was working differently with some previous release?
As you can see on the first 2 pages of this thread, once Impulse is in DAW mode, it use channel 1 messages for DAW controls. And so it sends "normal" modwheel to channel 3. From my understanding, that can't be fixed by preset in AZ Controller.
You can force channel for any track to 1, so any message will be as from channel one (you will need to use Cakewalk MIDI plug-in to render that permanently into MIDI items).
-
I have the latest release version installed.
I reset my Impulse to factory settings and upgraded the Impulse firmware.
Then I open Reaper to test the sustain pedal and mod wheel.
All is working fine.
Then I open Cakewalk,assign the Impulse to use the AZSlow in the usual way.
Then I test my Impulse and the Sustain and Mod Wheels no longer function.
AZSlow kills the Sustain Pedal and Mod Wheel in other DAWs as well.
Then I have to reset the Impulse to factory settings again to get my Sustain pedal and Mod Wheel back again.
I am on Windows 11.
P.S. I tried just re setting the Impulse to factory settings then using AZ Slow but the problem still remains.
-
"AZSlow" is my nick... And I don't kill anyone. What you try to use inside Cakewalk is "AZ Controller", the program I have written.
Also the preset you try to use is developed by Hermu, not by me.
So you can also write Windows 11 is killing you Sustain Pedal, just because Cakewalk is working inside, AZ Controller is working inside Cakewalk and preset is loaded into AZ Controller.
Or you can blame your computer manufacturer...
Note that nothing is "killed" and you don't have to do full factory reset. The reason and how to get it back from the DAW mode is mentioned on the first 2 pages of this thread.
Do you use HUI firmware on the controller and HUI plug-in in REAPER? Then Impulse should have 3 MIDI inputs/outputs, one of pair is HUI and you can try to use HUI preset for AZ Controller. It has limited functionality, but I guess your pedal and mod wheel can stay on channel 1. The preset in this thread is not working in HUI mode.
If you use Impulse DAW mode, both controls are on Channel 3. Novation decision. That is not a bug in AZ Controller nor inside preset from Hermu.
-
I'll give it a miss for now.
All good.
Kill has many meanings mate.
;D