Jump to content

swanny8777

Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    1

swanny8777 last won the day on September 15 2018

swanny8777 had the most liked content!

Community Reputation

3 Neutral

About swanny8777

  • Rank
    Just Startin'

Profile Information

  • Registered Products
    4

Recent Profile Visitors

377 profile views
  1. I don't have my Helix in front of me to know for sure, but I've encountered a similar bug with delays, reverbs, and amp settings: pretty much anything that I set to utilize snapshot parameters. I don't have a solution to my problem, nor yours, but I have dug and seemed to see what may be one of the issues. The .hlx file that presets are saved as are nothing more than text files using JSON formatting, which just means you can open the .hlx file in a simple text editor to view preset information on your computer if you've used HX Edit to save it from your Helix to your computer. When you look at the file there's quite a bit of information, that can be broken down as follows (picture a tree that branches off into more detailed branches): a data field which leads to a tone field which has several different fields under it: dsp0, dsp1, snapshot 0, snapshot1, snapshot 2 (thru snapshot7, which would be your 8th snapshot), global, and controller. Basically, the information is stored to tell your Helix what the preset should load when you switch to it on the hardware, and there is separate information stored for each snapshot that you have saved in the preset. Let's for the sake of argument say that the preset is saved so that when we switch to it, it loads on snapshot 8. When it loads the preset (and subsequently snapshot 8), it loads everything correctly because the default information for the preset stored under dsp0, dsp1, global, and controller are correct (it stores the information in these fields based on what blocks were on/off, where parameters were, etc. when you hit save), however, even if I change to no other snapshot, but merely hit to go back to snapshot 8, I might find that instead of the channel volume on my amp block being set to a hypothetical [5.0], I might find that it jumps to [0.0] or [10.0]. When I peeked into some of the preset files that were giving me errors I found that the default figures were correct (as mentioned above), but when I go to the dropdown for snapshot7 (snapshot 8 on the hardware), and cruise down to the block info for my amp (in my case, block6) and look at the ChVol parameter, I see be saved as either 0, or some number greater than 1. Here's why this last part is important, the .hlx file saves values as very long decimals, so my default preset value for amp channel volume (and also preset7) should be 0.5 to give me the volume of [5.0] I'd expect to see, but it may be something like 0.49999998275 or 0.50000001023 to still yield the same result of the channel volume being at [5.0]. I have found that when I experience errors with snapshot values (for instance, channel volume drops to [0.0] or [10.0] when I switch to the snapshot), the saved value in the .hlx file may be 0.0 (resulting in [0.0] when selecting the snapshot) or something strange like 45 (resulting in [10.0] when selecting the snapshot--remember that to get this value the saved value would only need to be 1.0 or even 0.9999 or something similar). That is A LOT to say this: I bet if you open your .hlx file, or share it with me so I can check it out, if "auto" is the minimum or maximum setting you can have for your snapshot value, then you may be experiencing a similar bug. I have reached out to Line6 about this before and I guess because it didn't happen to them when building presets (even though they could open my preset, either on an actual Helix unit, or by observing the .hlx file internally), they kind of just brushed it off as a corrupt preset, which may be all that it is. So I have rebuilt presets before when dealing with this issue, but it also makes me VERY leery of using snapshots at times. You may need to rebuild your preset, or you can manually adjust the level in the .hlx file, save it, and reload it into your Helix (the latter idea makes some people nervous thinking that it might brick their unit, but anyone with any IT background I know say that this is highly unlikely if at all, so if that makes you nervous, just rebuild the preset from a New Preset and save over your trouble preset). Hope this helps, sorry for the book I gave you to read lol. If you'd rather see me coming to these conclusions in real time, here's a video:
  2. I've had this issue intermittently since I've had my Helix; it's never been a bug that I've been able to reproduce from scratch, so I was told that perhaps I had presets that were corrupt. It's interesting that the values on your helix exceed 10, mine never did that. What I did notice was that if I open the preset file on my computer with a text editor or comparable application, the value for that snapshot state parameter would exceed 10 (for example, it would be 45 [see video link below if interested, but it's a long video]), but it seemed that the Helix never allowed the value to go over 10 and the bar beneath the value would be maxed to the right. I haven't updated to 2.8 yet due to all the bugs I'm seeing here, but I'm wondering if something was lost in the code that dictates what max value the Helix is displayed. Interesting problem to see, please keep us posted on your outcomes!
  3. Played a set last night where we were in the middle of sound check when I saved a change to one of my presets regarding my snapshot based Variax model. The tempo is preset based and had been saved at 68 BPM. When I clicked back through my presets after sound check I noticed the tempo light blinking very fast. When I double tapped the button with my finger to display the tempo I believe it was 255 (it was maxed whatever it was). Thankfully it was the first song of the set... otherwise that would have thrown me for a quick loop upon starting the song!
  4. I'm late to the convo, but man that would be sweet. It'd be an awesome in recording and tone shaping scenarios; record your parts and licks and modify everything in post with a click here or there. Of course Helix Native already makes much of this possible, but it's always nice changing guitar models live to hear the difference you get, it would just be nice to have that option after the fact too. I'd buy it. But, it definitely seems like quite the task as mdmayfield pointed out:
  5. Yes, sorry, I wasn't thinking of adding the error; perhaps when I have some time to read through your resource and troubleshoot I'll be more specific :-) Thanks for the help!
  6. Yeah, it seems like it would be straightforward enough, just extracting information from the .hlx files (and the fact that you have all the neat little images and such in the package contents of HX Edit)... I just have next to NO working knowledge of doing this stuff... I was able to add buttons though for snapshots that fill in the snapshot names on loading a preset, but that's all I've gotten to work so far (I couldn't get the dropdown menu to work as such). It's fun playing around with though. And it makes me wonder why exactly we're still not able to utilize HX Edit without being hooked up to the Helix. Oh well. I've recruited my buddy's help for working on this fun little project; he's in IT and is apparently well versed in JSON (or at least more than I am), so we'll see. test 2.html
  7. Hello there! I'm trying to run your Python app from Terminal, but I'm having trouble getting syntax errors... Is there any chance I could get some help with this? I've never played with Python, but would like to get the readout from the Helix Bundle file. Thanks in advance!
  8. Wow this is great! I've been looking for a possible way to easily view the details of my .hlx presets and this is an awesome start. Would it be easy to add to this GUI? I've not done any real coding or application design, but I'd love to help in any way to add functionality to this file viewer. Specifics that I'd like to see is possibly buttons to change which snapshot you are viewing, as well as the parameters and values of the different blocks. What do you think? I know what sounds easy is not always possible... By the way the main reason I'd like to have the ability to view the files is because I'm wondering if I'll be having to rebuild many of my presets from scratch; I've been dealing with some buggy issues with parameters jumping around but after filing a support ticket I'm being told they are user error; I'm pretty sure it's an issue with my unit, but I'm not sure if simply doing a fresh install of the firmware and a reloading of my presets will help my situations, SO I'm planning on doing a fresh install and rebuilding each preset manually; my hope is that there will be a convenient way for me to view the information in each of my presets without having to reload them into the Helix and possibly causing "contamination" if that makes sense. Sorry for the rant! Regardless, let me know what you think of your GUI--I think it would be an awesome tool to utilize!
  9. I have found in 2.60 that occasionally when I switch snapshots the time parameter of delay and mod fx blocks switch from say 1/8, 1/4, etc. to ms... If I were you I'd go into your preset, make sure you do not have the fx block in question selected (I've found that hitting the amp button and changing snapshots can cause this problem on my unit), change snapshots a few times, and then go to your fx block and see if the time has changed from a note value to a millisecond value. Not sure if you're having the same problem as I am, but it's worth checking...
  10. I know it’s been a while since 2.21, but has 2.60 fixed this for you? I still get the random dim/lit switch occasionally when changing snapshots...
  11. Hi Redwan, just curious: when your volume drops out have you been able to stop and check if any parameters have dropped to zero? Perhaps you have your amp’s master volume set via snapshot and it’s bugging out? Again, just curious-I just posted about some of my parameters in other blocks going haywire; on the amp though it’s usually my presence going up to ten...
  12. So I updated to 2.60, and have been enjoying the update. There are two things that I have noticed: 1. MIDI Messages Assigned to Stomp Buttons I have posted before regarding MIDI bugs in stomp mode and command center; so far the Instant Commands are working better than they were before, but sometimes the stomp CCs can be a bit buggy. The main thing I've noticed is that if I have a CC message assigned to a stomp button, it will occasionally switch to a lit state in between snapshots; this wouldn't normally be a huge deal for me, but I mainly use the CC messages to utilize transport controls in Ableton Live. Occasionally when I switch snapshots, the Fast Forward button will be lit, and then I can't stop the fast forward function unless I completely clear the MIDI message from that particular stomp... weird... Anyone else run into this? 2. Unexpected Parameter Changes In Snapshots So, I believe I have experienced this before 2.60, but it was never so frequent that I felt the need to post to forums... Since updating, however, it seems to be happening a lot more often. The unexpected changes occurs on a multitude of blocks--Amp (Presence settings), Modulation (Time), Delay (Time, Feedback, and Mix), and Reverb (Mix). Two things happen: First, there are occasions when the time parameter switches from my tempo specific note values (such as 1/4 or 1/8) to milliseconds. Second, there are times when the snapshot value shifts whatever value I have to 0%, 1%, or 100%. This is of course a huge shocker to me when I hit a note or chord with delay on and suddenly the note doesn't stop repeating due to the feedback being at 100%. I've not been able to pinpoint exactly what causes the issue, but I think it may have to do when I plug in my Variax and press the model knob to turn on the Variax (which, by the way, my Variax always turned on automatically [if I'm remembering correctly] when I'd connect to my old HD500, is this the way other peoples' Variax functions with their Helix?). It may also just happen when I change quickly between snapshots. One last strange thing in regards to this issue: It seems like this either affects how the Helix exports or imports the presets as well. There are times when I know I export the preset with all the right settings, but other times I can load the preset and the issue is evident upon importing it to a new preset. Again, anyone else run into this problem?
  13. Any idea on when (if ever) the latency on sending notes might be fixed? Maybe it has already; I only ever tried using the MIDI notes on the Helix once to trigger some samples in MainStage 3... ideally they would have synced up with the click the band was playing with if I hit the button relatively near on beat, but sending the MIDI note from the Helix didn’t work too well. Funny enough, sending the MIDI note from my FCB1010 worked flawlessly and that signal passed through the Helix on its way to the laptop... so I’ve settled with that routing ever since. I’d love to one day have the Helix be my sole controller for both sounds and MIDI :-)
  14. So I was dealing with an issue this past week with my Variax USB interface (probably the 1st of June) and I spoke to a rep via telephone who mentioned the upcoming 2.6 update for Helix would have a massive number of midi bug fixes. Nothing more specific than that, but here’s hoping they live up to their claim that the Helix should be a “world-class master remote control for your entire touring or studio rig” (page 45 from the 2.0 Owner’s Manual).
  15. Ha! Wow Saxer, that's a ton of info! I can't really talk though-my video was fifteen minutes long! Like you, I'm glad (I use that word loosely) to hear someone else shares the same issue. Like Phil suggested, I did send a support ticket and received this response: "I'm sorry about the trouble with your gear. Thanks for the detailed info. We are aware of these midi bugs and have them logged. A fix will be implemented in a future release. Thanks for your patience while we sort this out." Not sure how long the wait will be until the "future release" arrives, but I'm hoping soon :-) Thanks Phil and Saxer for your input!
×
×
  • Create New...