Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Butters]

Greetings,

Windows 7
Media Center 24.0.45 (64-bit)

When I do a library restore (File -> Library -> Restore Library...), and choose only the "Restore library and playlists" option, and the source of the restoration .zip file resides on a USB flash drive, the restore works perfectly.

However, when I then ask Windows to eject the USB drive, via the "Safely Remove Hardware and Eject Media" feature, it warns me that the device is in use.
It turns out that the device (the USB drive) is in use by Media Center.

Only after I close Media Center will Windows release/eject the drive.

Is it necessary for Media Center to retain an "in use" relationship with the drive, after the library restore is completed?

Please note that this is not a big deal to work around.  It is just that I do frequent restores, because I own two licences, and I routinely update fields on only computer #1, backup that library, and restore it on computer #2 (resulting in maintaining both computers with identical playlists, tags, etc).

Thank you.

[swiv3d]

Have you tried the eject drive function from within MC > Drives & Devices? Why two licences - a licence is good for about ten computers?

[~OHM~]

or before you restore, copy the file off the flash to your hd...

[Butters]

or before you restore, copy the file off the flash to your hd...

Yes, that work-around is simple enough.

However, I am a believer in correcting issues, rather than working around issues -- for two reasons:

1)
Media Center is holding on to a file, unnecessarily so.  This indicates that something is wrong.  How wrong?  Perhaps it does not go beyond releasing the file.  Or perhaps the restore is incomplete, in some way, resulting in it not releasing the file?

2)
Even simple work-arounds eventually become a nuisance.  If no one ever fixes the low hanging fruit, eventually you end up spending more than a few seconds each day ducking, side-stepping, skipping and jumping over, around, and under countless work-arounds.

If it involves a rewrite of their library tool, well, then I would understand them leaving it as is.  On the other hand, if it involves adding a single line of code to their next release, then that is what they should do -- and I suspect that they can spot the issue in a few seconds.

Media Center developers should take a look to see if a simple fix can be applied.

[Butters]

Have you tried the eject drive function from within MC > Drives & Devices? Why two licences - a licence is good for about ten computers?

Crap.  I did not realize that I needn't purchase a second license.  :-(

[RoderickGI]

1)
Media Center is holding on to a file, unnecessarily so.  This indicates that someone is wrong.  How wrong?  Perhaps it does not go beyond releasing the file.  Or perhaps the restore is incomplete, in some way, resulting in it not releasing the file?

MC holds on to files longer than it should in many situations. It is causing me issues with TV recordings at the moment. The issue is certainly on JRiver's radar, and some work has been done to fix it for recordings. But the underlying problem seems to be fundamental to the program, so it may not be as easy to fix as one line of code.

Of course, it doesn't hurt to keep reporting such issues. Eventually, the cause may be found and fixed.

[Butters]

MC holds on to files longer than it should in many situations. It is causing me issues with TV recordings at the moment. The issue is certainly on JRiver's radar, and some work has been done to fix it for recordings. But the underlying problem seems to be fundamental to the program, so it may not be as easy to fix as one line of code.

Of course, it doesn't hurt to keep reporting such issues. Eventually, the cause may be found and fixed.

Good to know that this is on someone's to-do list.

Thank you.