SinDromX

Members
  • Content Count

    7
  • Joined

  • Last visited

About SinDromX

  • Rank
    New User
  1. It would be great to be able to change this setting in the options. In my case, I don't need to keep archives on my android device, not even for 1 day. I transfer mainly video files, my storage keeps running low and I have to manually delete the files several times per week.
  2. +1: Improve the UI and add tooltips when a long message is displayed bu the column size is not sufficient to show it (as column resizing doesn't work on Firefox)
  3. Yep, the user is the same. Well, I have no idea how but I finally managed to get it syncing :-)
  4. I do have the exact same issue on a Synology NAS since upgrading the btsync package to 1.3.94. My client computer is running 1.3.94 too. I can't manage to downgradre or upgrade the package on the Synology NAS. Right now, there's no more sync between my NAS and the client computer (Win 7).
  5. Thank you piotrnik. I now understand why it didn't work, let me explain: Basically, I'm testing with a linux box and a windows seven pc both running btsync 1.3.93. I've generated a random file on the Linux box and let btsync do it thing to obtain the same file on both machines. Adding/removing data anywhere in the file triggers a transfer from the added/removed chunk to the end of the fileReplacing data anywhere in the file (not adding/removing but replacing data bit by bit) triggers transfering only small parts (the replaced data + probably some chunks around)At first, I was adding data at the very beginning of the file, so the whole file was transfered. When adding a few bits at the end of the file or replacing a few bits in the file, only a fraction of the file is transfered (the smallest possible chunk seems to be 32kB). So yeah, btsync definitely does delta transfer, and the chunk size is a multiple of 32kBytes. Just keep in mind that the chunks are calculated from the beginning of the file, so when adding at the beginning, each chunk of the source will be different from the destination file, so a full file transfer will be triggered. Same with adding data somewhere in the file, the first chunks will be the same, but the chunk containing your added data and all the following ones will be different, meaning possibily a big transfer depending where you change your data. Replacing data in the file is ok since only the modified chunks will be transfered. Adding data at the end of the file is also ok since only the new chunks will be transfered.
  6. Thank you GreatMarko . So according to this, files greater than 4 MB with be chunked in smaller parts and only the different chunks will be transfered. But my tests proves me that this is not working :-( Anyone has a feedback on this? Or call. Anyone test it? Maybe my setup is incorrect and prevents delta from working, or my test protocol is biased.
  7. Hi, I know the feature wasn't available around a year ago, has it changed? I've ran some tests on my current setup, changing only 1 bit of a file triggers syncing of the whole file. I'd love to see only a small portion of my file beeing transfered over.