PIN Error

In the release notes for version 1.01:
* Known issues:
The same PIN may be entered for more than one tune/playlist - the empeg-car will play the first one it finds.

Sorry if I missed the discussion on this. Will the empeg also play the second file too?

DiGNAN

Why don't you try it and let us know the results?

___________
Tony Fabris

Sadly, my empeg is all packed up to ship back to empeg for repair. obviously, that would have been my first step

DiGNAN

Well now that I have my player back (I'm a bit suprised that nobody tested this in the past week), I thought I'd try.

It doesn't work. Kind of wish it did.

The player does play the first one found, but that is the one and only song in the playlist.

For testing I applied the PIN# 99 to Nirvana's "Son of a Gun" and to the Vaselines' "Son of a Gun". Because I bought the Vaselines album after I had loaded the Nirvana album, I suppose it had a larger FID. So it started playing the Nirvana file and doesn't pay attention to the Vaselines one.

I suppose that's fine.

DiGNAN

I'll put something in Emplode v1.1 to check for duplicate PINs. Don't know when the public will see it, though.

Roger - not necessarily speaking for empeg

Actually, I was wishing the opposite. I wish I could have 2 tracks with the same PIN play when that PIN number was searched. So in the example above, a new, temporary playlist would be created with those 2 songs in it.

Bu I understand, you've got to have it one way or the other. Either this way or 1 PIN to a track. That's okay I guess.

DiGNAN

Well, we could do it the other way. I'll talk it over with Mike and Peter, to see which way we think is easier. It'd^H^H^H^H.

I was about to say that we'll still need a facility so that people can check which tracks currently have which PINs associated, so that either way, they're not surprised, but emplode v1.1 already has this facility - you just do a search for items with a PIN set, and they get displayed in a nice list format .



Roger - not necessarily speaking for empeg

I wish I could have 2 tracks with the same PIN play when that PIN number was searched
we could do it the other way. I'll talk it over with Mike and Peter

*Not* the other way around, Peter. It'll defeat the PINs purpose.
Remember that they were invented as alpha keys: 2222 for ABBA, as well as ABCA, etc. Thus PINs cannot assumed to be unique

Henno
mk2 6 nr 6

Remember that they were invented as alpha keys: 2222 for ABBA, as well as ABCA, etc. Thus PINs cannot assumed to be unique

Are you sure you're talking about the same thing? The 2222 thing applies to a search by artist, and 2222 get's you ABBA (in most cases, 22 will also probably get it).

And as Roger explained, you won't have to assume that PINs are unique in 1.1, due to this very cool search utility (thanks for the info). And hey, PINs can be unique if you want them to or not-unique if you don't want them to be.

So what's your complaint?

I am eagerly awaiting v1.1 all the more.

DiGNAN

So what's your complaint?

One needs a simple method to assign and remember PINS. Hence there is little opportunity to keep them unique as Roger seemed to suggest
(if I'm not mistaken)

I am eagerly awaiting v1.1 all the more.
Agree. Hey Mike/Rob/Roger; any idea yet when you might release 1.1? How are the alpha tests going ????

Henno
mk2 6 nr 6

How are the alpha tests going ????

You're making the assumption that Empeg's given us something to test...

___________
Tony Fabris

You're making the assumption that Empeg's given us something to test...

Yes, I thought the bare bits were out in the field already. So they're not??

Henno
mk2 6 nr 6

I appologize. I don't seem to understand which method you like. Just to clear it up for my sake, which did you like:

1) One PIN to a song, kept in check by emplode doing something if you assign the same PIN to more than one song.

2) the empeg will play any song with a certain PIN.

Sorry, just trying to sort out my own mind.

DiGNAN

Actually, I was wishing the opposite. I wish I could have 2 tracks with the same PIN play when that PIN number was searched. So in the example above, a new, temporary playlist would be created with those 2 songs in it.

Wouldn't it make sense to just create a playlist with those 2 tracks in it, and then assign a PIN to the playlist (or refer to the playlist by name)? (Can PINs be assigned to playlists in 1.0? I've never used the PINs, but this seems like a natural, logical extension of the functionality they provide for tracks)

I mean, you've got to use Emplode to assign the PINs anyway, and then you have to actually remember them; certainly it would be reasonable to just copy the tracks into a new playlist (like the "mood" playlists Tony's mentioned earlier - as it happens, from what I can tell, his playlist layout and mine are almost identical in methodology) and give that playlist a descriptive name, instead of assigning the same PIN to all the tracks seperately and then having to remember the PIN. Being able to assign a self-chosen PIN to a playlist would just provide an additional shortcut, in this case.


-----
Daniel M. Zimmerman, Caltech Computer Science
Mk.2 #060000058, 36GB
Mk.1 #00101, 10GB

Can PINs be assigned to playlists in 1.0?

Yes -- or at least, if they can't, that's a bug.

I'm inclined to change the PIN behaviour so that all songs with a given PIN get played when that PIN is selected; this is fine for the people who want that, and for those people who want their PINs to be unique, it gives them a quick and simple reminder that they've got a duplicate...

Peter

The alpha team got a really early build of emplode-v1.1 to try a while ago. Unfortunately, I can't release another build until we're ready to preview the player, since the protocol has changed slightly (obviously, we'll be releasing emptool v1.1 at the same time, with source, as normal).

Since we're not ready to preview the new player (there's some licensing issues to be worked out, IIRC), I can't release emplode to the alpha testers.



Roger - not necessarily speaking for empeg

I mean, you've got to use Emplode to assign the PINs anyway, and then you have to actually remember them; certainly it would be reasonable to just copy the tracks into a new playlist

We're investigating doing something much more flexible than that for v1.1 emplode .


Roger - not necessarily speaking for empeg

Greetings!

I hate it when they do that...

Paul G.
Q# 15189
SN# 090000587 (40GB Green)

Wouldn't it make sense to just create a playlist with those 2 tracks in it, and then assign a PIN to the playlist (or refer to the playlist by name)? (Can PINs be assigned to playlists in 1.0? I've never used the PINs, but this seems like a natural, logical extension of the functionality they provide for tracks)

Yeah, I know. I don't know why I thought it would be better, but it still would. As Roger says, that way you would at least know if there were more than one track with the same PIN.

But anyway, I am very excited about the next release.

Just curious, I've always wondered what determines the number of a release. I mean, with all that will go into v1.1, why isn't it called v2? This always puzzled me with AIM, which always has versions like 4.2.2110

What the heck?

DiGNAN