Jump to content

Dave Oliffe

Members
  • Posts

    62
  • Joined

  • Last visited

Posts posted by Dave Oliffe

  1. On 1/27/2022 at 10:27 PM, azslow3 said:

    Since I don't have the device, I can't tell what exactly M-Audio is emulating in Mackie mode. They also don't write that in the documentation. With one fader and 8 knobs it is hard emulate 9 faders and 8 encoders, not to say around 100 physical buttons, jogger, etc. That is why I have written "more or less" work, just the way M-Audio has foreseen. BTW close to the same functionality you will get in many other daws in which this controller works as Mackie (f.e. REAPER and Cubase).

    Just from photos it is clear that this controller is Ableton oriented. No wonder it gives most it can when used there, out of the box.

    MIDI learn technic is good to use with instrument plug-ins. Most of them support such learning. Also changes will be recorded into MIDI items and edited as CCs.
    "Universal" plug-ins control,  including FXes, use "ACT Dynamic mapping" approach. It exists and works well, once configured right.  You can try it if you try "Generic Surface" approach mentioned later. There are long living related bugs, you will need "AZ ACT Fix" utility to use it in practice (some people claim they can use it without... my mapping file was always broken after a while, so without that utility I had no joy).

    For DAW controlling, some (more smart then MIDI learn) integration should be used. If Mackie mode will be "no go" for you, the next bet is Generic Surface. For that you will have to learn more (under 1 hour for reading M-Audio documentation), to make DAW mode on M-Audio not try emulate Mackie and send simple CCs to DAW port instead (any... just different for different controls).  "MIDI learning" inside Generic Surface is then as easy as in VSTi - select parameter, click "Learn", press/turn control, repeat for other controls.

    I don't recommend "ACT MIDI" for that device, that plug-in is strictly 8+1 buttons and 8+8 continuous controls oriented. Your 8+1 continuous controls + 8 buttons + 16 pads do not "fit" into it (multiple "ACT MIDI" instances, suggested by some people, is looking for troubles). If you need the "next level" (so you find Mackie and Generic Surface insufficient), you will need AZ Controller. But that is more then an hour time investment...

    I appreciate your help with this, thank you.

  2. 14 minutes ago, azslow3 said:

    Cakewalk supports a lot of staff, including DAW control and  plug-ins control. Normally it is up to hardware producer to integrate with Cakewalk (you pay them, not Cakewalk). M Audio does not (as well as all other producers).

    Making the device more or less work with Cakewalk takes about 1 minute. F.e. see my post in mentioned thread. Could M Audio at least write that in documentation? Yes, they could. But they have not. Are lengthy changes of setting mentioned in the thread required? Not really. But some people like hard ways.

    Finally, are there some reasons to take "hard ways"? Yes. If you don't like what and how is controlled by default, you can setup it the way it does what you want (from available in Cakewalk features). But that requires background in MIDI and surfaces, as well as time. But primary factor is the wish to accomplish the task. In most cases with Cakewalk and surface, it ends with "I wish someone else has done that already...".

     

    Thanksm, I'll take another look at your comment in the thread. All I want is for one or two of the knobs to control things in Cakewalk - i'm not interested in anything further or more complicated than that.

    Somehow, I've managed to get my Oxygen 25 to control functions in a couple of synths - this is progress! However, I can't get it to control anything in Cakewalk - namely, the pan and send controls on a track. If I could just work this out!! MIDI listen/learn doesn't work.

  3. On 1/25/2022 at 8:58 PM, Mike Z said:

    Hi Dave, this post might be of some use to you.  I struggled to set up my Oxygen Pro 49, spent a lot of time trying out various options. My post linked here covers the steps I took to make it work (more or less, there are still some issues) but take the time to read through the entire thread because there's a lot of good information about setting up controllers.

     

     

    Thanks, Mike. I've actually read and re-read this thread several times, but there's so much of it that just goes over my head, I have no idea and feel nervous about dabbling or changing settings in case it messes something else up.

    I actually installed the free version of Ableton Live Lite which came with my M Audio purchase - WOW! From the get-go, EVERYTHING is in perfect harmony. Even the drum pads lit up in colours I'd never seen and could trigger sounds. Every single knob is assigned already to every instrument or plugin. Fantastic. I really wish Cakewalk had that kind of integration. We shouldn't have to jump through so many hoops. I'm gonna try and learn Ableton - use it perhaps more in the composing/sound design stage, then open it all up in Cakewalk for the mix stage.

  4. 8 minutes ago, Tony Conway said:

    Right-clicking on a slider, knob, etc usually gives you a midi learn option. Then it's just a case of wiggling the controller that you want to use and the PC 'catches on' to what you want to do and pairs the parameter with the controller.

    Hi, yeah this is something I've tried and even this doesn't work. It always used to though, with previous controllers, which is why I'm positive it's gonna just be a silly setting somewhere. 

  5. Hi folks,

    I have 2 controllers, an M Audio Oxygen Pro 25 and an Arturia Keylab 49.

    Both are set up and working in my CbB, as far as inputting MIDI notes using the keys.

    However, I have no idea how to get the faders and sliders set up to control automation changes. I currently have to use the mouse. 

    I've tried and tried to find simple steps to get them working, but everything I find feels complex and confusing.

    Can someone help me out? Surely it's a simple process.

    Thankyou

  6. On 10/23/2021 at 7:17 PM, Nio Sebez said:

    I want to dance. 😉
    Can you tell what kind of drums you have used?

    Hi sorry for the late reply!

    The drums are a big mixture of things. The finger snaps are from a REALLY cool little plugin called El Snappet (check it out, and the others in their range too). There's a LANDR sample in there, then some layers using Lethal - then a lot of saturation from Shaperbox (if you make electronic music, SB is awesome). I like to sit drums in a 'bed' of rhythmical saturation, it just adds to the groove.

  7. 44 minutes ago, Wookiee said:

    The kick sounds a little boxy and lifeless what are you using for it? Very much classic club material.

    Hi Wookiee,

    Thanks for your time. I chose a dusty sounding kick, can't remember where I grabbed it from. I've added some noise and saturation to it also. I agree, it's got some flab to it and doesn't have the attack/squash of many house tracks, but that's what I was going for. I wanted it to actually sound a bit clumsy. 

    • Like 1
  8. Hi folks,

    I find myself trying to find a MIDI Controller that will actually work - I've had to send back an Alesis model and now I've just sent back the Arturia Keylab Mk2. The keyboards themselves work, but unless I connected them via MIDI cable, I just couldn't get them operational just using the USB connection. When connected via MIDI cables, I could trigger softsynths with the keys, but none of the transport controls would work at all and none of the accompanying software to edit where things are mapped, velocity, etc etc would work at all.

    My knowledge of this kind of stuff is very small - I've always had a Roland Edirol PCR 500 - it just plugged in a worked, simple as. But since buying a new PC very recently, this controller no longer seems to be able to connect at all. It won't show up in Cakewalk Prefs as a controller, where it always used to. 

    So I started looking at the the M Audio Oxygen and thought I'd check out if others have had any issues with Windows 10 / Cakewalk. 

    Can anyone here give me any advice before I waste yet more time and money purchasing something that won't work to its full capability? Will the above steps work for me if I get an Oxygen Pro? Losing hope with it! I thought MIDI controllers were more basic than this, they certainly were when I last purchased one (about 8 years ago).

    Dave

  9. 3 hours ago, msmcleod said:

    From what I can gather, I think the MIDI Control Center is used to configure the device - i.e. set the various modes. You should be able to use the MCC to configure the device, then the device should remember those settings from then on.

    But as it doesn't specifically list Cakewalk or SONAR as one of it's listed compatible DAW's, you'll probably find it limited in support for Cakewalk.

    In saying that, it does say it supports generic Mackie Control and HUI.  You may be able to get it to work using either of those modes by setting it up using Cakewalk's Mackie Control Surface, and making sure the "Disable Handshake" setting is checked. 

    As the button layout for the Mackie Control mode is DAW specific, you may find that while it connects, the buttons don't do what they say on the keyboard. So you may want to try HUI mode instead. If you've selected HUI mode, make sure you've checked HUI as the protocol within the Mackie Control Surface dialog.  

    Alternatively, you might want to contact @azslow3 and see if he or any of his users has an Arturia Keylab II profile for AZController.

    Thank you, I've sent him a message to pick his brains. I'll set the keyboard back up and test a few things out, now that I understand a bit more about the MIDI Control Centre. 

  10. 15 minutes ago, msmcleod said:

    As long as the drivers are compatible, and they actually support Cakewalk/SONAR you should be ok.

    For example, I've got a Samson Graphite 49 which has a SONAR mode - this works fine with Cakewalk in Windows 10 both as a keyboard and a controller via Mackie Control.  Pity the keyboard itself is not great - the velocity is so inconsistent, I find it impossible to use for anything other than organ.

    One thing you should bear in mind with these types of keyboards:  The keyboard should present itself as two MIDI devices; one for the keys, pitch bend & modwheel; and another for any knobs, sliders and transport controls.

    You'll need to consult the user guide of the keyboard in question to see how exactly the second MIDI device needs to be set up. Sometimes they have Mackie emulation, in which case you can set it up as a Mackie Control surface. Others just send out CC information, in which case set it up as an ACT control surface, or just use MIDI learn on the fly.

    If they only present themselves as a single MIDI device, then you're limited to using MIDI learn.  Setting it up as a control surface will render it useless as a standard MIDI keyboard, as the control surface will steal the MIDI port.

     

    Thanks for your reply, I almost messaged you personally yesterday because I had seen you supported someone on a different thread who was having issues with the set up of the Arturia Keylab Mk2 - which is the keyboard I have (which is in it's original packaging again now, ready to be sent back). So frustrating.

    So how would anyone know if the keyboard they're buying is even gonna work properly? Unless they ask very specific questions to the manufacturer beforehand. Is this just a Windows 10 pitfall? It just seems crazy to me that something as generic as a keyboard controller could require such a careful selection process. I literally don't know which models to look at now, I need a keyboard controller but have already wasted time and money on 2. 

    Arturia support have just sent me the following response, which I'm guessing is connected to what you mention above...

    """"[IMPORTANT: Keep in mind that Windows is not Multi MIDI, meaning that you can't use a MIDI Device on multiple applications at the same time, so for example you can't open the MIDI Control Center and your DAW at the same time and use the MIDI device in both applications. Before opening the MCC, please make sure to close all Audio/MIDI applications first and when working with your DAW, make sure is the only MIDI/Audio application open.]""""

    So my initial thought on this is: What's the point in the MIDI Control Centre, if I can't use it in conjunction with Cakewalk?! So, say I have a softsynth open and I want to assign certain notes to certain drum pads, I'd have to close Cakewalk in order to do that? That makes zero sense. Am I misunderstanding this?

  11. 1 hour ago, DeeringAmps said:

    WARNING! Incomplete answer

    I have an A-Pro 500 (Roland, labelled Cakewalk)
    With the A-Pro (bear in mind I installed to Win 10 three years ago) you install
    the A-Pro (meaning plug in the usb cable and turn on the keyboard) while connected
    to the internet and Windows "runs" and "grabs" the driver. Evidently that's what I
    did because it works fine (there's also a Cake Control Surface dll that needed installing)

    I guess that is  a long winded question; do the Alesis and/or Arturia have Win 10 drivers?

    t

    Thanks for your answer, so my (very limited) understanding is that class compliant is exactly what you've just described above - it basically doesn't need any additional driver downloads, it just kindov uses it's own (or uses drivers that are already part of Windows, I guess). 

    That's useful to hear the A-Pro 500 works, but I wonder whether Windows 10 has changed lots in the last 3 years and now has compatibility issues?

  12. Hi folks, 

    So in the last week, I've unsuccessfully set up 2 new MIDI keyboard controllers. One from Alesis and the other from Arturia. With both, I encountered the same issue. Both were class compliant USB connections and neither seemed to be able to fully operate or communicate via USB. More specifically, it was the accompanying software or extra features of each model that just wouldn't sync properly. 

    So now I'm left with a brand new all singing all dancing PC, made for audio production, but unable to get myself set up with what I thought should be a pretty basic piece of kit. I've never had this issue in the past. Anyone know what the hell is going on? 

  13. 1 hour ago, chimkin2 said:

    Yes that's what it's used for in Studio One as well..very handy !

    In Cakewalk I have to leave a space and then I use the far end of my project to use for the same sort of thing - It's a bit of a workaround as you do have have to go back and do some housekeeping towards the end so it would be nice to has this type of feature - Good call ! ☺️

    Here is the S1 feature in action

     

     

    Thanks for sharing, yeah that's a step in the direction I'm thinking of. 

    The other thing I could do is just use clip effects, rather than putting FX on the whole track. I could bounce as I go that way.

  14. Is this a bug, or am I doing something stupid? (Probably the latter).

    Sometimes if I try to loop audio, the clip will become a Grooveclip, but it will suddenly shrink itself to a new length, making it totally out of sync. Only sometimes.

    This never happens with MIDI clips, only audio.

    Sometimes, I'm able to stop this happening by Bouncing to Clip a few times, then attempting to Groove Clip it again. Sometimes it just works, other times it doesn't.

    Anyone know what might be causing this?

  15. 9 hours ago, chimkin2 said:

    I think this is a good idea, it sounds similar to the scratchpads in StudioOne ☺️

    Yeah, I think there would be loads of creative possibilities with it. It could be a space which encourages quick, creative decisions - perhaps you'd be able to drag any other audio on top of the clip you're working on and it automatically 'bounces to clip'. It could have splicers, a bit like 'Breaktweaker' to quickly create chops and stutters etc. But everything you do is seperate to your main project, so there's no residue anywhere, less room for mistakes etc.

  16. On 8/15/2021 at 12:14 AM, Starship Krupa said:

    To answer your question of Kevin, I'm not sure precisely what he had in mind, but you could use Archive and Hide as follows:

    Do your usual bit, but after you make the bounce, instead of deleting the original track, click on the "A" button to Archive it , then right click on its header and select Hide This Track. If there isn't already one, you could create a custom keystroke for the hiding part.

    Alternately, instead of hiding them, you could make a folder for archived tracks and send archived tracks to that folder. Use the folder like the Windows Recycle Bin: don't delete the tracks in it until you're not in the excitement of your creative zone and you're absolutely sure. If you need to save screen space, you can even hide the folder. Side benefit: maybe tomorrow you listen to your project and decide you want to do something different with the track that you tortured with your Glitchmachines or Unfiltered Audio fx, it's there in your Recycle Bin folder in its unmolested state.

    (Safety is part of what the Archive function is for, when you're not sure if you want to keep the track, but don't want it sucking resources. I use it all the time to save alternate takes that I don't want cluttering things up.)

    I would find this simpler and less confusing than opening a second project. When I do that I find myself making mix moves on one that I meant for the other, etc. It's for special occasions only.

    Thanks for breaking this down for me, much appreciated. Yeah this could work - it certainly appeals to me when it comes to treating audio with care. I'm often quite cut throat with my decisions and try to bounce stuff down quickly and not allow myself to second-guess it (otherwise I'd never finish anything). However, if I'm handling someone else's audio, what you've explained here will serve me well. 

    However, I still find myself wishing there was something more like my original suggestion. I get the impression there aren't many electronic music makers on Cakewalk, generally speaking - when compared to your Abletons and Reasons etc, so maybe there isn't the demand for such a thing.

    • Like 1
  17. 7 hours ago, noynekker said:

    Hi David . . . had a few listens, and really like the piece, it's got some interesting moments throughout. I don't mind the reverb wash for the instruments, but as Wookiee says, and as you allude to, maybe a bit too much on the lead vocals ? Call me old school, but I really had to struggle to clarify the lyrics, and yeah, I always want to know what a song is about, despite the genre.

    On my headphone listen, couldn't make out most of the lyrics, though, on my small speaker listen, I could hear a few more of the lines. Think you could just bring out the dry part of the lead vocals a bit more more . . . and it would help that first time listen by all who will hear this . . . and I hope it will be many, good luck !

    Thanks for this, I'll definitely bear it in mind on my next mix. I was so hell-bent on achieving a dreamy-sounding vocal that I've sacrificed it's identity somewhat. It's hard when you've written the lyrics yourself isn't it - I guess it creates the illusion that the lyrics are audible.

  18. 6 hours ago, bitflipper said:

    That pop is unavoidable when the audio's numerical value at the split point is anything other than zero, because otherwise you're telling Cakewalk to go from X to nothing in an instant. Speakers can't go from X to zero instantly, but they'll try to comply and move as fast as they can. That results in the pop you hear. It's the sound of your speakers being kneecapped. Ouch.

    The term "zero crossing" just means a point in the waveform where the sample value happens to be zero. It's called a "crossing" because unless the clip is silent that zero value occurs as the waveform is crossing from a positive to a negative value, or vice versa.

    Open Preferences (press "P") and scroll down to Customization -> Snap to Grid. There is a checkbox labeled "Snap to Nearest Audio Zero Crossings". Even if you don't have grid snap enabled generally, with this option selected you'll always select a zero crossing when splitting a clip. No more pops.

    Thanks for this, very helpful. I had a basic understanding of this, but no idea Cakewalk had tools to solve it. I'm guessing that I'll have to be careful when creating Groove clips that the clip is 'numerically' lined up first as the zero crossing is likely to be at a point which isn't exactly in line. 

    Certainly don't want my speakers getting kneecapped anymore, that won't do. I dislocated my knee playing football (soccer) so I know how much that hurts!

  19. Yeah, with electronic drums, it's more about getting out of your own way than anything else.  Use your ears, rather than experience. They rarely need corrective treatment, it's more about personalisation and 'roughing them up' here n there. You almost have to work backwards and think 'how can I make this sound less perfect?'

    I tend to throw them through Decapitator at least 4 times, and put hats and percussion through EchoBoy for some really interesting rhythmical inspiration.

     

    • Like 2
  20. Some really beautiful textures and atmospheres. The lead sounds are complimented by the glittering arps in the background. Very nice! 

    Edit: Also love the throaty depths of some of those bass notes. They really growl!

    • Thanks 1
  21. Since we're thinking of who the vocalist sounds like, I'll add: Eddie Vedder 😜 or the guy from Nickleback.

    I like the song and how the mix allows the vocals to shine. Nice delay on them. They could perhaps be backed off in volume/more verb during chorus for dramatic effect. I think the strings at the start could also come down even 3 or 4 db and still be present.

    The scream at 2.22 needs tuning as it's completely out and takes away from the strength of the song. Also, the very very last vocals are a little out too. 

    Apart from that, I really like it - nice power in the distorted guitars, they really slam home. The drums are almost there - the cymbals perhaps have a frequency that needs cutting in the mid/high region.

    Nice work!

     

     

    • Thanks 1
×
×
  • Create New...