GPU-Z sensor log file using two CR-LF per record?

[Hawkwind]

Just updated and like many prev versions, GPU-Z sensor log file is using two CR-LF at the end of each record. (viewed via hex editor it's: 0D0A0D0A) Is there a reason for this? (if it matters, Windows 7 64bit, GPU-Z.0.6.2.exe)

After renaming the file to .csv for example and then opened in Excel, OpenOffice Calc, etc, you get the record then an empty line, then the next record.

This is not a big deal, but unless there is a special reason for the 2nd CR-LF, would be nice if it were only one set of CR-LF instead, which would remove the empty line between all the records.

Thanks

 

[Xaviien]

If anyone else has this issue (like I did) and can't work out the easy fix (like I couldn't) all you need to do is import or open as CSV, then sort by time. This will move all the empty lines to below the data.

It's so simple, and obvious, that it can be easily overlooked, especially during a 4am mod benchmarking session.

Credit to this page for the answer.

 

[W1zzard]

hmmm

Edit: Looks like my Ultraedit turns 0D 0D 0A into 0D 0A.

 

[Xaviien]

Yeah, I have no idea what that means, but yeah, good thanks.

 

[W1zzard]

i invited you to the gpuz beta thread, check the first post for a build that should no longer write empty lines.

please report back here

 

[Xaviien]

Yep, that's fixed. Thanks very much!