gordwait

Double aha! Scotterp's comment made me take another look. The "hidden" files that showed up on my SD card that I could see from the Mac command line are Mac OSX files, not M20D files. I looked up the directory names ".Spotlight-V100" and .Trashes and .fseventsd and found out that Mac OSX creates these on any new SD card plugged into the Mac. (to do with Mac OSX disk search and backup software) So the updated theory is that the M20D doesn't like these files.. Windows probably doesn't put the same sort of files on the SD card, so the M20D doesn't get bothered with these hidden folders.

Aha.. I used the mac command line to poke around the SD card and found a whole bunch of "hidden" files that the M20d put there. I completely erased every file and folder on the SD card and now the M20d likes it again. I recorded some stuff to play around and found: If I delete the recording folder on the sd card using the M20D my card behaves just fine. If I delete the recording it using the Mac, it messes up the card for the M20d. My guess is those files store the state it thinks the SD card is in, and when you delete a file using a PC or Mac then it no longer matches, and the M20D operating system gets messed up. Moral of the story, delete old recordings using the M20d or go in with some PC/MAC utility and wipe the card completely clean between recording sessions..

I too found that when I deleted folders on the SD card on my mac, that I can no longer use the card in the M20D. It spins on "initializing".. I'll try to erase the card in the m20d instead and see what happens. Note that same card is still fine when I put it back into the Mac.. Kind of buggy..

Sweet! I will try this out, thanks for the responses! (was this in the manual?) (answer, yes it is, just came across it looking at other features.. )

Is there a way to move around the controller strips at the bottom? My setup has things kind of scattered around, and I'd like to put things together. IE all the monitor icons beside each other. I did look around the manual but didn't see a way..

I have to agree with bassforlife2013. I design embedded hardware for a living. If the m20d were suffering from bad firmware updates, there would be complaints of dead and even possibly bricked m20d units on the forum here. There is an infinitesimal chance that a firmware loading issue would result in the same encoder shaft bug every time a firmware update went bad. There's also very little chance that there is no error checking of the firmware when loaded. The industry standard is to first check the new flash file is good, then load it into a clean erased flash location, then check that the new flash programming worked via checksum(s), then change the boot loader to aim at the new verified flash image. If at any point something goes wrong, it would just keep the previous flash version running, or in some cases, run a permanent "safe recovery image" that can be used to retry the programming of a new image. If the firmware doesn't load properly this almost always results in a complete failure to boot, not a tiny (but important) feature acting a little strange. Updating the m20d firmware is really no different than updating a PC motherboard flash rom update, or cellphone rom update etc. I too see the same bug by the way. Spin too fast and the volume can go backwards. This means some math errors at the shaft encoder logic. It probably means the m20d can't keep up with the volume knob messages quickly enough when the user spins it too quickly. I do notice the m20d gets laggy once in a while, then seems to get back to normal..

I too think that the SD card slot is too "flimsy", I could easily imagine it vibrating in and out of contact while recording. I'll be trying my first recording tonight. So far tests have shown it to be working, I get audio in the SD card files no problem..

Resolved my USB playback issue (and closed the ticket). Once I got it in my head to just use the same Laptop icon for either analog mini jack aux in, or USB stereo in, I was able to make it work. It would have been a bit more intuitive if the laptop icon changed to show a USB plug as opposed to a stereo analog input.. The bad news is yes, the USB record latency is huge (at least 1/4 second) making the m20d all but useless as a multitrack interface for a DAW like Logic etc. I'll have to keep my old presonus around instead of selling it off as I planned when buying the m20d.. Hopefully it's a driver thing, and not a hardware limitation.. The record levels thing is on purpose - to give live users lots of headroom, 0db on the M20d meters is -15.4 db "digital", whereas Logic uses 0db as "full scale digital" so the audio in looks to be at -15.4 db when set to zero on the M20d. I'm actually ok with this, I changed the Logic metering section to one that shows more detail for lower signal levels: Preferences->Display->Mixer->Level Meters set to "sectional dB linear". I also set Logic to 24 bit to match the M20d.

Try another card? If more than one known good card doesn't work, you may have a hardware problem with the m20d.. I've put a few different SD cards in, they all cause a little icon to appear on the stage..

