INTERACT FORUM

More => Old Versions => Media Jukebox => Topic started by: chrisjj on October 05, 2010, 01:39:39 pm

Title: Failure of library import on SUBST drive
Post by: chrisjj on October 05, 2010, 01:39:39 pm
If I

1) Create new library
2) Import tracks from a SUBST drive
3) Delete tracks  from library
4) Reimport tracks from the SUBST drive

I expect all the tracks to appear ("Ignore files previously deleted from library" is UNcheckmarked) but only some or none do. I have to delete the library before reimport works.

This does not happen on non SUBST drives.

Can anyone suggest a better workaround?
Title: Re: Failure of library import on SUBST drive
Post by: Alex B on October 05, 2010, 01:48:24 pm
MJ and MC do not actually know that a drive is a "SUBST (http://en.wikipedia.org/wiki/Subst)" drive (if you mean a drive letter that has been created with the SUBST command). The operating system exposes a SUBST drive just like a regular drive.

I use virtual drive letters (substituted) for my complete main library on several PCs and I have never noticed any difference in the behavior when compared with the behavior with non-substituted drives.

Probably something else is going on.
Title: Re: Failure of library import on SUBST drive
Post by: chrisjj on October 05, 2010, 02:21:35 pm
Hi Alex

MJ and MC do not actually know that a drive is a "SUBST (http://en.wikipedia.org/wiki/Subst)" drive
Excellent - thanks.

(if you mean a drive letter that has been created with the SUBST command)
(I do.)

The operating system exposes a SUBST drive just like a regular drive.
(I have experienced SUBST drives being not totally equivalent to regular drives e.g. the otherwise excellent FolderSize program does not work on SUBST drives.)

I use virtual drive letters (substituted) for my complete main library on several PCs and I have never noticed any difference in the behavior when compared with the behavior with non-substituted drives.
That's good to know.

Probably something else is going on.
Your best guess?? :)
Title: Re: Failure of library import on SUBST drive
Post by: chrisjj on October 05, 2010, 07:24:05 pm
I use virtual drive letters (substituted) for my complete main library on several PCs and I have never noticed any difference in the behavior when compared with the behavior with non-substituted drives.

Probably something else is going on.
Another difference is the fail case operates on the root level and the success cases on a folder.

What level are your successful virtual drive imports operating on?
Title: Re: Failure of library import on SUBST drive
Post by: Alex B on October 11, 2010, 09:56:35 am
...What level are your successful virtual drive imports operating on?

I noticed your reply in the release thread and browsed to here (I didn't notice your last reply here earlier).

I have never tested the root of a SUBSTed drive. For example, on this PC I have the audio files in T:\Music\[Album Artist]\[Album]\ and MC sees the "T:\Music\" path as X:\. The file paths inside my main library use the X:\[Album Artist]\[Album]\ rule.
Title: Re: Failure of library import on SUBST drive
Post by: chrisjj on October 11, 2010, 10:15:31 am
I have never tested the root of a SUBSTed drive.
Ah... I wonder if Import works on the root of even a regular HD drive? Sadly I have none free to test.
Title: Re: Failure of library import on SUBST drive
Post by: Matt on October 11, 2010, 11:04:19 am
I'm unable to reproduce any problem with SUBST or root drives using Media Center 15.

Perhaps you could try it.
Title: Re: Failure of library import on SUBST drive
Post by: chrisjj on October 11, 2010, 12:39:18 pm
I'm unable to reproduce any problem with SUBST or root drives using Media Center 15.
Thanks. Which build?