Jamcast

Hi GD,

No, no known compatibility issues with dBPowerAMP and if Jamcast picks up one tune it should get them all.

If you were ripping while Jamcast was running, this might be an issue with realtime library synchronization, in which case a restart of the Jamcast service should take care of the problem. Sometimes change detection (new files) doesn't quite work write if Jamcast thinks the file is ready to import and there's still a write lock on the file, for example.

Does the track count appear correct on corresponding folder on the Shares tab? In this case, the files might be shared but tagged/imported incorrectly and therefore difficult to find. You might find them easier via Browse Filesystem.

Finally, if you can post your importlog.txt to http://pastebin.org and share the link here; any import errors or errors with realtime sync should be reported in there. I'm happy to take a look for you.

Look forward to hearing back from you.

Thanks!

Hi George,

So at this point you've got all tracks accounted for in Jamcast?

Definitely sounds like a realtime monitoring-related thing -- depending on how the ripping application interacts with the filesystem (how and when it writes, closes the file, etc.) it can be difficult to know exactly when a track is ready for import, and if Jamcast is wrong the file will be locked and unreadable.

I'll try ripping with dbPowerAMP myself and see if there's anything that makes sense to change to make this smoother. In the interim, after you do some ripping you can restart the Jamcast service to force a startup scan of your tracks so they import.

Thanks!