Jump to content

RafterRattler

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

1 Neutral

About RafterRattler

  • Rank
    Just Startin'

Profile Information

  • Gender
    Not Telling
  • Registered Products
    2
  1. Well none of the suggestions or descriptions of how it is supposed to work have panned out. I just can't force it to the state I want, and it doesn't seem to work as the last few posts have suggested. I guess if I really want to take this further I'm going to have to take a video of me changing settings to prove it. If it's me, then maybe you'll be able to tell me what I'm doing wrong. RR
  2. Ok now we're getting somewhere - that could very well be the case. If I understand you correctly, you're saying that whenever I resave a patch, the selected effect on the screen and it's state (on or off) becomes the 'on' state of the footswitch? Does it only apply to effects assigned to the footswitch or any effect in the patch that may be selected? If I have that right, then I'm glad I reported it as a bug, because unless I'm missing something, it seems like a pretty stupid design decision. RR
  3. I'll try one more time, then I'm giving up. I just don't know why I'm apparently being so unclear. The blocks are working as they should. The block states are saving as they should. When I hit the footswitch, the blocks toggle as they should. It's the STATE OF THE FOOTSWITCH DISPLAY that I'm questioning. Here's a simple example: - Say I create a patch with two amps - one dirty, one clean. - Before assigning ANY footswitches, I bypass clean one, and turn on the dirty one, and I save the patch. - I then decide for my footswitch strategy that I want the LED ring to be bright and the scribble strip text solid when the clean amp is selected and the dirty amp is bypassed. I also want to rename the footswitch to 'CLEAN'. Step 1: I bypass the dirty amp and turn on the clean amp - ie: CLEAN AMP is in the ON STATE. Step 2: Since I want the LED bright and scribble strip to be solid when I select this state, I first assign the dirty amp to the footswitch. THEN I assign the clean amp to the footswitch - ie: the last block assigned represents the state I want the footswitch to reflect - ie: LED bright, scribble strip solid. Step 3: I rename the footswitch to 'CLEAN' in the customize dialog Step 4: Save the patch. Now I never mess with the footswitch assignments or toggle states again. I do, however, mess with amp levels, other effect parameters, etc...and resave the patch. AGAIN, I have not touched the footswitch assignments prior to saving. Now when I go back to the patch, occasionally the CLEAN footswitch I created will have a bright LED and solid scribble strip text when the dirty amp is selected and the clean amp is bypassed. Changing the states so that the clean amp is on/dirty amp off and then reasigning the clean amp to the footswitch doesn't change the state of the footswitch status display. This is a simple case just for illustration only. In reality, I will have other blocks toggling like - like volume blocks and modulation. I am equally careful with their toggle states as well. RR
  4. I'm not sure how much clearer I can be. As I said in my OP: "I've tried various block assignment procedures - such as making sure the last block I assign to the switch is in the state I want the footswitch to show..." Am I missing something? RR
  5. I'm 99% sure I'm doing it right, but I'll try one more time. I toggle (some to on, some to bypass) up to 7-8 different blocks with one switch, and the switch state doesn't hold, even if I haven't reassigned any switch controllers. MonkeyXT has been reporting it as an error as well in the bug thread. RR
  6. Yeah....that's the assumption I was under, but it doesn't appear to work that way (at least with several diff effects/amps being toggled), and the reason I posted. The switch states appear to swap randomly after I've saved the patch, and just reassigning the last active effect (the one that reflects the state I want) does nothing. For the record, I'm on firmware 2.54. RR
  7. Thanks Monkey - I've opened a ticket as well. RR
  8. Without using Snapshots, I have several patches where I have footswitches configured to toggle multiple effects - ie: turn some on, and some off with a single press. While it functions perfectly, the state of the footswitch on/off indicator that gets assigned seems to be rather random. For example, suppose I want to bypass one amp and turn on another with one switch, and I want the switch to be bright & the scribble strip solid when I select the second amp. I've tried various block assignment procedures - such as making sure the last block I assign to the switch is in the state I want the footswitch to show....but it seems to randomly change on it's own sometimes after the fact. At this point I'm assuming it's a bug. Correct?
  9. Thanks. Unfortunately that is what I originally tried, but it appears to be hit or miss. It doesn't work reliably, and even when it does, some of them invert again after saving. I guess I have my answer though - there is no way to force it. I'll report it as a bug. Thanks for your help! RR
  10. Hopefully this question isn't too redundant. I haven't found a good set of search terms that return anything. Without using Snapshots, I have several patches where I have footswitches configured to toggle multiple effects - ie: turn some on, and some off with a single press. While it functions perfectly, the state of the footswitch on/off indicator that gets assigned seems to be rather random - and I haven't figured out how to force it. For example, suppose I want to bypass one amp and turn on another with one switch, and I want the switch to be bright & the scribble strip solid when I select the second amp. Is there a way to manually assign it? I've tried various block assignment procedures - such as making sure the last block I assign to the switch is in the state I want the footswitch to show....but it seems to randomly change on it's own sometimes after the fact. I'd love to be able to set the default in the same way I can set the default LED color and name. Hopefully that was clear. Any thoughts? Thanks, RR
  11. Some additional interesting behavior: - If you power cycle the FH while it is connected to a device, it will automatically reconnect with the device - If you power off BT on the device and then power cycle the FH, the FH does not try to reconnect...BT just stays disabled until you press the BT button. FWIW... RR
  12. Some new info. While my Android tablet was charging, I did a little playing around with iOS. Here's what happens once paired, and then I power cycle the FH: 1. If no paired devices are in range or BT is turned off on my iOS device, the BT light on the FH just automatically blinks quickly - indicating pairing mode. 2. If the paired device is in range and BT on the device is on, the FH immediately connects, even though the BT light on the FH starts out off. 3. If an unpaired device is in range and BT on the device is on, the FH blinks slowly, does not connect, and is unavailable to pair. I'm guessing the slow blink indicates that it is trying to connect. In order to pair, I have to hold the BT button on the FH for a few seconds until it starts blinking quickly. Now here's the kicker. If I UNPLUG the FH completely, then plug it back in and turn it on, the BT appears to be disabled. It doesn't try to pair, and doesn't connect until I press the BT button. So: - BT light off = BT is off, or you just powered the FH on and it is already connecting. - slow blink = attempting to connect - fast blink = pairing mode - solid = connected Again, shouldn't this be documented somewhere?
  13. I may resort to trying that, but it seems I shouldn't have to. What's the point in a "no thanks" button if it doesn't do anything? I don't like rating apps because I don't like my real name showing up...privacy thing... RR
  14. So when you turn your FH on, does the BT light automatically start blinking, or does it stay dark until you press the BT button? Mine stays dark until I press it - then it connects. I'm using both iOS and Android, same result. I'm now wondering how it's SUPPOSED to work. BTW, with Android, mine stays connected when I minimize the app. iOS disconnects....which is one reason I prefer the Android version. Thanks!
  15. Is there a complete writeup anywhere on the bluetooth button modes and unit capability? Both the specs and BT FAQ online seem to be missing information. For example, can it pair with multiple devices? Can it connect with multiple devices at once (like one for eduting and one for music playback)? Does pressing the blutooth button really put it in pairing mode, or just connection mode? I frequently switch between iOS and Android tablets, and I have found that when I switch, I can't just turn on bluetooth and have them connect to the FH. I have to make each tablet forget and re-pair. In addition, although it works this way with many BT receivers and speakerphones, just pressing the BT button on the FH doesn't initiate re-pairing even though it is flashing like the FAQ says. I have found I have to hold it for a few seconds until it flashes faster before I can re-pair. Finlly, when I turn the unit on, do I really need to press the BT button to connect, or should the devices automatically connct like a speakerphone? Seems like this should all be documented somewhere. RR
×
×
  • Create New...