Jump to content

hal3001

Members
  • Posts

    37
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by hal3001

  1. I just saw the end of your post about being able to listen to YouTube. On a Mac, (sorry can’t help on windows) your system default sound card has nothing to do with Pro Tools. You generally specify your output device using Setting -> Sound -> Output tab. Sounds like this is configured correctly for using the helix as your system audio device. Again, the problem is this has no control over Pro Tools. For Pro Tools, you need to select the audio device specifically under Setup -> Playback Engine.
  2. I can give you more details when I’m at my computer but basically setting it up in PT is a three step process. 1. Under setup -> playback engine, make sure you’ve chosen the helix. I usually set the buffer all the way up here since you will be monitoring the helix directly so latency won’t affect you. 2. In setup -> I/O, you will may need to default the input, output, and bus pages. Simply go to each tab and click default 3. Make sure you’ve created an audio track in either mono or stereo and that you have I/O shown for each track. I’ll have to double check but make sure either inoutv1 or 1/2 are selected. You can also record the dry signal if you want on channel 7/8. 4. Record enable the traffic and you should see signal. This is where I would normally mute the track so you aren’t hearing it twice. I’ve had weird results in PT with low latency monitoring enabled and still hearing the track when recording do I just do both now.
  3. I used a Helix with a pair of Mission pedals on a Pedaltrain Classic Pro for about a year and had no problems with viewing or usage angle. If you did have issues, you could always put the Helix itself on a couple of risers and leave the pedals on the board as normal but I never saw a need to do it. At one point I did put the Helix on a riser because I moved it to the back and had a couple of other pedals in front and didn't have any issues either.
  4. I managed to get it all sorted. I borrowed an HD500 and after a few hours of fighting to get the drivers installed on High Sierra, it still failed. After that, I fired up a Windows 7 VM and was able to install everything I needed and it restored the first time.
  5. @soundog thank you for the offer. For some reason I wasn't receiving notifications for this thread and didn't think to look back. I actually do have a friend with an old HD500 that I could borrow. I didn't realize that you could use it for that. I even owned an HD500X and Variax and just used the VDI/USB adapter. I'll give that a shot and see where I get and I may take you up on the offer.
  6. Not the output bit depth of the interface, the input bit depth. I plugged in a real USB cable and it only has one input and no output (as expected) and it’s hard set at 44.1, 16-bit. Also, thank you for this btw. I’ve been a Rocksmith player since it’s launch and have been wanting something like this since the initial OSX release and it never occured to me that it was just looking for that audio device name.
  7. My guess is that it's because the actual Rocksmith cable is set to 44.1, 16-bit, and I can't find a way to change the Helix from 24-bit to 16-bit mode. I'm assuming your old Scarlett supports both?
  8. I recently found a Variax 700 Acoustic and unfortunately the firmware update failed in the middle of the update using a Helix/VDI cable and I can’t get an update to complete and now it’s partially bricked. I’m pretty sure I can fix it with the original USB to VDI adapter but would really prefer to not spend 75 on one if it’s not going to work so I was wondering if there was anyone in my area that has one who would be willing to meet me for 15 minutes and let me use their adapter to get the firmware updated.
  9. Latency from an interface is usually associated with the buffer size setting specified for the interface (usually in the DAW). If you are going to be monitoring your guitar through the DAW, make sure it's as low as you can get without artifacts. I generally suggest against monitoring through the DAW with the Helix or any other interface that can route audio on it's own. If you've selected the Helix as your input and output interface (some DAWs won't let you choose a different interface), you can just disable input monitoring on an armed audio track that you are trying to record so that you are only hearing the guitar directly from the Helix and just play the other tracks as normal. Again, you don't have to do it his way and can just set your buffer settings as low as possible but make sure you aren't monitoring both the Helix and the Helix routed through the DAW.
  10. Check out the templates that come with the Helix. I believe it's the last page of presets in the editor. There is an example of doing just that. I've done two guitars and microphone before but you are very limited to the effects and cabs that can be used. It definitely does work. You also didn't mention which Helix you have. I've done it with the helix rack and 2x G90s. Both G90s going into individual returns and the microphone in the XLR.
  11. So, I've had a Helix Rack and floor controller for quite a while now and I love it but one giant pain in the butt is having so many cables going back and forth between the rack unit and my pedalboard. My current set up uses a BeatBuddy, Infinity Looper, ProCo Rat, Helix Control, ProD2 DI, and two mission pedals. I ended up running 2x MIDI cables, 3x TS cables, and power from the rack to the board, then two XLRs from the DI to mixing board. It's just a bit too much to deal with when moving everything so I think I'm just going to move from a rack to the floor unit where I can just run everything at the board and either run just one XLR out from the helix or keep my DI set up. So after all that, my actual question is other than not having wordclock in (which I use for recording but I can live without it) is there anything else that isn't on the floor that is on the rack or any other gotchas that I might be over looking? My wiring setup would probably be the same. Send/Return 1 <-> ProCo Rat (or another other pre amp pedals), TS main left -> Infinity Looper -> DI -> Mixer, and BeatBuddy -> DI -> Mixer. I can't see any reason why that wouldn't work. I may end up bringing the looper and BeatBuddy in via send/returns and just sending the whole thing out XLR but we will see. The beatbuddy was introducing a lot of noise when trying this with the 15ft cables rack->board->rack. Also, I was thinking about using a G70 with this setup. I assume there isn't anything different than using the G90?
  12. I kind of solved my own problem today. Instead of plugging into the Helix and sending my wet and dry signal out SPDIF, I realized I could just up a hardware insert in Pro Tools on the SPDIF interfaces then just plug into either my HiZ on my Apollo or my ISA 428 and then use my Helix Rack as a standard insert. It worked really, really well.
  13. Just a quick question. I was just wondering if there was a quick way (option somewhere) to send a dry signal out one channel of the SPDIF connection? I usually just create a split and have that run directly to the outputs with the digital outs selected then record the left/right signals separately which works fine if I've set up the patch myself but a lot of presets have pretty much every available path in use. I run SPDIF from the Helix Rack into my Apollo 8 and would like to keep things digital if possible. I know I can run the dry out into an input on the interface but I really don't like all that conversion.
  14. Yeah, that's pretty much the way I had to start looking at it as well.
  15. I've actually always wondered the same thing. As you've said, in the real world, a reverb pedal would be placed in the loop after the pre-amp but before the power amp (and to the speaker). Now placing the reverb after the speaker would be better for spatial recreation type reverbs but an emulation of a reverb pedal placed after the speaker (which the designers never assumed would be placed after cabs/mics) seems a little odd. I know, the nice thing about the Helix is the ability to put anything pretty much anywhere you want, but I've always wondered why the default patches didn't go from gain effects -> amp -> spatial/delay effects -> cabs.
  16. I’m curious. Did you happen to have anything connect via MIDI in that would be sending MIDI clock messages by any chance?
  17. So for the last hour I've been trying to update to 2.21. I thought I had the latest firmware but I guess I've just been using 2.20. My first attempting completely failed with the Helix going black and the updater telling me that it was unable to complete the update after a few seconds of trying. Having just updated to High Sierra I thought it was probably a driver security issue. I doubled checked that and it was fine. Also one thing to note, the Helix goes black on the failed update but I can just reboot it and it comes back fine (without a new firmware). I decided to factory reset it in case there was a setting that I had changed that was causing an issue then tried again. Same thing. Black screen, failed update. On a hunch, I I thought maybe Line 6 MIDI sysex messages for communicating with the device from the updater and editor and I do have a BeatBuddy coming into the Helix MIDI in and going out to an Infinity looper so I figured it couldn't hurt to disconnect those. Sure enough, after disconnecting the MIDI connections the new firmware installed without issue. Moral of the story, while I still have no idea if they are using MIDI sysex, make sure to disconnect anything that might be sending MIDI clock and or messages from your Helix before attempting a firmware update. I'm sure that is somewhere in the manual or update notes and I probably just missed it. Hopefully I can save someone else an hour or two of their time.
  18. Oh you guys are awesome! Thanks so much. That definitely makes me feel better. Going to open a ticket for it today.
  19. Looks like something is definitely wonky. I hooked it up to the BeatBuddy I ordered which has a BPM on the display and disabled sending all MIDI except for clock all I have to do is turn the right selector knob and the BPM on the BeatBuddy goes all over the place.
  20. Nope, no phantom power. I'm actually glad to know that it won't fry it if I accidentally enable phantom. I was actually considering by a line isolator box just to protect against that. Just for a test, I just did a factory reset and loaded up the ANGL Meteor preset (assuming it is a loud preset) and with everything at default and confirm that XLR outputs were at line level, the only change I made I made was to turn the main volume know all the way up and I'm only getting around -18dB on my X32 meters. Also tried on the Apollo and if I dropped the reference to -10 from +4 I could get it a little louder. Thanks everyone for your feedback. I'm going to open a ticket. Unfortunately, I just looked and I bought it in July of 2016 so I assume I'm probably also out of the warranty period.
  21. Ok. I’m home 2. Guitar pad is off 3. Line 6. Multi 7. Multi
  22. Sorry, I meant that there are tons of questions about low volume here in a couple other places but most of the time, it's as simple as having instrument instead of line level on the output of choice, or master volume being turned down, etc. This is my first time asking because I kind of just figured it was normal since it's not unusable but then I started seeing people respond to similar questions say similar things about preset levels being too loud, etc. 1. Yes. I am currently. Originally, I was doing XLR -> Apollo 8 line in, but after moving to X32, I read that it could handle mic and balanced line on the XLR inputs so I chose to use that to make my snake choices easier. Also, the problem existed long before the X32 with my original Apollo 8 and also into just a pair of powered monitors. 2. I'll have to check when I get home but it should the default as I don't usually change that. 3. Again, I'll check when I get home but I believe that setting is for instrument/line which should be set to line for me. 4. A 2008 LP Standard, a 2017 LP Standard, PRS S2 Mira, and the same with a JTV-59 via VDI cable. 5. Part of the reason I just thought it was normal is that it's not very quiet. I'm not a high gain guy and I don't usually listen to music over 85dBC for very long so I don't really like loud. Even with the headphones, 75% up a little quiet but usable. Anything below is pretty quiet and I usually have to keep the headphone levels at 80-90% of full. 6. I believe it's default so that it controls ... I don't remember everything that setting controls. Again, I'll check when I get home. 7. Probably default because I don't remember that setting at all but I'll check.
  23. I'm sorry to bring this topic up for the hundredth time. I've owned my Helix for over a year and I've searched and read this question quite a number of times and I'm quite familiar with instrument/line level options for the outputs. The levels I get are not inaudible but from other posts on this topic, they are definitely not as loud as some others have posted. I would just like to be able to open a preset and not have to crank every output level to get it to a nominal output level. My question is actually pretty simple. For the built in presets (not custom), what output levels out of the XLR mains do you get? Since I've owned my Helix, I almost always have to go in and crank the master volume on the amp as well as the output block volume as well as the main volume knob to get levels anywhere near the -18db to -12db range on any mixer I use. Originally, I was running into the line-ins into my Apollo 8 but had to change their reference level to -10db to get even close to loud. I contacted support and they confirmed that XLR outputs in line mode should be at +4db. At one point (I have a Helix Rack), I was using spdif into my Apollo and the levels there were very consistent across any of my (or the built-in presets) but recently I've moved it out of my rack and more for live use and I'm using it with an X32. At least now, I do have actual trim on the mixer so I can bring the level up to a usable point without having everything on the Helix maxed out but I'm starting to wonder if this is normal? Headphone levels are pretty much the same. I've also used the Helix directly with a pair of ZLX-12Ps for practice and while I could get it to be loud, I had to set the trim on the 12Ps a little higher than 0db to get any kind of volume range. One thing to note, is that most of the time, I have a G90 wireless that runs into the Aux guitar input but the levels are pretty much the same if I plug directly into the guitar in.
  24. I have a bit of an odd issue. First, I should say that both the Helix and looper are running the most recent firmware. I've had my Helix for about a year and I've used it exclusively since I bought it. Like most people, I'm not a huge fan of the slightly unforgiving built-in looper but it was just fine for practice but I've recently been wanting to use a looper more for composition recently and having a few more features would be useful so I picked up an Infinity Looper and a Beatbuddy (I'm still waiting to receive the BB). I received the looper last weekend and have been reading the manual and just getting generally acquainted with it and ran into a bit of a weird issue. When I connect the looper to the Helix, set the Helix to send midi clock after a few seconds everything seems to sync up just fine. I can send commands correctly to arm/play/etc just fine as well. However, if I try to edit any MIDI controls on the Helix (scrolling through channels, or CC values) but not sending any messages, the looper will start to speed up or slow down pretty dramatically. I also noticed, that if I setup a button with a CC command that doesn't do anything or put it on a channel that the looper isn't receiving on, and start to tap that button to send the message very quickly the same thing occurs. In some cases, I only have to send it once and it will go all over the place. I did read in the looper's manual that it's slaved clock sync function will detect a change in clock, and slowly attempt to shift toward the new clock timing until it is in sync again (while still trying to keep the running loop at the correct speed), so my assumption is that the editing and or excessive (or not so excessive in some cases) MIDI messages being sent is some how taking up processing time on the unit causing it to delay the clock messages but I have no easy way to confirm this. I guess I could write a MIDI sniffer log the messages but I figured that would be overkill. I tried a few things to debug this and one of which was to disable sending clock from the Helix just to confirm that somehow CC messages weren't being sent (to possible trigger Varispeed) as I was making edits (but not triggering them) and everything worked perfectly. Has anyone else experienced this or have any other things I could try to enable/disable in order to test this? My only other option is to send clock from the BB once it get's here but I would prefer to just have Helix -> BB -> Infinity instead of BB -> Thru Box (Helix, Infinity)
×
×
  • Create New...