TexLefty65

I did like some of those CustomTone presets in Mobile POD 1 also, but that feature actually was never a "live" searchable link to import tones from CustomTone site - it was just a good size static set of tones that Line 6 took from the CustomTone site and included them as a set of presets within Mobile POD 1. Since I've used Mobile POD for a while now I find it pretty easy to make my own presets with it, and Mobile POD 2 makes it a bit easier with the larger controls now thankfully!

I have a mid 2014 Retina MacBook Pro i7, OS X 10.11.4, which has two USB 3.0 ports, and I've not had any problems whatsoever with it seeing or updating Helix. So, apparently it is not specifically a USB 3.0 problem. Seems more like some very specific USB port hardware that was used on a few Mac models - obviously there a LOT of Mac owners with Helix units out there now, and only a handful of people seeing these problems, so it is definitely not all MacBooks, or all with USB 3 ports. I have not really tried anything with using the 5-pin MIDI on Helix, but the audio driver seems to work for me, other than an occasional click or pop in recording or playback when using Reaper. I recall hearing that Line 6 is supposedly doing their own Mac Helix driver though, so hopefully that will help overcome the problems some people are seeing.

Partial answer for you... Helix uses the inherent USB class compliant driver on Mac, which apparently results in only native support for 48kHz. Most DAW apps will be fine with that and just resample the audio to still allow you to run your projects at other sample rates though, so this is not necessarily a problem. I have seen some folks here say they have problems like you describe with Helix on Mac where they get clicks in audio, and/or audio turns into static after a while. Some have said the latest El Capitan 10.11.4 update helped this. Again, I suspect this has to do with limitations of the Apple USB driver, and I've seen other audio interfaces report problems with this driver too, but not all, so it seems to affect some devices (seems hard to say whose "fault" this is, but seems fair to say maybe both Line 6 and Apple to some degree). For me, my MacBook Pro doesn't seem to have these problems with Helix, other than the occasional click in audio. Line 6 has stated they will be writing their own Mac USB driver for Helix in the future, and I think that is the best solution (they do write a custom ASIO driver for Windows - and probably why we're not seeing much complaints from Windows guys!)

I suspect all the keyboard shortcuts just aren't implemented yet, but the Release Notes mention a few (remember to click in the editor panel - these shortcuts don't work if the focus is in the preset/IR librarian panel): - Bypass Block Shortcut - Press B on your computer keyboard to bypass/enable the selected block - Clear Block Shortcut - Press Delete or Backspace on your computer keyboard to clear the selected block Edit: Ah, one more! To "reset" a parameter slider to its default setting use Alt-click (Win), Option-click (Mac)

I tried the 4 cable method with my bogner amp head and no problems here. Helix has level controls for most ins and outs so you should be able to optimize the signal at almost any point as needed. But your particular amp is a factor too - some amps' FX loops are buffered and some are not, and some have level controls or +4/-10dB switches. I think Helix should still work with any of them, but the amps' loop settings will make a difference too. Helix also sounds very transparent to me in this setup too, which is great!

I have not had a problem with any updates at all using El Capitan (now using the latest 10.11.2) on my MacBook Pro. Maybe make sure you have the latest version of L6 Updater installed? Also try a different USB port on the Mac and disconnect any other USB devices not needed for the update period??

I think you need to configure the source for the Dry USB7 and 8 within the Global Settings > Ins & Outs, on the 3rd page. USB 7 and 8 are different than other Ins/outs and always carry the dry, unprocessed signal, and you have to choose their source there (rather than from the input block menu for the current preset).

LeBoist - I have not tried connecting to another S/PDIF device yet, but are you saying you tried the settings in the Global Options > Ins and Outs? On the the 3rd page of screens here, the very last two options are one for toggling between S/PDIF and AES-EBU and the other for Sample Rate, which offers 44.1, 48, 88.2 and 96kHz. I believe this is where you configure things for digital output.

Where do you guys see that Sonic Port is not supported for iOS 9? Is this supposed to be true for Sonic Port VX? I just updated my iPhone 6 and iPad 3 to iOS 9 and so far all is working fine for me using Son Port VX with Mobile POD. Maybe you are referring to earlier iPad/iPhone models, or the earlier Sonic Port device (not the VX)?

