The_Elf
-
Posts
55 -
Joined
-
Last visited
Everything posted by The_Elf
-
I'm also seeing the built-in pedal setting itself to EXP2, despite the preset having it set to EXP1, on power-up after installing 2.8. (Why anyone thought that the built-in pedal should default to EXP2, rather than EXP1, in the first place beggars belief...)
-
I'm sure someone will have already reported this, but... All of my old patches are set such that the built-in pedal is EXP1 (why Line 6 decided the built in pedal should default to EXP2 baffles me!). Under 2.80 the pedal is always switching back to EXP2. Aargh! Not good.
-
Thanks, mate. I always very much appreciate folks taking the trouble to respond. I hope I've tagged correctly.
-
Well. sort of... I hadn't actually run out of authorisations at all, so this still looks like a bug of sorts. But yes, I'm fixed. How do I mark a thread 'solved'?
-
Fixed - I had to de-auth it on my account page, then re-auth, since I'd changed the name of my laptop since it was last authorised. That auth screen is utterly unhelpful!
-
It keeps telling me that I have a valid license, but must authorise this computer. When I click the authorise button it just comes back up - over and over. I can't use Helix Native at all now. I've tried in Cantabile and in Reaper - same result. I'm totally up the creek here and a gig next week that uses Helix Native in every song!!!!!! I've tried uninstalling and re-installing - no difference.
-
2.8 update stuck in 'boot failure, entered update mode'
The_Elf replied to tstanfield's topic in Helix
I was stuck too. I installed the 2.8 HX Edit, powered the Helix off/on and it finally worked. I missed the step where I was supposed to install the new version of HX Edit - and I suspect I'm not alone. -
Absolutely sure. I've checked this on two different PCs with the same result. There's obviously something strange happening between Helix Native and Cubase. It renders it pretty much unusable for me.
-
Helix Native works fine in Cantabile, for instance, but in Cubase 10 the reverb tails cut off before they've faded out. Is this a known issue?
-
I'm awaiting the ability to set buttons to 'Toggle' in the Command Centre. I'm creating my live set for June this year and I was really hoping I wouldn't have to do the faffy workaround yet again. Oh well. Better late than bodged.
-
Yep, that precisely the solution that we've discussed above. I use 'Send 3' blocks, since that's unused for me and and anyway can't cause any unforseen glitches. The only significant problem I've run into that I seem to get the odd situation where certain Snapshots send out a pedal press and I've had to go in and delete/re-assign the switches all over again to cure it. I played the first live show last night with the configuration and all went well..
-
If I wanted the switches to remain as toggles in Command Center, separate from their momentary behaviour in Bypass Control I'd call it a bug! Those two functions shouldn't be tied up with each other! We'll have to agree to differ on that one. Anyway, hopefully this will all be water under the bridge with the update. Thanks for all the advice and info - you've been a star!
-
It will be good to see a genuine way of doing this. I suspect the update and fix will likely break this workaround entirely, assuming it was the exploitation of a bug-ette. Do we know when the update is arriving?
-
Clever! It's a bit of a fudge, in that it seems I have to create a block to hang the footswitches on, so I created a row of dummy Send blocks to an unused output. Once created I could then assign the switch, and also assign it to a MIDI CC in Command Center (sic). In the Bypass Assign screen I set it to 'Momentary', and in Command Center I set it to 'Toggle'. I then named the switches to something friendly: 'Loop 1', 'Loop 2'... It looks odd, but it works. Thanks, mate! It seems like some odd, unintended consequence of an interplay between the Bypass Assign setting and the Control Center setting - I'd guess it's actually a bit of a bug. How you discovered this I can only wonder!
-
Ok, I'll take a look when I'm back in the studio. Thanks.
-
How? 'Toggle' and 'Momentary' are mutually exclusive.
-
No it doesn't That's the problem. Nothing is sent on the lift of the switch when 'Momentary' is selected. I've proved this by recording the MIDI output.
-
With 'Toggle' the Helix only sends the dim value when you press the footswitch a second time - so you have to make two presses for record, two presses for play, two presses for overdub - it's not a sensible way to work.
-
Yes, I suppose the Helix should send out a value 0 on release. Maybe not the RC-505 at fault then...
-
Just hitting this problem myself. It would appear that something is going amiss and it points at the RC-505. I'm trying to assign a Helix footswitch to the RC-505's Rec/Play function. With the Helix in MIDI CC mode and the RC-505 in Toggle mode: The first Helix control message fires the Rec function, but any further Helix-generated commands are ignored. With the Helix in MIDI CC mode and the RC-505 in Momentary mode: All commands from the Helix are ignored. With the Helix in MIDI CC Toggle mode and the RC-505 in Toggle mode: This *almost* works, but the Helix footswitch has to be pressed twice for every single action to be activated on the RC-505. So close! With the Helix in MIDI CC Toggle mode and the RC-505 in Momentary mode: Identical to when the RC-505 is in Toggle mode, as above. The Helix footswitch has to be pressed twice for every action to be activated on the RC-505. I think the problem is with the RC-505. Anyone found a way around this? It's a shame, because this pairing were almost made for each other, but for this gaping chasm!
-
For some of us the accuracy of the tap light does genuinely matter. Since I raised this problem I've met others who have had the idea of doing what I'm doing (improv over repeating echoes), but have given up due to the tap light problem. That's a shame. I really hope it can be fixed with firmware. TBH there's really no excuse anyway - that tap light should be accurate no matter what clock it is running from; the maths behind it is trivially simple.
-
Thanks, mate. I never expect perfection, and I never have a go at anyone for making an honest mistake (individual or companies) - it is how we react when a mistake is discovered that is the measure. In this case Line 6 has acknowledged my ticket, recreated my findings, given me an explanation and passed the message on - hopefully to someone who can look at the software. That's pretty good in my book. For my part I have thanked them for their response, and I will certainly keep this thread updated with progress in the hope that it can help someone else. BTW my current way around this problem is to set tempo to 60.3 and delay time to 3.994 seconds. That combo stays close enough in time to do the current improv job I'm undertaking. It means I can't use tap to change tempo mid-gig, but I can work with that.
-
Just got this response to my ticket: "I was able to reproduce the issue and have already contacted our QA. They informed me that the delay timing is spot on, but that the TAP LED may be slightly off because it runs on a separate clock. They are looking into it. Best regards Line 6 Support Europe" At least now they accept the problem, maybe they can provide a fix. Here's hoping...
-
I've had a response to my ticket. Unfortunately the respondent doesn't understand what I'm telling him, and I very much doubt that has he tried to recreate the problem. If anyone else can please confirm my findings I would appreciate it, as it looks like I will need to convince them that this is a real problem and that a fix is required.
-
Have done. No response yet...
