Bug with tempo/time-sig markers

If there is no tempo/time-sig marker present in the project, manually entering a new BPM or time signature 'at edit cursor' does not work. Talking about this: Insert a marker (using dialogue box, shift c), and everything is fine again. Feature works as intended. The workaround is to save your default project template with a marker at the start. You know how you can't delete this start marker? Doesn't make sense that if you can't delete it, it's not there to begin with. It should always be there. So my suggested fix for this bug is to 'make it so' as C. Kirk would say. Waiting to make bug report as I'm not confident in there being no existing reports already, it was hard to search for.

Thanks for saying what I already said.. I still consider that a bug because the tool-tip of the time signature button in the transport specifically says 'at the edit cursor'. If I want to change the project tempo it would make sense to either redefine it at the start or create one and move it to the start. It doesn't make any sense that there isn't one there to begin with, and yet the project plays at default 120, and then on further editing a tempo marker is placed there and then never removable. there is no point to that and screws up the way the tempo/time signature marker placement is made as evidenced.

What i tried to point out is that you can only write data to an existing envelope. So there must be a tempo envelope active/present to write stuff from the bpm field. (You cannot add points to a nonexistent envelope...) That's reaper's current rule as far as i understand it. I personally wouldn't exactly call it a bug. But what's bugging me too is that you can't remove the first tempo marker without a self-created macro. Should there by default always be a first tempo marker ? I don't know. I personally use an action (Toggle show master track and tempo envelope) to quickly create a tempo envelope.

Can't reproduce. For me it works well.

I don't have a marker at the start and I can manually enter a tempo change at edit cursor and it works as expected. It also works changing tempo or signature from the transport and it doesn't add a marker at start or anything. I don't understand what is the problem.

Heda, you don't add a new point when there is no tempo envelope. You just change the project tempo. Try the same (dragging the bpm field with the mouse) with an active tempo envelope and you will see the difference and what this thread is all about...

Yeah as I said in my first post Shift + C (insert tempo/time marker) works as expected, I am talking only about the buttons on the Transport. Which, if Cockos indeed has this envelope 'rule', are labelled wrong.