silverhead

Yes, keeping an old XP system is the way to go if you want to keep old technology working. And those who want top keep their Variax JTV/Standard working with Workbench HD in the future should take note of the last OS supported by Line 6 for those products (when that time inevitably comes some years from now) and keep a machine of that vintage on hand. By that time I expect Line 6 will have released the next generation of the Variax/Workbench products whatever/whenever they may be. This applies to any Windows (and Mac) based programs that have been around for decades, in all industries. It's certainly not unique to Workbench or to Line 6. On my shelf right now I see boxes and CDs of Microsoft Project 2002 and Microsoft Small Business 2003. Neither of those products work on my Win10 system. Time to throw them out. Microsoft has long since stopped supporting those dinosaurs as new versions of Windows were released. The good news is that your Variax 300 continues to work, and so would Workbench if you had an old XP system.

Alternate turnings in a Variax 300 do not work with Helix nor with any previous guitar multi-FX processor like the POD HD series. The Variax 300 supports alternate tunings within the specific Variax models using Workbench. This is a limitation of the Variax 300, not Helix. In fact, Helix does not support any sort of interaction with older Variax models like the 300. In some cases the 300 will respond to model selections in a Helix preset but it is not a supported feature and may not work reliably or in all cases. Since your 300 seems to respond to model selectoins within a Helix preset you could use Workbench to define the desired alternate tuning within a Variax model and then select that model in the Helix preset.

It is beneficial to do the update. There have been new features and models added this year. To back up the Helix device before updating, connect Helix to your computer using the USB connection and run the current Helix app/editor which should be installed on your computer. Select a Setlist and use the Export command to make a copy of the setlist on your computer. Do this for each setlist. Do not use the Export Bundle command - that is not a good option before updating. To update, go to the Downloads section of this website (under the Support tab above). Select Helix in the middle (Software) field. You will be presented with a detailed set of instructions, along with a Get Download button. Get the download and follow the instructions carefully.

The Sonic Port VX connects to the iPhone using the lightning connector (I think that's what it's called) not the Aux jack. However, there are about a zillion circumstances in which your question has no good answer. I believe Apple's answer is "We've trapped you. Buy this additional accessory that we will gouge you for in order to compensate for the lack of a ubiquitous and perfectly good decades old standard interface that we've decided to exclude in future products." They may use different words. 😎

For a jazz tone try the Rivet amp in Helix, based on the Roland Jazz Chorus 120 amp.

A setlist file contains all details of all presets, including snapshot data. Setlist files do not simply keep track of the preset order. Backing up individual presets within a setlist is not necessary as long as you back up the setlist, but it is prudent and often convenient. Check the file sizes. A setlist file should be much larger than a preset file - approx. 128 times larger I suspect. EDIT: I just checked file sizes. The above re: file sizes is not true so I don't know what's going on there but the setlist does contain all preset data.

Try searching your computer for all files matching your setlist names. It's at least conceivable that the Setlists you saved before updating were placed in a different folder, and you have in fact restored older setlists from the default folder from a previous (pre-snapshot) save.

Check your Output mode. For recording it should be set to Studio Direct.

Open a support ticket with Line 6. An ESN of a string of zeros generally indicates a hardware repair that was not fully completed.

Check your audio system settings in your DAW. Are you sure you are using the POD HD and its ASIO driver as your audio input/output device?

Have you downloaded and installed the driver?

Line 6 advises against using the 1/4" and VDI outputs simultaneously. While some people report that they do this without any problems there is a chance that some circuitry will be overloaded, causing damage.

What Line 6 product do you have that gave you the yellow leaflet? Go to the Downloads section of this website Under the Support tab above. Select the product (answer to above question) in the Products field and then select Pod Farm in the Software field. Then hit the GO button to download the Pod Farm software. Run the downloaded installer file.

Right - no different. Sorry for the unnecessary caution. As long as you're able to achieve satisfactory results there'll be no problem.

