Software: Emplode Beta11
Hardware: Mark II empeg 60gigs so to be 120gigs
OS: Windows XP latest update
----------------------------------------

Hello Readers
I am using the Emplode Pin system as a way to index my +1600 cd I have in my CD collection. when I entered in some of the pin numbers that I have choosen it does not keep the value enter. I have entered in about 100 thus far and now when I go to enter more it gives me a bogus number after I press "apply" or "ok".

My Pin number system goes like this

I have choosen a 7 digit Pin number system xxx xxxx
One of my playlist is as follows
Artist -> [ABCD] -> all of the Artist with names from A - D follows

So under each Artist I may have several CDs from that Artist
So lets use the Artist "Cameo" and it will have a Pin # of 3 digits ex: 123
If a user enters in "123" and press ok on the remote they will get to listen to all of Cameo (5 CDs). very "Quick" and to the point...

The other 4 digits work like this:
The next 2 digits indicate which album of the artist Cameo you want to play (1-5)

The last 2 digits equal which track of that CD you wish to hear. I choose to use the Pin number system because I have +1600 CDs and it's hard for me to tell my riders everything I have on my player So with a CD listing in the car a user and look thru it and choose to hear all of an artist or just a certain song.


But right now it looks like the Pin Number system is broken in Emplode or am I doing something wrong. Also what is the biggest number I can put in the Pin numbers is 7 digits okay or to much.


So now my riders are stuck listening to what I want to hear or choosing to watch a DVD or TV tuner while going to Vegas.

Please Help...

Ernest

So now my riders are stuck listening to what I want to hear or choosing to watch a DVD or TV tuner while going to Vegas.

And using the other perfectly-good ways to locate music on the player aren't available to your riders?

Not to say that there's not a bug or anything. I mean, I never use PINs, so I wouldn't know if it had gotten broken in a recent release.

My only question is: If you downgrade to 1.03, do the PINs start working again?

Or, more accurately, when did you notice that they stopped working?

I don't know how many digits they are limited to, but if you think there is a limit to the digits, you can do some experimenting to find out where that limit is.

The other ways are okay Tony but they have to learn how to work the player and then they have to enter in the searches if you have a Pin number of "3" "5" "7" digits it much faster. And they don't have to bother me while I'm driving "fast" and watching for Troopers.

I have not tried ver 1.03... is that what we do when something does not work, That's fine... I did not know if this Pin number problem was reported or not so that's why I have not tried ver 1.03. Is there a bug list someplace so this way I know how to go about troubleshooting a problem that's not in the bug list.

I noticed the problem when I went into add more Pin numbers and the numbers would change after I entered them I would say I have about 100 pins entered thus far and I can not add any more without the number changing to another random number

I thing the software programmer should know how many digits the Pin number can hold. The Pin number variable could be cast as a double,int,etc so to find how many digits is just a question for the software programmer.

emplode/player do not appear to have a fundamental problem with long PINs, I have just added a PIN of "11111111" to a tune and it worked fine. So the problem must be more subtle than just long numbers.

Emplode by the way, limits you to eight digits in the PIN (whereas the player lets you enter up to nine).

I have not tried ver 1.03... is that what we do when something does not work, That's fine...

Well, more specifically:

If you are running BETA software, and you have a problem, see if the NON-BETA version exhibits the same bug.

Often comparing the stable version to the beta version can reveal important things about the behavior of the software. It also sometimes helps to be able to tell the deveopers "this problem started happening when I installed the beta, and it didn't happen in the last non-beta release", that way they can more easily track down the code that caused the problem.

If the bug also happens in 1.03, the bug should still be reported, though.

Once you have decided whether or not the bug happens in 1.03, then you can make a choice yourself whether you want to give up the new features in the beta in favor of the stability of the old version. That's your call.

Where do you go to get ver 1.03...

http://www.empeg.com/cgi-bin/display.cgi?section=downloads&id=3

Thanks....

I tried to enter the Pin numbers into the Mark II with ver 1.03 and Emplode 1.03 and it works with no problem.

Will I have a problem with ver 2.11B if I was to go back to that beta with all of the info that I have entered using Ver 1.03

Can this problem be added tothe bug list

Can this problem be added tothe bug list

Already in there.

