Jump to content

RafterRattler

Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by RafterRattler

  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 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

  5. 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

  6. 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?

  7. 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 

  8. 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 

  9. 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?

    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

  10. 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?

  11. 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!

  12. 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

  13. Can anyone tell me how to stop this darned 'rate me' nag screen from coming up on the Android app? No matter how many times I press the 'no thanks' button, it continues to come back, sometimes multiple times per session. I don't want to rate it - and if it keeps nagging me, Line 6 won't be happy with my rating. Any help would be appreciated. I'm already running the latest app version and firmware.

     

    Other thoughts....

     

    Had my FH for about a week now, and while I do love some things, once again I've been bitten by a Line 6 product. So far every product I've purchased from Line 6 can be described as 'half-baked'. They have great, creative ideas, but the implementation always falls short for me - mainly due to bugs or other design point issues. In addition to annoying patch switching artifacts and lag, bluetooth disconnects in iOS when switching apps (Apple's fault), painfully long initial app hardware patch load times, just working with the iOS and Android apps is an exercise in futility for heavy editing. Press...slide...oops missed...press again....try to slide...nothing moves...press harder like an idiot...slide...oh there's that darned tweak prompt again, so I must have missed again...back...press...slide...sound barely changes...etc...press another slider... In addition, AB tone comparisons are downright infuriating to try to do....

     

    switch to a patch...

    wait 10 seconds for it to load....

    play a few chords or notes...

    switch to the second patch...

    wait 10 seconds...

    play a few notes...

    open the editor screen...

    make a change..

    play a few notes...

    in order to not lose the change, save to My Tones...

    wait...

    save to hardware...

    wait...

    swith back to first tone to compare...

    repeat...

     

    There has got to be a better way. Before anyone asks why I don't just match the settings directly, it's because I'm using another modeler in the external loop as the compared patch and trying to match it using the FH alone.

     

    Can you tell I was frustrated when I wrote this? :D. No, I'm not a troll...just aggravated at Line 6 at the moment. Frankly I really don't know why I keep doing this to myself. I guess I just love their creative ideas so much that I keep hoping they'll hit the mark. That said, I'm already making popcorn to watch the Helix release...

     

    RR

  14. Like I said, there were several annoyances.  However, I had no expectations of it being a real amp.   I went into it viewing it as a practice tool.  I still think it can be a darn good one provided they fix the annoyances without running into hardware limitations.

  15. However, once you start the AMPLIFi Remote app, you can only stream from within the app.

     

    Unfortunately, I returned my Amplifi because the occasional bluetooth dropouts were driving me crazy.  However, while I had it, the above was not true.   ALL of my music is in my personal cloud, so I used other DLNA software to play it - and it played via bluetooth.  I just couldn't stream it from within the remote app.  I had to start streaming from the DLNA app, then while it was playing I could switch to the Amplifi remote app and do whatever I wanted and my music kept playing.   Even better, I could stream music from my personal cloud through my android tablet connected to the Amplifi WHILE my iPad was also connected and editing/changing patches.   It was really quite slick...just not reliable.   In order to do it, I had to go into the remote app settings and enable the advanced routing so I could specify a different audio source.

     

    Mike

  16. Well, ultimately you were right.  It went back yesterday.   I REALLY tried to bond with this thing....I WANTED to bond with it.   The design is slick, it's one of the best looking and sounding bluetooth speakers I've come across, and it's a great practice concept.  Unfortunately, to me it comes down to value....it was simply too expensive to have to deal with so many shortcomings.  Again, purely a personal judgement.   The bluetooth dropouts were the biggest annoyance, happening across multiple devices, even when just using the thing as a bluetooth speaker.  It would just hiccup every once in a while, but it was enough to be annoying (again, considering the price).   All I kept thinking was 'this is a great start', but I couldn't escape the nagging feeling that as time went on, it would never get finished, the fixes would stop, and Line 6 would end up releasing a new version after figuring out they couldn't overcome the hurdles with the existing hardware....leaving me with a $400 brick.   Unfortunately, with the business model for most hardware/software companies these days being 'just release it and let the public do the thorough testing', it just wasn't for me.   I'll check back after the next generation.

     

    FWIW, I did submit several ides to the idea website....hopefully Line 6 is listening.  I'd like to go back and get one of these someday.

  17. Hi folks.  I've been looking for a smallish STEREO practice amp for a while, and I have a Blackstar ID:Core40 on order.  Although quite a bit pricier, I picked up an Amplifi 75 yesterday as well - mainly because of the hype over its stereo effects.   I thought I'd share my thoughts here.  Do the Line 6 folks watch these forums?

     

    After two days, I have mixed feelings.  I really like this thing because it's fun, cool looking, powerful and a great Bluetooth speaker - but if I look at the whole package objectively, I have far more dislikes than likes.   I went to bed last night pretty intent on taking it back.  Today I like it a little more...but just a little.  Unfortunately, if the consensus is that this is truly the completed product, it will likely go back.

     

    First of all, I bought the 75 because I liked the size (and because GC didn't have the 150 in stock).   It's quite possible that some of my complaints will apply only to the 75.

     

    Likes

    - Really slick and modern styling (even though it does feel a bit delicate).

    - One of the best sounding Bluetooth speakers I've heard

    - Integrated PS - no brick

    - For the most part, the app is easy to use 

    - Seems to have quite a bit of low end for a small amp, even with just an 8" speaker

    - Lots of power for the size

     

    Dislikes

    - Virtually NO stereo separation for guitar effects.  Where is all the hype coming from?  Given that this was sold as a feature, this one is baffling to me.  They are definitely running in stereo, but I have to stick my head right between the two little speakers and concentrate to notice it.   Would it really have been that hard to add 5-10ms between the channels to fill it out?   Any chance of adding an adjustable delay between the L/R channels in the next firmware & app drop?

    - Bluetooth skips fairly often - VERY annoying when you're playing to tempo.

    - Bluetooth can only pair with one device at a time - a real PITA when I want to use both my iPhone and iPad, or stream from my Android.

    - Patch changes through the app are slow, and add Bluetooth breaks/skips.

    - App is WAY too dependent on it's own player.  I have my music in a personal cloud and not local to my device - so I can't even use the player.  How about adding DLNA support to the player?

    - Way too difficult to find tones.  I should be able to just search without going to the player.

    - Annoying to create a brand new tone.  Can we have just a 'new tone' button where I can start from scratch?

    - No way to type in parameter values directly...forced to use the sliders.  Can we have a value input box?

    - No clear way to port tones from POD Farm (since it appears to be based on the POD Farm tech).  I ported a few of my tones manually and they actually translated fairly well - much to my surprise.

    - No clear way to back up tones other than in the cloud - which is automatically synced.  Make a mistake, lose your tone.

    - Higher gains leave something to be desired.  I almost want to say they have a cocked wah sound to them....at least to my ears.

    - No detailed manual anywhere that I can find

    - Why is it so hard to find detailed specs?  How big are the satellite speakers?   Does it use BT 4.0?  APTX? 

    - Can we have a way to turn off that infernal tap temp light when we don't need it?

     

    Like I said earlier, it's a shame because I really like this thing....but I also find some of it's limitations extremely annoying.  It's kind of an expensive toy to be on the fence about....

     

    Mike

×
×
  • Create New...