Live segment limit

The 1030+ took the segment limit to 300. 

The 1040 has the same segment limit.

Thanks. I can understand a limit when the memory and speed of these units was limited, other vendors seem to cope with it. I can work with with 300, might look at the 1030+ as well.

to be honest, Live Segment is too buggy and unreliable at this stage on the 1040, so whenever I want to do live segment rides, I still use my edge 830 instead.

Hopefully it won't take too long to get fixed

Can you provide more details describing what the issue are that you are seeing when using segments. You can send me PM if you want.

Hello,

I think I already mentioned the font size of the live timing, but I experience other issues such as:

* beeping sounds don't make any sense

* exiting live segment screen because supposedly we're not on the segment anymore (even though we still are)

* I had one occurrence of trying to exit a running segment, and when arriving to the "Yes/No" option it would not accept either option (touch was registered but had no effect) and kept staying superposed for 20 minutes before disappearing by itself.

I saw the message of trickytree1984 on the beta 12.14 thread, I believe this is the issue I'm describing with inversion of "losing sound" and "beeping sound" 

Also, this issue is exacerbated with the issue of "off segment" I just mentioned, as it would play the "losing sound" a few times in a row thinking (wrongly) we have exited the segment. I think I mainly saw this issue when multiple segments would exist on the same route (which doesn't cause any particular issue on the edge 830), maybe it's trying to switch from one segment to another? or maybe it's totally by coincidence.

The "stop" segment was maybe a one-off, and was on 12.11 so maybe due to general stability of the device, dunno...

If you are near the start of multiple segments this can be expected as it loads up the first one it comes to, if you then don't start that one and move nearer to another it terminates the first one and loads the second one. This gives the off segment message and sounds for the first segment it loaded.

In terms of the tones played upon  segment completion, both the 830 and 1040 currently have the same behavior in that always play the success tones when you complete a segment irrespective of if you beat the VP or note. The success is associated with completing the segment. I'm not saying Garmin has this right, but there is no change in behavior. 

I've passed on the suggestion that they sound should be based on the outcome on not based on just completing the segment.

I rode with my 830 yesterday and confirmed that it does play the success tones when you lose. It may be because the speaker on the 1040 is louder that this is more noticeable. 

I'm 100% sure the behaviour is different between 830 and 1040.

Don't remember exactly how the other user described it but here's how it works on 830 (which is I believe "as intended):

* The "success tone" is indeed played at the end of a segment, regardless of your final result.

* The "lost tone" is played when the time you chased has been achieved and you're still in the segment (indicating you didn't beat the chasing time, but haven't finished your segment yet)

* The "single beep" occurs when you lose track of the segment (either by not starting it or changing directions during a segment"

On the 1040, the single beep occurs in scenario 2 and "lost tone" occurs in scenario 3, so this is reversed compared to the edge 830.

Thanks