Line 6 V 2.xx Editor Workaround... 24-05-04

Line 6 EDIT V2 .xx is now available for download , download Line 6 Edit from the Line 6 website

Line 6 Edit V2.xx is free Windows and Macintosh OS X software from Line 6 that provides complete editor/librarian features for PODxt, PODxt Pro, Vetta II, HD 147, Flextone III and POD 2.0. It can be run on its own and in tandem with ToneTransfer / Custom Tone to transfer Tones directly from the online library to your connected Line 6 product and Line 6 Edit.

Due to different set-ups and sometimes behaviours of different computer systems a workaround is sometimes needed to get everything working in order. Underneath workaround for when you are running into trouble with the interconnection between hard and software. Hope this helps..., it's unedited tekst directly from Line 6.

WORKAROUNDS BY LINE 6

Here are the "known issues and workarounds" that we've compiled for Line 6 Edit. If you are experiencing problems with the software, please start by working through these, then let us know if anything's still not working for you by replying to this posting here. When posting a message seeking troubleshooting assistance, PLEASE be as complete as possible in telling us what version of Line 6 Edit you are using, what Line 6 hardware, what MIDI interface, what version of Windows or Mac OS X, and aything else about your set up that might help us solve your problem. We'll do our best to help!
Line 6 Edit MIDI Configuration Basics (after latest Java and Line 6 Edit are installed)

Windows XP:

1.Set up 2-way MIDI connections between the MIDI Interface and Line 6 Amp (2 cables: MIDI Interface Out->L6 Amp In and L6 Amp Out->MIDI Interface In). Confirm MIDI Interface is connected to the PC properly. If Pod XT 1.05 is used, connect the Pod XT via USB or MIDI. If Pod XT 1.02 is used, use MIDI. Power up the Line 6 Amp or Pod and reboot the PC.

