Opened 16 years ago
Closed 16 years ago
#973 closed defect (fixed)
Cannot playback wav files if timestamp is correct
| Reported by: | anonymous | Owned by: | framm |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | Core | Version: | tested |
| Keywords: | Cc: |
Description
Cannot playback .wav files when the time-tag is correct (see http://www.w3.org/TR/xmlschema-2/#dateTime):
<wpt lat="XX" lon="YY">
<ele>ZZ</ele>
<name>voice</name>
<time>2008-06-27T16:02:10Z</time>
<link href="20080627_180205.wav" />
</wpt>
I get the error: "this is after the end of recording"
But it works when it is wrong:
<wpt lat="XX" lon="YY">
<ele>ZZ</ele>
<name>voice</name>
<time>2008-06-27T16:02.10Z</time>
<link href="20080627_180205.wav" />
</wpt>
Attachments (2)
Change History (9)
comment:1 by , 16 years ago
by , 16 years ago
comment:2 by , 16 years ago
JOSM does accept both the correct hh:mm:ss notation in trackpoints as the incorrect hh:mm.ss notation.
It doesn't accept the correct hh:mm:ss in voice waypoints, producing the popup notice mentioned earlier. Omitting the <time> tag inside <wpt /> gives playable voice waypoints, leading to tools putting the time in a <desc> or <cmt> tag to circumvent this bug.
comment:3 by , 16 years ago
the Problem is the Timezone tag at the end of your datum.
I try to fix it.
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
ok I fixed it.
I added another SimpleDateFormater with Timezone. So it should work fine now.
comment:5 by , 16 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
arg after the change it accepts Timezones but it is an error from the AudioPlayer
comment:7 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Filename checking patch commited for r942.
Unreproducable. Add more information (e.g. the wav file and the gpx file).