From time to time (really… this happens often!) I have to deal with tracks that have absolutely zero silence at the beginning, even more, some seem to miss milliseconds of the audio content itself. I hear you thinking „bad source“ now, but those files all come from (different) legitimate stores, so this problem is something Rekordbox needs to address, because the very first beat occasionally gets placed outside the wave at a negative timecode*, and this is something Rekordbox is not capable of. If quantize is turned on, creating a loop in the beatgrids bar-0-hole will fail, as the loop is then positioned at the second beat. This affects instant playback as well.
Solution 0: Teaching the Rekordbox capable set of DJ Players how to deal with beat bars at negative positions. (u bet)
Solution 1: Turning Q off. - Not practical in most scenarios
Solution 2: Adding silent audio frame(s) at the beginning of the file.
This solution consists of a subset of methods for various cases and should only be applied on a file written when exporting to a device (and when using ProDJ-link loading of the track). The original track should not be modified (some people relay on the hashes of audio content, and further more the audio is copyright to it’s creator bit per bit. U don’t mess with Mona Lisas smile!). Cases are the derivations of different audio codings and file containers Rekordbox deals with, which is quite a lengthy list. The user should be informed about the changes that are made to the files of export devices and the consequences. (Think of a changelog on the export device that helps Rekordbox remove the added silence when doing a back import) Tags and headers need to be kept intact. (Partial) reencoding must not be used.
—place for various details I might have forgotten—
*In some rare cases, placing the first beat at the very beginning of the track might solve the problem, but this does not always help and is then way too inaccurate for my beatgridding.
Post is closed for comments.
Sorry, I don't understand why you couldn't just put the 1.1 at the start of the second bar...?
You say "creating a loop in the beatgrids bar-0-hole will fail, as the loop is then positioned at the second beat." but a loop will always start from wherever you position the start and extend for whatever length you decide. Are you quantizing the loop? You can change that in the preferences.