Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by the_bees_knees22

  1. @OP yeah it's a good method. I've been doing that workflow since the POD XT. It's always worked well for me too. I run my helix straight into the fx return of my marshall jcm2000 and into my orange ppc2x12 cab. It sounds great If i want to use the actual marshal channels I'll run 4cable method, but eh... going straight into the fx loop is simpler and it sounds great so I do that 90% of the time.
  2. I made the switch. It's been fine for me so far. Line6, cubase, UAD stuff, all my plugins have all been ok. I've been on big sur for the past couple of weeks. I haven't ran LUNA on big sur, but so far zero issues with anything. if you're in the middle of a project though, I wouldn't switch.
  3. I just installed big sur on my backup laptop. wow....it's so....ugly lol. What the heck? What was Apple's design team thinking lol
  4. It'll really depend on what you're monitoring through. I have a pair of Adam A7's and I can definitely hear a difference. On my laptop speakers though they sound identical.
  5. Agreed there is a slight fullness and tightness as well to 3.1. It is slight, but it's there for sure. I believe it is an improvement for sure. In my own tones i mostly use the uber and badonk and i notice less crackling when driven really hard.
  6. Is today Christmas?! !!! !!!! I don't see my presents yet lol
  7. same. I use my Apollo twin X as my interface. I just throw on Native on the track I'm recording along with my IR loader and just record like that. I keep plugins to a minimum on my base writing session so there's no real noticeable latency. (at least not enough to bother me, but I have a beefy machine... so I don't have the same limitation as you're experiencing. I'd save up if you can for a heavier duty computer at some point. It just makes life easier) Then I spice things up later. I use my Helix floor to control cubase for punching in and out. It's pretty awesome for that. There's a preset for it actually. (but I'm not actually plugged into my helix floor at all otherwise.) I don't record a wet track at all since Native is right there. IF I had a session where I had already done a lot of mixing and there were a lot of plugins already in the chain then I would then probably use my helix to monitor a wet signal and record the dry. I doubt I'd even bother recording the wet signal tbh. I just know I'd never use it personally with how I work.
  8. lol I keep dragging my feet on my new round of writing because I keep telling myself it'll come out soon. I need to stop using that as an excuse and just knock this out, and stop being lazy. haha
  9. is it Christmas yet? When do we get our presents? lol, Should I keep pushing on my demo's or wait for 3.1 'cause everything will be loads better? lol
  10. You can still type them! lol :D :) -_____- ¯\_(ツ)_/¯ O_o X_X
  11. His videos are great! I just went through them all. I'd love to see more technical content like that. It helps a ton!
  12. I've been discussing this IR pack from Kristian Kohle on another forum. I guess I'll throw it here in case anyone is curious. This is just 2 of the IR's in the pack though. Left side - uberschall > DV77 Linear IR Right side - Badonk >DV77 presence boost IR (horizon drive in front of both amps with slightly different settings. room verb post amp. IR's loaded with STL tones Libra with high and low cuts and a bit of resonance added) (also ran it through a few UAD plugins, but with minimal EQ. helios, studor, and pultec eq, and a few other things. some things were just flat and used for a bit of color only) If peeps want to hear it without all that, I can export it.
  13. oh actually, I just tried luna again with arm mode off and a Native plugin on after updating to 1.3. Seems a lot better now. There's still a tiny bit of latency but it's not nearly as bad as it was last time I tried it under 1.1 or whatever it was a while back.
  14. yeah you can't load a helix plugin into a UA device so there's that @guitarboy_02451 But I realized, I could just get a di box and split the signal. 1 to helix floor and 1 to my apollo twin x. They're not all that expensive so that shouldn't be a huge deal. I could then have my dry signal to the apollo, and my latency free monitoring signal from the helix into another channel. boom! all good to go. ..or i could just use the 1/4" out on the helix to go to my apollo and just have a dry L channel for the DI and a wet R channel for monitoring, but that would be converting the signal twice which I don't really want to do. It would probably work fine though, and it would be a cheaper work around.
  15. yeah luna is pretty limited right now. I was inquiring about a good way to track without using UAD amp models with no latency since if you have ARM mode on it disables all plugins like Helix Native, and if you have it on with no plugins at all, there's really bad latency. In short there is no way to do that either right now. Whatever is going on under the hood with luna is processing the signal enough that you can't even get remotely close to low latency unless ARM is on. Plus you can't use a 3rd party IR loader that I know of right now like Libra from STLtones. Luna is just way early days right now, and the workflow when trying to do anything non UAD related leaves a lot to be desired. You may want to just track in another DAW and then bring it into Luna for mixing if you really want to use Luna for the Summing and whatnot (it does sound nice tbh)
  16. I get what OP is saying. Right out of the box it sounds a lot smoother in the mids than any of the other high gain models if you're flipping back and forth between them. I find that the cab model/IR makes a huge difference and with the right one the diezel sounds massive and ballzy...but that goes for any amp model. I dunno. they all sound great, you just need to find the right IR for the right amp. Like i usually use Orange IR's because that's what my real cab is, but they're a terrible pairing with the diezel. So tried a few other IR's and boom, sounded great.
  17. yeah, I just got LIbra from STL for an IR loaded. It's nice. I don't think it would suck up a lot of resources to improve the IR management side of the helix though. I think it's important to address at some point since the Helix is all about a fast and user friendly workflow, and it's the one area that seems to slow people down the most. lol I need speed! haha
  18. Do you just do 2 instances of helix if you want post fx from Native? ex) helix IR loader Helix post fx
  19. Hi! I'm kind of getting tired of getting a pop up any time I switch to a preset where an IR has changed in Cubase with helix native. "The IR's associated with this block cannot be found..." I swap out IR's all the time and I don't care if it's changed. I don't see any preferences that I can change, and the pop up is getting super annoying. thoughts? I know it's been posted on here a lot, but the IR management is probably the weakest part of the helix. I'd like to be able to expand the IR window to see the full names, but it's locked at a specific width. And just having a char limit when a lot of IR's have much longer names is a bit frustrating. maybe it can be addressed in 3.1? lol :D
  20. Just update to the latest and greatest directly. It's fine. I can't help you on #2. I never use my acoustics with my helix. /shrug
  21. I get lots of strange frequencies on OH Orange IR's. I recently just picked up celestiondigital's orange pack and it's a lot better to my ears. Less raw. Fewer strange frequencies. I pretty much only use Orange IR's since that's what my real cab is so I can't speak to the other ones that much. I have OH's heavy hitters II pack and their mesa cab bundle, but I just never use them.
  22. I just upgraded to 10.5.20 as well. after a LOT of debugging... (i'm on a 2015 macbook pro).. the solution I found was to 1. set the asio guard level to High. Then 2. on my external monitor, I have to make sure I keep my Cubase interface small. Like half the screen size on my external monitor. Otherwise cubase just chokes. biggest factor that seems to kill cubase for me is making the UI full screen. ...ridiculous I know... I'm not a happy camper with cubase right now. The free version of 10.0 ran perfectly fine so I went all in on 10.5 pro.... and was borderline unusable at times until i figured out the above fix. ...and making the UI super small is not a great fix.. So anyway, I don't think it's helix native, but cubase that has issues as I've had it spike without having any instances of Native running. If you go to the steinberg forum you'll see lots of users complaining about CPU spikes that don't have anything to do with native. :( ...sigh.. good luck dude. It's super frustrating I know. I'm tempted to try out Luna since I have an apollo interface, but I haven't given it a shot yet. I hate pro tools with a passion. Haven't tried reaper or anything else yet. I like the workflow of cubase, but these spikes are totally garbage. ..hopefully it's fixed in the next version..
  23. My DT-25 along with my marshall is just collecting dust after buying a helix. They make nice decoration though so I keep them.
  24. @OP - I'd go helix + helix native. Then after that start gearing purchases to be more toward a studio setup. You can start with reaper since it's free, and get a bass somewhere down the line. Then upgrade to cubase or one of these other DAW's at some point down the line. so go Helix + helix native get a DAW next get a bass. get a decent mic (even if you don't sing, you may surprise yourself) then later get some nice plugins. fab filter stuff. maybe some UAD stuff if you get monies lying around. Then circle back around to more guitars...more basses. more guitars.. more basses. lol that's your 5-10 year plan.
  • Create New...