id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
6912	Regression: IOException playing a marker: This is after the end of the recording	mdk	OliverW	"ColumbusCSV uses a separate audio file for each Marker. While debugging I found, that the Markers (in Marker.java) are created with a offfset. Only the first Marker has (the correct) offset of 0.0. The following (in my example) have increasing offsets (313, 338, 369, 413, 468, ...). Because the offset is in seconds and my recordings are NOT 5min.+ long, this cause the seen errors.
The offset calculation makes only sense, if I have ONE audio file for all markers. If there are separate offset files for each Marker, the offset must always be 0.0.

Possible solutions:
  1) A hack in ColumbusCSV.java after creating the new MarkerLayer in line 88:
  loop over all markers and set offset to 0.0.

  2) A little bit shaky solution in the MarkerLayer constructor (line 79) where the individual markers are created (Marker.createMarker()):
  Reset firstTime to time if indata.storageFile changes (this did not handle alternate re-usage of some files)

  3) A new MarkerLayer constructor (or a new parameter in GPXData) specially for the case that indata has separate audio files for each Marker.

I wonder if nobody else has problems using ColumbusCSV plugin, or if the problem only occure with a new version of the Logger.

I choose Core for the component, because ColumbusCSV plugin can only implement a hack and not a real solution."	enhancement	closed	normal		Plugin columbuscsv	tested	fixed	play marker