INTERACT FORUM

OK, sorry, I misunderstood.

The other threads about pauses I see there are:

• "Dropped Frames (pauses) with Video"

I don't use JRiver for video.

• "Arcam renderer pauses at end of track"

I'm not using any Arcam anything.

• "Pauses in Video"

See above.

• "Playback Pauses
  A new drive solved it"

My drive is fast and healthy.

And I'm not about to reinstall my entire OS just to see if that gets rid of this. I'm really hoping this is addressed in the next update.

To get another view of what is going on:
Do a binary side-by-side comparison of the contents of the two files.  For example, the program Beyond Compare can easily do this.  BC shows a line-by-line view using its intelligent alignment algorithms which are pretty effective at detecting gaps or large sections of differences.

The file compare allows you to see if file differences are restricted to the header section, the music section, or appear in both.

I sometimes find that two flac files for the same track are different, but the files are the same size!  In my cases, it is always due to a re-writing of the file header with some tags in different positions within the header, while the music sections are binary identical.  Header buffering keeps the file sizes the same.

So not exactly your problem, but you might learn something.  Since you say the audio CRC's are the same, it could be something in the headers like extra buffering, which you raised.  That would be immediately obvious in an intelligent side-by-side comparison.  On the other hand, if it is a bit rate effect, that might show up as differences in the music section.

Not what I meant to convey. The DLNA client, for instance my TV, shows a list of Playlists. I want to filter what Playlists are shown. Right now, it shows all the Playlists that are configured on the Server. The ones I want to show are only in one of the Playlists folders.

Why will the playlist not play? Can you convert the tracks that do not play to another sample rate/format just for just that DLNA zone? You can associate that zone with a specific server that does the dsp changes.

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.