2.Open XP Control Panel / Sound and Audio Devices / Hardware tab and click on the name of the MIDI Interface. User should see "Device Status: This device is working properly". Also go to Audio tab and check to see if MIDI Interface is available under MIDI Music Playback / Default Device (it is not necessary to select it - just confirm it's available). If Pod XT is plugged in via USB instead of a MIDI Interface, it should be available as both a MIDI Device and a Sound Device.

...if MIDI Interface name (or Pod XT) does not appear in the Hardware list, install latest Driver for MIDI Interface (or Pod XT), as provided by MIDI Interface manufacturer. Download it from their web site, install it on the PC then repeat Step 2 above.

3.Launch Line 6 Edit and click Configure. In the Configure Line 6 Edit window, MIDI tab, select the MIDI Interface (previously confirmed in the XP Control Panel as "working properly") for both MIDI Port In and MIDI Port Out . Click Detect. The Detect button should now have a blue outline and the connected Line 6 Hardware name should appear.

4.Click Okay. Line 6 Edit should load Tones and be ready for editing.

Mac OSX:

1.Set up 2-way MIDI connections between the MIDI Interface and Line 6 Amp (2 cables: MIDI Interface Out->L6 Amp In and L6 Amp Out->MIDI Interface In). Confirm MIDI Interface is connected to the Mac properly. If Pod XT 1.05 is used, connect the Pod XT via USB or MIDI. If Pod XT 1.02 is used, use MIDI. Power up the Line 6 Amp or Pod and reboot the Mac.

2.Open Audio MIDI Setup and confirm that the MIDI Interface appears in the MIDI Devices window.
a.If Pod XT is used, its Icon should appear in the window - if so, move on to Step 3 below.
b.If the MIDI Interface was previously set up and connected to the Line 6 Amp or Pod, double-click the Device Icon, open More Properties / Basic tab and confirm MIDI Channel 1 is selected for MIDI Send and Receive, click Okay then proceed to Step 3 below.
c.If there are no Devices connected to the MIDI Interface icon, click Add Device, name it Line 6 Device, connect it to the MIDI Interface Icon with virtual cables using the mouse, then double-click the Device Icon, open More Properties / Basic tab and select MIDI Channel 1 for MIDI Send and Receive, click Okay and proceed to Step 3 below.

...if MIDI Interface Icon (or Pod XT Icon) does not appear in the MIDI Devices window, install latest Driver for MIDI Interface (or Pod XT), as provided by MIDI Interface manufacturer. Download it from their web site, install it on the Mac then repeat Step 2 above.

3.Launch Line 6 Edit and click Configure. In the Configure Line 6 Edit window, MIDI tab, select the MIDI Interface (confirmed above in Audio MIDI Setup) for both MIDI Port In and MIDI Port Out . If Pod XT via USB is used, select Pod XT for both MIDI Port In and MIDI Port Out. Click Detect. The Detect button should now have a blue outline and the connected Line 6 Device name should appear.

4.Click Okay. Line 6 Edit should load Tones and be ready for editing.

=============

Known issues:

Windows/Mac OS X:

Latest PODxt firmware required: PODxt 1.05 Firmware is required. Install it using the PODxt Updater software downloadable from software.line6.com . When a PODxt is running firmware 1.02 and connected via USB on Windows, Line 6 Edit may successfully Detect the PODxt in the Configure window, but then report "PODxt is not responding." On a Macintosh, it may fail to detect the PODxt and also report "No Device connected." Upgrading the PODxt to firmware 1.05 should fix this problem. Or, while using 1.02, you should be able to be connected with MIDI cables instead, select the MIDI ports that these cables are connected to, and Line 6 Edit should work normally. (PODxt Pro does not require a firmware update; all versions of firmware shipped work fine with Line 6 Edit.)

PODxt USB transfer failure: The PODxt (and PODxt Pro) will sometimes fail to send all of its patches when using MIDI over USB with Line 6 Edit. Once this problem occurs, both the PODxt and Line 6 Edit must be restarted (quit Line 6 Edit, power cycle the PODxt, then re-launch Line 6 Edit). This problem occurs only on selected computers, and may be related to communication errors on the USB pipe of that computer. Line 6 Engineering is currently working to attempt to fully understand the problem, and fix it.

Edirol: Users have reported problems with Edirol MIDI interfaces used with old Edirol drivers, or the standard MIDI interface support built into Operating System software. Their Edirol interface worked fine with other software, but not Line 6 Edit. They reported that switching to the latest Edirol drivers for Windows fixed these problems. With versions of Line 6 Edit before 1.99.5, we found some remaining problems on OS X with the latest Edirol drivers. These appear to be fixed when using Line 6 Edit 1.99.5.

Emagic AMT 8 (and other MIDI interfaces?): There seems to be a compatibility issue between Line 6 Edit and the AMT 8 MIDI interface from Emagic. There is no known solution at this time. It also seems likely that the AMT4 has the same incompatibility, and at least one user has reported problems with the Unitor8.

Yamaha UX-16: One user also reported that after extensive testing he believes the Yamaha UX-16 MIDI interface is also incompatible.

Cubase: If Line 6 Edit is to be run alongside Cubase, the MIDI ports that Line 6 Edit will use need to be disabled inside of Cubase (they are all enabled by default).

Flextone II/ POD Pro: You can use a POD Pro or Flextone II with Line 6 Edit by selecting POD 2.0 mode. (This does not affect PODxt Pro or Flextone III.) A POD Pro or Flextone II used with Line 6 Edit will be treated as a POD 2.0 by www.CustomTone.com.

Non-allowed characters: Line 6 hardware products allow certain characters ( / * ? " < > | \ : [ ] ) to be used in the names of Tones (aka Channel Memories) that are not supported by some versions of Windows and/or Mac OS X. To avoid problems, these characters will be removed from the filename that Line 6 Edit auto-generates when saving a Tone to your computer. The name that is shown in the Editor Windows of Line 6, and stored in the Line 6 hardware, will not be affected by this.

Tone Name Length: Line 6 Edit allows Tone names up to 32 characters, but Line 6 devices limited Tone names to 16 characters. If a Tone name is longer than 16 characters and it is sent to a device and then retrieved, the Tone name will be truncated.

Absolute/Relative Knobs: Line 6 Edit will re-set the Vetta to use the "Absolute" mode for the knobs if you've selected "Relative" mode. It pops up a dialog to inform the user of this fact.

Vetta Tempo: In the Vetta Editor, Tempo is displayed and editable only if at least one effect is set to lock to Tempo and turned on. Editing Tempo will cause the amp's display to show the edit page for one of the effects that is locked to Tempo. Line 6 Edit displays Vetta's Channel Tempo with a decimal. On the amp, the value is rounded up (no decimal).

===============

Windows Only:

Hibernate: Line 6 Edit can (but doesn't always) become unresponsive when returning from Hibernate mode in Windows. The application must be terminated from the task manager. We recommend that you disable all Power Management features to avoid problems.

Java 1.4.2 or Higher: Line 6 Edit requires version 1.4.2 or later of the Sun Java VM (The Microsoft Java VM is not supported). If a previous version is installed, Line 6 Edit will fail to run. Use the Add/Remove Programs control panel in Windows to select the Java Runtime Environment, check its version, and remove it if it is an older version. Then install the latest Java software by running the Line 6 Edit installer with an active Internet connection (it will grab the latest Java from the web), or get the latest Java from www.java.com.

Line 6 Edit installer errors during Java download: The Line 6 Edit installer on Windows should check to see what version of Java is installed (if any), and install an up to date version if necessary. It does this by grabbing a Java installer from Sun's website as it runs. If it can't get the Java installer for some reason, it make give an error message such as "Unknown error during Java download." If this happens, an up to date Java installer can be downloaded separately from www.java.com and run, and then the Line 6 Edit installer can be run.

Custom Tone and Microsoft VM: (We need more detail on this one, because this fix apparently hasn't worked for some users.) Custom Tone requires version 1.4.2 or later of the Sun Java VM. If the Microsoft VM is selected as the default Java plug-in, the LOAD NOW buttons in Custom Tone will not be displayed at the right side of each Tone in the library listing. Make sure Java 1.4.2 or higher is installed (as shown in the Add/Remove program control panel in Windows), then open the Java Plug-In control panel in Windows, click the Browser tab there and check the box to use the Java (TM) Plug-in as the default Runtime environment for Internet Explorer. Restart Explorer, and ToneTransfer and its LOAD NOW buttons should work.

DDHELP.EXE Crash on exit: One user on Windows 98SE reported that each time he quit Line 6 Edit, it crashed and gave an error message saying that "DDHELP.EXE has caused an illegal exception in <unknown>…". This user reported that the problem was fixed when they downgraded Java to 1.4.0_04, which may indicate that this version of Java will work better from some users of 98SE.

===============

Workarounds:

Cross-Platform:

Restart: If problems are encountered with Line 6 Edit, it is always a good idea, as a first troubleshooting step, to try quitting and restarting to see if that corrects the problem.

Bulk Dump SysEx Files: Line 6 Edit loads MIDI Sysex files containing the data for a single Tone (patch) for a supported device, but does not load "bulk dump" files that contain all the patches from a device, except for a Vetta II.
…workaround: User Line 6 Edit to save a Bundle file of the hardware device's current Tones (if you want to save them), transfer the SysEx to the hardware device using a SysEx utility like MIDI Ox, then use Line 6 Edit to save a Bundle file from the device and the data from the SysEx file will now be in the Bundle file.

Load Amp 2: The "Load Amp 2' feature available for Vetta II editing allows a Tone file to be opened and loaded into Amp 2, and is intended for loading the Amp/Cab portion of a PODxt Tone into Vetta's Amp/Cab 2. SoundDiver or SysEx files can't be used with this feature.
…workaround: If a user wants to use a SoundDiver or Sysex file as the source for Amp 2 settings, they must first convert the file to a Tone file, and may then use that file with this feature.

Mac OSX:

1.Hot-swapping any MIDI or USB Device then re-configuring L6E and trying to load a Tone from ToneTransfer may cause Safari to "hang" showing its "beach ball: cursor, requiring a force quit.

...workaround: set up the desired MIDI Device before booting Mac and using L6E, or reboot Mac if a hot-swap is initiated, then re-launch L6E.

Re-configuring fails: Re-configuration from one MIDI Device to another (MIDI>MIDI or MIDI>USB) can cause Line 6 Edit to respond as if the first Device is still connected. The result is that some Tones won't load into the second Device, because the MIDI SysEx data from Line 6 Edit to the second Device (upon loading a Tone) will carry the first Device's Family I.D.
...workaround: re-launch L6E if a Device re-configuration is initiated.

Recan MIDI in Audio MIDI Setup disabled M-Audio MIDI interfaces: Initiating a Rescan MIDI command in Mac Audio MIDI Setup utility will 'gray out' an active M-Audio MIDI Interface and cause problems with Line 6 Edit. (This may be an M-Audio Driver/OSX bug.)
...workaround: if Rescan MIDI is initiated in Audio MIDI Setup utility and the MIDI Interface greys out, quit Line 6 Edit if open, then quit Audio MIDI Setup and re-launch it. The MIDI Interface will automatically become active - do not Rescan MIDI a second time. Then re-launch Line 6 Edit.

Windows:

USB Plug/Unplug: Line 6 Edit will not survive a USB unplug or Line 6 Device power cycle. The App may freeze and require a PC reboot.
...workaround: quit Line 6 Edit before making any USB or MIDI Device re-connects, then check Control Panel settings to confirm selection of the desired Audio & MIDI Interface and re-launch Line 6 Edit. For a trouble-free scenario, reboot the PC.

MIDI not working: In case of MIDI problems, locate the Windows control panel called "Sound and Audio Devices" or "Sounds and Multimedia" or something like that (each flavor of Windows calls it something different), choose the Hardware tab and confirm that your MIDI Interface (or PODxt connected via USB) is there and shows "This device is working properly" when you click on the name. Then launch Line 6 Edit, click the Configure button and confirm both MIDI In Port and MIDI Out Port are set to your MIDI Interface in the 'Configure Line 6 Edit' window. If all is confirmed, click Detect and the Detect button will have a blue outline. If so, click Okay and it should work. After confirming your MIDI Interface is "working properly" as outlined above, reboot if you've had another MIDI program open. Sometimes a MIDI app will 'claim' the MIDI Interface and not release it to the next app if it's still open - sometimes even after the other app has been quit.