In message <556d99e6ffjcgl@xxxxxxxxxxxxxxx>
Jim Lesurf <jcgl@xxxxxxxxxxxxxxx> wrote:
In article <4e30936d55.Alan.Adams@xxxxxxxxxxxxxxxxxxxxxxx>, Alan Adams
<alan@xxxxxxxxxxxxxxxx> wrote:
In message <556d91e060jcgl@xxxxxxxxxxxxxxx> Jim Lesurf
<jcgl@xxxxxxxxxxxxxxx> wrote:
In article <556cac5586jcgl@xxxxxxxxxxxxxxx>, Jim Lesurf
<jcgl@xxxxxxxxxxxxxxx> wrote:
1) When I look in some directories it only shows me *some* of the
subdirectories present. In once case is shows less than half of them.
Whereas Sunfish shows them all. This is in a 'public' (for our home
network) area.
No-one here seems to have experience with the above. But FWIW I raised
the issue on the ROOL forum and a number of people said they had
encountered the same problem. So it looks like there is a problem with
Omni. I'll go on using Sunfish.
The most likely problem is permissions. Sunfish uses the NFS protocol,
while I assume Omni is using SMB. The server ends of these are
significantly different on the Linux end, and may well treat
permissions differently.
The directories all have the same owner and group and set of permissions.
That was the first thing I checked. I used NFS from my Linux boxes for
this. Afraid I'm not clear how SMB would recognise them differently. All
the files and directories involved here were added via FTP from my main
Linux boxes.
Another possibility may be with folder names having unusual characters
in them. One protocol may be able to translate them while the other
cannot.
The filenames are all ones that use the standard alphabet and set of
numbers, plus using an underscore as a 'space'. I use the same filename /
directory naming format for all my audio recordings. So something like:
LP_Brahms_PianoConcertos_Barenboim_Barbirolli_EMI_SLS874
for a directory and something like
Brahms_1stPianoCon_Side1.flac
for a file.
would be typical. I can't see any pattern in the names that would correlate
with if they appear or not.
So I can't rule out the possibility that Omni has a quirky sensitivity to
some complex patterns of characters in names that I've not spotted, but it
seems unlikely.
I'd initially assumed the problem was because I was doing something daft as
a result of not knowing how to use !Omni. But...
Give that others fairly quickly reported similar problems on the forum I
guess this is something others have experienced and have dealt with by not
using Omni! Which seems to be my path to a solution. But it does seem that
there is a problem that may need to be fixed.
Jim
