--- Log opened Fri Jul 17 00:00:37 2015
00:38 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Remote host closed the connection]
00:38 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit
00:38 -!- mode/#navit [+o KaZeR] by ChanServ
00:43 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 255 seconds]
02:05 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has joined #navit
02:44 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
02:58 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has joined #navit
03:19 -!- jjelen [jjelen@nat/redhat/x-nigseygouxsdefdi] has joined #navit
03:25 -!- Horwitz [mich1@baldrian.franken.de] has quit [Ping timeout: 264 seconds]
03:34 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has joined #navit
03:49 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
04:10 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has joined #navit
04:19 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has quit [Ping timeout: 248 seconds]
04:39 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit
04:39 -!- mode/#navit [+o KaZeR] by ChanServ
04:43 -!- KaZeR [~KaZeR@c-67-161-64-186.hsd1.ca.comcast.net] has quit [Ping timeout: 250 seconds]
05:06 #navit: < rcorello> re
05:58 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has joined #navit
06:09 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
06:11 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has joined #navit
06:31 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
07:55 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has joined #navit
08:11 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has quit [Ping timeout: 244 seconds]
09:10 -!- xenos1984 [~xenos1984@95.235.14.239] has joined #navit
10:01 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has quit [Ping timeout: 265 seconds]
10:20 -!- xenos1984 [~xenos1984@95.235.14.239] has quit [Ping timeout: 256 seconds]
10:32 -!- xenos1984 [~xenos1984@95.235.14.239] has joined #navit
11:06 -!- jjelen [jjelen@nat/redhat/x-nigseygouxsdefdi] has quit [Ping timeout: 264 seconds]
11:59 -!- gernot_ [54b56f5c@gateway/web/freenode/ip.84.181.111.92] has joined #navit
11:59 #navit: < gernot_> hi
12:01 #navit: < gernot_> I have recorded a nmea file which loose track. The GPS-Signal was a bit off road.
12:02 #navit: < gernot_> Destination was Ampfing BY
12:06 #navit: < gernot_> http://pastebin.com/ZkPTTdWN
12:07 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
12:11 -!- KaZeR [~KaZeR@64.201.252.132] has joined #navit
12:11 -!- mode/#navit [+o KaZeR] by ChanServ
12:11 #navit: < gernot_> I think my map is Ok. its a geofabrik export. I think also OSM coordinates are correct.
12:12 #navit: < gernot_> Maybe my device is bad
12:13 #navit: < gernot_> at this trip i had 3 times this problem.
12:16 #navit: < gernot_> Target was 84539 Ampfing
12:46 #navit: < rcorello> gernot_: out of couriosity: do you happen to know which line in the nmea log corresponds to the problem losing track?
13:01 #navit: <@KaZeR> hi there
13:02 #navit: <@KaZeR> rcorello: looking into testing your patch i found three bugs into the current implementation of the key highlighting :)
13:10 #navit: < rcorello> KaZeR: hehe
13:10 #navit: < rcorello> so at least my patch is good for something ;)
13:10 #navit: < gernot_> I check this, but if i disable tracking the position has a offset for many kilometers
13:10 #navit: < rcorello> which bugs did you find?
13:11 #navit: < rcorello> gernot_: aha.. if i don't totally misread your dump, then at some point your gps appears to deliver quite inaccurate data
13:11 #navit: < rcorello> gernot_: line 61 seems to indicate this to me
13:12 #navit: < rcorello> gernot_: sorry. 81.
13:14 #navit: < gernot_> yes look so
13:15 -!- epy [~epy@78.195.42.29] has joined #navit
13:15 #navit: < gernot_> Now i check the signal quality, but i think my device send dummy values.
13:15 #navit: < gernot_> for now i see value 3 and 5
13:16 #navit: < gernot_> Also simulate the track.. This takes time...
13:16 #navit: < rcorello> hm. i'm currently experimenting with the vehicle_gpsd stuff as well, because i observed similar issues.
13:17 #navit: < gernot_> verry interesting
13:17 #navit: < gernot_> tomorrow i add a other sample, but i have to leave now
13:17 #navit: < rcorello> if you're interested i'll gladly share my findings
13:18 #navit: < rcorello> sure, see you tomorrow then :)
13:18 #navit: < gernot_> a skip to the other side.
13:19 #navit: < gernot_> You see the problem while using the nmea log as file source for the vehicle.
13:20 #navit: < gernot_> by
13:20 -!- gernot_ [54b56f5c@gateway/web/freenode/ip.84.181.111.92] has quit []
13:24 #navit: < rcorello> alright, time for a test drive. bbl
15:18 #navit: < rcorello> re
15:19 -!- xenos1984 [~xenos1984@95.235.14.239] has quit [Ping timeout: 256 seconds]
15:19 -!- mvglasow [4d046f33@gateway/web/freenode/ip.77.4.111.51] has joined #navit
15:19 #navit: < mvglasow> hi everyone
15:19 #navit: < mvglasow> KaZeR, are you near the keyboard?
15:20 -!- xenos1984 [~xenos1984@95.235.14.239] has joined #navit
15:38 #navit: <@KaZeR> hi mvglasow
15:39 #navit: <@KaZeR> i saw your email yesterday ( but i missed the previous one )
15:39 #navit: <@KaZeR> sorry that i broke the translations
15:44 #navit: <@KaZeR> so, the good way to fix that would be to used branches tags in launchpad. but launchpad does not make it easy
15:47 #navit: < mvglasow> KaZeR, no problem – do we still have to do that branch stuff in Launchpad now that everything's in the main branch?
15:47 #navit: <@KaZeR> no we should not
15:47 #navit: <@KaZeR> so currently the .pot file is pushed to launchpad from circleci
15:48 #navit: <@KaZeR> the .pot in launchpad should match the current pot in the trunk branch
15:48 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has joined #navit
15:48 #navit: <@KaZeR> i hope to be able to figure something to be able to get different pots to be pushed automatically for different branches. the trick is that it need to be a different branch in launchpad
15:56 #navit: < mvglasow> umm... iirc I did update the .pot files when I pushed highfive
15:57 #navit: < mvglasow> ...sorry, I was wrong, that was the .po.in files
15:59 #navit: < mvglasow> KaZeR, where do I fond the .pot file in the source tree?
15:59 #navit: < mvglasow> err, where can I FIND the files...
16:13 #navit: <@KaZeR> mvglasow: the .pot is not versionned in the trunk because it
16:13 #navit: <@KaZeR> 's built as part of the compilation
16:13 #navit: <@KaZeR> but you can find it in the artifacts on circle ci
16:13 #navit: <@KaZeR> here's the latest : https://circle-artifacts.com/gh/navit-gps/navit/326/artifacts/0/tmp/circle-artifacts.c9aquxc/navit.pot
16:14 #navit: < mvglasow> OK, so that file would need to be pushed to Launchpad? do I have permission to do that?
16:16 #navit: <@KaZeR> you should be able to do it, but anyway it should not be necessary : https://circleci.com/gh/navit-gps/navit/326
16:16 #navit: <@KaZeR> in the "Dependencies" block : curl "https://translations.launchpad.net/navit/${CIRCLE_BRANCH}/+translations-upload" -H "$lp_cookie" -H "Referer: https://translations.launchpad.net/navit/${CIRCLE_BRANCH}/+translations-upload" -F file=@bin/po/navit.pot | grep title
16:18 #navit: < mvglasow> which means what? just re-apply my updates to the .po.in files and commit, and the rest will happen automatically? or do we need to do anything else before or after?
16:20 #navit: <@KaZeR> sorry i should have given more details, and we were talking about the pot file. i'll try to explain better how it works today
16:20 #navit: <@KaZeR> the .pot file is uploaded via circleci. it seems to work correctly, but if you spot an issue please let me know
16:21 #navit: <@KaZeR> i would like to avoid using different sources for the .po.in, so all of the translations should be done in launchpad.
16:21 #navit: <@KaZeR> otherwise it's a hell to maintain
16:22 #navit: <@KaZeR> i have a script that can do most of the translation import from launchpad almost automatically. i want to finish it and i should publish it, or even better have it run automatically somewhere
16:22 #navit: <@KaZeR> you can technically import a .po file in launchpad. it would be better than importing that file directly in the trunk
16:23 #navit: <@KaZeR> so you don't need to copy/paste from your fixed .po to launchpad.
16:23 #navit: <@KaZeR> is this helping?
16:23 #navit: < mvglasow> yeah, especially the part about importing .po files sounds good
16:23 #navit: <@KaZeR> ok great
16:24 #navit: < mvglasow> I assume that would also be the way to update the structure of eht .po.in file (order of translations, new translations)?
16:24 #navit: <@KaZeR> update the structure?
16:24 #navit: <@KaZeR> the order does not matter in the po file
16:24 #navit: <@KaZeR> where are you doing most of your code currently? if it's a git branch we can use this branch to fix import from a branch to launchpad, aside from trunk
16:25 #navit: < mvglasow> it's in a git branch which I cloned with git-svn, so I can't easily merge with the "official" git
16:25 #navit: < mvglasow> but if I can import into launchpad, that helps
16:26 #navit: < mvglasow> I'll check the files that got overwritten and hand-merge them
16:26 #navit: < mvglasow> then reimport everything that I touched into launchpad
16:28 #navit: <@KaZeR> i want to help you on this because the point is really to make it easier for everyone. also i'll probably send a poll to everyone who as write access to SVN about switching to git, but i diverge
16:40 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
16:45 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has joined #navit
16:48 #navit: <@KaZeR> mvglasow: is there a specific reason for you to keep these changes in a different fork? because if instead you use a branch in the navit repo it would also make it easier
16:51 #navit: < mvglasow> none apart from historical reasons – it is a git repo I created when the official one was SVN only
16:51 #navit: < mvglasow> I just have to switch over
16:56 #navit: <@KaZeR> ok
16:58 #navit: < mvglasow> thanks for the update – I'll let you know when the new translations are up
16:58 #navit: < mvglasow> bye
17:02 -!- mvglasow [4d046f33@gateway/web/freenode/ip.77.4.111.51] has quit [Quit: Page closed]
17:22 -!- Horwitz [mich1@baldrian.franken.de] has joined #navit
17:22 -!- mode/#navit [+o Horwitz] by ChanServ
17:33 -!- _rd [~rd@p4FD1E6AD.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
17:43 -!- xenos1984 [~xenos1984@95.235.14.239] has quit [Quit: Leaving.]
17:47 -!- epy [~epy@78.195.42.29] has quit [Quit: Quitte]
17:49 #navit: < rcorello> KaZeR: btw. while doing some tests, i also observed another potential problem: after some driving, navit was lagging behind several minutes.
17:50 #navit: < rcorello> the problem may very well be caused by a lack of cpu power on my side. however, i'd have expected navit to just skip to the newest gps information, instead of sequentially follow all past data
17:53 #navit: < rcorello> after reading through vehicle_gpsd.c and the libgpsd source, i think the issue is that vehicle_gpsd.c calls gps_read() once the respective fd has some data available. i believe however that gps_read() will only read one gps update instead of all available updates
17:54 #navit: < rcorello> i'm currently in the process of testing a patch i made for this. are you interested to see it?
18:02 #navit: <@KaZeR> definitely
18:02 #navit: <@KaZeR> rcorello: are you using gpsd ?
18:03 #navit: < rcorello> yes.
18:03 #navit: < rcorello> is that a bad idea?
18:06 #navit: < rcorello> as in: is there any better alternative?
18:12 -!- woglinde [~henning@f053047220.adsl.alicedsl.de] has joined #navit
18:18 #navit: <@KaZeR> it's not a bad idea as it usually works really well
18:18 #navit: <@KaZeR> it's just that i had the exact same issue when testing a pi some times ago
18:18 #navit: <@KaZeR> on a long trip ( several hours ) the gps updates were getting delayed by more than 10 minutes before i notice it ( driving on the highway )
18:19 #navit: <@KaZeR> if you look at the load on your pi it should be >1, for this little device when this happens you're in trouble for real time stuffs :)
18:19 #navit: < rcorello> ha! that's pretty much what i experienced.
18:20 #navit: <@KaZeR> a raspi2 should solve this issue for cheap. otherwise you can try to bypass gpsd too
18:20 #navit: <@KaZeR> btw : what's your use case for kodi? is it running all the time ?
18:20 #navit: < rcorello> yeah, my todo-list contains testing the setup on a raspi2
18:21 #navit: < rcorello> but still i feel that navit should at least attempt to handle that case
18:21 #navit: < rcorello> my use case for kodi is simple: mostly listening to music. and yeah, it's running all the time.
18:23 #navit: <@KaZeR> "navit should at least attempt to handle that case" -> avoiding delayed gps updates ?
18:23 #navit: < rcorello> yes
18:23 #navit: <@KaZeR> about kodi : what is your music source? mp3 files ?
18:24 #navit: < rcorello> hm. mp3 and some m4a i believe
18:24 #navit: <@KaZeR> i haven't tested bypassing gpsd, maybe reading directly from the device using navit would solve it. it's worth having a look cause the raspi is a wonderful device for carpc
18:24 #navit: <@KaZeR> ok. what about playing the files directly from navit ?
18:24 #navit: <@KaZeR> robertp ( the guys who was also interested in rotary encoders) was also looking into this
18:27 #navit: < rcorello> well, yeah.. for music that would work. but kodi has such a pretty ui... :)
18:27 #navit: <@KaZeR> it does
18:27 #navit: <@KaZeR> here's a quick example of a very basic music player with gui internal : https://github.com/pgrandin/navit/blob/staging/navit/navit/gui/internal/gui_internal_spotify.c
18:28 #navit: < rcorello> so if you want to look at the stuff i added, it's in the branch "kalman" of my fork on github
18:28 #navit: <@KaZeR> cool i'll definitely do that
18:29 #navit: <@KaZeR> and i intend to start working on a qt5 UI really soon. gui internal is great because it works everywhere, but it has some technical limitations... and we should do better
18:29 #navit: < rcorello> oh, cool!
18:30 #navit: <@KaZeR> any help appreciated :D
18:30 #navit: < rcorello> i'll see what i can do :)
18:37 #navit: <@KaZeR> great
18:37 #navit: <@KaZeR> i see some interesting commits in your branch, e.g. https://github.com/greg42/navit/commit/b5fb027f38ec993c7e8e67195e68214110ee1e22
18:38 #navit: < rcorello> yeah. i've added a bit more than just avoiding delayed updates
18:38 #navit: <@KaZeR> ok. it will make my life easier if you could submit PR per features next time :)
18:39 #navit: <@KaZeR> e.g : the gpsd version
18:39 #navit: < rcorello> oh yeah. sorry about that.
18:42 #navit: <@KaZeR> no worries
18:44 #navit: < rcorello> once i believe that stuff is ready for a PR, i'll do some rebasing first :)
18:48 #navit: < rcorello> alright. time to get some sleep. if you have some time to look at the stuff: comments and thoughts are always welcome :)
18:53 #navit: <@KaZeR> great. thanks!
18:53 #navit: <@KaZeR> and good night
19:37 -!- woglinde [~henning@f053047220.adsl.alicedsl.de] has quit [Ping timeout: 244 seconds]
20:19 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
20:19 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
21:18 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
21:30 -!- KaZeR [~KaZeR@64.201.252.132] has quit [Remote host closed the connection]
21:30 -!- KaZeR [~KaZeR@64.201.252.132] has joined #navit
21:30 -!- mode/#navit [+o KaZeR] by ChanServ
21:35 -!- KaZeR [~KaZeR@64.201.252.132] has quit [Ping timeout: 244 seconds]
--- Log closed Sat Jul 18 00:00:38 2015