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

silverhead

Line 6 Expert
  • Posts

    12,448
  • Joined

  • Last visited

  • Days Won

    415

Everything posted by silverhead

  1. If you’re lucky this is caused by a loose wiring connectors inside your POD HD500. The connectors are just plastic plugs on the ends of two wiring cables. They may simply have come loose. It can be fixed by opening up the device, locating the loose connection joint, and plug the connectors back together tightly. If you’re unlucky a chip of some sort has failed and a replacement will need to be purchased and installed at a Line 6 Service Centre.
  2. Yes, an HX Stomp is fine. Preset transfer is done using HX Edit, the HX editor/librarian program that runs on your computer while connected via usb to your HX device. You can import/export files to/from both HX Edit (and hence your HX device) and Helix Native to files on your computer. You can download the manuals for both HX Edit and Helix Native to investigate all this in advance if you wish.
  3. You would need to have one of the Line 6 Helix family hardware devices. There are several to choose from and all of them allow you to transfer presets between Helix Native and the Helix device. I use the workflow you describe all the time with my Helix Rack. I will often record both a dry and wet signal (using a Helix preset) simultaneously, import the preset from my Helix Rack into Helix Native via HX Edit, and then tweak (or completely replace) the preset in Helix Native as the project progresses. I rarely end up using the initial wet recording but there’s really no extra effort to record both wet and dry simultaneously so I tend to do it. When the project is finished I import the Helix Native preset back into the Helix Rack and am able to take the recording’s studio tone to the stage.
  4. I don't think there's been any change. As noted in the linked old post you can retain the Looper phrase when switching among presets as long as all presets involved contain the same type of Looper (1-switch/6-switch. mono/stereo, same path). Are you saying that's no longer true? If so I haven't noticed it.
  5. 1. Use Multi, which includes both Variax VDI and Guitar inputs. Variax by itself ignores the 1/4” Guitar input. 2. Correct. Helix does not object to the Multi setting if a Variax VDI connection is absent. It simply means that any VDI related settings in the preset (e.g. Variax Model) are ignored. The guitar connected to the 1/4” Guitar input will be fully processed as specified by the preset.
  6. Then why are you still using Windows? Helix Native and Cubase work on Mac OS too. And if you're also against Apple/Mac and want to work exclusively with Linux then you'll need to wait for the rest of the world to catch up to your clearly advanced status. Meantime, enjoy your marginal market share with correspondingly few meaningful apps.
  7. You're welcome. I hope you find it useful. Since you're coming from a POD HD500X with DT25 setup I presume you are familiar with 4CM? It's important that you use either a modeled Helix amp OR your DT25 amp's preamp section at any given time, not both simultaneously. If you're not familiar with 4CM please read the Helix manual's section about it and ask if you have further questions.
  8. No need to apologize. You don’t sound stupid by any stretch. And your instinct is right. Yes, you do need to configure things manually using presets. The POD HD500X and its editor were designed to use L6 Link to provide communications between the POD device and a DT amp. The editor provided a direct map/view of the DT amp controls to let the user configure the appropriate MIDI commands to send to the POD device without needing to know the MIDI command details. MIDI was being used; you just didn’t see it and didn’t need to know it. That is not the case with Helix devices. HX Edit does not provide this DT25 map/view, and does not use L6 Link. However, the Helix device and the HX Edit program do provide the Command Centre, which can easily be used to control the DT25 in the same way that the POD did. The only difference is that you need to know the specific MIDI commands to configure; it’s no longer hidden from you. And you need MIDI cables, not an L6 Link cable. You will need the DT MIDI Implementation Guide as well as the Helix device manual (see Support -> Manuals). Some time ago I wrote a little guide to help users like yourself (more specific my son-in-law!) control the DT amps using a Helix device. I’ve attached it here for your convenience. If you’re already familiar with using MIDI it won’t be too difficult to understand. If MIDI is new to you there will be a learning curve - but it’s a MIDI curve, not a Line 6 curve. Don’t hesitate to come back with questions. HX:DT - ReadMe.docx
  9. Wow. So much disinformation. Let’s look at the above …. - yes, if you prefer eye candy to sound quality a larger screen is nice - as has already been noted, the cloud has nothing to do with running out of memory on your presets - see Customtone for sharing presets - the new cabs in v3.5 are actually thousands of individual IRs wrapped up in a simple interface, greatly reducing any need to make/purchase and organize your own set of thousands of individual files. And they will likely keep coming in future updates. - if your Helix doesn’t connect to your PC there’s a solvable problem with your computer setup. Unsigned drivers are not the problem. If you do want to connect via USB without a rain dance, provide specific details of your problem, including your computer OS and all versions of Helix and driver software/firmware involved.
  10. I don’t see the specific terms that you are using ( OFF and PRESS ONLY ) in the manual. It says there are three settings: Touch, Press, and Both. You want Press. Note that Press does NOT mean ‘Press and Hold’.
  11. Can you describe exactly what you mean by ‘the way the POD HD500X did’? Midi? L6 Link? Voicings? Call up builtin amp models? Parameter changes? What exactly is it you want to do? Generally speaking you would want to use midi I think. Helix is not designed to communicate directly with the DT25 using L6 Link the way the HD500X is. Connect the Helix Midi Out to the DT25 Midi In, use the Helix Command Centre, and consult the DT25 Midi Implementation Guide for details.
  12. In the Input block of a preset you can select Variax or Variax Mags (along with the usual Guitar, Mic, Multi...). Selecting Variax accesses the Variax models (piezos), Variax Mags accesses the magnetic pickups.
  13. What are ‘them’? Lots of dedicated looper pedals do this, and yes, you can buy them new. The Helix looper does not do this. The DL4 MkII does using an optional micro SD card.
  14. Look for a menu item called Preferences or something similar. In most DAWs it is under the File or Edit top level menus.
  15. Craig might or might not be under any NDA with anyone but I never heard him deny that he wouldn’t not use no FX from any non-Helix device unless nothing was missing in Helix that he couldn’t find a way to avoid using elsewhere. ;-) Pretty sure Craig could agree with that.
  16. Check Global Settings -> MIDI/Tempo. There's a parameter MIDI PC Rx. Does this fix things for you?
  17. Have you opened a support ticket? Perhaps they can help you out.
  18. Hopefully Helix Native will, in a future update, incorporate this in the backup. It exists in HX Edit. The Helix backup file puts the numeric prefixes to the names in the IR portion of the backup. It’s transparent when you use the Restore feature, but when you use the Extract Files From Backup feature for the IR files it creates a folder of all the IR files and you can see that the filenames include the prefix.
  19. Please describe what exactly you want to do with Midi and Helix Native. Just PC messages for HN preset loading? Or more ambitious things? If it’s just PC messages for preset loading you don’t need anything in terms of HN preset construction. You just need to configure Cubase to recognize Helix Native as a midi ‘device’ and then configure your Airstep midi controller (I presume that’s what it is?) to send the correct PC command to Helix Native when desired (see HN manual for PC details). Assign the command to whatever Airstep trigger/controller you want. If you want to be more ambitious search for a thread I started a few weeks ago for details about automated midi control using Helix Native.
  20. I don’t have a Pod Go Wireless but I see from the manual that you can select either the Guitar or the Wireless input (or both) for any given preset. The manual says this: POD Go Wireless users can choose Guitar for some presets and Wireless for others, effectively turning the Input block into an input switcher. That suggests you may not be able choose this switching on a Snapshot basis but it’s worth experimenting. In one snapshot set the Input block to Guitar and in another set it to Wireless. If the Input selection behaves like any other block parameter you should be able to do this. Again, I’m not sure and can’t test it but I don’t see any reason that it would not work this way(except that if it did the manual would likely say so).
  21. silverhead

    PodGo Wireless

    Earlier I suggested you buy the non-wireless version. Now that you are concerned about an impedance issue also I suggest you avoid both versions of the POD Go. You seem to have set yourself up for a good case of buyer’s remorse. Buy a product that doesn’t have negative online reports.
  22. Just a guess, but…. When you update, are you logged in to an Administrator account on your desktop and a regular user account on your laptop?
  23. silverhead

    PodGo Wireless

    If the online reports you are referring to are the ones here in this forum, remember that this is a support forum. Users report their problems here. You won’t find the (many more) satisfied users who are not experiencing problems here.
  24. Therein lies the rub. A multi-client ASIO driver is an oxymoron. By definition the ASIO protocol requires that the same audio device be used as both the input and output device. For the same reason that you say ‘Not Asio4all’ you should also say ‘Not a multi-client ASIO driver’. Because if it’s multi-client it’s not ASIO. Or perhaps I misunderstand what you mean by multi-client in this context? I use my Helix Rack and the Line 6 ASIO driver almost daily, with multiple sound applications and plenty of plugins including multiple instances of Helix Native. No performance issues. How much RAM in your computer?
×
×
  • Create New...