Jump to time does only work with values equal or less than 9,999,999 samples

mnnm-std · 01-09-2024, 05:24 AM

Reaper v7.06/OSX64

Steps to reproduce:
1. Set Project Timebase to Samples
2. Open Jump to time/marker/region dialog (Cmd+J)
3. Enter a value equal or greater than 10,000,000 (10 million samples)

Result: Jumps at least to 10:00:00.000 in hours:min:sec.millisec (or 1,587,601,470 samples in project with 44.1 kHz).

Relative values (+/-) are working as expected.

schwa · 01-09-2024, 05:46 AM

Regardless of the ruler display units, plain 8-digit numbers in the jump dialog are always parsed as HHMMSSFF. We'll think about the best way to handle this, whether by adding an option or by supporting sNNNNNNNN to specify that the user wants to jump to a specific sample.

Or, probably it's fine to always parse as a number of samples if the user has set the primary ruler display to samples, since that's a specific/unusual choice.

01-09-2024, 05:24 AM	#1
mnnm-std Human being with feelings Join Date: Jan 2024 Posts: 1	Jump to time does only work with values equal or less than 9,999,999 samples Reaper v7.06/OSX64 Steps to reproduce: 1. Set Project Timebase to Samples 2. Open Jump to time/marker/region dialog (Cmd+J) 3. Enter a value equal or greater than 10,000,000 (10 million samples) Result: Jumps at least to 10:00:00.000 in hours:min:sec.millisec (or 1,587,601,470 samples in project with 44.1 kHz). Relative values (+/-) are working as expected.

01-09-2024, 05:46 AM	#2
schwa Administrator Join Date: Mar 2007 Location: NY Posts: 16,954	Regardless of the ruler display units, plain 8-digit numbers in the jump dialog are always parsed as HHMMSSFF. We'll think about the best way to handle this, whether by adding an option or by supporting sNNNNNNNN to specify that the user wants to jump to a specific sample. Or, probably it's fine to always parse as a number of samples if the user has set the primary ruler display to samples, since that's a specific/unusual choice. Last edited by schwa; 01-09-2024 at 06:02 AM.