Community: Message List

USTREAM Mobile In Broadcast

support@line6.com — Sun, 20 Nov 2011 08:52:23 GMT

Hi,

Could the Mobile In stream please be added to the archived list of recent videos? I was only able to catch the 2nd half, and it was mostly talking, so I'm hoping to hear a bit more of how it sounds.

Thanks!

Re: RE: Basic questions not answered in FAQ

support@line6.com — Sun, 20 Nov 2011 08:48:57 GMT

Line6Hugo wrote:

2) It is currently compatible with iPhone 4, iPad, and iPad2. It is not officially supported to work with the iPhone 4s at this time. And the older iPhones (3GS, etc.) are not capable of using the device.

Has any in house testing been done with the 4S? Will 4S owners have to wait for a newer version of the Mobile In hardware, or is this just a matter of jumping through some hoops for Apple hardware certification and/or a software update?

Thanks!

Re: TCDDK on 64-bit OS?

support@line6.com — Sun, 02 Oct 2011 19:03:30 GMT

I've been using a virtual XP image myself, and find it works rather well for development. However, flashing the MCU fails horribly from an image. After trying to flash the MCU from an image, the MCU was essentially a brick until I was able to find a physical XP machine to re-flash the MCU from.

It would be nice if a Line 6 dev could at least just try compiling against Windows 7 (32 and 64 bit) and see what happens. For whatever reason, the installer bypasses normal Windows compatibility APIs and probably just has some precompiler flags or such with a hard coded list of allowed operating systems. It should only take a few minutes to recompile and another few minutes to test it on Windows 7.

How about it Line 6? Could you please at least try to recompile the installer for us? It'd be a huge help to those of us without physical XP boxes, which are becoming more and more rare.

Re: new ToneCore Developers Kit pedal not working

support@line6.com — Sun, 02 Oct 2011 18:52:20 GMT

When you hold down the pedal and the LED blinks on and off, what color is the LED? I wonder if you've managed to get your module stuck in MCU Bootloader mode? When you are pressing the pedal down and manage to connect with USB, does a window pop up? Does the title say "Download DSP code", or does it say "Freescale JM16 Bootloader"? If you've managed to get it stuck in MCU bootloader mode, you may be able to just flash a new MCU and be running again.

Re: Brand new devkit - knob failure?

support@line6.com — Thu, 01 Sep 2011 21:28:50 GMT

dhodgson wrote:

Well,

My ToneCore devkit just came in - actually, it's my second because the first one Line6 sent was DOA. The second one works, but before writing a single line of code I can't help but notice that three of the knobs in the TCDDK_GUI.exe application don't update correctly. When turning knobs on the ToneDock module, three of its rotary knobs (and all switches) update smoothly in the GUI when turning them, but two don't turn at all (they seem to vibrate slightly as if from some kind of trimpot noise) and one of the three knobs rotates fine but also makes two others rotate in sympathy along with it!

This is where I have to wonder - did I just get another bad pedal from Line 6, or might this be something that could be solved my reflashing the MCU?

-djh

I can't recall anything like that, although that's based on a rather small sample size of one ToneCore dock and two modules. The knobs don't have a perfectly smooth sweep, but they've always worked well for me. If you mess up your code badly enough to freeze or such, you can cause the whole thing to become unresponsive, but even then, they're either all working or all not working.

If you have access to a regular ToneCore pedal (such as Verbzilla, Echo Park, etc), you might try one of those commercial modules in your dock, to narrow down whether the problem is in the dock or the module. You might also try the other case of the dev module in a regular dock. Also, have you tried just twiddling the knobs while hooked up to an amp, to eliminate the possibility that the knobs do in fact work, but perhaps the USB communication with the TCDDK GUI is failing somehow?

I doubt reflashing the module will help, but it can't hurt, and might give you more information. Sorry I can't be of more help, but your issue is definitely not normal - you might want to get in touch with Line 6 support directly by phone.

Good luck!

Re: New Line 6 Sound Demos

support@line6.com — Tue, 07 Jun 2011 02:52:37 GMT

The sound demos all work now - thanks for fixing that. Any comment on the rest of my question, regarding what was used for recording the other demos? On that topic, any other info about what was used in the recordings - guitars used, presets that could be shared, etc would be great too.

Thanks!

New Line 6 Sound Demos

support@line6.com — Fri, 03 Jun 2011 22:37:49 GMT

The HD series sound demo page has 4 new demos I don't recall seeing before:

http://bx.line6.com/podhd/multi-effects/sounds.html

The new ones are "Blues Traders", "Doves in Toto", "Synths and Sustainers", and "Ethereal Shredding". "Blues Traders" sounds quite good, but the other 3 don't work. Could someone from Line 6 look into fixing this? Also, there is a note at the bottom of the page:

*In the sound samples noted with an asterisk, every sound excluding drums was created with a guitar and POD HD500. All these tones can be downloaded from CustomTone

I've found all the presets and will be trying them soon, but the first comment has me curious - what was used on the other demos?

Incidentally, from what I've heard on "Blues Traders", I think this is a much better way of doing demos. Hearing the guitar parts more within the context of a song, along with providing us the presets to try out ourselves, seems incredibly useful to me.

Thanks!

Re: Developers kit in the U.K.

support@line6.com — Wed, 25 May 2011 00:24:36 GMT

It's still available for sale in the Line 6 Online Store:

https://www.globalfulfillment.net/gfsnet/line6/10Expand.aspx?ProductCode=99-043-0001

Unfortunately they only ship to the USA. When I was trying to get one a few months ago, I called up Line 6 to ask about this, and the support staff suggested looking to eBay, getting an American friend to buy one on my behalf, etc. I eventually found a used one from this forum, so you might try that as well.

Re: 2-Band Stereo EQ not switching on when pedal is depressed

support@line6.com — Tue, 24 May 2011 23:54:48 GMT

This trips up a lot of people at first. The foot switch has two "modes" - it can work for tap tempo with a gentle press, or it can control effect on/off with a more forceful stomp. (Of course you can program it to behave differently on these events) You have most likely been pressing gently and activating the tap tempo event. Try being a bit more firm, and it may help to put the pedal on the floor and use your foot. Once you get the hang of it, it's not a big deal.

Hope that helps!

Re: HD500 DSP overload with CustomTone patches and others

support@line6.com — Tue, 24 May 2011 16:47:16 GMT

zbcs wrote:

I get the DSP overload and cant load certain patches from the Pod HD500 CustomTone section - "Rush", "Rush of Floyd", "Harcore Bomb" and others:
"Steve Vai - The Animal" patch from http://www.benvesco.com/blogfiles/tones/hd500/vai-animal.zip.
"Glenn_DeLaune_Clean_Delay2" from http://www.glenndelaune.com/Glenn_DeLaune_HD500_Patches_11-2-10.zip.

I've encountered the DSP error in all of the flash and driver updates, even todays.
I've loaded a bundle of "Empty Tones" into the unit and still am only able to load patches into the "POD HD500 Edit" program.
I have to reduce the amps or FXs to load to the unit.

Is my unit defective ?
Any ideas?

Thnx !
-amazing product !

I've also tried the patches from Glenn, and the Glenn_DeLaune_Clean_Delay2 didn't work as-is for me either. With firmware version 1.0 and 1.1, I was able to get it working with the cab disabling trick, but Line 6 has since plugged that loophole. At some point I was wondering if I was doing something wrong, but Glenn had a post explaining that the cab disabling trick was necessary to get it working. I doubt there is anything wrong with your unit, as Nick explained, most of those patches were probably created for previous firmware revisions and may have been abusing the cab disabling loophole too.