Search the Community

Hi, I am with a company designing a custom midi controller that we wanted to have work with the M9. We are using Arduino to implement the controller. I have the looper doing play/stop and record via midi, all of which work great. When I tried to implement overdubbing, the M9 does not respond. I am sending a midi control change message with controller number 50 and a value of 0 on channel 1. I have tested this by sending the midi message to Abelton, which recieves it correctly and verifies this is what is being sent. I have also tried implementing it via Arduino's midi library and via their serial.write sending the message manually. I checked the midi input in setup as well, and have tried it both as channel 1 and omni. Another weird thing is that when the M9 is in record mode and receives this message it goes into playing while overdubbing, but once the M9 is playing the message does nothing. Really unsure what is wrong here unless our M9 is just defective, I have exhausted every other factor of error I can think of. I am going off the midi controls listed in the manual here: http://line6.com/data/6/0a060b316ac34f0593fca717b/application/pdf/M9%20Advanced%20Guide%20-%20English%20(%20Rev%20A%20).pdf We are on a deadline to have this working so any help is very much appreciated. Thanks!

Hi everyone.. I had a Line 6 Spider Valve 212, and when i plug in FBV2 footswitch its delay when i want to switch betwen chanels, and after that it changes randomly... I tried FBV2 on other Line 6 amp and it worked correct... Please help if you now something becouse i have some gig for about 10 days so i realy need help... Thanks...

Hello. I am sure I have read about some real bugs of HD Edit in the past, so we should take the time and ask Line6 to fix them. This thread should be used as a collection to provide all needed changes in one list. So, at the end we should have a list of errors to be fixt and (additional) also some realistic (!) wishes (probably never will be fulfilled). First error I remember was something with mixer volume, which would not be saved in some instances (maybe only if the POD is connected via USB?). Maybe someone can specify this error more detailed? My personal biggest (realistic) wish for an update of HD Edit would be a tab-functionality to jump to the next knob or parameter and a much more straight visualisation of the chosen (or mouse-over) effect. So here is the list (I would like to keep updated) Bugs take a look at the system defaults and set them to the most common and flawless values. get rid of "(Code 8000000a) Operation timed out". add the software-ability to fix the hardware knobs, as those seem to move by themself through vibrations. expression-pedal related multi-platform bug crashes Edit, if you extensively use wah for more than a couple of minutes (Details 1, 2, 3). DEP lack of displayed knob-values (missing value-display is a known bug. Feature introduced with Ver. 2.25). Error when saving mixer volume (only HD is connected via USB) >>> ideascale I can recall encountering a bug where one side of the mixer, the right channel, occasionally went silent for some reason, and the solution was to just move the volume slider, if using HD Edit. strange general behaviors when HD is connected via USB (should be explainded more detailed). f.e. changes in FX and Amps that are performed over footswitch or expression pedal are not instantly updated/visible (some times not at all) on the edit software. There is no way to know if changes (for example, volume) are actually taking place. Communication between the software and the unit must be improved. I found after editing multiple patches and then quitting the POD HD 500 EDIT you have to restart your pedal to reread the newly edited/loaded patches or they won't play right. the delay settings are not properly transferred from the editor to the device afaik there might be some unfixed issues with some amps in the model packs. Wishes tab-functionality to jump to the next knob or parameter add an overload Indicator in the HD500 signal chain add a vertical scrollbar to allow native resolution of netbooks much more straight visualisation of the chosen (or mouse-over) effect I want to be able to see value of knobs before turning any. Its hard to tell EXACTLY what % your knob is on. The dot that represents true button placement does not get you close enough. I want to edit by the numbers not a grainy LCD screen. Often I need to edit just a couple numbers. add some more mic angles for the SM57 and some valuable mics add some kind of Global EQ patch-wise as an effect-block or DEP Dual Output Modes add API-functions or let the HD Edit go Open Source

Trying to rename a preset that's called "New Preset". In the save menu I rename it "Hendrix" and clear out any remaining unused letters, in this case there is an "et" at the end that gets deleted. I then save the preset, and it saves and displays it correctly. However, if you try to re-save the preset what I see is "Hendrix et". This is repeatable, no matter how many times I update the name this keeps showing up.

I have a strange problem. I made a preset as seen on the picture: The signal paths are as follows: Path 1A is a seperate path to be usaed for a microphone so I can put some effects on my voice. Path 1B is for guitar and continues to path 2A. Pathe 2A splits after the amp to path 2B with a Y-split. Path 2B Contains some post amp effects. I do this to have a signal without the delays going to the output as wel as a singnal with delays. This makes my guitar playing more articulate, not completely being delayed. Both 2A and 2B ar set to Digital output because I send to my DT25 through Line6 Link. The problem (bug?): If I change the output to something else I can't return to Digital. Somehow the digital output is not available, eventhough it's selected allready. Why is this? Am I doing something wrong? Is it a bug?

I'm using the Teemah model to drive a clean amp model and I can hear the dry signal along with the distorted one. Has anyone noticed this or am I hearing something that's not there? BTW, before anybody asks: It's a very basic patch, just an amp+cab block and the drive Other than this..."issue"? I'm enjoying my new Helix :) (I got it three weeks ago)

