is there a way to stop this

[protooleriate]

say I put a marker in at 1.00.00.00, then want to put in a marker 15 seconds previously, so I type *-1500, but before I hit enter to move the cursor back 15 seconds i change my mind and want to make it 10 seconds so i hit escape. then I type *-1000, and then hit enter, then the cursor goes somewhere completely different and wont let me do any moves relative moves like that without going to completely the wrong place every time, often out by hours. If i save, then quit tools, open it up again it's fine, is this me and is there a way of canceling some mode I have got into, or is it just a bug??

[SimpleNatureSpirit]

say I put a marker in at 1.00.00.00, then want to put in a marker 15 seconds previously, so I type *-1500, but before I hit enter to move the cursor back 15 seconds i change my mind and want to make it 10 seconds so i hit escape. then I type *-1000, and then hit enter, then the cursor goes somewhere completely different and wont let me do any moves relative moves like that without going to completely the wrong place every time, often out by hours. If i save, then quit tools, open it up again it's fine, is this me and is there a way of canceling some mode I have got into, or is it just a bug??

I assume the -1000 and -1500 are samples. change your counters to samples and highlite a region starting where you want it (you might use grid mode for this or you can type it in the counter window). Then inset a marker. It will be loacated at the beginning of the highlighted area.

[protooleriate]

no, that is what I would type to go back 10 or 15 seconds, so if I type *-1000 and then hit enter the curor wll go back 10 seconds and no framses, assuming I am using timecode as my main ruler. so if i have a cue that starts at one hour, I would want a marker there, and anotehr 10 seconds earlier to give 10 seconds preroll every time, whatever timebase I am in

[snaggle]

I just tried your scenario and it's working fine for me.

[protooleriate]

ok

I just worked out that it only does it with the big session counter up, which I guess fixes my problem, however it's still annoying

[snaggle]

Just to let you know...I couldn't reproduce that either in 5.3.1cs2 or 6.4cs8.

Hmmmmmm?

[protooleriate]

how weird, I can reproduce it on over 6 different rigs, with software versions ranging from 5.1.3cs11 through to 6.4cs8, havn't had a chance to try this, but I always enter if using the numeric keypad

[tj_davies]

Happens to me as well.

I'd love to know, whether there is a way of resolving this, as it is extremely annoying. For it being "only" a BIG COUNTER problem doesn't really work for me, as * jumps into the big counter only, which means, I'd have to go into the small counter using the mouse, and that would slow down my work routine.

So if anyone has a solution, let it be heard.

Tim