Opened 14 years ago
Last modified 11 years ago
#6912 closed enhancement
IOException playing a marker: This is after the end of the recording — at Version 4
| Reported by: | mdk | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Plugin columbuscsv | Version: | tested |
| Keywords: | play marker | Cc: |
Description (last modified by )
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.
Change History (4)
comment:1 by , 14 years ago
| Component: | Core → Plugin columbuscsv |
|---|---|
| Owner: | changed from to |
comment:2 by , 14 years ago
| Component: | Plugin columbuscsv → Core |
|---|---|
| Owner: | changed from to |
| Summary: | ColumbusCSV IOException playing a marker: This is after the end of the recording → IOException playing a marker: This is after the end of the recording |
| Version: | → tested |
comment:3 by , 14 years ago
comment:4 by , 14 years ago
| Description: | modified (diff) |
|---|
I experience the very same problem, and it's very annoying because I have a lot of fresh tracks with voice markets in it, but I'm only able to hear the very first marker in the track.
I'd be happy to assist, by providing more details, testing, etc..
As voice records is main feature, which makes mappers choose Columbus tracker, I believe, we can rise priority of this issue till major. Personally for me it's blocker.
Unfortunaltely I've never done Java programming, nor I've looked in code of JOSM, to help with more.



I put this ticket back to "Core", because (in my oppinion) it is a bug in the MarkerLayer while creating Markers with separate audio files and NOT a bug in ColumbusCVS.