Hey guys! I think I found a bug in the Line6 Pod HD500X Edit software. Version number is "2.26.0". The bug can be reproduced pretty easily. Start the software with the HD500X disconnected. (I don't know, if it happens when the patches are synced to the device.) Choose an empty patch and create a dual-amp setup. The exact amp models do not matter, but it should be full amps, not preamps, as only the former have an "amp parameters" section. Move all the knobs in the "amp parameters" section off their zero ("all-the-way-to-the-left") position. Store the preset to a ".5xe" file via "File" --> "Save As ...". (You can also save to a ".5xs" setlist or even an entire ".5xb" bundle. It doesn't matter. The bug is always triggered.) Open the ".5xe" (or ".5xs" or ".5xb") file again via "File" --> "Open ...". (You can also close the application and open it again and then open the file, or even open the file via a double click from Windows Explorer. It doesn't matter. The bug is always triggered.) Note that all the knobs in the "amp parameters" section of "Amp B" returned to their zero ("all-the-way-to-the-left") positions. I hope that this "somehow" gets to the software developers at Line6 and gets fixed. Like I said, I don't know if it also happens when syncing patches from/to the device or if it's an issue with the file storage only. But of course it's pretty severe, as it basically means that at least any dual-amp patch that is shared online or used as a backup is "broken" (or incomplete to say at least). If these values get "lost" while syncing to the device as well, it basically means that any dual-amp setup created with the Edit software is broken, as the "amp parameters" of "Amp B" never arrive at the device. Thanks!

Hello. I own a Pocket POD with firmware version 1.01. I've been playing with puredata sending MIDI messages to the POD controlling things like volume and wah position. I'm facing something I believe to be a bug on the firmware. Upon receiving lots of MIDI messages (~9/sec), the POD reboots itself both on batteries and power supply. It shouldn't be a fault with my computer (I'm running everything on Linux Mint 17.2 with no additional drivers) since it works at smaller speeds. I tried resflashing the latest firmware 'just in case' today. Around 2 years ago I managed to burn an internal capacitor on it's power stage by misconnecting the power supply. Even tough Line6Hugo said "The Pocket POD is not repairable", I managed to replace the burnt component (which Line6 wouldn't tell me the value of). Everything works fine by now, except that my Pocket POD turns on even with no guitar plugged in, which for me is not a big deal. I just want to know if this is a firmware bug or hardware related. I'm willing to cooperate as much as possible, since MIDI is a supported feature and should be working. Thank you in advance. PS.: pic related. My pocket POD and a second capacitor I bought just in case I blow it again.

Please put any software/firmware/hardware bugs you discover in the Helix here. Hopefully they will be addressed in future updates. If the issue turns out to be user error instead of a bug perhaps someone can offer up the correct procedure. Please include your firmware version when you post your bug. Thanks! This topic is not intended for bad-mouthing the Helix but for providing Line6 with maximum feedback to assist them in fixing issues as early as possible. Please provide as much info as you can on your use case so they can recreate the problem in their "lab". Important: Please submit a support ticket once you establish you have indeed discovered a bug. Line6 has a process in place for bugs and you have a much better chance of them seeing and responding to your issue here: http://line6.com/support/tickets/ Please come back in to this topic and comment that your bug has been fixed once and if Line6 addresses it. Thanks! Submit your bug in whatever manner communicates the issue best but here is a suggested format. Hardware: Helix (e.g. Helix, LT, HX Stomp, Pod Go, etc.) Firmware/Editor: Firmware 2.82; HX Edit 2.82 (Make sure to include your firmware and editor version, hopefully the latest, don't want to waste Line6's time with bugs that have already been fixed) OS: Windows 10 (Include your OS if relevant to issue, computer hardware/manufacturer also if pertinent) Global Settings: Bottom row presets, top row pedals [assigns] (Include any global settings you think could pertain to your bug) Attach Preset: Attach your preset if you think it will help troubleshoot the issue! Bug: When saving preset to another list, pedalboard reverts to Factory 1 list song 1 ("WhoWatt 100") after save. (Short description of bug) (Step by step description of how to reproduce bug) Use Preset knob to select preset from Factory 1 list (I selected 21C "Almost Not Fair") Save "Almost Not Fair" to User 5 list in the first position, 1A. After Save Helix home screen reverts back to the first song in Factory List 1 ("WhoWatt 100").

Mine arrived with a bad scribble strip (see pic). All the money I paid for priority shipping is wasted as customer support says the cannot pre-ship the replacement unit. This is very disappointing. Any other defects out there?

I have seen others on the forum with the same problem, with no solution, so bare with me or point me to the solution. When making edits and creations in the PC editor the "send" button does not send the data to the pod entirely. Double-clicking the preset (in editor) loads the sounds and visual representations as expected on pod and PC However, attempting to save a preset from editor to pod by pressing the send button only sends half the info- Visually the amp and effects appear to be stored on the pod but the sounds are from whatever was saved in that patch previously and have no reflection on the sound. The only way to get the "new" preset is to power the pod on then off and then the preset appears AND sounds as expected/saved. using pod HD500x with the designated editor

