scotterp

I have since moved on to another product and no longer use the M20D. I have gone through 4 of them with only one of them still working 100%, but just could no longer take the chance of it eventually breaking down. If I were proficient at soldering, I'd tinker and try to get them back up to speed, but I'm not. So... I have a couple "for parts" M20D's if anyone is interested. :)

I am curious to know if there is a way to reset the pin as well. I have a similar situation, but had a second mixer as a backup. Just haven't gotten back to fixing this one yet. If there is a way to reset, that would be great. Don't feel like trying 9999 possible pins before I hit the right one. On my second mixer, I wrote the PIN on the mixer itself to avoid this in the future! :)

Must be a 30 day limit or something - although not mentioned in that email. My original procrastination on buying the book in the first place actually paid off in this situation.

That's exactly how I feel. I don't know how to identify what the sound is. For a few years now, I have used external synths live and the reaction from people is always that they are impressed that I can do it, and that we don't use tracks to do it. I have used the EXH S9, Boss SY-300, and now a SY-200, and even Midi Guitar 2. Mostly because the built in synth is monophonic and I didn't want to take the time to create sounds from scratch. All of these have their own pros and cons. Being able to do it all within the Helix would be preferred for sure. The video above is going to get me to spend a bit more time to perhaps use some internal synths for the parts that monophonic is fine.

Looks like they fixed it. I went to my original email (dated Jan 23rd) and clicked the link. Took me to Sweetwater where I could click the Download and it downloaded Version 1.1. Thank you @craiganderton!

I have done the dual path as well and toggling output volumes for different snapshots. I have a gig this Friday and don't want to mess around too much until that is done with. Then I will reinstall 3.11 and see exactly what it did before. I know that it is working differently now than it did before. I just want to prove that I'm not going crazy and misremembering something. :) Thanks guys!

I think I will need to go back to 3.11 and capture exactly how it worked there, then come back to 3.15 and compare. Just to make sure I have my head straight. IIRC (and I'm not sure I do 100%) I could save a snapshot with the Variax enabled with a specific Variax setting. I could then change to another snapshot, disengage the Variax, save the preset and the disengagement of the Variax was saved for that snapshot only. Toggling between the two snapshots would engage/disengage the Variax. Now, if I save the preset with the Variax engaged, it saves that state for all of the snapshots. Same if I disengage it. It no longer saves the state of the Variax per snapshot. I hope this explains it? It's been a while since I set these up and it just seemed to work that way.

Variax settings is per preset. Factory reset was done (twice to be sure) and reset from backup each time. This seems to work fine for the initial snapshot when coming into a preset. But if there is a " secondary" snapshot where the Variax should be "turned off" and let the mags take over, this is where I'm having an issue. The Variax is not turned off. I can always change the snapshots to use another Variax setting, not a big deal, but the behavior does seem to be different than previous releases. This is the only issue I have found.

Good point. I did check. I'm thinking the one that would affect this is the Recall snapshot edits vs Discard Snaphot edits. It is set to Recall. I can't think of another that might affect this behavior.

OK - So I have gone through the update process a couple of times and have reset things from my backup and I'm having one issue in particular. I only have 2 presets where, within snapshots, some snapshots are using Variax settings, and others are using the built in pickups. For instance: Snapshot 1 uses the spank setting #2, where snapshot #3 uses Variax mags, wherever the switch may be positioned. What I'm finding is that when I switch to snapshot #3 now, it maintains the spank setting. It used to turn off the Variax and just go to whatever the mags were currently positioned to. The Variax no longer turns off when I switch to a snapshot where it used to do that. Anyone else seeing this?

I have used various cables from BTPA including this one. A little pricey and takes time to arrive but VERY GOOD cables. Never had an issue with them.

This is kind of what I have done myself. It would just be nice to be able to do it all within the Helix. :) If the synth is AUV3 compatible, you don't even have to use AUM to make it work.

^^^^^^ Me too... :(

Looks like this happened to me last night at a gig. It happened during soundcheck and I bring a backup M20d with me just in case as these units are getting older. Saved the gig totally. @treewiz, did you ever get this solved?

Yup... always has been. Elaborating even more on this... Depending on the laws of each city, local Pawn shops "may" be required to submit ALL pawn tickets to the local PD. At a couple of our customer sites, this was an electronic file where we would upload all of the data from the pawn shops into the PD's property database, and if any serialized items were found, we would spawn the automatic NCIC check to verify if the item was reported as stolen. If so, we would email the pawn detective of the hit to confirm if it was a matching item. There are some larger agencies that have a detective dedicated to monitoring the pawn shops because they are the most common place for thieves to sell their stolen items. There are some Pawn shop software companies that may be handling this themselves these days though as I haven't seen this requirement at our newer customers. It then comes down to whether the pawn shop owners themselves are recording all of their purchases and who they are buying from. :)