Please ensure Javascript is enabled for purposes of website accessibility Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Registered Products

jpspoons's Achievements


Contributor (5/14)

  • One Year In
  • Dedicated Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges



  1. @jeffb79I can't remember the setup process now, but if you're being told that you need to do it through the Devices menu, then I think on recent versions of Cubase that's in the Studio tab / Studio setup submenu. Once you've done that setup bit (or even before if you want to check that Cubase definitely CAN'T see Native) then - Add a new audio track. I recommend setting to a stereo track even though you're running mono in, it means you can use stereo effects on an insert without having to mess about in the background - On the track inspector (left hand side) go to the Inserts section, pull down the selector in slot 1 and look under Other - if all is working then Native should be there. Good luck, let us know how you get on.
  2. Quick update for anyone interested. I've made a load of progress on this using MIDI Remote with some great help on the Steinberg forum here: MIDI control of Helix Native in C12 - Cubase - Steinberg Forums There's a "but"... when I close / re-open the project, moving the controller resets the parameter(s) to zero, no matter what their previous value was. Not great when you have a preset built and want to nudge the drive up from 60 to 65, for example! That doesn't happen with "native Steinberg" plug-ins, or indeed other third party plug-ins. If anyone has any thoughts on resolving this I'd be most appreciative. Many thanks, JP.
  3. For anyone following this, I've eventually found a workaround using Cubase's Generic Remote functionality. I've mapped Helix Native parameters to MIDI CC numbers corresponding to the Mobi outputs (although some are reserved by Native eg CC0-4 so creativity is required). Then I've used Cubase generic remote to set up each dial (Thresh, Ratio etc) to send those MIDI CCs to the plug-in, with flags Receive and Relative set. The only foible is that if I change the parameter setting via the software rather than the hardware, it jumps back to the last value set by the Mobi. (This is your point about lack of two way communication I think @soundog?) Still it's usable and if I get it mapped correctly then hopefully I'll default to the unit rather than mouse. Thanks all for the feedback and help with this :-) Cheers, JP.
  4. Hello again @silverhead I'm definitely getting closer, but... The midi track has done half of the trick, thank you for that! I can get the quick controls to work, but I would also like to be able to use >8 rotary encoders. When I set up a dial with either midi learn or specifying the CC number, the signal is sent and received BUT the slider in native doesn't change in increments - it basically flips between 0 and 100. Any ideas? I don't know whether it's a setting in my controller, or Cubase, or Native... Any thoughts much appreciated. Thanks again, JP.
  5. Thank you for this @silverhead- as soon as I get a chance to test I'll report back. Have a great weekend \m/
  6. Hi @silverhead, thanks for this. The controller that I want to use is a Qube Mobi One but I'm guessing the same principles apply. The bit that I haven't tried is setting an automation track, thanks for the tip! Do you run Native as an insert or a send in Cakewalk? Thanks again, JP.
  7. I discovered tonight that if you save a Cubase preset for Native, you can call it up even if you don't save the preset in Native... so you could re-use the same slot over and over again if you wanted to with different presets. I don't know whether this is a known thing or even useful, but just wanted to put it out there and see if anyone else knows / is using this. Cheers!
  8. As per title, any hints on how to control Native through Cubase with a MIDI controller? I can do quick controls, but MIDI remote and even generic remote have so far been beyond me.... any hints would be more than gratefully accepted. Thank you!
  9. Just seen this, don't trawl the Native forum but about to post so spotted it. I took some backups from 2.80, is this it? @a6strng Kashmir.hlx
  10. jpspoons

    Helix 3.5

    In fairness to the OP, I think he was referring to the pinned threads. And as @PierM states, the 3.50 release notes aren't up there in the same way that the 3.15 and earlier version were. @rwinkingthe release notes seem to be standalone rather than posted into this forum, you can find them here: Helix 3.50 Release Notes - HELIX/HX - Line 6 Community And as others have stated, if you scroll down past the pinned threads, you'll see a multitude of user threads about 3.50. HTH
  11. Noted, sign me up :-) So then @craiganderton, what new chapters will there be in v1.2 of Helix Tips to cover the forthcoming new features in 3.20? (Worth a try!)
  12. I guess I'd been thinking that my preset outputs were ok at analogue level, but needed an increase to hit the "optimal" digital level (Powercab amber) - and I was hoping to use the digital output global to do this without impacting the analogue output level. So now I think - I could probably go into each preset and change the output block level like @PaulTBaker , without adversely affecting my XLR outputs after all. Or... - I could increase the digital output level globally, but might still need to tweak each preset to get to the "perfect" amber LED. - But... neither of those will actually be a significant benefit, because the amber LED on the Powercab doesn't actually make that much difference - thanks @PierM So at the risk of making myself stoopid, I may as well put it out there that I've never had a problem with the Powercab being too quiet, so I'm probably trying to fix a problem I didn't even have in the first place - I was just trying to follow the best practice advice :-/ Note to self - spend less time on the internet figuring out what to do, and more time actually doing. Thanks for the input everyone.
  13. @HonestOpinion you're right, global EQ doesn't impact digital outs - I wish it did though, and there's at least one request for this on Ideascale. The setting I was hoping to use is this one (page 3, knob 6) - disclosure, I haven't tried it yet, hence the question here, but I was *assuming* it would allow me to bump all my patches by say +3dB if that's enough to hit amber. I have started to set up patches with a footswitch for Helix cab vs Powercab speaker... so if this works, I could keep all my current patches which work fine through XLR outs and be able to switch between Powercab and direct as the situation dictates. @PierM I think you're saying that Powercab green is fine though - in which case I don't need to make any changes at all! What a time to be alive :-D
  14. I've posted a related question in the Powercab forum but it doesn't get much traffic there these days so I hope you don't mind the repost here. My presets are pretty consistent output-wise but need a 'bump' to get into the amber when I play through the Powercab. Everything I've seen (including Jason Sadites videos) advocates setting preset levels individually for the Powercab - is there any reason NOT to increase the digital output level in global settings so that I can 'bump' them all at once rather than individually? This would save me a lot of re-work. TIA.
  • Create New...