pilottes

I wondered about the same thing when I read it. I would think if you can drive a speaker in 0.1W mode that would be to much for AUX. Can you drive a speaker with a line level signal. I would think not but I' m electrical engineer.. It sounds risky to me....

I must add that my quest was to find a cab setup that would sound as good as possible (for my set of ears) with a headphone set. I find it easier to dial in a good sound when I go through an actual guitar cab. I don't have an FRFR system yet but I'm looking at the EV ZLX12P...

Two months with the Helix now. I spent a lot of time on Redwirez IR some Ownhammer etc. I revisited the cabs last weekend with all the mics and mic positions. Wrote down all the ones that grab my attention and that sounded the way I like. When the dust settled I ended up with a dual cab with 4x12 1960 T75 160 Ribbon 1" High Cut 7.7 kHz and a 2x12 Silver Bell 67 Cond 1" High Cut 7.7 kHz. Whatever amp I use they all sound great now! (Obviously I don't look to recreate any specific vintage amp....)

Its a different DSP you cant move it on the Helix either. You have to copy nad paste.

This was my version of a 3 ch amps with an access to my JVM for solos. By default, the signal goes simply throught path 1A - Brit45 Clean Hitting a footswitch lablelled Tweed would switch Y split A to B and bring signal to tweed for more dirt For still more distortion for rock I have just beside a footswith rock. It disable the tweed and switch the »Y split A to B on Path 2 so you go throught only one amp. (The third amp 2204 is activated also but could have been on all the time since A/B is used to select it) To access the JVM for a lead sprint you would have to step on the previous two foorswitches to revert to clean before hitting the footswicth that would disable the clean amp and enable FX Loop. Three different amps, FX Loop, wah, chorus, tremolo, tube driver, comp, delays, EQs, -> DSP pretty much maxed out. All in all it would work but it gets confusing and we do need scenes! Secondly, in my opinion, I wanted to eliminate the latency by putting as much in a single patch but if you have to step twice on footswitches you create some other type of hesitation so in the end I'm not sure what is best.

I mentionned I would come back to you, Here is a preset that illustrate a couple of things This is set up to play Still got the blues. For the clean part, the clean amp (BritJ45) is used on Path 1A together with chorus between the send and return block. When hitting my JVM label footswitch. The amp block is disabled, the send and return block become active and the chorus becomes bypassed by the JVM preamp for the lead part. You could place a second chorus on path 2A with its own foorswitch ... so you always have a chorus available. Always multiple ways to a solution. This is by no means a textbook exampleof what should be done.

Done ! I ran into it last weekend when I was setting patches for a guitar using a stereo cable for mag and piezo. I had figured a way to make my life easier when I discovered the send was shorter on options than I thought

I can see you already thought about this! The PC Toggle would only make it possible to work as long as you have discipline. I mean you'd have to remember to turn off the footswicth before you selec another one. I admit after a few cold ones its receipe for ... adventure. I am not familiar with scenes in the M13 but as I collect from other comments it would greatly enhance versatility. At a minimum, if we could create something like a group say 3 footwitches for 3 amp channels with a mutualy exclusive behavior. Only the last one pressed it activated. That also could work.

OP! I was rereading your post but it does sound like you are using a variation on the 4CM. You use 2 cables to feed Path 1 to pre-amp. Then you extract post-preamp in Helix Path 2 and out to power amp. Here I'am not sure what you mean by send 1 & 2. You would be better off (in flexibility) to link Path 1 and 2 in a super serial connection and use an FX Loop block Send-Return. Just my 2 cents..

I don't think it would work the way you want. I followed the same path. I started by setting up different presets associated only one amp setting. One instant MIDI PC change command in command center. To eliminate the latency between preset change I thought I would put all in the same patch but hit a snag. If you associate a PC change message to a footswitch it will be sent when you press. In latch mode it will send the same message latched ou unlatched. To change channel you would have to press two consecutive footswitch everytime. Skip one and it will change to the other channel possibly but you will loose the routing scheme and get the signal lost in an unwanted path. Momentary does not help since it will not allow you modify the routing and/or the active FX Blocks. You need to vote :-) that is what you need. Ipromise. http://line6.ideasca...ds/810763-23508 I'll try to get a screen capture of what the routing I was refering to, but only this weekend. Good luck

I have used A/B switching to hide or unhide FX blocks. Together with block switching I was able to do neat routing. Now you got me curious with the MIDI switching how are you planning to do it within a single patch? I looked at the Blackstar Series One and it's behaving more or less like my JVM....

I am looking to something similar and I have something that could almost work but the MIDI limitation gets in the way. read my recent post here http://line6.com/support/topic/19974-midi-pc-toggle-for-all/ and follow the suggestion from D_I and vote on ideascale http://line6.ideascale.com/a/dtd/On-sending-MIDI-PC-commands/810763-23508 Thanks,

Yes! Yes! It's doable!

Really sorry if I was not clear. I agreed that MIDI PC contains only 1 parameter, the preset number. All the amps I refered to will react to a PC message by recalling the state of the amps as a PC change from 0 to 127. We can program an Helix footwitch to send a unique PC message and have say 3 footswitches for 3 different channels on the amp. The problem is that you really want these footswitches to work in latch mode. To be able to add EQ, REVERB, DELAY, whatever for the duration of the part you need to do. And you want to see the state of lit or unlit. Pressing again the footwitch to revert to the base state, say the clean channel of the amp, is not possible presently. To do this you need the ability to program a different PC message number when you press (lit) than when you press (unlit). What I call PC Toggle as a similar functionnality (but not identical) as what is already programmed in the Helix as CC Toggle. Working with momentary mode footwitches is a no go obviously since you loose the ability of adding needed FX blocks and have no visual status As I said, same idea and practically the same code to implement. Little effort and ideal payoff to control recent MIDI amps. Hope I explained it better this time. But I'm willing to do it again since this limitation as been nagging me since I bought the Helix.

Hum ?... that's my point why we need PC Toggle. JVM, H&K amps and others, only support PC messages.

I see. You want to control the Helix that way. You have the inverse dilema. Most of the MIDI amp I know support PC message only. So my Helix footswitch act as you described. Lit unlit tap tap its a big mess. I decided to use a single channel from my amp and does the other voicing within the Helix.

I know I've been through this path before but after two months with the Helix, I finally came up with a solution to the MIDI PC limits, thanks to a fellow member. An other purchase would be necessary. But I realise the CC Toggle functionnality is it. From a software development point of view, The code is already there. Cut and paste and change a few things to get PC Toggle. At nearly no expense we would get a mean of controlling any MIDI controllable Amps like JVM, H&K and more. Please ,please make it happen before I worn my pant at the knees. It would be much more elegant than convert CC# message to PC message via a 3rd party box. D_I? You alreadfy looked into this, I remember. What do you think?

Excellent! It might be exactly what is needed while waiting for L6 and a MIDI update. Thanks

That's interesting. It might answer the limitation in controling my JVM. Have you used it with the Helix? By reading the online info it needs to be powered by the Helix to work. The voltage on the power pin need 5V. In the list of device not able to power the Event Processor" I noticed , BOSS GT-10, Axe FX, ...

Now, you got me all curious again. I could not resist. So I did a few things. I could have done it differently but I learned something in the process. 1- I resetted the global settings with boot + footswitch 5+6 2- I export the full bundle under the 1.10 HELIX app 3- I imported the said bundle and can confirm the behavior is reproductible, many presets footswitche's states altered 4- Install HELIX app 1.11.1 5- Correct one patch so it reflects the state of effect blocs vs lit or unlit color ring 6- Re-exported as a bundle 7- Re-imported bundle to find the preset changed again. SO! I have to go through some 50 patches again for the hmmm... 4th time. I'll leave it be for a while.... darn

That's more or less what I thought. Since I've been working relentlessly on my patches as I learned to get out the most out of the device I don't really want to go back to my ste from a week ago. I'll sit tight and work on the Helix itself until the full release is out. I noticed this when I did all the touchup on the presets for the third time I realized it must be something related to the editor. I'm not going to investigate further at this point. And yest I did reset all when I flashed to 1.10.0. Thanks

I jumped on the bandwagon with the new Helix beta application and the 1.10 flash update. I'm still early in the process of improving a set of patches and I realized when I reordered them in the editor the status of some footwich changed from unlit to lit for no reason other than they have multiple assignement. Will my latest batch of presets load on the 1.06.5 flash with the old Helix app?

It's fairly easy to get going with the Helix. What's more difficult for me is figuring out some of the effect parameters. Makes me realize I am far from an effect guru and what is the best use of such and such effect ...

I agreed with OP at least on making the Helix more friendly and enhancing the way we can use it. I mean by that, updating quickly items which are issues in making the best out of editing the beast. More characters in labels. Fixing the dual cab reset thing, improving the MIDI programming. For me and the JVM it's not perfect but it could be if only. What I'm affraid is that the resources are going to be spent duplicating in an editor of what we already have in the Helix and we may have to wait longer to get improvements. I bought the Helix with 1.06.5. I found a bug with the MIDI and teh command center. I reported it. They thanked me and indicated that it had been reported. When I installed 1.10.0 it was corrected so they are doing something. Time will tell. Beside amps and effects, Helix is young and there is a few things that could definetly be improved quickly. Ideascale is a good plan but please lets fix the small things first and quickly.

May be its something related to what I found on Windows 7. If you go Control_Panel->Hardware_and_Sound->Manage audio devives On the plaback tab Right click item and make sure the Show Disabled Devices and Show Disconected Devices are checked. Once it is you'll see all the audio device and you will be able to change where you want to sound to go. Hope that works for you.