This is one of the reasons to get 2.0 out of the way - so we can move on to 3.0 and the all new all singing all dancing audio filter network. It should never glitch, short of hitting the player with a sledge hammer.

Rob

I would prefer that it left the singing to the recording artists. Feel free to let the Flancedoor people continue dancing, though.

Feel free to let the Flancedoor people continue dancing, though.

And hopefully in a future release, dancing in sync with the beat of the songs, as has been suggested in the past.

I'd vote, but I hadn't noticed *any* of those bugs.

I'd vote, but I hadn't noticed *any* of those bugs.

Me neitha! Sniff!

When I insert a song with jemplode I do get a stutter, which I assume is close enough to the visuals glitch that I voted for that one. Honestly, none on the list seemed to be any that I had.

You can vote for the one that sounds hardest to fix.

Voting is now closed, and the results are:

Emplode: emplode consumes 100% CPU during download/synchronise
28 (26%)
Roger Lipscombe

Emplode: USB connection under Win XP
19 (18%)
Mike Crowe

Player: RDS AF should scan and re-tune in the background
17 (16%)
Toby Duckworth

Player: Volume Ramp doesn't work after power fail
12 (11%)
Toby Duckworth

Player: Need a "button code" for "Prev Visual"
8 (07%)
Toby Duckworth

Player: No pause icon after reboot
7 (06%)
Peter Hartley

Player: Distortion in EQ with certain settings
6 (05%)
John Graley

Player: Settings not retained between menu invocations
3 (02%)
John Graley

Player: Player screen flickers when inserting/enqueing tracks from emplode
3 (02%)
Mike Crowe

Emplode: Plays MP3 hyperlink is broken
1 (00%)
Roger Lipscombe

Player: Clock visual still truncated in 2.0b11
1 (00%)
Toby Duckworth

Congratulations Roger, you get a bottle of wine for your services to synchronisation.

Rob

I'd vote, but I hadn't noticed *any* of those bugs.

Me neitha! Sniff!

really? you've never noticed a missing pause icon on reboot, or that the volume ramp was jerky at best in the car? not exactly earth-shaking bugs, but it's hard to imagine missing them if you use your player much.

--dan.

I feel for Toby - beaten by the British "First past the post" voting system...

I use mine every day in the car to and from work and at home in the evening and have never noticed a missing pause icon - I guess I never turn the empeg off when paused.


And I never thought of the volume step as a bug, it gives me enough time to kill it if it is going to be too loud, or it just launches as I get out of my driveway, thus making the loud pedal work better

The voting seems rather unfair to me. I understand the contest rules. If however, you look at the number of votes per bug fixer rather than per bug, Toby Duckworth should have won. Will you consider at least a beer or a really cheap bottle of wine for him?

Duckworth should demand a recount.

Yeah, besides, who uses Emplode?

The only think that causes me any problems, is the sony stalk interface. I get quite a long delay sometimes when using it. It seems to be ok when im using the tuner (although i havnt used it much so cant confirm that). Also seems to do it whether i have HiJack installed or not.

Do many other people have this problem?

Yep, can confirm that problem.
I use the Stalk interface almost exclusively and its a bit erratic at times in terms of responding to my requests, sometimes its really fast and others really slow/misses button preses.


.

I have leanred to live with the button response delay since getting my tuner.

If this is a software issue, then its the #1 bug for me.

I have a feeling its a hardware / signal translation issue, but I have absolutley no evidence to support this theory

long delay between what and what? pressing a button and having the event acted on?

the stalk interface plugs into the tuner, right? perhaps the data being passed when you're in tuner mode from the tuner to the empeg has to flush or something before events from the stalk get flushed, and that's what you're waiting for?

In reply to:

---

long delay between what and what? pressing a button and having the event acted on?

---

Yep, thats it in a nutshell, happens in player mode almost exclusively - when I'm in tuner mode the buttons work fine I think.

And thats whether you're on AM or FM band.
I use AM occasionally when the cricket is one as thats the band they broadcast on - and also where the BBC World Service Radio is, otherwise its moslly FM.

The buttons I use most are next and prev track (inner ring on Stalk), and I skip through songs I don't like.

I have considered the possibility that the empeg is trying to cache the new song you just skipped to - but the buttons seem to run slow even when the song you're playing is well and truly cached from disk as you've been listening to it for half its length without touching any buttons.
[and I have the disk icon active on my player so I know when its accessing the disk and when its not].

I also considered that the stalk buttons may be wearing out or something, but I find that other buttons go slow too [like mute] which I use once or twice a day (max), the "source switching" button (on the end of the stalk) hardly gets used either and its also slow, so I doubt its the particular mechanism wearing out in the stalk and getting sloppy or not switching properly.

I do notice that it tends to be most erratic when the car is warm - so maybe the temperature is making the resistors go "off value" more than is expected, thus causing the tuner to read the wrong resistor values - this would however result in the odd "wrong button" - and that happens very rarely in my case.
But we are not talking major heat here - player says 30-45 degrees C and my car is air conditioned so if the stalk was getting to hot, the cold air from the vent would cool it down within minutes and make it work "better" - but I don't see that either.

The whole stalk control feels sluggish sometimes, and not at other times.

When you use the front panel buttons they respond pretty quickly so its something to do with stalk processing.

I run Hijack on 2.0B13 - with no IR mappings and my Hijack is fairly recent (about 4 behind the current I think).

I think it was better on 2.0B7.

Im pretty sure its a software issue. I remember when i first got my tuner (as soon as it was released). I cant remember which version of the software i was running but it worked perfectly for quite a while.

>Player: RDS AF should scan and re-tune in the background
>17 (16%)
>Toby Duckworth

Toby you're my hero!

The voting seems rather unfair to me. I understand the contest rules. If however, you look at the number of votes per bug fixer rather than per bug, Toby Duckworth should have won.

He'll get over it.

Rob

Not often we see the cold, heartless, managerial side of Rob's personality...

What´s the contact info for your favorite pub again? I might want to sent some money over for a pint or two (who might be receiving it/those is up to me exclusively, of course).

cu,
sven.

Try This Link for "The Wrestlers" Pub
(where the Empeg chaps seem to practise their product design,drinking and curry eating sessions).

I vote for fixing the seek tool pointer on tracks more than 4hr 39 min. Here.

"The Wrestlers" Pub

No Shepherd Neames: God's own beer, not my idea of a pub!

Oh no! Now I want a curry because of you!

- Trevor