Skip to main content

Topic: foo_onewaysync (Read 29594 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • lvqcl
  • [*][*][*][*][*]
  • Developer
Re: foo_onewaysync
Reply #200
Are there any known conflicts or am I doing something wrong??  It looks like an excellent tool & I'd love to be asble to use it.  Thanks in advance for any help or suggestions.

Error code 3221225501 = 0xC000001D = illegal instruction.
Probably this component was built with SSE2 instructions enabled, and your CPU doesn't support them.

  • 2sevens
  • [*]
Re: foo_onewaysync
Reply #201
Thanks for letting me know.  That old CPU is certainly creaking with age now.  Maybe time to retire it.

Appreciate you taking the trouble to help :)

  • zimjo
  • [*][*][*]
  • Developer
Re: foo_onewaysync
Reply #202
Error code 3221225501 = 0xC000001D = illegal instruction.
Probably this component was built with SSE2 instructions enabled, and your CPU doesn't support them.
Possible, but I just double checked, there are no such optimizations. In principle, it should run fine on WinXP. Asking google shows that sometimes also bad drivers or a messed up windows installation can result in this error. My suggestion is to try with a clean windows install.

  • kode54
  • [*][*][*][*][*]
  • Administrator
Re: foo_onewaysync
Reply #203
If you are building with MSVC 2013 or newer, SSE2 optimizations are enabled by default, and must be explicitly disabled.

  • zimjo
  • [*][*][*]
  • Developer
Re: foo_onewaysync
Reply #204
The component is built with MSVC 2012.

  • zimjo
  • [*][*][*]
  • Developer
Re: foo_onewaysync
Reply #205
It is assured that generation of the PCM file is finished before the conversion command is executed.
The component does not make any distinction between different encoders. It simply executes the commands that you see printed to the console. So, if it works with lame, qaac must have some special requirements.
The latest version 0.6.1 has a workaround for this issue.

  • dawolman
  • [*]
Re: foo_onewaysync
Reply #206
It is assured that generation of the PCM file is finished before the conversion command is executed.
The component does not make any distinction between different encoders. It simply executes the commands that you see printed to the console. So, if it works with lame, qaac must have some special requirements.
The latest version 0.6.1 has a workaround for this issue.


Thank you! Everything is working great now.

I really appreciate the hard work you have put in to developing the plugin. Keep up the good work!

  • lvqcl
  • [*][*][*][*][*]
  • Developer
Re: foo_onewaysync
Reply #207
If you are building with MSVC 2013 or newer, SSE2 optimizations are enabled by default, and must be explicitly disabled.
AFAIK it was MSVC 2012.

  • zimjo
  • [*][*][*]
  • Developer
Re: foo_onewaysync
Reply #208
Thanks for letting me know.  That old CPU is certainly creaking with age now.  Maybe time to retire it.
Here is a special build for you to test.

  • jmaeshawn
  • [*]
Re: foo_onewaysync
Reply #209
Hi again,
I really thank you again for how you made it work with qaac after I pointed it out a while back.

This time, I wanted to ask about something different. I know that individual songs can be synced by right clicking on them and choosing File Operations>One Way Sync> Last Used.
But is there a function for dynamically choosing which playlists to sync other than choosing them each time in the "tasks" preference page?

The reason I'm asking is because I'm trying to make two buttons on my foobar2000 skin for "Sync All Playlists" and "Sync Current (Active) Playlist", which is when I realized that the fb.RunContextCommand used for buttons only accepts functions in the context menu. That menu currently only shows File>One Way Sync>(NameofDevice).

This is when I realized that it would be helpful if expanded context menu options could be added as such:
File>One Way Sync>(NameofDevice)>Sync All Playlists
File>One Way Sync>(NameofDevice)>Sync Current Playlist
File>One Way Sync>(NameofDevice)>Sync Selected Playlists
In which the first two would do as stated, and the "Sync Selected Playlists" would run the current method of only syncing the playlists that were pre-selected in the tasks page.

Would it be possible for you to add these options in a future version, or is there already an option for these in One Way Sync somewhere that I am just overlooking?

  • zimjo
  • [*][*][*]
  • Developer
Re: foo_onewaysync
Reply #210
From what you write, it seems you are talking about the main menu. Anyways, that would be the proper place for such a command. In principle, this can be done and I might look into it.

  • belidzs
  • [*]
Re: foo_onewaysync
Reply #211
First of all, big thanks to the dev who donates his time to develop this plugin for the community.

I decided to give this plugin a try after I finally abandoned m-TAGS which was incompatible with most of the synchronization/conversion plugins out there.

Unfortunately even though I didn't configure anything fancy I experienced that OWS modifies some of my source files. By the time I realized this, many of my files have been changed and had to be restored from backup. Checking a few of them revealed that mostly the image tag has been changed, but some files also had changes in the middle of them (according to KDiff3)

Considering the circumstances I'm unable to currently make use of this plugin, however I'm glad if I can help tracing down this problem, so maybe it can be fixed.

Please let me know which files are needed to replicate the issue.

  • zimjo
  • [*][*][*]
  • Developer
Re: foo_onewaysync
Reply #212
Make sure to uncheck the options 'One Way Sync->Store path to lossy file in tags', 'One Way Sync/Devices->Always embed cover art', and maybe also 'One Way Sync/Devices->Copy cover art'. Then source files should no longer become modified. In any case, OWS only alters meta information, i.e. in the tags/embedded cover art, not in the music.

  • belidzs
  • [*]
Re: foo_onewaysync
Reply #213
Make sure to uncheck the options 'One Way Sync->Store path to lossy file in tags', 'One Way Sync/Devices->Always embed cover art', and maybe also 'One Way Sync/Devices->Copy cover art'. Then source files should no longer become modified. In any case, OWS only alters meta information, i.e. in the tags/embedded cover art, not in the music.

Thanks for the tip, this solves my issue! To be honest I didn't expect a plugin called One Way Sync to touch any of the source files. I thought all of these alterations will only take place in the destination files. Even if it's only the metadata, any modification can cause problems if the source files are hashed for some reason (for instance because they are shared by a torrent client).

Just out of curiosity why did you decide to go this way?

ps: I think a warning message would be nice when user selects one of these options

  • zimjo
  • [*][*][*]
  • Developer
Re: foo_onewaysync
Reply #214
Just out of curiosity why did you decide to go this way?
'One Way Sync/Devices->Always embed cover art'
It would be very slow (USB sticks etc.) or even impossible (MTP devices) to modify the file at the destination. Creating a temporary copy would be slower as well.

'One Way Sync->Store path to lossy file in tags'
When conversion speed is low, it makes sense to store the converted file at the path of the lossless source. Then, if the user decides to move the lossless source file to another path, the converted file can no longer be found by OWS. Storing the path as a tag resolves this problem.