Jump to content

jroseberry

Members
  • Content Count

    166
  • Joined

  • Last visited

  • Days Won

    1

jroseberry last won the day on August 22 2018

jroseberry had the most liked content!

Community Reputation

55 Neutral

About jroseberry

  • Rank
    Iknowathingortwo
  • Birthday 12/11/1966

Contact Methods

  • Website URL
    http://www.studiocat.com

Profile Information

  • Gender
    Male
  • Registered Products
    1

Recent Profile Visitors

337 profile views
  1. jroseberry

    Helix LT sucks. Badly.

    Assuming your Helix is properly functional, it's *far* better than the GT-100. Not even in the same ballpark...
  2. jroseberry

    Helix LT sucks. Badly.

    Using one of the more advanced modeling devices (Helix, Axe-FX, AX8, etc) is a large paradigm shift from simply plugging into a 100w tube-head w/4x12 cab. Do you have access to a FRFR PA speaker? That would provide SPL levels similar to an amp/cab... and would provide a much better perspective from which to gauge the Helix. Also, it takes a while to get up-to-speed with Helix/Axe-FX/etc. When I first got the Helix, I didn't like the bottom end (same is true for the Axe-FX II XL+ and AX8). For me, placing a high-pass filter prior to the Amp Block (on all of them)... instantly made the bottom end sound much better (tighter). Little things like that go a long way toward achieving the desired result. What I like about Helix: Once you're up-to-speed, if you can imagine the sound, you can quickly/easily create it. If you like your particular cab/s, create your own IRs with the cab/s mic'd the way you prefer. This help take you even farther toward achieving your sound. Proper monitoring setup is paramount to achieving good results (similar to studio monitors being necessary to achieve a good mix).
  3. jroseberry

    Occasional lack of clarity/high end

    FWIW, I always run a high-pass filter before the Amp Block. Results in tighter more controlled bottom end. You can always add a little "bump" at 150Hz (post Amp Block) if you want more thump.
  4. jroseberry

    Alternate settings for Para EQ in lieu of Cab/IR block

    Hi Markus, Glad you like the EQ settings. Before actually trying it, I didn't expect to like the results. After playing/tweaking, I thought it sounded surprisingly good.
  5. jroseberry

    Alternate settings for Para EQ in lieu of Cab/IR block

    FWIW, If you're even vaguely familiar with using parametric EQ, it's not particularly difficult. You've got three bands of EQ and high/low pass filters. 11 total parameters It would only take a minute or two to checkout the above settings. ;)
  6. First, thanks to Chad Boston for the idea of using a Parametric EQ in place of a Cab/IR block. An IR is essentially a static filter... so a Parametric EQ could shape the sound in a similar manner. Chad's work inspired me to load up a Parametric EQ (started with his settings)... and tweak till I came up with this. Give it a try... and let me know what you think. Parametric EQ: Low Freq = 130Hz Low Q = 1.7 Low Gain = +6dB Mid Freq = 1.9kHz Mid Q = 0.7 Mid Gain = +5.5dB High Freq = 3.4kHz High Q = 8.8 High Gain = +4.4dB Low Cut = 50Hz High Cut = 5.0kHz Level = -2.8dB
  7. jroseberry

    TIPS on getting the FX Loop to sound full and robust?

    With the H9 not engaged, you're mixing slightly delayed dry signal back with the original. This will cause phase-cancellation (and thus sound thin/hollow). That's perfectly normal. If using the EFX Loop in Helix, if the H9 is off, the Loop also should be off.
  8. jroseberry

    Helix Rack Seems To Get Quieter Over Time

    Rule out the hardware... But it's certainly not uncommon for a band to get louder as the night progresses. ;)
  9. jroseberry

    Helix native tones muddy/undynamic

    I'm guessing that post was referring to other (higher-end) audio interface specific features. ie: RME audio interfaces offer rock-solid performance with lower round-trip latency. I run Helix (digital) AES into a Fireface UFX. Best of both worlds. ;)
  10. jroseberry

    helix vs focusrite

    There's no doubt in my mind that the DI input (quality) affects results achieved with Helix Native. Record a passive Fender bass (straight DI) thru a cheap DI box. Sounds completely anemic... Run the same bass thru a Neve Portico-II channel (just the preamp)... and it sounds great. Both have Hi-Z inputs... but sound worlds apart.
  11. jroseberry

    Will IR's work via Effects Send/Return

    The IR block will work the same as the reverb/delay/distortion blocks.
  12. jroseberry

    Will IR's work via Effects Send/Return

    If you get the routing setup correct (send/return), you can use an IR block in Helix to process your acoustic/Fishman rig.
  13. jroseberry

    Helix native tones muddy/undynamic

    There's a world of difference in DI inputs... and this does affect the results you'll achieve using Helix Native. If you've ever heard DI electric bass thru a cheap DI box vs. something like a Neve channel, the difference is night and day (as is the cost difference). The cheap DI box sounds anemic compared to the Neve. It's the same with DI electric guitar. Part of what you're paying for with Helix Floor/Rack/LT is an analog input section tailored to this specific task. To achieve similar results to the Helix hardware, you need a quality DI input.
  14. jroseberry

    Helix sounds boxy through studio monitors

    The Yamaha HS7 monitors are pretty decent. If your goal is setting up sounds to be played live, I'd try to monitor thru a rig similar/identical to what you'll be using live. Even with a great pair of studio monitors, the 8" woofer isn't going to have the same bottom end as a 12" or 15" PA speaker.
  15. jroseberry

    Helix Native

    Many folks feel the same. From a DAW performance perspective, there's no difference between Home and Pro... But the convenience of gpedit.msc is easily worth the extra $40.
×