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

silverhead

Line 6 Expert
  • Posts

    12,450
  • Joined

  • Last visited

  • Days Won

    415

Everything posted by silverhead

  1. I have the Beyerdynamic 770 Pro and they work great with both Helix and HD500/Pro/Bean
  2. That seems like more work than just including the IR number in the IR file name. Is there some reason you don't want to do that? And what happens if you misplace the paper?
  3. I would create a split path and put the two IRs in parallel rather than series. To create the split select an FX block in path 1A and drag it downwards. The display will create/show path 1B. Drop the block there and then make it a 2nd IR block. Keep your amp in front of the split so that the amp signal will be routed to both IRs independently.
  4. That is the correct type of cable. If it doesn't connect properly to either your Helix or your JTV then the cable is likely faulty. I would return and replace it.
  5. If this happens again, an easy fix is to pull the knob off, place a little wad of crushed paper in the hollow of the knob, and push the knob back on. This raises the knob on the shaft so that the bottom of the knob no longer rubs against the body of the guitar.
  6. Yes. In fact Helix sounds better than 500X imo.
  7. Have you pushed down the Model select knob? That's what switches the sound from mag pickups to modeling.
  8. Your post has been viewed more than 70 times. It just has zero answers, which suggests none of the viewers so far know the answer to your question.
  9. There's no software involved in the OP's question, other than a standard web browser. He's having trouble simply downloading a tone file from the Customtone website. He's not talking about having/using the Helix editor. The editor only becomes relevant after he's successfully downloaded a Helix tone file - which is what he can't do at the moment.
  10. For example: - you have an IR named 'ThisIR' and you have imported it into the Helix IR bank in slot/location #17 (or whatever). - you have a preset that uses 'ThisIR', and by 'using' it we mean that your preset specifies that it will use the IR in slot/location #17. It happens to display the name of the IR but that's just for convenience. It will use whatever IR is in slot#17. - you also have a bunch of other IRs loaded and they too are used in a bunch of different presets. - a firmware update is released. As advised in the release notes, you back up (export) all your presets and your IRs before updating your firmware. If you look you will notice that the Export IR function saves the file name with no reference to its slot/location number. - you update the firmware, follow the release notes resetting the global parameters and restoring the factory presets. This deletes all your custom presets (User setlists) and all your IRs - you import your custom setlists. The presets are all as you saved them, but...... - they sound different. On investigation you find that, of course, your IRs are gone. Your preset says it is using the IR in slot/location #17, but of course that slot is <EMPTY> so it's using a null IR. - you realize that you have absolutely no idea which IR you had stored in slot #17. - you grab a bottle of scotch and settle in for several hours of reconstructive surgery on your helix IR imports, and you never are sure that you actually got it right.
  11. That's the most common use of the looper, I think. That way the looper records the processed signal so the playback always sounds like it did when you recorded the loop. However you can also put the looper at the beginning of the signal chain. This records the dry (unprocessed) signal. On playback the dry signal is fed into the beginning of the signal chain and is then processed by whatever preset is being used for the playback. This is very useful for tweaking your tones/presets. Record something, start the playback, put your guitar down, and use your hands to edit the tone while hearing the changes immediately as you make them.
  12. Yes. Go to the Sounds control panel item. In the Recording tab select the POd and make it the default device.
  13. One suggestion as you are renaming your IRs: include the Helix IR slot/location number as a prefix in the name. You will eventually discover that the Export IR function in Helix does not retain its slot/location number. This becomes a nuisance after updating your Helix with the next firmware update, resetting global parameters and restoring factory presets. Those actions delete all your IRs meaning you have to restore them to their original locations so that your custom presets will continue to work as designed. But simply saving them before the firmware update doesn't keep track of their locations. Hence the importance of you doing it yourself. I find including the location in the file name is a good method but feel free to devise your own method.
  14. There's no right or wrong. Do what sounds best to you.
  15. Does the FH1500 have global EQ? I didn't see it described in the manual.
  16. The Earvana handles bends as well as any other good nut in my experience. I think bending strings in general puts them out of tune regardless of the nut. The more and more often you bend, the more frequently you need to retune. I have not read anything about string height above/below nut level. That doesn't mean there's nothing written about it.
  17. I had a black Earvana nut installed on my JTV59 by a good guitar tech. Intonation accuracy up and down the neck is improved by the Earvana design. I also had him replace the jumbo frets with regulars. The jumbo frets themselves were the cause of some tuning issues due to my heavy handed and overall sloppy chording/playing.
  18. It's common to have to tweak your tones when changing listening environments, especially if the great tones you hear/designed were done using headphones, or using an amp as the speaker, or listening at low volume levels. Listening through a PA at gig volumes can sound dramatically different than listening at home under any of the above conditions. That's normal. First, for output to PA make sure the Firehawk Output Mode is set to Line and that your presets are using cab/mic selections. Don't use just the amp with no cab. After doing that if the PA system isn't able to compensate enough in its Channel EQ settings you will need to individually edit your tones in the Firehawk. It would be best to do this using the actual PA system you will be using at your gig.
  19. When your POD HD is connected to your computer it becomes your computer's soundcard. Your internal computer soundcard, and the computer's speaker connections are bypassed. You need to connect your speakers to the POD outputs to hear the sound. That's normal. Here's a preset designed to record a wet and dry track simultaneously. It was designed for the HD500; you can load it into HDPROX Edit if you change its file extension. You may also need to change the Inputs. http://line6.com/customtone/tone/217206/
  20. Not sure about FCPX nor Mac but on every Windows system I've used, every audio program that uses plug-ins identifies the location of the plug-in file directories/folders. There is likely some specification in FPCX that defines the directories in which it will find plug-ins. Edit this to remove the Line 6 directory/folder location.
  21. Thanks - now I understand. No further help I can offer though. You can't do that now and it is a reasonable Ideascale suggestion. I've been doing that manually when necessary. Takes a few seconds to copy/paste the amp+cab block for reference, replace the original with separate amp and cab blocks, replicate the settings in each new block from the reference block, and then delete the copied reference block. Btw.... You can audition different cabs in an amp+cab block. Just change the cab section.
  22. By 'cracking tones', do you mean really good sounding tones or do you mean that there's a nasty and undesirable sound like something cracking? (Blimey, the ocean between us sometimes makes terms confusing, eh?)
  23. The way to do both of those things is to use separate amp and cab blocks - not an amp+cab block. The design provides both options; use the amp+cab as a combined unit, or separate them. By choosing the former you are saying you don't want to separate them. If you do, choose the latter setup. A good analogy would be to consider a combo amp vs. an amp head and separate cab. You decide which setup you want to use/purchase. But having picked the combo amp you don't then try to disassemble the cab from the integrated preamp.
  24. Perhaps I misunderstand, but it seems to me that you can do exactly what you want now by using separate amp, cab, and IR blocks. Do not use the amp+cab block. Assign footswitches to turn these three blocks on/off in any combination you want. It only takes a few seconds to modify the factory preset in this way if you want. For instance, to quickly compare the stock cab to an IR, leave the amp block on. Assign the same footswitch to the stock cab block and the IR block. Save the preset with one of these blocks on and the other off. Then use the footswitch to instantly toggle between these two blocks to compare them. One thing's for sure - as soon as all the factory presets were modified in this way as a result of an Ideascale submission, you would immediately see a new Ideascale submission to combine the separate amp and cab blocks into an amp+cab block in order to save some DSP.
×
×
  • Create New...