[Done] More granular time entries (start/stop/etc)

[mbatchelor]

In an audio file, you go down to at least ten-thousandths - but in SCS, it only supports hundredths. This means that for some loops, it's impossible to get things click-free. The Bass Library supports much more granularity than hundredths.

For example, in a loop, 25.27000 is way different than 25.27433 which is even way different than 25.27942. In my cases, I was able to locate a zero crossing in an audio-specialty program, but I wasn't able to use the detailed location in SCS because SCS only accepts the .27 part of the location.

Thanks for considering this,

Marc

[mbatchelor]

I know it's bad form to reply to your own post. I'm wondering if you've had an opportunity to look at this. It's be about a year and a half since I requested it.

Marc

[Mike Daniell]

The SCS user interface displays and accepts times to an accuracy of 1/100 second but internally SCS works in milliseconds. So it would be feasible to modify SCS to accept times to 1/1000 second. Increasing the granularity further would require more work but could be done if there is a need for it.

An enhancment I hope to implement soon after SCS 10.8 is released is recognition of file markers, such as those available in WAV files. This will allow you to set start, end and loop points from file markers, and these will be set as accurately as reasonably possible.

[djvomght]

Hm,

filemarkers. Would be nice to have. Perhaps import from Wavelab?

Regards Jörg

[Mike Daniell]

Probably. The initial plan is to read "cue points" from WAV files. These are defined in the WAV format standard so I would expect Wavelab and similar software to comply with this standard. I haven't looked into any equivalents in other audio file formats.

[mbatchelor]

For now, if I modified the XML document, would it work? That is, if I hack at the persisted file, would the parser read the more granular zero-crossing?

I have another project coming up very soon that will be using SCS. I'd like very much to be able to do some click-free looping to simulate vamps and such.

Marc

[Mike Daniell]

For now, if I modified the XML document, would it work? That is, if I hack at the persisted file, would the parser read the more granular zero-crossing?

Yes, that would work provided you don't subsequently edit the affected cues using the SCS Editor. You will see the times are already in milliseconds in the file.

I have another project coming up very soon that will be using SCS. I'd like very much to be able to do some click-free looping to simulate vamps and such.

Using cross-faded loops should avoid clicks.

[mbatchelor]

*bump*
I originally reported this ask four years ago. Since the times are already stored in MS, does the editor now after all this time allow us to enter the time in MS or is it still in hundredths? I've been real patient and all... As a software engineer, it seems like really low-hanging fruit... Pretty please... Sugar on top...

[Mike Daniell]

In an audio file, you go down to at least ten-thousandths - but in SCS, it only supports hundredths. This means that for some loops, it's impossible to get things click-free. The Bass Library supports much more granularity than hundredths.

For example, in a loop, 25.27000 is way different than 25.27433 which is even way different than 25.27942. In my cases, I was able to locate a zero crossing in an audio-specialty program, but I wasn't able to use the detailed location in SCS because SCS only accepts the .27 part of the location.

SCS 11 allows you to enter loop times etc in milliseconds as shown under Audio File Cues in the documentation. But it goes even better than that if you have markers in your audio file (if they are supported). See Audio File Cue Points and Markers for more info.