Skip to main content

I tried it—it's awesome! few questions

Feature Request

Although it’s still a prototype, it feels like the future is promising. I have a few questions:

  1. Retrace’s file is separate from Rewind, right? I’m worried it might modify or contaminate my original files; I couldn’t find the Retrace folder.

  2. If both are recording at the same time, how does Retrace handle overlapping parts?

  3. If I don’t use Retrace to record and instead treat it as a Rewind viewer, how will Retrace handle the videos that Rewind renders and adds in real time?

Posted by yjcaaaaaaaa ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • haseab@retrace.to

    Team•

    Jan 27

    Thanks so much! Excited to drop the next version, it is SIGNIFICANTLY better

    1. Correct — it is completely separate. Good news: It will not modify or contaminate any of your files. I designed it so that this touches nothing in your rewind database. I made it so that it only READS, and never writes to the rewind database.

    2. Great question! I do not fetch any Rewind data after their cutoff date on Dec 20 2025. That way there is no overlap.

    3. If you want to use Retrace as the viewer and Rewind as the recorder, I would need to remove the cutoff date of Dec 20 2025 and it will query it normally.

    For #3: you might want to do this because of rewinds compression and lower storage, but Retrace (in the new version) is just shy of Rewinds compression levels (about 14-28 GB per month). And it’s only been a couple of weeks. I’m going to further optimize it in the coming weeks.

    Retrace will also provide better data handling and exporting so you won’t have to worry about storage issues with this app :)