View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update | 
|---|---|---|---|---|---|
| 0009278 | ardour | bugs | public | 2023-03-13 03:06 | 2023-03-15 01:49 | 
| Reporter | thekoala2 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always | 
| Status | new | Resolution | open | ||
| Platform | Ubuntu | OS | Linux | OS Version | (any) | 
| Product Version | 7.3 | ||||
| Summary | 0009278: Information in the selection clock widget is not accurate when set to "samples" | ||||
| Description | If you do the math on the sample info in the selection clock widget, you will find it is innacurate End - Length =/= Start  | ||||
| Steps To Reproduce | 1 Set selection clock to samples 2 select a range 3 information is not accurate  | ||||
| Additional Information | The number of samples difference is not consistent Snap or free selection makes no difference Tempo map or simple bpm makes no difference A few screen shots provided  | ||||
| Tags | No tags attached. | ||||
| 
		 | 
	
	 | 
| 
		 | 
	
	When counting frames  Length = End - Start +1 (similar to the fencepost problem) start 00:00:00:00 end 00:00:00:00 references the first frame. The length is 00:00:00:01 An "empty" selection has neither start nor end. This convention dates back to editing tape and film.  | 
| 
		 | 
	So is this intentional behaviour? If it is, I will close the report. | 
| 
		 | 
	In general yes, except in the first case I'd expect the length to be 97086. There is still some oddity here. | 
| Date Modified | Username | Field | Change | 
|---|---|---|---|
| 2023-03-13 03:06 | thekoala2 | New Issue | |
| 2023-03-13 03:06 | thekoala2 | File Added: example1.png | |
| 2023-03-13 03:06 | thekoala2 | File Added: example2.png | |
| 2023-03-13 03:06 | thekoala2 | File Added: example3.png | |
| 2023-03-13 03:15 | x42 | Note Added: 0027471 | |
| 2023-03-15 01:42 | thekoala2 | Note Added: 0027476 | |
| 2023-03-15 01:49 | x42 | Note Added: 0027477 |