You helped fix an issue I was having once before, but now I am having a different issue, and I have no idea what is causing this,
Basically, what happens is this:
I want to sync a playlist with 97 songs in it, and have onewaysync start doing so. It begins converting the files and I can see them in the windows %temp% directory as
OWS1CA8.tmp.m4a
OWS1CD8.tmp.m4a
OWS1D27.tmp.m4a
OWS2DB6.tmp.m4a
OWS2DE6.tmp.m4a
OWS2E54.tmp.m4a
OWS3ACC.tmp.m4a
...
etc.
However, the strange thing is that about halfway into the sync, many of the .tmp.m4a files in the windows temp directory begin disappearing, before all of the songs have even been converted,
Therefore, only 36 of the 97 songs get synced, with the rest generating the following errors in two different error windows:
Could not load info (Object not found) from:
"C:\Users\Jmaeshawn\AppData\Local\Temp\OWS1CA8.tmp.m4a"
Could not load info (Object not found) from:
"C:\Users\Jmaeshawn\AppData\Local\Temp\OWS1CD8.tmp.m4a"
Could not load info (Object not found) from:
"C:\Users\Jmaeshawn\AppData\Local\Temp\OWS1D27.tmp.m4a"
Could not load info (Object not found) from:
"C:\Users\Jmaeshawn\AppData\Local\Temp\OWS2130.tmp.m4a"
...
etc
and
Could not update tags (Object not found) on:
"C:\Users\Jmaeshawn\AppData\Local\Temp\OWS1CA8.tmp.m4a"
Could not update tags (Object not found) on:
"C:\Users\Jmaeshawn\AppData\Local\Temp\OWS1CD8.tmp.m4a"
Could not update tags (Object not found) on:
"C:\Users\Jmaeshawn\AppData\Local\Temp\OWS1D27.tmp.m4a"
Could not update tags (Object not found) on:
"C:\Users\Jmaeshawn\AppData\Local\Temp\OWS2130.tmp.m4a"
...
etc
I also tried a test sync using the mp3 conversion that is default with onewaysync, but have the same issues with it.
I'm guessing these errors are caused by the files that are in the %temp% directory disappearing before onewaysync has finished processing them, but do you know why this is happening now, even though it was working just fine before?
The only thing that's changed since the last time I synced is that there was a windows update that updated me to the latest Windows 10 build (I'm now on "Version 1803 OS Build 17134.228").
Would the Windows update cause this problem with onewaysync to suddenly arise, somehow? I updated the component to the latest 0.6.3a build just to see if it was some sort of compatibility issue between the new windows version and the previous version of onewaysync that I was using, but the problem remained.
Please help me with this. Thank you in advance.