reading data from G64 track

One more question regarding the G64 format (the answer could also possibly find its way to the doc ;-)

When scanning G64's track data for whatever (SYNC, header, payload, ..) can it happen that the data "wraps-around" the buffer?

A theoretical example: sector was found 128 bytes before the end of the G64 track data. While its headers and part of the payload fits still there, what happens with the remaining part of the payload? Will I find it at the beginning of the buffer?

Or another example: I try to find next SYNC mark. Found three consecutive bits set in the last byte of the track data. Should I check for the remaining seven in the first byte of the track data?

-- 
SD!
       Message was sent through the cbm-hackers mailing list