I've attempted to reproduce this bug, and can't. Can you confirm whether this is still causing you a problem? There was a major rewrite in this region of the code recently (but I can't remember whether it was pre- or post-beta11).

If not, can you confirm whether there's anything particular about the numbers that are causing you problems? For example, do they have 8's and 9's in them? How many digits (the limit is 8 by the way)?

In reply to:

---

For example, do they have 8's and 9's in them?

---

And do they begin with zero?

Quite.

Can you confirm whether this is still causing you a problem?

Email Ernest about it, I only put it into the bug list because Ernest reported it. I never use the PINs.

I am using Ver 1.03 just like Tony told me to until the bug get's fixed. So If I were to go to the new beta11 again will I lose the pin number data that I have entered using ver 1.03??????

The problems that I had with Beta11 was that I would use a 7 digit number in the pin number playlist section, I would put a 3 digit number in for the artist tree so if you want to listen to all of an artist you enter in a 3 digit number or to a cd tree of that artist you enter in a 5 digit number or a certain song tree off that cd you would enter in a 7 digit number. The problem was that it would not keep that value after I pressed Okay button. I have entered in about 400 or so pins thus far. If you guys tell me that I would not lose the pin numbers that I've entered I will load up the beta and try it again for you this way I can help you guys trouble shot the problem.

What, it wouldn't keep the 7 digit PIN, or the 5 digit, or the 3 digit? Which one? I don't think that the number of PINs that you've entered has anything to do with the problem, so it must be something to do with the PINs themselves. Are you prefixing these with zeroes? Could you include more information about a specific number/numbers that have not worked?

You shouldn't lose the PIN numbers if you go back into emplode. If you don't press the sync button, then you definitely won't.

Also, just to confirm: this occurs when you press OK, and then immediately go back to the dialog box, yes? Rather than having to go through a sync?

Correct, The problem happen before I a Sync is done. I can load up the beta and try again.
This is how I have my playlist

artist
>>>> abcd
>>>> ........
>>>> wxyz

abcd
Barkays (pin# 172) This would allow me to play all of the CD albums of the Barkays

Barkays
CD #1 (pin # 1720100)
CD #2 (pin # 1720200)
CD #3 (pin # 1720300)

When I entered pin numbers in that arrangement it would not stay in the pin number list box after I press OK and then entered into to it again.

Works for me in beta11.

Okay, I'll re-load Beta11 today (3/26/02) and I'll do a screen capture of a before and after to show you the problem.

Just to be certain, make sure to completely de-install the previous version of Emplode before installing the Beta11 version.

Hello Beta Team,

I loaded up the Beta11 and Emplode program and my recent Pins from Ver 1.03 are still there I have not checked them all but only a few.

When I entered a value preceeded by a zero and press the apply button the pin number does not take but if I just enter the pin number and not preceed with a zero the number stays the same after I press apply.

Pin Number ex: 014
enter 014 and press apply it returns a pin number of value "12" if I enter 14 it returns 14 after I press apply.

I will continue to use Beta11 and report any more problems I see with the Pin number, I have finished entering all of my 3 digit pin number that use 0 as the preceeding value.

Ernest

Three things:

1. Your example numbers do not include zero-prefixes. If you'd mentioned that initially, I could have tracked down the problem weeks ago.
2. tms13 specifically mentions leading zeroes, above. No response from you.
3. It'll be fixed in the next release, hopefully .

I apologise if I seem rude, but I think that this just reinforces the fact that one should provide all available information to help track down a problem. Particularly when specifically asked for it.

Pin Number ex: 014
enter 014 and press apply it returns a pin number of value "12" if I enter 14 it returns 14 after I press apply.

That's because 014 is interpreted as an octal based number (14(base8) equals 12(base10))

Wonder if it'd interpret 0xe or 0xE as 14(base10)?

/Michael

Hello Roger,

There is no iindication on this BBS that I had mail waiting for me. I had to hunt around for this thread. Once I found this e-mail from you then and only then did I start to monitor it.

Sorry I did not give you all of the info you needed but I thought I gave a detail description of what was going on with the player and software and did not see any info from tms13 until now.

Sorry.

Ernest

No problem. I apologise if I sounded a bit crabby, but I'd just spent about 2 hours hacking on something without really getting anywhere .