Community: Message List - Further M9 looper problems

Re: Further M9 looper problems

support@line6.com — Tue, 11 Sep 2012 16:41:36 GMT

So another year goes by with not even a note from Line 6 to say yes or no on a fix? It's a crying shame

Re: RE: Further M9 looper problems

support@line6.com — Tue, 11 Sep 2012 16:00:42 GMT

Maybe hopeless but has anything been done about this bug? Also does anyone know if it was in the original firmware? I would like to use my M9 with confidence again!

Re: Further M9 looper problems

support@line6.com — Wed, 02 May 2012 21:08:25 GMT

i also get this on my M9, it's almost a deal-breaker. please fix it soon!!

Re: Further M9 looper problems

support@line6.com — Fri, 30 Dec 2011 14:14:09 GMT

So, is this problem ever going to be addressed? Like mynameizbrian, I have pretty much stopped using the looper function now because of this.

Re: Further M9 looper problems

support@line6.com — Wed, 17 Aug 2011 17:57:22 GMT

I see this is marked as answered and while I understand the issue has been found, it hasn't been solved. I too am having this problem and I was playing out with the M9 pretty regularly and now it makes it useless to be able to do so, since I rely heavily on looping. Has there been any update as to a fix for this problem? I've been using the M9 since it released and made a lot of demonstration videos and talked the unit up a lot...and if this isn't a fixable issue that's going to be a big problem...

Re: RE: Further M9 looper problems

support@line6.com — Fri, 22 Oct 2010 22:11:28 GMT

Hugo,

Have a quick listen to the attached short wav file which demonstrates the nature of the problem well. I first recorded a silent loop, then pressed overdub to add a pure tone, then pressed reverse to produce the glitchy repeat. I did this first using very low pitched, then higher pitched sine waves. So, you first hear the original signal, then the glitchy OP from the looper. The first attached jpg file ('M9 Looper - Original and Glitched Waveforms') shows nice graphical waveforms of the original, then the glitched waveforms (low pitched only). This should help your engineers to work out what's going on.

But the crux of all this is that I have finally discovered how to reproduce the glitching with 100% repeatability. Begin recording a loop by pressing REC/OD, then end loop by pressing REC/OD again. Then press REV and add new material to the loop. IF THE TIME BETWEEN PRESSING REC/OD THE 2ND TIME AND PRESSING REV IS SHORTER THAN THE LENGTH OF THE LOOP, THEN THE ADDED MATERIAL WILL PRODUCE THE GLITCHING. If the time between pressing Rec/OD the 2nd time and pressing REV is longer than the loop length, the new material will be glitch-free. This is easy to understand if you look at the jpg - 'M9 Looper - How to produce glitching'

I hope this helps to solve the problem.

Regards,

Stephen

Re: RE: Further M9 looper problems

support@line6.com — Thu, 21 Oct 2010 16:53:48 GMT

Excellent, thanks Hugo. Hopefully this will be sorted out in a future firmware upgrade.

Stephen

RE: Further M9 looper problems

support@line6.com — Thu, 21 Oct 2010 16:00:51 GMT

Stephen,

With your description, I was able to reproduce the noise on the overdubs. Sounds like the overdubs are running through a ring modulator.

Thank you for the reproduction information. I will be logging this as a bug.

Regards,

Line6Hugo

Re: RE: Further M9 looper problems

support@line6.com — Thu, 21 Oct 2010 15:38:59 GMT

So, Line 6, any more ideas about this ? This distortion (check out the previously uploaded files) is now occurring just about everytime I use the looper. It seems to be associated with pressing the REV button while in Overdub mode. Do I have a faulty unit, or is it a s/w bug (? can be fixed in the next upgrade). Can you reproduce this fault?

Stephen

Re: RE: Further M9 looper problems

support@line6.com — Tue, 19 Oct 2010 16:51:17 GMT

Yes, I have tried using different cables, makes no difference.

I have already done a factory reset (as described on page 2-5 / 2-6 of the advanced user manual) and then reinstalled the latest firmware. This has not helped.

Stephen