INTERACT FORUM

One notable difference between ET Easy Grey and Easy Grey (1.6) is the contrast between text and background when mouse hovers over an unselected tab.  In both skins the tab changes to whitish text with "light tan" background color.  For ET Easy Grey I find the contrast is very low and the text is barely readable.  Adjusting MC's Skin Effects does not help matters.  The contrast is higher in Easy Grey (1.6) and the background color choice is a little more consistent with the theme.

No criticism, just pointing it out.  Personally I currently use a horizontally striped dual grey-tone scheme for the tab mouseover, and a light grey underline for the selected tab (screenshot attached).  Aside: A low blue dot indicates the tab is locked.  An "i" prefix in the tab name indicates an Image View of the album artwork which is stored in the audio album folders as sidecar files.  I have 5 such Image Views defined in the Tree, each synced (i.e. same sort order) to its corresponding Audio View.

BTW, thanks to all for the discussion and sharing of your history and expertise with this challenging corner of MC.  I must confess to borrowing a couple of ideas. 


5/12/2024:  Updated second paragraph.

Win 11 Pro 64-bit | Win 10 Pro & Home 64-bit | MC 32.0.45 (currently in beta)

Yes, that'll work Bob, I was unclear in my post, I meant 'Media Center command line' using the MC executable not the linux command line.
I still don't think an eject command is particularly useful.
However, an 'eject, remove disc, put it back in the jewel case and return it to the shelf' command, now that I would find useful

Found out where it's failing. Don't know why yet.

Oh! That's great news that at least the source is identified!

I'd like a DLNA Server that will only show certain Playlists. In the Customize View for the DLNA there's no configuration settings for the Playlists Item so there's no way to filter what Playlists are shown. Is there anyway to do this?

Might be related if the block size on file system partitions differ

That was my first thought, too.

674,000 bytes seems too much though.

No one a sollution? 

Check the CRC32 and/or MD5 and/or SHA-256 and/or SHA-512 hashes of both files and see if they're the same.

I have checked MD5, SHA-256 and SHA-512, and the files have different checksums. (I am comparing the "corrupt" copy and a second correct copy, both files now on my Windows 10 computer.)

Might be related if the block size on file system partitions differ

I don't know. The partition formats may be different, but how should this affect one file out of tens of thousands? I copied the files from a Synology NAS to an NTFS drive on my Windows 10 computer. As far as I can tell, this only happened with one file.

Jappie

I spent this morning running MC32 on both my Mac Mini with it's Samsung 24" 1920x1080 Screen and MacBook Air with it's 13" Retina Screen switching between the ET Easy Grey Skin and ModernCards Dark Skin.

The attached link is for a set of Screenies from both Mac PC's mostly with Screen Size set at 100% but some are set to 150% and for 1 of them it was set to 200%.
But there is something you need to know about some of Apples Odd-Behaviour before you look at them.
Regardless of which app is being run there is always a Whitish (Apple) Header Bar at the top of the screen where the App's Menu is placed; however the Windows Control Buttons (Close/Min/Max) are always on the Apps own Header Bar
Apple's Retina system has a dislike for drawing anything (usually images) that is 1 pixel wide or high so if you look very carefully at any of the images where the Details List is visible you should spot the Vertical Gridlines between the Columns are "Absent".
The Apple OS also replaces the header bar on any small/secondary window; like the Tools > Options and DSP Studio Window with a whitish one that has rounded corners and the Apple System windows control buttons instead of the ones from the skin.
There is a small problem in respect of the Segoe UI Font - None of the Segoe font family are shipped with Mac PC's but they can be downloaded and installed. Unfortunately for the OS and MC to be able to use them the PC has to be rebooted.
Mac Pc's have always has had better graphics presentation than that thing IBM developed so there is less tendancy for small/light fonts being discoulered.

Images 1-12 are from the Mac Mini where I was using the Verdana Font some are with Size at 100% others are at 150% and 1 of them is at 200%
Images 3, 4, 8, 9 & 10 are for the ModernCards Dark and reveal a couple of the reasons why it should be sent to the rubbish dump.
Images 7 & 11 show that while the OS hijacks the MC Menu, which means the Drop Down Menus are located just below the Apple Header Bar they are still using the MC Skin and do get resized by the Skin Size Command.
Images 13-15 are from the MacBook Air, where I did install and use the Segeo  UI Font, and as long as the user is no more than 30" from the screen the lower line in the Display Panel is still readable.

So just as with the Win PC once again those images reveal that your skin was thought out, planed and constructed with a lot more thought than that Naff ModernCards Dark Skin; your Contrast Level is far better.

I wish I'd remembered to switch to the ModernCards skin on the MacBook and taken a screenie of it because that would have definitely revealed why I hate the thing.

Incidentally if you are wondering where the Dark Gey background ModernCards uses for the Currently Playing Track and the Selected Option in the DSP Window in images 2, 3, 4, 8, 9 or 10. It appears as 3 very short lines at the left hand side of the line in the images where the Track List is visible and at the right hand edge of the line in the DSP Window.

Link to Images on Pix01 - https://pix01.jriver.com/sM1%40m4ZV 

Might be related if the block size on file system partitions differ

Check the CRC32 and/or MD5 and/or SHA-256 and/or SHA-512 hashes of both files and see if they're the same. You can use apps like HashTab (this is what I personally use) in Windows or even from the command line/PowerShell get the hash of a file.

If the hashes match but both report different file sizes, this could be due to the file system used on the NAS and the file system used on the other drive being different from each other. If the files were just copied and pasted from the NAS to the other drive, it makes no sense bitrate would change. If they're converted/re-encoded, then it could explain it.