#RACERENDER GEAR MOVIE#
#RACERENDER GEAR 720P#
#RACERENDER GEAR 1080P#
#RACERENDER GEAR ANDROID#

#RACERENDER GEAR ANDROID#

The default 'Internal' storage space is a good reliable place to store data, which is why it is the default, but Android generally does not allow that space to be accessed by other apps or via USB. In order to access the TrackAddict files this way, you'll need to have them on either Android's 'External' or 'SD Card' storage spaces. Some guidance for that is displayed when you go to Share -> USB File Sharing, but I'll elaborate more here. In those cases, you're probably better served by the USB transfer method instead, which should be fast and solidly reliable. That typically indicates that the OBD connection did not succeed, or no columns were selected, prior to the time of that recording.Īs for WiFi transfer, most of those issues tend to be related to device or network conditions, particularly when there's signal congestion, heavy network traffic, or when near the range limit.

I'd need to see the data file to better understand what may have actually happened there. But I'd like to solve data transfer problem first. I may try to run Trackaddict on a Nexus 5, because it does have a slightly faster processor and may solve the OBD problem. Yet I know they are there because I can view the complete session on the Nexus 4.

#RACERENDER GEAR MOVIE#

Where are the Trackaddict data and movie files stored on the Android 4.4.4 Nexus 4 file system? I've spent much time trying to locate them in the standard places and they aren't to be found. I've tried several times now and the result is the same each time. I am monitoring the bandwidth use over WiFi, so I know exactly when the transfer fails and then does produces both a Trackaddict and Racerender failure message. Session 2 WiFi transfer breaks at about 1/2 way through, and it takes about 20-30 minutes to get there. No OBD there either, and when I looked at the raw CSV file the OBD data was zeroed out, no data was actually captured. I WiFi transferred Session 1 to Racerender. There was no OBD data being reported by any of the Trackaddict overlays. OBDLink was enabled and functioning while on the grid, OBD and GPS status in Trackaddict read 'green.' I'd selected only a few OBD parameters: RPM, Relative Throttle, maybe one other.Īfter the event I reviewed both sessions on the Nexus 4. Everything from Google Play runs correctly and without flaw on this platform.įrom a recent event I captured 2 sessions, both approx 20 - 25 minutes in 720p. Trackaddict is on a Nexus 4 with Cyanogenmod 4.4.4. I've WiFi transferred several track videos successfully with no problems. Racerender is running on a Windows 7 machine with 32G RAM and i7. I recently purchased Racerender and obtained current Trackaddict from Google Play, and am having somewhat the same problem. That could be caused by simply not having enough RAM in your system, by other applications and services consuming a large amount of your RAM, or if those aren't the case, then I'd speculate that something unique with the video file and/or system may be causing the operating system's decoder to have runaway RAM use (but we've never actually seen that happen, so it would be very rare). I'd suspect that you're running your system out of RAM and causing it to use virtual memory, which can be extremely slow (especially with laptop hard drives).

#RACERENDER GEAR 720P#

If you're getting 1 hour out of a 4GB file, then it may be 720p rather than 1080p, which may even use less RAM due to the smaller video frames.

#RACERENDER GEAR 1080P#

They will obviously need some amount of system RAM, but to put some numbers to that, I just loaded a 1080p video file that was just over 4GB, and it only increased RaceRender's RAM use by about 150 MB. That's not much information to work off of, and there should be no problem with large video files in RaceRender.

Racerender gear