Please ensure Javascript is enabled for purposes of website accessibility Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


MonkeyXT last won the day on April 25 2017

MonkeyXT had the most liked content!

1 Follower

Profile Information

  • Registered Products

Recent Profile Visitors

1,103 profile views

MonkeyXT's Achievements

Community Regular

Community Regular (8/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Reacting Well Rare
  • Week One Done

Recent Badges




Community Answers

  1. Yes indeed - same cable as Variax. I use one of those exact ones - *knock on wood* works great, and is very robust.
  2. Hey. Absolutely I am - a pair of them. They sound great - and I've compared them to a few things... Speakers actually tend to sound better when they're worked in some I find; other input would be welcome here on this sub-topic. I wouldn't hesitate to test-drive and even take a rental - I did... and bought brand new and have been working them in =]
  3. I recall someone mentioning working with one of the NX units. At my suggestion, while at my local Long & McQuade location, there was a unique opportunity to do an A/B comparison between a YX10P and one of the Friedman powered FRFR 12" cabs which had just come in on trade. The YX held its own very very well - the employee who was interested in this comparison and had been considering grabbing the Friedman instantly changed plans and went with the YX10P.
  4. If the CV doesn't work out for you, I recommend you consider the Yorkville YX10P - somewhere here on the forum I posted some details about my experiences with this model, including a comparison session with the higher-end version E10P, which on paper looked like a surefire winner, but in practice there was 'something' which didn't sound as sweet as the YX10P - my good friend likely identified it precisely when he pointed out that the crossover point is a bit different between the two, with the YX10P having a bit more ear-pleasing result. They're a simpler, less feature-rich solution as compared to the CVE-10, without a doubt. However, if the sound of the CV doesn't quite do it for you, I suggest it's worth a listen. And I'll be watching this thread to see how your CV experience goes - which could trigger a test-drive/comparison session for me. Good luck - hope it works great for you.
  5. If I'm not mistaken, I think fish95 was actually asking for something simpler; an on-screen way of long-pressing the Tap button in order to engage the tuner on the hardware. That's how I read the original post.
  6. Lightning fast! Looking to install now.
  7. For the record, to add to the data on user experiences: Two evenings ago I updated my Helix Rack/Control from v2.82 to v2.90, following the release notes' instructions to the letter (using the new HX Edit pathway to acquiring the update, etc.). It was the first time I had any real issues during an update (practically a comedy of errors which saw me re-doing the process 3 complete times); the end result was that my Helix was afflicted with the Volume Knob glitch - it wasn't controlling anything, no matter what steps I took to reboot, change the settings, etc. In fact, on the last reboot attempt I made, the volume came on sky high, higher than it had on previous reboots. There may have been other issues which I didn't even get far enough to investigate, like the tuner glitch, which I know that my good friends' Floor ended up with - he was also in the process of re-doing the installation. Last evening I simply wiped the slate clean yet again, and re-did the update procedure - important to mention, with only one difference in the methodology of the process (same computer, USB cable, port, etc. - the only functional difference being that I had to use the Updater application to re-flash after I factory reset the unit again, something that HX Edit 2.90 does not have a pathway to doing). I've not spent much time investigating the latest greatest from this new version, but I can certainly say that the REVV Purple channel amp is a fast favorite - I've already bonded previously with the REVV Red channel model as well. As is being often reported, I do believe I'm seeing the tap-tempo misbehavior issue, for which I'm looking forward to a hot fix, but in general it's not a feature I actually use all that often or critically - I generally set my tempo manually. Kudos to Line 6 for a feature-rich update, delivered during - to say the least - challenging circumstances. The end result was that it all appears to be working as expected.
  8. Hands down one of the best navigation-related updates in the history of Helix to date. I've done the same thing as the OP - as I'm certain MANY of us have... once this option became available, I absolutely immediately changed it in Global Settings to the new option.
  9. As I recall, that's the only way it has ever worked; one state is lit up, the other is dim/same colour. Interesting possible option, though I don't know if I'd want to give up any horsepower for that feature if it introduced any unintended lag anywhere else.
  10. I would implore Line 6 to do us the favor of resisting the temptation to use characters in the preset names which equate to illegal file-system characters. For instance, on the factory presets with names similar to; BAS:Whatever Something +/- Why * ... exporting those as individual files - at least on a PC's file system (I have no experience with Mac/other file systems) - will create failures/errors, because those characters cannot be used in file names - and the preset name is of course automatically used as the preset file's name. Before creating backups (wherein I do both setlist AND individual preset backups), I go into the factory setlists and re-name the ones with those types of characters (using a dash (-) instead of a colon (:) for instance, so that those individual files won't fail or cause an error/hang-up. I recommend to anyone who'll listen to make a habit of sticking to 'legal' characters for preset names. This of course is a non-issue for anyone who strictly works with setlist & full-state backups only - but if there's even a remote chance that you'll be exporting individual presets for other purposes, save yourself confusion and headaches by sticking to the 'legal' characters in your preset naming conventions.
  11. Ok - now I see it wasn't just my imagination. I have a preset which has followed along up through various firmware versions from 2.0 upward. Somewhere early on, this carefully crafted preset which, early on, had its parameters mangled in an update. I never did get it back to where it was meant to be - wasn't a huge deal, but... Once I'd put 2.81 in, I decided to test the waters by revisiting that preset in order to get it re-set to work how it originally did (it uses a couple of twin harmony blocks to create an oddball harmony section for a solo break). Got it back to where it was meant to be, saving its various states to the Snapshots and footswitch that control the parameters. Multiple tests. Moved away from the preset, then back to ensure it was saved as intended. All good. Shut down after noodling a while. Next day I went back to it; some of the assigned values were entirely different - in fact, max'd to the extremes both + and - (interval shift). I managed to convince myself that I'd somehow messed with it one time too many, and had unintentionally saved the preset in an unintended state... I was skeptical of this, but it had to be /something/... Though I don't know how I'd managed to botch it, AND recall it with expected results. When I checked it again last evening, it was still ok. But seeing other reports - like the above - of Snapshot values not saving properly, I've come back around to thinking I might not have been an error on my part after all.
  12. My pleasure. The other individual considered that 'solved' after that, having been able to get predictable and repeatable results, once getting used to the quicker press habit. Hopefully that works out the same for you. I look forward to hearing the result.
  13. ... you might find that pressing and releasing the joystick push function quicker makes it act predictably - it seems to ignore 'long' presses since v2.8x, and 'long' isn't all that long either.
  14. I was able to point someone else in the right direction with what I believe is the same behavior as you're seeing here - I believe that with the new options available for the joystick control, some internal parameters for the joystick controller functions have been adjusted. Specifically, the push straight in to select. It seems that v2.8x instructs that device to ignore any 'long' presses - and its idea of 'long' is still pretty short. But, if you tap it in and release relatively quickly, I believe you'll find the control function will work predictably. If you're willing to re-update, maybe give this a try.
  • Create New...