I can't speak for Amplifi, but Mobile POD is working fine for me. I just updated both my iPad and iPhone to iOS9 and I am using a Sonic Port VX. I don't really notice any difference with Mobile POD as compared to iOS8 so far. What problem are you seeing??

I did the free update to Windows 10 this weekend and so far the 4.2.7.6 driver is working fine for my ux2. I've been letting the Windows Music app play music wav and mp3s off my hard drive for most of the day today and no problem. I also gave it a quick try with Sonar 64 bit (using ASIO) and it appears to all be working there too. I think I saw some reports of problems with Flash in general lately, so if anyone is having problems with playback in their browser, then it might be worth going to adobe's site and make sure you update to the latest Flash version.

I have not tried it yet, but I suppose you could use the 'email tone' option in Mobile POD to email a tone to yourself, open the email on your computer and save the attached tone preset to your hard drive, then open and sign in to customtone.com in your computer browser and use the Upload option. BUT... uploaded tones will still not appear in the Mobile POD - Best of Custom Tone setlist, if that is what you are wanting - that list of tones in Mobile POD is not a live feed from the site, just a set of tones that were taken from CustomTone.com and are installed within the Mobile POD app.

POD Farm 2.58 works fine and you'll want the latest Mac driver 7.3.7 for Yosemite - you can download them both on http://line6.com/software/ . Much better than GearBox in my opinion, and you can use it the same way with Logic or other Mac audio software, where you can monitor the ToneDirect output and record either that or the dry output in your track.

I am pretty sure you need to be running OS X 10.7 or later - the earlier OS X versions probably don't support AMPLIFi as a USB audio device. This is pretty common with a lot of devices and software now since Apple changed quite a few things as of OS X 10.7.

Monkey is working fine for me on Yosemite, but I saw some others reporting problems earlier. Did you get the newest 1.68 version of Monkey? I think you need that for Yosemite. By the way, you may not need Monkey at all - you can get updates for POD Farm, Monkey and ALL Line 6 software and device driver installers directly from the downloads section of the Line 6 site - http://line6.com/software/

Are you guys able to run Pro Tools or a Digi device on Yosemite? Last I saw neither was supported on Yosemite yet. Avid says not to even install them on Yosemite (except for Sibelius). Looks like I am completely out of luck for my old MBox 2 and I don't think it will ever be supported on Yosemite. Here is the info page on the Avid site. Seems strange that might affect Line 6 Monkey, but maybe that is why some are having Monkey problems??

I was just checking into this topic since I updated to Yosemite - my Line 6 Monkey works fine after I updated to the newer 1.68 one on Yosemite. I use a POD HD now (also working fine on Yosemite with POD HD Edit), but I used to have a POD X3 - as I remember, doesn't POD Farm (and then POD Farm 2) software work with POD X3 and was the replacement for GearBox? I still use my POD Farm 2 plug-in with recording software and it works fine on Yosemite too since my license key is stored to "My Computer", so I assume the POD Farm 2 program would also work with POD X3 on Yosemite, and still open the old GearBox preset files?

I have an HD500 here (not a HD500X) but I've tested the tuner by feeding in exact test tones to check the notes and they are dead on for me. For example, You can do this by creating a pure sine wave tone that is 196Hz with no modulation (you can do this in an audio editing software such as Sound Forge, Adobe Audition, or maybe Audacity). Send the playback of this tone into the POD HD Guitar Input jack with it in Tuner Mode and see how it reads. 192Hz is the frequency for a guitar's open G string (assuming you are tuned to 440Hz calibration, and POD HD tuner is set to 440Hz as the base setting). What you might be seeing when tuning your guitar is perhaps how much your particular guitar's strings temporarily go sharp or flat - typically the note will go a bit sharp on attack and then settle down a few cents as it sustains. Some guitars or even strings can vary more than others on this, and how hard you pick can affect it. Or, of course if you are fretting a note instead of plucking an open string, then your bridge intonation comes into play. How fast the tuner reacts, that is, how many times per second it reads the note and updates the display, is a big factor to how easy it makes it to read as well. The POD HD tuner does not have an adjustment for this, and maybe you'd prefer a tuner with a different or adjustable refresh/sensitivity rate.