Hello folks, another disconcerting tale to tell I'm afraid. It has happened to me before on various occasions, but this time (last weekend) was the first time the M20d screen froze solid on me without any external doodads attached. No SD card inserted (for recording or playback), no WiFi dongle, no nothing. Just a single microphone and a stereo line in. As usual, when you operate the M20 so that people can see it, a tech aficionado stepped up to have a closer look at it, and wanted to know if this could be operated like a standard mixer. Sure, I said, look right here, "Show faders", show the faders it did, the encoders worked just fine, but as soon as I went on to demonstrate sliding a fader up and down - kaboom, frozen. None of the encoders worked. The only thing that would still react was the main volume knob. I had to reboot the unit to regain control. Now I'm sure someone is going to come up to explain that it's usually the cables ;) or that I need to update my firmware. Well, it's on 1.2 like probably everybody else's. Also, I don't think it's a hardware issue with the touchscreen (if so, then why did the encoders quit working, too?). I maintain that the firmware is still bug-ridden and that it's HIGH TIME somebody got their act together and fixed it. Before the freeze the guy had asked me how much the unit cost, and where to buy it. He was really eager to get one. After the freeze, not so much. In other words, he was horrified. I told him to give the Behringer X32 a closer look.

Ok, I hope this is just a tiny bug and not symptomatic of something a little bigger. I have noticed that when I adjust an amp's volume via the HD edit software (say loweing an AC-30 from 75% to 40%), it is reflected immediately in the unit (over all volume is lower). I then send the selected patch to the pod to save it. If I go to another patch and then back to the original - the pod has lost the new amp volume. HD edit says the level is the same as what was saved (40%), but it is much louder (sounds like 75%). If I adjust the volume on the pod and save it on the pod - all is good. I suspect there is nothing to do but hope it gets ironed out in the next update (which might be when??) Thanks -Paul

Has anyone else noticed that when editing patches in the HD500X Edit software (and probably the HD500 Edit) and trying to set the BPM value, it doesn't "stick"? For example, let's say I have a patch for a particular song and want to set the BPM to 75. I select the BPM field, type in 75 and and then save that selected preset. Then, I double click some other preset to change to that one and then double click back on the preset I set to 75. I look at the BPM value and it's not 75. It goes back to whatever it was previous to setting it, say the default of 120. The workaround I have is to just hold the view button on the unit and go down to the 6th menu screen and manually set the BPM there for the patch, but that seems kind of dumb that I need to do that. What's the point of an editable BPM field in the software if it doesn't really work? Maybe I'm doing something wrong in terms of how to get it to apply? Not sure. Any thoughts on this?

For years, people (including myself) have been complaining about how Podfarm reverts back to 16 Bit / 44.1 Hz even when the default in Windows control Panel on the playback tab for the respective device is actually set to 24 Bit /48 Hz (just do a Google search and you will find user inquiries to Line 6 for this subject dating back to 2010). This is especially a problem when using the SPDIF Connection as it defaults to 24 Bit, meaning your cound crackles when Podfarm is operating at 16 Bit. Every time you load a new patch, it resets to 16 Bit. The way Line 6 has handled that (including in support tickets) was not overly impressive IMHO and seemingly geared at confusing people so they would give up and let it rest. Here is how one can easily see the problem when using SPDIF out (the AISO Settings have nothing to do with this): 1) Open Start / Programs / Line 6 / Tools / Line 6 Audio-Midi Devices 2) If not already set as a default on your system, click "Sound Control Panel" and on the playback tab for the UX-2, select 24 Bit 48 Hz. Click ok. 3) Leave the Line 6 Audio-Midi Devices window open, observe the value in the "Driver Format" box and start Podfarm 4) Typically already with the start of Podfarm, the Driver Format resets to 16 Bit but maybe you are lucky and it does not. Your luck will run out if you load another patch (file /load) into Podfarm - latest by now, your Driver Format is reset to 16 Bit and your Sound crackles, if you use the SPDIF Connection 5) In order to reset it to 24 bit, go back to the Line 6 Audio-Midi Devices window, click Sound Control Panel, click on the playback tab of your UX-2 (you will be suprised to see it still at 24 Bit even though it says 16 Bit in the Driver Format box one page before, so you have to select any other value, press apply and then change back to 24 Bit and press apply again in order for the correct 24 Bit value to show and Register for the UX-2 - now you can play in 24 Bit until your next pacth change. 6) Interestingly enough, instead of selecting and applying twice as laid out under 5) you can also just press the "test" button on the playback tab and the UX-2 will reset to 24 Bit (attention: depending on your listening volume that nasty Windows chime sound can be damn loud). A lot of text above I know but I do not want to get "brushed off" again by Line 6 with a smoke granate. Here is in fact what I want from Line 6: (1) Test it - follow the steps above and tell me if you can reproduce the same problem! (maybe others can try it too so we have a honest and representative result) (2) Admit that it is a bug in Podfarm and tell us when it will be fixed FINALLY! I do not want to rant and I do not want to be impolite but seriously, this has bugged me for years and the fact that Line 6 has denied it p... me off. Line 6 - please advise!