Harry's GPS Suite Forum

First time user here.

iPhone4s 16GB, Jailbreak on iOS 6x, RoqyBT4, QStarz BT1000 (in 5hz mode)

Using PetrolHead

Had a go at recording video on the drive to work and noted that at no point during the trip was speed recorded.

It traced the "track" properly as I'd defined a new one (though I just realised I'd defined the "start" as "start/finish" accidentally). GPS signal was solid, 4-4.2hz the whole way.

I started and stopped the recording manually and after examining data there's no speed recorded.

Was it maybe that manual recording was not enabled in the settings?

Also, The main reason I wanted this app and paid for it was the ability to do it all on one device (video, timing, and overlay - as I used to use a seperate camera and phone with RaceChrono then overlay later).

An 18min trip to work resulted in a 2.7GB file, but then wouldn't allow me to overlay the data, stating that I needed another 400mb or so of space, despite having around 6.5GB free (and that's AFTER the video was recorded not before). I'm happy to clear the phone after each track session (usually around 20mins), but I'll be left high and dry if I've paid for an app and I can't export a single sessions worth of video.

Further info re the video aspect.

I had to clear out apps, photos and music, and had over 7gb free space total before it would allow me to overlay the 2.7GB file (the end result was 3.3GB). Even 2 times the orignal file + 20% comes in under the 7GB of free space I had. As it's a 16GB iPhone, I'm essentially being forced to not store any photos or music of I want to overlay, or is there a way to do this more easily that I'm missing?

I also note that the system status balloon tips do not contain any data, that is, the balloons are just white empty spaces.

Firstly, a 18 minute lap is not a typical lap length When LapTimer overlays a video it creates another video using space on top of the raw one. So if your original vid is 2.7 GB, you get another 2.7 GB video (because the "lap" is the complete "session" in your case). Now LapTimer stores this video into the Photo library. This transfer is a copy and delete - not a move, so we have another 2.7 GB temporarily... So the 400 MB missing makes sense... Usually you will record an 18 minutes session including e.g. 6 laps 3 minutes each. This will require space for 18 minutes + 3 minutes + 3 minutes temporarily. This scenario will work just fine even for the 16 GB iPhone.

The iPhoto transfer cannot be implemented differently, it is the API iOS offers.

Hope that clarifies and helps for you next tests and track days. For a 16 GB iPhone you may consider using HD instead of FullHD in addition. You can find the setting in LapTimer's Settings.

Harry

It's not a typical lap length, but it's a typical session length.

Regardless of if there's one lap in a 18min session or 6, the data size would be the same wouldn't it? As LT records the whole session (video and data) until asked to stop. Or does it only record a single lap of video? OR are you saying that when doing overlay you'd normally only do overlay for a particular lap in a given session and not the whole session?

Either way, It was a 2.7GB file, if it needed another 2.7GB, and I had almost 7GB available, why would it not overlay?

Or are you saying, it needs the 2.7GB, plus another 2.7GB to overlay, then it needs ANOTHER 2.7GB to move that file around? That'd be 8.1 in total and was more than I had free.

I guess I need to know what the "right" process is and what to expect. I had HD selected (1280x720), thinking this was a step down from Best Available.

Or is 1280x720 considered full HD on this phone? (4s) The next step down in the list is 640x480.

What about the speedo being 0 and the tool tips being blank?

EDIT: I've just confirmed that HD 1280x720 is a step down from top quality and will use that next time as it's more than big enough.

The question remains though, can you explain how the file sizes work, as in, the base file size doubled plus X amount is needed etc.

Also, why no speed or balloon tips.

Also, make it so that corner speed comes up in videos like I've seen on youtube? What sort of POI is that?

DanS13 wrote:It's not a typical lap length, but it's a typical session length.

Regardless of if there's one lap in a 18min session or 6, the data size would be the same wouldn't it? As LT records the whole session (video and data) until asked to stop. Or does it only record a single lap of video? OR are you saying that when doing overlay you'd normally only do overlay for a particular lap in a given session and not the whole session?

Either way, It was a 2.7GB file, if it needed another 2.7GB, and I had almost 7GB available, why would it not overlay?

Or are you saying, it needs the 2.7GB, plus another 2.7GB to overlay, then it needs ANOTHER 2.7GB to move that file around? That'd be 8.1 in total and was more than I had free.

I guess I need to know what the "right" process is and what to expect. I had HD selected (1280x720), thinking this was a step down from Best Available.

Or is 1280x720 considered full HD on this phone? (4s) The next step down in the list is 640x480.

What about the speedo being 0 and the tool tips being blank?

Memory requirements are

raw session video length
+ lap length
+ lap length during copy to photo library
+ some additional space to not run into out of memory situations while processing

So it is a big difference if you have standard laps compared to a full "session" video. To recap: in your case the overall memory requirement

2.7 GB
+ 2.7 GB
+ 2.7 GB (temporary)
+ the named additional space (500MB)

For a "normal lap" with a 18 minute session this would have been

2.7 GB
+ 0.5 GB
+ 0.5 GB
+ named additional space

So you can see full video overlay require significantly more space. LapTimer currently supports lap overlay by the way, not session overlays.

Reducing resolution to 720 (HD) is the right step and exactly what I proposed for a iPhone 4S. Nevertheless, for a 16GB iPhone things get tight fast. That's the reason I recommend 32 GB or 64 GB version in case you plan to video record (check the www.gps-laptimer.de/Compatibility.html recommendations). With a 16 GB iPhone you need to take care...

On the missing speed and bubbles: both are no known issues and may depend on your configuration. For the speed, please check the whole thing without the QStarz and roqyBT and use the internal GPS instead. In case the speed appears, you know where the problem is. On the missing bubbles: I cannot reproduce that behavior. Pressing any of the question marks brings up a little text for my iPhone (configured in English). Please let me know for which item this happens. I have no iOS6 device around currently, that, or the jailbreak may cause the issue too.

- Harry

P.S. The min / max speed inserts are derived from the actual speed minima and maxima. They are no POIs but get generated in positions these local maxima happen. As you are currently missing speed, no min / max values are shown.
P.P.S. Ran the app in a 6.1 simulator, there is indeed a skinning problem (white text on white background). Will be fixed in the next release.

OK that makes sense re the video data.

I'll keep that in mind.

I'll test the internal GPS tomorrow on the way to work and report back.

On the way home, when I drove through the Start gate I'd defined on the map, nothing happened, I was expecting a timer to start?

There was also no speed, but as mentioned I'll test the internal sensor for comparison. Interestingly, on the map screen it was tracking me properly implying functional GPS from the Qstarz.

The map view - as an Apple gadget - will always use the internal GPS.

Harry