Jump to content

Indianrock2020

Members
  • Content Count

    622
  • Joined

  • Last visited

Community Reputation

34 Neutral

About Indianrock2020

  • Rank
    Gear Head

Profile Information

  • Gender
    Male
  • Location
    Bellingham, WA
  • Registered Products
    4

Recent Profile Visitors

1,022 profile views
  1. It appears the Helix Asio doesn't have good performance....showing 65 Ms delay in jamulus, as opposed to 43 or so on the Mackie driver.
  2. I do use sonobus with some others in the Seattle area. Since I have the time and there is already a convenient Thursday mid-day session on Jamulus, I've started participating in that. I'm looking at running two instances of Jamulus, with the Helix driver set up on one and my regular "interface" ( mackie mixer) serving vocals and backing tracks to another instance of Jamulus. There is also a solution using Reaper's rearoute. Then you have an approach using ASIO Link Pro -- too much info to digest :-) But even just continuing with guitar/vocal/tracks through the Mackie only I've found that panning before sound hits Jamulus or Sonobus makes a big difference. When I was struggling to get IEMs dialed in someone pointed out the advantages of a stereo mix over mono. They likened mono to listening to six other musicians who were standing single file facing you. So first in line is the piano and it's too loud, so you turn up the level of the drummer who is 3rd in line. Then you can no longer hear the piano or others adequately, and on and on and on. But if you can put the drummer and bass in your left ear, say panned out 50%, the piano and lead vocal in the right ear, etc etc and possibly also lower or even remove some sources you don't need, you can hear what you need at lower volumes. In Jamulus etc you can't mute people because you won't hear them talking, unless they're using multiple sessions so you could mute their instrument if desired. ( or if they are panning ahead of Jamulus you could pan them in Jamulus to get what you need from them) My brief experiment with this panning yesterday did make a big difference. It was in Sonobus but my vocal was totally in the left ear, with most of the guitar in the right and it made it easier for all of us to hear what I was doing more distinctly.
  3. Thanks for providing this. I'm just now getting around to trying my Helix driver with Jamulus. I've been using Jamulus with the ASIO driver for my small Mackie mixer ( running Helix and vocal mic into the Mackie) but now I want to explore running two instances of Jamulus so others can adjust my vocal mic and Helix guitar levels independently.
  4. Chiming in on an old thread because I'm considering upgrading my Youlean loudness app to the pro version. When our rehearsals start, just after the last member arrives, we go quickly through all of the songs and then go home. THERE IS ZERO time to tweak patch levels with the band present. Often, the sound guy isn't even there on rehearsal nights. The leader might break for 20 seconds to let you adjust if a specific patch is way off , level wise, but that's it. And that's why I use my ears and meters at home.
  5. I'm playing a few hours per week using Jamkazam ( online jamming). Latency is key. I just wanted to see if removing the audio interface and running Helix direct to laptop would be better ( seems logical, remove something and there's less overhead, exactly why I always remove the headers and mufflers on my cars). Unfortunately, that's not the case.
  6. I set up two patches, both with usb 3/4 input and usb 1/2 output. Best latency on the empty patch was 9.1ms at 96 khz and 64 buffer size On a normal patch with my usual blocks, with usb 3/4 input and 1/2 output, best was 11.5ms at 48khz/64 My audio interface reports about 6ms
  7. Reinstalled the drivers. Now cakewalk sees inputs 1,3,5,7 ( usb) not the even numbered ones. When I ran RTL it now sees the Helix asio and shows 8 inputs and 8 outputs so I selected all of them. Cable from 1/4 to guitar 1/4 input
  8. When I updated to 3.01 a few days ago, it didn't require a new version of HXedit. but it is suspicious that the Helix driver shows May 2019 and not more recent. Will deleting and reinstalling the latest hxedit update the drivers?
  9. Went ahead and tried it. Well neither RTL nor Cakewalk recognize the Helix ASIO driver. I do see HX Stomp in RTL but otherwise no recognition. It's there in the control panel (Helix Control Panel) as well as under devices. Audacity recognizes it. Helix edit runs fine and everything is up to date to 3.01 with the Helix driver date shows May 2020. Rebooted/restarted everything. Not too impressed with this driver.
  10. I'd just like to hear from others who have tested Helix latency by running a 1/4 inch cable from 1/4 out to guitar input. I'll be using the RTL utility and just want to make sure it's safe to use a patch cable like that. I'd guess testing should be done on a blank preset as well as on one typically used.
  11. What driver are you talking about? if it's not the Helix driver what other one works with helix
  12. For RTL did you just run a 1/4 inch cable from 1/4 out to guitar input?
  13. I tried using my Helix today as an interface to my laptop running Jam Kazam for online music.... I used helix USB channels one and two for the guitar and channel 8 for the microphone ...the latency showing in jamkazam was about 12 milliseconds ....this is the local gear related latency, I wasn't connected to anyone on the internet.... my regular audio interface gets about 5.7 milliseconds so unless I'm missing something using the Helix in this way makes no sense. I verified the audio interface latency that jamkazam shows by running the RTL utility... how would you safely route a patch cable on the helix to run RTL against that?
  14. I followed all of qwerty42's advice but was still getting record errors. I know I've had recent Windows updates......actually I see now that I had the microphone (the built-in microphone on the laptop) disabled because I wasn't using it... I'm going to re-enable that and see what works now. The windows updates don't seem to have affected the microphone privacy settings. 9999 Unanticipated host error: this means means "something is wrong". And appears to most often be due to either: A lost connection to a USB audio device. Recent Windows / Mac update requiring that user gives permission for Audacity to access the microphone.
  15. Some people like to use the output block on a preset basis so that all of their presets in a given set or performance are volume balanced rather than doing what I've been doing and changing the volume there on a snapshot basis.... the only problem with the amp channel gain exclusively is that in some of the early fender models there just isn't enough gain available with that control in certain circumstances
×
×
  • Create New...