Sorry for my missing details:
Windows XP SP3
I downloaded the exe file.
The error I get is “Including your time offset of ~a seconds, your requested~%label interval of ~a seconds is greater than the duration~%of your selected audio (~a seconds)”. I just copied the error from the plugin, because I found a way around my issue. The problem might be that I’m running Windows XP.
I’ve built a label file generator, that fits my needs. It’s a bat file and will ask for hours, minutes, seconds, timesplit period and the title for the labels. It handles up to 999 files.
echo "Remove this line" s> test.txt
set /p Hours="Hours: "
set /p Minutes="Minutes: "
set /p Seconds="Seconds: "
set /p Titel="Titel for tracks: "
set /p Timesplit="Timesplit in seconds: "
set /A TotalSeconds = %Hours% * 60 * 60 + (%Minutes% * 60) + (%Seconds% * 1)
echo Total time is "%TotalSeconds%"
set /A Counter = %TotalSeconds% / %Timesplit%
echo Total chapters is "%Counter%"
set /A countTemp=0
set /A Counter=%Counter%+1
set Chapter = 0
FOR /L %%G in (0,1,%Counter%) DO (
set /A Chapter=!countTemp!+1
set /A Temp = !countTemp! * %Timesplit%
echo !Temp!,000000 !Temp!,000000 %Titel%-!Var! >> Labels.txt
set /A countTemp=!countTemp!+1
But I might try import the next large file to my Win7 machine and compare what I can do on either machine.
I will do a screen shot in the weekend - so you can see what my settings are when it’s working and what they are when it doesn’t work.
From my point of view - no. I did CTRL+A (Select ALL), and the time periods in the bar at the bottom was 00:00:00.000 - 14:37:20.000. In the Regular Interval form I only changed the period and how the numbers should be applied to the prefix text. When I tried with a smaller part of the track(00:00:00.000 - 08:00:00.000), but it still failed, the time selection in the bar at the bottom defaulted back to the full length of the track. So I concluded that something must have gone wrong, since it changed my selection.
if I’m selecting all of a track that long at 44100 Hz, I can reproduce the error “Including your time offset of ~a seconds, your requested~%label interval of ~a seconds is greater than the duration~%of your selected audio (~a seconds)”. It doesn’t give that error if the 14.5 hours track is at 22050 Hz. This is one of the 32-bit limitations still in Nyquist or Audacity, I guess - at just over 13.5 hours, a 44100 Hz track exceeds the 32-bit limit of 2^31 samples of audio.
Perhaps you clicked outside the track in error, so that Audacity would not have the selection in the track any longer. In that case Audacity would select all the track. Regular Interval Labels works for me in a selection 8 hours long in a 14.5 hour track at 44100 Hz.
But if you can reproduce a problem, please give the steps and the plugin settings.
I did my test before Splaxi said that he was applying to a 14+ hour selection.
Yes, Nyquist works entirely in 32-bit, so 14 hours of audio at 44100 Hz sample rate will overflow (the number of samples is greater than can be represented as a “signed 32 bit integer”).
To work around this limitation, create a new track (Tracks menu > Add New > Audio Track), and use the track control panel menu to set the track sample rate to a low rate (such as 11025 Hz) http://manual.audacityteam.org/o/man/track_drop_down_menu.html
Then ensure that the selection is in the new (low rate) track only.
This can be altered for the next audacity version (or rather the version after that).
The selection end time (from the property '*selection–>'end) is expressed in seconds and not affected by this limitation.
OK my name’s not Robert, but what he is (correctly) saying is that once Audacity 2.1 is released, this limitation can be easily fixed.
Audacity 2.1 supports version 4 plugins, which give Nyquist access to additional information from Audacity, including the start/end time of the selection in seconds.
The current version of the Equal Labels plugin has to calculate the start / end times either from the (get-duration) function, or from the ‘LEN’ (number of selected samples) variable, both of which amount to much the same thing because they both depend on the sample count.
To fix this limitation, the plugin version needs to be changed from version 3 to version 4, and then instead of
Several of the shipped plugins are likely to benefit from updating.
I was planning to update Regular Interval Labels anyway - I think it would be a useful enhancement if there was an option to start the labels at a specified time (currently the start time is relative to the start of the selection, but with version 4 we can start the labels at an absolute time position).
The code in the snippet has to know how long the selection is.
Normally, this is achieved with
for seconds or with the variable ‘len’ in samples.
Due to the 32-bit limitation, len takes the highest possible value–which is negative and ‘get-duration’ = 1 (s).
However, Version 4 plug-ins deliver the start and end time as a property of the variable 'selection and those are expressed in seconds.
Thus, the lines 117 and 118 in equalabel.ny have to be changed to