Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Search the Community

Showing results for tags 'osx'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Support
    • Multi-Effects Units
    • Variax Instruments
    • Amplifiers
    • Computer Based Recording
    • Live Sound
    • Pedals/Controllers
    • Dream Rig - Line 6 Product Integration
  • General Discussion
    • Tone Discussion
    • Line 6 Lounge

Categories

  • General FAQ
    • Operating System-specific Information
  • Tutorial Videos
  • Effects/Controllers
    • HELIX/HX
    • DL4 MkII Stompbox Modeler
    • M5
    • FBV Controllers (MKII / 3)
  • Amplifiers
    • Catalyst
    • Powercab
    • Spider V
  • POD
    • POD Go
    • POD Express
    • Pocket POD
  • Guitars
    • JTV / Shuriken / Variax Standard / Workbench HD
  • Relay G10 Digital Wireless
  • Recording
    • Helix Native
    • Metallurgy
    • Echo Farm/Amp Farm
    • POD Farm 1/2.0/2.5
    • Computer Audio Set Up and Troubleshooting
  • Legacy Products
    • POD
    • Amps
    • 1st Gen Variax Guitars / Bass / Workbench
    • Effects and Controllers
    • AMPLIFi Series
    • Live Sound
    • Digital Wireless
    • Mobile Products
    • POD Studio / Tone Port / GuitarPort
    • Software
    • Dream Rig

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Registered Products

  1. Hello, I didn't got replies from the DTedit author, so I post the link to the OSX version I've compiled today of his brilliant software. Some tweaking was necessary, so we must give a try and return some feedback. On my systems, win and mac, dtedit was not working. I've added a sysex identifying request after any Control Change message sent, and this works for me. I will try to compile the same code for Win32 very soon. Let me know! Flavio Ronco Torino, Italy. Download DTeditOSX.dmg file size: 22 MB ::UPDATE: I've updated the package, there was a wrong set of library files included. Please re-download it and give a try.
  2. Background Apple has pivoted away from using Intel-based CPUs with its computers, instead favoring the Apple Silicon processor, also known as the M1/M2 Chip. Later Intel and and all Apple Silicon systems run on macOS 12.0 Monterey and macOS 13.0 Ventura. As it stands, some Line 6 products are not fully supported on computers using Apple Silicon processors, so we cannot offer technical support for those products installed on M1/M2 systems at this time. We encourage you to please check with the manufacturers' websites of your music system’s hardware and software for M1/M2 compatibility. Workaround on M1/M2 Systems NOTE: Any workarounds offered are not official solutions. Issues experienced with workarounds offered cannot be addressed until official support is offered. Starting with Big Sur macOS 11, Apple introduced Rosetta v2, which allows applications to run in an emulated mode. Rosetta runs automatically with our software that is NOT a plugin. To use Rosetta with our plugins, locate your DAW in the Applications folder. Use command ⌘+I and check the “Open in Rosetta” box. You may have to rescan your plugins afterwards. Testing Software status on M1/M2 systems running macOS 12 Monterey and macOS 13 Ventura Metallurgy Collection: working as expected Helix Native: working as expected Echo Farm 3.0: requires Rosetta workaround Amp Farm 4.0: requires Rosetta workaround POD Farm 2 (Plugin): requires Rosetta workaround POD Farm 2 (Standalone): working as expected POD Farm 2 (Elements): working as expected HX Edit: working as expected POD Go Edit: working as expected Powercab Edit: working as expected POD HD Edit: working as expected POD HD500 Edit: working as expected POD HD500X Edit: working as expected POD HD Pro X Edit: working as expected Spider Valve Mk II Edit: working as expected Spider V Remote: working as expected Spider IV Remote: working as expected Workbench HD: working as expected Line 6 FBV Control: working as expected Line 6 Updater: working as expected Line 6 License Manager: working as expected Helix Hardware Driver: working as expected POD Go Hardware Driver: working as expected Audio-MIDI Driver 1.0.0 (TonePort/POD Studio/GuitarPort): working as expected Software that will not be updated to support Silicon-based systems: StageScape: Audio Driver POD X3: Audio Drivers, Editors, Updaters, Control Panel app and License Manager POD XT: Audio Drivers, Editors, Updaters, Control Panel app and License Manager TonePort UX8: Audio Drivers, Updaters, Control Panel app and License Manager TonePort/POD Studio KB37: Audio Drivers, Updaters, Control Panel app and License Manager POD HD 300/400: Audio Drivers, Updaters, Control Panel app and License Manager Line 6 Monkey Line 6 Hardware status on M1/M2 systems running macOS 12 Monterey or macOS 13 Ventura: The following hardware products are being tested for general compatibility with macOS 12 Monterey or macOS 13 Ventura running on M1/M2 CPU systems when using the latest available Line 6 driver or the macOS 12 or 13 class-compliant driver, as applicable. AMPLIFi 30/75/150: working as expected AMPLIFi FX100: working as expected AMPLIFi TT: working as expected Firehawk FX: working as expected Firehawk 1500: working as expected Helix Floor: working as expected Helix LT: working as expected Helix Rack/Control: working as expected HX Effects: working as expected HX Stomp: working as expected HX Stomp XL: working as expected POD Go: working as expected POD Go Wireless: working as expected PowerCab 112 Plus: working as expected PowerCab 212 Plus: working as expected Catalyst Amps: working as expected DL4 MkII: working as expected Relay G10: working as expected Relay G10S: working as expected Relay G10T: working as expected Relay G10TII: working as expected Relay G70: working as expected Relay G75: working as expected Relay TB516G: working as expected Spider V 20/30/60/120/240/240 HC: working as expected POD HD: working as expected POD HD 500: working as expected POD HD 500X: working as expected POD HD Pro: working as expected POD HD Pro X: working as expected Sonic Port VX: working as expected Variax: working as expected Variax USB Interface: working as expected Mobile Keys 25/49: working as expected TonePort DI/GX/UX1/UX2/: working as expected POD Studio GX/UX1/UX2: working as expected
  3. Hello Line6 Team, I am currently writing an open source software (LGPLv2) to use the podhd 500x under Linux in a similar manner as "POD HD 500X edit". Would it be possible to have the protocol data sheet to complete my implementation? I am currently supporting basic features, i.e. reading and writing pedals settings, but I am lacking some understanding of the whole protocol. Thanks in advance, Aurryon The code https://github.com/StarAurryon/lpedit Note: Protocol reverse engineering is perfectly legal if we listen to the usb port, which is what I am doing. As a EU citizen I would also be allowed to reverse the assembly in the name of interoperability: which I am not doing now as it is harder
  4. Hello there I recently purchased the Helix LT and I have been enjoying it both for playing at home, and for party gigs. I realised that I can practise in my room by connecting it through the USB, and play through my jbl LSR305 monitors, which really sounds great, and also gives convenient parameter control through the HX edit software. A recurring error is however stifling my enthusiasm. When I've been playing for say 5-10 minutes, the Helix freezes and becomes unresponsive. In the HX edit software it disconnects from the device, and refuses to recognise that the helix is still connected. The sound goes through unaltered, but I can now no longer change parameters, and to access this again I have to reboot the pedal (discarding possible changes). This is really problematic, as it essentially removes the functionality that I want from the pedal, and googling it has yielded no results. Does anyone have similar experiences? My specs are: Helix LT is running v2.54.0 firmware. 13'' MacBook pro running high sierra 10.13.5 HX edit v. 2.52 playing through Logic Pro X v. 10.2.0 Best, Jonas
  5. Hi ! I've recently bought Pod Farm 2.5 hoping to make it work on Propellerheads Reason 9.5. I try to make everything work on an iMac on Sierra. I've found the directory containing the VST plugin, namely /Library/Audio/Plug-ins/VST/Line 6 but Reason can't find the plugins... I already use Kontakt Player as a VST plugin on /Library/Audio/Plug-ins/VST, without any problem. If anyone has a hint, it is welcome ;)
  6. Here is how to update the Firehawk 1500 step by step: Note: The versions of the drivers and software may have older versions. Make sure to always select the latest versions. For Windows 7, 8, or 10 systems, please start with step 1. For OSX 10.8 and up, skip to step 8. 1. In order for your computer to see the Firehawk 1500 you will need to install the driver for the device to your computer. Open a web browser and navigate to www.Line6.com/software and select Product: Firehawk Software: Drivers from the drop down menus at the top of the page. 2. Pick the top selection from the next page by selecting "Get Download". 3. Accept the terms. 4. If in Windows, choose the run option and run the installer or navigate to the downloads window and run the installer. Pressing Control + J will bring up the downloads menu in most windows browsers, alt + command + L for Safari on Mac. 5.Disconnect your Firehawk from the computer if it's connected via USB and run the installer. 6. In the installer make sure the drivers from the Firehawk have a green check. Click next until the installer completes. 7. Reconnect Hardware when prompted and let Windows assign the driver. Now your computer will be able to communicate properly with the Firehawk. 8. Now, let's download the updater utility. Open your web browser, navigate back to www.Line6.com/software and select Line 6 Updater under the software drop down menu. 9. Select get download under the top selection, the latest choice will always be at the top. 10. Accept the agreement. 11. If in Windows, choose the run option and run the installer or navigate to the downloads window and run the installer. Pressing Control + J will bring up the downloads menu in most Windows browsers, alt + command + L for Safari on Mac. Or the installer will be in your downloads folder. 12. Run the installer for Line 6 updater. 13. In the installer make sure Updater has a green check, click next until the installer completes. 14. Run Line 6 updater from the start menu on WIn 7, Applications Folder on a Mac, or C:/Program Files (86)/Line 6 on Windows 8. 15. Accept the agreement. 16. Login to Updater with your username and password from the Line 6 website. 17. Select the Firehawk. 18. Select the latest version of flash memory. This is always the top selection. 19. NOTE: This part of the updater explains how to reset the Firehawk if it should fail. You can refer to the image here for instructions if that should ever happen. Click Next to Proceed. 20. Wait for the progress bar to complete. 21. Updater will let you know when the update is complete.
  7. I recently bought a used POD HD300 and I use the POD HD300 Edit software on OSX High Sierra with no problem. There is however an OSX update to Mojave and I do not know if I updated the OS would the POD HD300 Edit still work. Mojave is not mentioned in the supported OS list of the latest 2.03 (10/14/14) version of the Edit software. Is there anyone who has OSX Mojave with a usable POD HD300 Edit out there?
  8. i just bought pod farm 2.5 im using mac osx 10.12.6 running fl studio 12 I have installed pod farm ran line 6 monkey and updated everything registered and authorized my ux2 authorized my mac I have no issues with it as a stand alone
  9. MacBook Pro (Retina, 15-inch, Mid 2015) Processor: 2.5 GHz Intel Core i7 Memory: 16GB 1600 MHz DDR3 OS X HighSierra 10.13.5 TonePort KB37 Driver 7.6.7 Flash Memory 1.03 Line6 Monkey 1.77 Since my KB37 doesn't send midi data like modulation wheel or stop, play, record... etc. I tried to re-install flash memory of 1.03 many times but doesn't work. And shows this message: ----- Update failed. (Code 80007204) Hardware device failed to enter update mode. ----- Plz give me a solution. Thanks.
  10. Hey all I just got the hx effects today and am trying to update it to 2.5. I have a macbook pro running 10.9.5. I downloaded the most recent Line 6 Updater from https://line6.com/software/?submit=Show&name=Line+6+Updater. I am having problems getting my HX effects updated. I plugged the included cord in to my computer and the hx effects. I can start the updater when the hx effects is powered off. I, of course, don't see the device in the "Select device to update" list after signing in. Once I turn the hx effects on, the updater crashes with the error "Line 6 Updater quit unexpectedly." I have tried different USB ports on my computer and have restarted once. Anyone have any ideas? Thanks!
  11. The problem is pretty self explanatory, and will need an alternate download given the idiotic update model Line 6 picked for the Monkey.
  12. Simple question here. I have a really awesome set of bluetooth headphones and just bought a Pod UX1 to compliment my Spider Valve MKII. I have opened Logic Pro X and also tried Garageband and noticed latency. I also noticed that Pod Farm will not work with the BT headphones at all. Like the original question asks, is latency avoidable? Also, is it possible to get Pod Farm to see the BT headphones. System is a MacBook Pro 2.8GHz i7 with 16GB RAM. Thanks everyone.
  13. I was happy to see that Line 6 finally added a computer-based version of the Spider V Remote app so that I can dig in deeper on my computer screen and change tones while using a DAW. There was also talk in the email that I received of downloading new tones from the customtone.com website to upload and use in the app. I have not found this to be true. The customtone page does not list the Spider V and when I try and download a tone I get a message that says "Valid product registration or software purchase required to use CustomTone. I have registered my Spider and so this message is quite confusing Love my Spider but please work out the kinks.
  14. Hi, Recently I updated my system to a beta version of mac osx sierra and because of this I'm unable to use my pod hd bean. Line 6 Monkey is able to determine the device and shows options to update drivers. After updating the drivers there is an automatic restart and line 6 Monkey shows me the same old driver and gives an option to update. Have tried installing the drivers manually from the line 6 website but still the same issue. It is not possible now to downgrade the mac to older OS. Any help appreciated. Thanks!
  15. Cubase LE 9 on OSX and Windows no longer supports 32-bit plug-ins, which includes Pod Farm 2.x. You can read more about this change on the Steinberg website here: https://www.steinberg.net/en/newsandevents/news/newsdetail/article/cubase-85-is-last-version-to-be-32-bit-compatible-3469.html https://www.steinberg.net/en/newsandevents/news/newsdetail/article/future-releases-as-64-bit-only-3778.html
  16. I have An Apple MacBook Pro i7, running El Captain 10.11.6. I recently upgraded to El Captain and did not have any issues using GearBox with Yosemite. If I launch GearBox without my TonePort UX2 plugged into the USB, GearBox will start up just fine but when I plug the USB in for my UX2 I get the pinwheel of death. If I launch GearBox and have my UX2 plugged in before i launch, it gets stuck on "Initializing DSP" I downloaded POD Farm 2 and it woks but only in a trial capacity as I have not purchased the program, but it does works with Garageband. I can launch Garage Band and use my TonePort and the effects Garage Band has pre installed. All my drivers are up to date according to Monkey. It all seems to revolve around GearBox. Any known solutions to this?
  17. I've been using my Pod UX1 for about 5 years now with absolutely no issues. Today i updated to El Capitan and suddenly i'm getting no audio from pod farm and no visible input signal. Not only that but when i try to open Logic Pro 9 it scans all my audio units and then stops on POD Farm forever. It will NOT scan Podfarm. What is wrong here? I have all the latest drivers etc but it just isn't working. Should i try reinstalling podfarm or is it simply that Line 6 hasn't updated it yet? HELP
  18. I’m not sure if this is a software or hardware problem but now it’s really driving me crazy. Since acquiring my Helix at the end of November 2015, I have been using it at the heart of of my studio set up, effectively replacing my old POD HD500 and Focusrite Saffire Firewire interface recording system. Essentially the Helix is connected via USB to my 6 month old, 3.3GHz iMac Retina 5K (with 32GB of RAM installed). From new the Helix has had every update done, up to the latest firmware v1.06.5 on the release date16th Feb and the Mac is now OS X El Capitan 10.11.14 (installed 28th March, a while after problems started). My near field powered monitors are cabled to the Helix 1/4†out sockets with gold plated jack plugs and my Variax then hooks up on the dedicated input. In addition my, very old (if it’s good enough for Brian Eno then it’s good enough for me), RolandED PC-180 MIDI keyboard controller which uses the old school DIN plug to input MIDI data to the various software synths available in GarageBand or whatever, goes to “MIDI in†on the rear of the Helix. I have to say that the swap over was quick and painless (i.e. no drivers etc.). Everything simply worked perfectly normally, as it should, until about 2 weeks back (early March) when things started to get very weird. Any audio from iTunes or via the internet seems to function normally. It’s when I playback a GarageBand/Logic X track, it will start out O.K., and then after very short while (less than a couple of minutes) the audio degrades to the point where it sounds like it is running through a bit crusher effect, spluttering and popping until it ultimately fades into silence. This then becomes a system wide problem, screwing any and all up audio coming from any other source, iTunes, YouTube etc. The only way to clear the bug is by switching back and forth to the iMac onboard audio, except on returning to your favourite DAW it happens again, and again, and again. Apart from the audio output being screwed, the MIDI has also ceased to work properly. Any pre-recorded MIDI played back O.K. until the audio channels start to go flakey. Using the PC-180 keyboard I can get soft synths to trigger intermittently on single notes in GBand, but in Logic - not a sound, nada, zip, zilch, zero. It’s totally bizarre, because nothing has really changed - once the recording system had been set up, it was, fire and forget, nothing else required. It just worked! O.K. To try and figure this out I wanted to go through everything in the chain. First hurdle - cannot test the Retina iMac and FocusRite because the interface is FireWire400 into the module and the Mac is Thunderbolt to FW800 crossover. ARRGH! Right! I decided to connect everything up to the old iMac, how it had been pre Helix days. So I have the Focusrite patched to the MIDI keyboard on DIN, that sends/receives audio and MIDI via FireWire and outputs audio to the monitors. Yep - that works just fine, no stuttering, soft synths respond to slow swelling chords and fast single note sequences. So, now I use Helix as the hub, in the way listed above except this time it’s the old Mac running GarageBand. Well, I think you can guess what happens - correct we are back with the spluttering, stuttering, crackling popping and fading audio and flakey MIDI. Now don’t get me wrong but, when it comes to this hi tech MIDI sort of stuff, friends and associates usually ask me to fix it for them (hence the handle “data commandoâ€). I’ve been using computers and MIDI for over 30 years, in 1984 I owned an early Roland JX3P - the first synth with MIDI - which was hooked up to a Yamaha CX5M II MSX Computer System, and later to an Atari 1040ST (1986) running Sternberg’s Pro24 Sequencer (early version of Cubase). I still have a collection of rack mounted vintage synth/sample,FX modules e.g., Roland U110 and D110, Yamaha TX81Z and SPX90, Kawai K3M and K1M plus an AKAI S950 and XE8. Oh yeah, there is a Roland GR33, BOSS GT6, PODXT Live and a HD500 along the back wall, and a Korg digital drum machine in a box somewhere in here. Please note: on the iMac I have done all the usual “fix it†stuff - repair permissions, reset SMC and zapped the PRAM/NVRAM. There must be someone out here in Helix land who can maybe give me a clue has to WTF is happening - please help! And while I’m at it - why does Line 6 and the Helix state audio sample rates of 44.1, 48, 88.2 and 96KHz. On the Mac only 48 can be selected - surely some mistake? See attached png. At the moment this whole shebang is totally FUBAR!
  19. Hi there, let me start of by saying that I absolutely love the Helix: The sounds, the ease of use, the flexibility, the looks! However, at this moment my Macbook pro and Helix don't communicate that well. The App is very unstable and crashes every few seconds/minutes when exporting or importing or doing nothing at all, can't find the Helix, disconnects and gives me messages like: "No symbol lookup table present for models and parameters", and so on. Today I installed the update and the problem persists, no worse no better, but just almost impossible to work with. I have a ticket open on this issue, so I'm expecting it to be solved anytime soon. I opened this topic, to see if anybody has found a practical workaround for this and to learn from other experiences. tnx!
  20. fukuri

    Helix and Logic

    Is there a known clock issue using this with OSX? Logic sees the interface but loses clock after a couple of minutes (at least I assume that's what is making the audio all jittery and daleky) Does anyone use this with Logic with no issues?
  21. I'm currently running the 4th public beta of OSX El Capitan which will be released to all Mac users in the near future. I've encountered an issue where the operating system is not able to use the POD HD500 as an external soundcard for music production in Logic Pro X or even just for general media consumption. I was going to chalk it up to it being an unperfected beta release but the curious thing is that my Native Instruments Guitar Rig audio device works perfectly fine. Will Line 6 release a driver update after the public release of the operating system? Have Line 6 had to do this in the past when new operating systems are released? Anyone experiencing a similar issue? Any feedback would be much obliged. Cheers, Jordan.
  22. I have been using my HD500 through USB with my old Macbook Pro to control patch changes via MIDI for a couple of years now and it has worked great. I use Digital Performer for my DAW. I recently purchased a new Macbook Air running OSX Mavericks ver. 10.9.4 and the new Macbook doesn't recognise the HD500 as a MIDI devise in Audio MIDI Setup. I have the latest driver 7.3.6, from Line6 installed. The HD500 has all the latest updated software thru Monkey. The Macbook Air does recognize the HD500 as an audio devise and I can get sound to and from the HD500. They say that the driver makes it so you can use MIDI over the USB connection. Is there something I'm missing in the setup?
  23. Here is how to update the Firehawk FX step by step: For Windows 7, 8, or 10 systems, please start with step 1. For OSX 10.8 and up, skip to step 8. 1. In order for your computer to see the Firehawk you will need to install the driver for the device to your computer. open a web browser and navigate to line6.com/software and select Product: Firehawk FX Software: Drivers from the drop down menus at the top of the page. 2. Pick the top selection from the next page by selecting "Get Download". 3. Accept the terms. 4. If in Windows, choose the run option and run the installer or navigate to the downloads window and run the installer. Pressing Control + J will bring up the downloads menu in most windows browsers, alt + command + L for Safari on Mac. 5.Disconnect your Firehawk from the computer if it's connected via USB and run the installer. 6. In the installer make sure the drivers from the Firehawk have a green check. Click next until the installer completes. 7. Reconnect Hardware when prompted and let Windows assign the driver. Now your computer will be able to communicate properly with the Firehawk. Make sure the Firehawk is turned on attempting when this. 8. Now, lets download the updater utility. Open your web browser, navigate back to line6.com/software and select Line 6 Updater under the software drop down menu. 9. Select get download under the top selection: 10. Accept the agreement. 11. If in Windows, choose the run option and run the installer or navigate to the downloads window and run the installer. Pressing Control + J will bring up the downloads menu in most windows browsers, alt + command + L for Safari on Mac. OIr the installer will be in your downloads folder. 12. Run the installer for Line 6 updater. 13. In the installer make sure Updater has a green check, click next until the installer completes. 14. Run Line 6 updater from the start menu on WIn 7, Applications Folder on a Mac, or C:/Program Files (86)/Line 6 on Windows 8. 15. Accept the agreement. 16. Login to Updater with your username and password from the Line 6 website. 17. Select the Firehawk. 18. Select the latest version of flash memory. This is always the top selection. 19. NOTE: This part of the updater explains how to reset the Firehawk if it should fail. You can refer to the image here for instructions if that should ever happen. Click Next to Proceed. 20. Wait for the progress bar to complete. 21. Updater will let you know when the update is complete.
  24. So Ive been having problems with L6 monkey when I try to update it on OS X. Now I notified Line 6 of my problem however that was two weeks ago so I figure this is the next best. When I click on the icon it bounces like it normally does in mac, but then nothing, no window, no nothing and I can't make it do anymore. I tried uninstalling then reinstalling and still nothing. I was hoping to update and maybe look at the new model packs but thats not looking very likely.
  25. The HW/SW details: PowerMac G5 1.8 GHz DP/4GB RAM Mac OS X 10.5.8 PodXT Live info screen displays: v 3.01 / USB v1.12 / ESN 01278564 Line 6 Edit v 3.0.1 Line 6 Monkey v 1.32 Brand new USB cable, tested, known to work with Printer & Scanner. All USB ports work fine with every device I’ve tested. I purchased my Pod XT Live used, several months ago. I’ve tested it with guitar amps and headphones, and it seems to function properly. It’s in perfect condition, save for a few small paint scuffs on the corners and edges of the housing. The retirement age gent I bought it from said he’s never had it out of the house, and I believe him. There’s not even any visible wear on the footswitches or the CC pedal. Unit seems virtually new. After connecting the Pod XT Live to my PowerMac and launching Line 6 Edit, the software does not recognize that the Pod is connected, telling me it is “offline.†Nothing I do in Configuration seems to get them to handshake. I’ve connected directly to the front and back USB ports on my G5. I’ve disconnected all devices except for my mouse and keyboard (which are both wired) Help files in Line 6 Edit suggest that I run Line 6 Monkey to make sure I’m fully up-to-date, but even when I apply the same username and password which allows me access to the Line 6 website and this Forum, a floating alert window appears telling me that: My rebuttals to the Alert message: • I am ALWAYS connected to the internet with a robust, fast cable connection. • I have no system-wide popup blockers, or malware utilities running. • Just for good measure, I disabled popup blockers & AdBlock Plus in my browsers • (not addressed except on the License Manager FAQ page...No anonymizing apps in use) I perused the Line 6 forums & support pages and followed suggestions to download the Line 6 License Manager; after some trial and error I discovered that v 1.0.4 is the most current which will install on PPC architecture. It was only after I installed it and logged in (this time with success, I got no alerts about a failure to connect to the internet) that a message was displayed in the License Manager app that told me: Sooo...what installation or troubleshooting procedure am I missing here? BTW...the following message on the following page http://line6.com/support/page/kb/_/computer-based-recording/computer-audio-set-up-and-troubleshooting/usb-compatibility-with-line-6-devices-r342 is a HUGE engineering FAIL: ------------------------------------------ If you have tried all available USB ports on your computer and have either no device recognition or poor audio quality (clicks-pops), you will want to consider purchasing a PCI USB 2.0 card to connect your Line 6 USB audio interface. ------------------------------------------ Thanks in advance for pointing me toward any solutions...I champing at the bit to drive this thing around in Apple’s Logic!
×
×
  • Create New...