That support answer is definitely not correct! My understanding was always that the POD HD FX Loop is primarily designed for adding additional pedal/rack fx units into your POD signal chain nothing to do with an amp (although lots of folks use the FX Loop for other connections too, since they are basically a nice way to take another signal out to an amp or other device). Regarding the FX Loop stereo operation though - I don't see the problem you describe with my HD500. Perhaps the HD400 is different. Have you tried turning all FX off except for one stereo effect?

You also need to set your Roland device to "Slave" or "External Clock" if is offers a clock setting. POD HD's are fixed to act as the master clock in SPDIF connection, which of course means that any other device needs to follow the POD HD clock. If the Roland does not offer a clock setting then look in their manual and see if it is also "fixed" to be a master clock device - if so then the two will likely not work together for SPDIF.

Did you check the Audio Buffer settings for the app you are running? This determines the latency, and most audio apps include this as an adjustable setting. For the Mobile POD app you get to this in the iPad's Settings app - scroll all the way down in the Settings app menu to Mobile POD in the list of apps and you can set its Audio Buffer there. My iPhone 5 has this set to 4 ms and latency is pretty low. If you set it too low you'll get some clicks and pops in the audio but you can likely get yours down to 4 or 6 ms.

Zap - I am pretty sure only the AU plug-ins in the Mac POD Farm 2.5x version are 64 bit, and the Mac VSTs are 32 bit. (The Windows version POD Farm 2.5x VSTs are 64 bit too, but not for the Mac version). I would guess that so few Mac DAW host apps utilize VSTs (or also use AU) that Line 6 did not bother. If you run Reaper 64 on Mac you'll see that you can use either the POD Farm AU or VST plug-ins, but the VSTs open up obviously as 32 bit "bridged" (and with the Edit window as a floating window instead of in the regular Reaper FX window frame), where the AUs do not. But, as I mentioned, I have no problems running the 32 bit POD Farm 2.56 VSTs in my 64 bit Cubase v5.5 or Reaper 64 Mac software. Some folks report problems trying to use some 32 bit plug-ins on 64 bit DAWs, but more typically those are older plug-ins or perhaps heavier VSTi's that utilize more processing/memory. Torbiz - are you having a specific problem using the "bridged" POD Farm VSTs in Cubase?

I think the POD Farm 2.5 Mac VST Plug-Ins are only all 32 bit, but they work fine for me within my Cubase ver 5.5 (64 bit). I am not sure there would be much advantage to them being a true 64 bit version since they don't use a ton of memory (such as VST instruments can). Are you having any problems running the 32 bit plug-ins in Cubase 7? I hope not - I was thinking of upgrading my Cubase soon!

I see your points RobertMan that you shouldn't get conflicting driver settings, but it seems to me that it you might get similar problems with any audio interface/driver when two different applications are trying to access it. The Line 6 Driver in this case is being accessed by both your Windows Sound-Control panel settings AND then by the POD Farm app when it launches. If each app is initially asking the driver for a different bit and/or sample rate, the the driver is trying to do the right thing and switch to provide it. When using any audio interface's ASIO driver with a DAW app, I NEVER set it to also be the default Windows sound device at the same time. Windows multimedia apps (that use the Windows Control Panel settings) are typically 16 bit apps, or might request who knows what sample rate, so it seems just not a good idea to try to share an audio interface between them as the same time. Do you need to have the UX2 set as your Windows default audio interface while also using the POD Farm app for your guitar playing? What about setting your computer's internal sound card as the Windows default for playback of Windows apps (Win Media Player, YouTube playback, Windows sounds, etc.) and just use UX2 for POD Farm?

For Logic (and pretty much all other recording apps) you want to always change the sample rate within the app itself rather than in the Audio MIDI Setup window, unless the recording app does not offer these options itself. In Logic you do this in File > Projects > Audio. You can use 44.1, 48, 88.2 or 96khz with any POD HD and it supports these rates without re-sampling. You'll also want to go into Logic's Preferences > Audio and check the 24 Bit box for 24 bit recording (in the Devices tab, where it should also be set to use your POD HD as the CoreAudio device). Also worth noting, GarageBand ONLY supports 44.1khz sample rate, so there is nowhere in GBand that you can change this sample rate - and if you try changing the rate in the Mac Audio MIDI Setup window, it will simply flip back to 44.1 when you go back to GBand. Hope that helps! My older HD Pro works great with Logic Pro 9.