Accurate calculation of track duration time

nelson c

Well-known member
Hi Dmitry, I'm looking for a way to process tracks as I add them to the library. Is that possible?
I add each track to a library with the MakeLibrary command via the API.

Reading the manual I see that for example I have to specify the mixpoint time, silence:skip|mixpoint:-14.0;skip.
Is it not possible to take the values from RB?

The idea of this is to improve time streach
 
You should use the Tools->Schedule automatic library update menu command in the Music Library command to create a makelibrary command that will do the processing you need (it's much easier than manually creating it).
 
This is useless because I have tracks in the same folders for each library. (And with this command each library is associated with a folder)
I need to process without editing the songs in the database.
Also: Why can't the file types be omitted? Because the calculation would be useless, if you then have a specific crossfader configuration.
Maybe a command to process a single track per api would be useful.
It's also strange that you have to enter the threshold value in dB for the mix and it doesn't take it from the program. What's the reason?
 
This is useless because I have tracks in the same folders for each library. (And with this command each library is associated with a folder)
I need to process without editing the songs in the database.
If you only need processing, without modifying the libraries that you use, you can create a temporary library that will be updated with the makelibrary command. Any values (mix points etc) are saved separately, not in the libraries.

Also: Why can't the file types be omitted? Because the calculation would be useless, if you then have a specific crossfader configuration.
Do you mean omit the file types from processing? If so, you should exclude them from the makelibrary command (do not add folder with the files you don't want to process, or use a separate makelibrary command for them without processing).

Maybe a command to process a single track per api would be useful.
What is the use case for it?

It's also strange that you have to enter the threshold value in dB for the mix and it doesn't take it from the program. What's the reason?
There may be different thresholds, e.g. for Mix Point general option can be one value and any of the file types can have different value.
 
Do you mean omit the file types from processing? If so, you should exclude them from the makelibrary command (do not add folder with the files you don't want to process, or use a separate makelibrary command for them without processing).
In the case of fixed mix points, this has higher priority than the file type for playback?
There may be different thresholds, e.g. for Mix Point general option can be one value and any of the file types can have different value.
Sure I understand, but the program could recognize the file types and apply this automatically
What is the use case for it?
Good solution to create a temporary library, but the idea is to have all the tracks processed from the moment they are imported into the DB. (I import the music from the API with the makelibrary command)..
So it would never be necessary to process everything again.
 
In the case of fixed mix points, this has higher priority than the file type for playback?
Priorities are like this:
Segue Editor > Track Tool > File Types > General Crossfades.

Sure I understand, but the program could recognize the file types and apply this automatically
The problem with this approach is that processing is done from the Music Library, and now all processing settings are there. If it was to take settings from File Types it would require opening RadioBOSS, Crossfade settings there and adjust the thresholds - doesn't look that obvoius.

You can have different makelibrary calls with different processing settings, e.g. add file types and process them as needed, then another makelibrary call to add music/another file type with different processing settings.

Good solution to create a temporary library, but the idea is to have all the tracks processed from the moment they are imported into the DB. (I import the music from the API with the makelibrary command)..
This can be done via the API in the same way. Temporary or real library, via the API you can call all the same commands. Processing has an option to skip the already processed tracks.

So I think you should use the Schedule Automatic Library update command in Music Library to make it create the proper makelibrary command for you. You can then call this command from the API.
 
So I think you should use the Schedule Automatic Library update command in Music Library to make it create the proper makelibrary command for you. You can then call this command from the API.
I use Makelibrary for each track I import into the library via the API, track by track (The path parameter is always a single track).
I think I can process them at that time, right?, by adding the identifiers
This would solve my request
 
The problem with this approach is that processing is done from the Music Library, and now all processing settings are there. If it was to take settings from File Types it would require opening RadioBOSS, Crossfade settings there and adjust the thresholds - doesn't look that obvoius.
The problem would be processing tracks that are institutional artistic.
Silence trimming is useful, but having start or end points would mean "removing" the specific crossfaders set for this, which is strange in my opinion. And although I haven't tried it, I think it would create voice overlays with music, which for now is perfectly solved by the file type. (In music we use an aggressive overlay)
 
Back
Top