I just started trying to connect the M20d to Apple Logic on my Macbook with the 1.2 drivers, etc, and found the levels sent to the DAW to be fairly low, but it sounds like it's on purpose. User ArneLine6 quoted this: "It is 24bit audio. The "0" on the M20d is at 0dBu which is an analog reference to encourage a good headroom and match any metering of analog gear that is connected. The full level before clipping is +15.4 dBu which is 0 dBFS, digital full scale. " And I found out via googling that Apple Logic treats 0db on the metering as 0 dbFS (db full scale) ie if you go above 0 on Logic, that's clipping digitally. In a nutshell, sending 0dBu from the M20d to Logic reads as -15.4db on Logic. After reading a bunch of other resources, I'm ok with it that way, it does leave lots of headroom, and I set Logic to 24 bit audio to keep some more bits around. Also, by experimentation, and by Line6 description I think yes, the USB audio out is post Trim, and pre fader, so if you trim your input very low, you will have a very low signal at your DAW.. Here's the thread: http://line6.com/support/topic/3026-trouble-with-streaming-audio-tofrom-usb-macbook-pro-since-v12-upgrade/ My issue is I can't play audio back from logic to the M20d via USB. I also see logic react to audio in from the M20d with a half second or so delay, so I too will have latency complaints if I ever get audio playback from USB working. I'm still happy with the M20d for live work, but I was planning on selling my old Presonus firewire26 setup and use the M20d as a replacement. I wanted to take that cash to help pay for a line6 floor monitor..

I signed up for Line 6's idea page: http://line6.ideascale.com/ and added this request to it. Sign up and vote!

My XLR inputs are used up, plus my acoustic pickup output is nice and strong, so I plug into input 13 with a 1/4 inch jack. I can get feedback on the acoustic, even though there is a pickup involved, and in fact that feedback kicked off feedback suppression in my vocal mic. I would love to enable FBS on the acoustic...

I've got the latest drivers installed, rebooted the Mac as required, and I used Mac preferences to set the audio for the laptop to the m20d choice. I can see audio coming in to the Mac, but when I play iTunes, nothing seems to come back out from the Mac to the m20d. I see in the FAQ it tells me I need to add a laptop icon to the stage, and then set levels, but I can't find one that accepts USB. I have used up the analog audio inputs, and when I try to drag the laptop icon to the stage it tells me "No jacks are available that can accommodate this icon." I need a laptop icon with a USB input, but the only one I find has a stereo jack picture attached. Also, when recording into Logic, I can see the audio in, but at a very low level. Stuck... Help.. OSX 10.8.5, Line6 m20d driver 1.23 m20d firmware 1.2

I haven't yet tried this (in fact we haven't bought the wireless gear yet) but the FAQ does list only a couple compatible USB wifi widgets: Q: Which USB WiFi products are compatible with the StageScape M20d? A: The EnGenius EUB-9801, Samsung WIS12ABGNX (WIS9ABGN and a WIS10ABGN are NOT compatible), and Linksys AE1000 (AE1200 and AE2500 will NOT work)are compatible with the StageScape M20D. However, they may be discontinued at this time. We recommend using an Apple Airport Express and use Apple's USB to Ethernet adapter (UPC: 885909439560). It is also possible to use the USB to Ethernet adapter and a DHCP enabled WiFi Ethernet router. I would assume once you have one that does work with it that you have to go into the wifi set up pages to get it to do anything. IE I doubt it will just autoconfigure when you plug in a working USB wifi adapter. Try yours again and check the wifi setup page to see if it's there? The m20d should act like a laptop connecting to an external wifi network, if I understand it correctly. IE you set up a hotspot and have both the m20d and an iPad connect to that hotspot..

Kind of a silly request I admit.. Both our drummer and keyboard guy sit while playing and singing, so none of the vocal icons is really quite right. Any thoughts to releasing an icon editing tool and let us load more from a USB stick or something? I could also put in my guitar amp instead of a line6 amp (sorry guys, I went to a Mesa Boogie Lonestar after a number of happy years with my Flextone II amp..) I do find the visual stage thing a bit odd, in that I "want" to make the stage picture look sort of right, but then the icons would be too close together for easy hunt and peck. (I'm using all but 1 input, and all 4 monitor outputs, could have used just one more monitor send too..) For example, on drums I have kick, snare, stereo overhead, drummer's monitor, drummer's vocal mike. I spread them out in a line across the back of the stage view so I can select them easier.. Looks funny, but easier to use..

I was going to say, sounds like a job for a scene change. I've never heard of a Y cable for a mic, I would assume the double loading of having one mic feed two inputs might cause some loss of quality.. especially if the input impedance is 600 ohms..