Hello all, I wonder if anyone can help with the odd glitch with my 10G Rio player 30102764 running V2.00-beta11

The player does not 'see' all the tracks that it has. Emplode shows eg. 2400 tracks but the player shows 2000. I certainly don't have 400 tracks doubled up in other directories. Here's what I found when I investigated further:

I deleted quite a few tracks but added lots of new ones today which brought the total my player displayed DOWN to 1980 tracks or there abouts. Then I
searched and played most of the music I loaded which brought the total up to
2046 as it stands now.

Emplode tells me I have 2437 tracks but my player says 2046. I have just searched the player to play a track
Emplode says I haven't played. The player found and is playing the '0 plays' track and has increased it's display to 2047

Now I have done the same with 3 more tracks, inserted them into the playlist
(not played yet but queued up) and it has increased its display to 2050.

Now that it has seen these few tracks it will probably play them next time I shuffle where it had previously not spotted them. Most of my tracks have
been played 9-13 times. Any ideas why it's not seeing 400 tracks which are
defiantely in there? Odd especially as I have 200 unplayed..... I certainly don't have 400 tracks in other playlists either

Next and still currently trying, I sorted all my tracks in Emplode to the order of number of times played and got Emplode to get the player to play all the tracks, in that order, replacing the current playlist with the new one. The player instantly saw all my tracks and is now playing them in my desired order. I am going to let 400 play before shuffling to see if it has remembered them now it's played them all

Any ideas chaps?
Kind regards
Fergus, UK

Note that this was posted here as a suggestion by me in a private email exchange we had. I've already asked him if it was the old "number of tracks changes when I shuffle" thing that's in the FAQ. He's convinced it's not that, so I said he should try it on the BBS to see if anyone else can figure it out.

I had a similar problem, I simply deleted everything from the empeg and then uploaded everything fresh...
That fixed it.
Your 10GB should fill up overnight, my 60 took 2 days.

Thanks, I'm trying that now
I guess it must be a bug of some sort
Does yours 'see' new track you add later?

Cheers

Ferg

I have a similar issue. Emplode lists 9096 tracks and the player lists 8616 only. The funny thing is that it only does so with shuffle on. When I turn shuffle off, it suddenly sees 8709 tracks!
Any ideas?
I'd rather not wipe the disk.

Frank

It's in the FAQ. When playing "All Tracks" from the root, it will play every track in every playlist. Yet, when you activate shuffle, it removes all duplicate tracks (when a track appears in more than one playlist). It's by design.

Where's Tony Fabris been? Does he need a reboot?

Right, Frank, it de-dupes on shuffle, as described here in the FAQ. What you're seeing there is normal behavior.

Edit: re-reading Frank's post I think that he might be seeing the same thing that GooseGog is seeing. Even with shuffle off, his full-player-playlist doesn't show as many tracks as Emplode says he has.

The problem GooseGog is complaining about seems to be a different one. At least in our private e-mail exchange, he seemed convinced that it was something different than what's covered in that FAQ entry.

I have a question for Frank and GooseGog:

Are any of your playlists tagged with the "Ignore as Child" flag? That might produce the behavior you're describing.

I figured it had something to do with duplicate tracks. But that still doesn't explain why I see about 400 tracks too little
Tony, yes as a matter of fact I do have a few 'ignore as child' albums. I'll add them again and see if the problem disappears.

edit: yup, it's the 'ignore as child' tag alright. I just untagged 200 tracks and the player now sees 200 tracks more.
I must have had about 400 'ignore as child' tracks.

Frank

Okay, then...

GooseGog... Do you have any playlists tagged as "Ignore As Child"? That would explain your observed behavior, too.

If this is the problem you are experiencing, then it's "by design". When you press down-down-down on the front panel, it plays the root playlist and all of its sub children, except those tagged "ignore as child", those filtered out by a Wendy, or tracks not existing in playlists. So playing the "entire playlist tree" might not play every song on the player.

Nope, I have no tracks as Ignore as Child

Goose

Playlists, I mean. Do you have any playlists marked as "Ignore as child"?

And it's possible you might have some marked that way even if you didn't deliberately mark them yourself. I don't know if there's an easy way to check this without manually looking at every playlist. So this might be tedious. But it's worth a check just to be sure.

type="playlist" and options=32

...in the advanced search box ought to do it. It won't catch any with "ignore as child" as well as one or more of the other options, though. And advanced search doesn't do bitwise operations yet.

Maybe you want to try type="playlist", then group-select them all, and see if the checkbox is checked or grey (indeterminate) or clear.

type="playlist" and options=32
...
And advanced search doesn't do bitwise operations yet.

Well, how many possible bits are there? Couldn't you do a:

type="playlist" and ( ( options>31 and options<64 ) or ( options>95 and options<128 ) or ( options>159 ) )

Which would match everything where bit 7 was set in an 8-bit wide bitmap, right?

That seemed to work, Bitt.

Interestingly, it revealed that some playlists I was sure that I'd marked as "Ignore as child" were no longer marked that way. Strangely, those playlists haven't had their contents appear in a full-shuffle in a long time, indicating that somehow the player was honoring my original desire to have them I.A.C., but Emplode somehow did not see that they were I.A.C. any more.

I'm confused.

Bitt, I have updated the FAQ entry on advanced searching to use your example. That's rather clever. Thanks.

Well, my example assumes that there are only eight options, which I have no particular reason to believe is the case.

Edit: Nevermind. See Roger's post below.

It's a 32-bit number. We've only defined about 6 bits so far, though, of which only about 3 (from memory) are used in the car player -- some of the others are deprecated, and some are used in the Rio Central (has CDDB been consulted, e.g.).

And your example is quite twisted. Maybe when I've sobered up a little, I'll work out what it does .

Any idea why playlists that had previously been marked as I.A.C. in previous versions of Emplode now suddenly appear as not marked in newer versions of Emplode? Yet the player still seems to honor that I wanted them I.A.C.?

Nope.

Okay, here are the options from the emptool source:

         Option                    Hex            Binary          Decimal

PLAYLIST_OPTION_ASONE             0x002    0000 0000  0000 0010      2

PLAYLIST_OPTION_NOGAPS            0x004    0000 0000  0000 0100      4

PLAYLIST_OPTION_RANDOMISE         0x008    0000 0000  0000 1000      8

PLAYLIST_OPTION_LOOP              0x010    0000 0000  0001 0000     16

PLAYLIST_OPTION_IGNOREASCHILD     0x020    0000 0000  0010 0000     32

PLAYLIST_OPTION_CDINFO_RESOLVED   0x040    0000 0000  0100 0000     64

PLAYLIST_OPTION_COPYRIGHT         0x080    0000 0000  1000 0000    128

PLAYLIST_OPTION_COPY              0x100    0000 0001  0000 0000    256

PLAYLIST_OPTION_STEREO_BLEED      0x200    0000 0010  0000 0000    512

The two listed in red are marked as unsupported in the source code, and are actually commented out, and the next three would seem to be the only ones relevant to the empeg.

Edit: Wait -- we have the stereo bleed, too, don't we?