Two reasons: - retailers typically resell returned and cosmetically like-new units as brand new units at the original price. Especially if a new device is returned with the 10-day (or whatever) return policy period. - The original owner repacked the box with the wrong power supply. The retailers don't inspect the packages closely, know little about compatible power supplies, and don't notice clear differences like AC/DC or mAmps.

Be aware that if you use your Helix as the audio interface, it a full ASIO device. That means it operates as your audio input/output device when using a DAW. In turn, that means there will be latency when you use any amp sims or VSTs that run on your computer. It takes some number of milliseconds (enough to be noticeable) for your DAW/computer to take the incoming Helix signal, process it with the sim/VST, then get it back to Helix for output to speakers/headphones connected to Helix.

Good choice. Have fun!

So your choices are: - use a dynamic mic with the UX1, or - purchase a stand-alone phantom power device like those in the link I provided, or - replace the UX1 with an audio interface device that includes a phantom power switch (like the UX2 - there are many others but if you want Pod Farm for free you need to stick with a Line 6 device).

Can't say for sure. It's doing what it needs to do - and only it knows what's needed! :lol: But a preset is only a specification of the amps, cabs, FX models etc. The actual modeling of those elements is what's updated in the firmware itself, done during the update process before you start reloading setlists and presets.

Youneed to connect your mic to a device that provides phantom power first, then connect the output of that device into the UX1 input. A quick Google gave me this for devices that provide (stand-alone?) phantom power: https://ca.images.search.yahoo.com/yhs/search;_ylt=A0LEVik0uF5Y9E4APDkXFwx.;_ylu=X3oDMTBsa3ZzMnBvBHNlYwNzYwRjb2xvA2JmMQR2dGlkAw--?_adv_prop=image&fr=yhs-tightrope-tig4&va=phantom+power+device&hspart=tightrope&hsimp=yhs-tig4

That's because your presets had already been loaded (and rebuilt) from their v2.0 (or v2.1) state into v2.11 when you restored the older bundle. In general, and in future, you will usually find that all presets loaded for the first time into a newer firmware version need to be rebuilt. It's best to do that by restarting Helix immediately after importing the setlist of older presets - before doing any editing.

Your UX1 does not provide Phantom Power. You need to either use a dynamic microphone (they don't require phantom power) or use an additional device to provide the required phantom power to your condenser mic. The UX2, for instance, is a device that includes the ability to provide phantom power.

You're right - restoring the 2.0 bundle replaced the new 2.11 factory presets with the old. But you don't need to reinstall the 2.11 firmware - just restart Helix holding down FS 7&8 (see link below) to restore the v2.11 factory presets. But this will also replace any non-factory setlists with the empty factory setlists. So if you haven't already backed up any custom setlists do that first. Do not export the bundle - just your custom setlists one at a time. Then restore all factory v2.11 setlists and finally restore your custom setlists. http://line6.com/support/page/kb/_/effects-controllers/helix/helix-reset-procedures-and-troubleshooting-tricks-r768 After doing all that, restart Helix one final time. It will rebuild all presets in your newly installed custom setlists.

I never owned a 700 so can't comment on your main question. But now that you have a Pod HD Bean you should definitely get familiar with using the USB connection to your computer. Downloading patches is the least of the reasons for that. The main reason is for backing up your presets using the HD Edit program. The second reason is to update the firmware. Since you got the HD Bean recently it may not have the most recent firmware. Do you know if it does? If not you should update it. http://line6.com/support/page/kb/_/pod/pod-hd/pod-hd500hd-desktophd-pro-v262-release-notes-r94 http://line6.com/support/page/kb/_/pod/pod-hd/video-tutorialpod-hd-series-flash-memory-upda-r209

Any amp/FX block that is included in a preset consumes DSP whether it is active or not. Its required DSP capacity is still reserved for it even when it is not active because it could be activated at any time. Assigning any block to a signal path is like reserving its seat in the DSP theatre. The patron may be in the washroom, or not even show up, but you can't sell the seat to anyone else in case they do show up / return. The space is reserved (and paid for in terms of DSP consumption). You want the seat back? Cancel the reservation (you have to delete the block - you can't just turn it off).