V3 alpha bugs
Posted by: Daria
V3 alpha bugs - 25/09/2003 13:30
Perhaps we can collect a list of issues we find here, now that we have something to play with?
Not so much as a list of stuff to bug the busy people about, but so we know amongst ourselves what to expect.
Looks like crossfade also happens when you ffwd over a track, don't know if that's intentional or not. There was another I noticed, I'll haave to remember now what it was. Sigh.
Posted by: tonyc
Re: V3 alpha bugs - 25/09/2003 13:55
Maybe before we go crazy, one of the original alpha peeps could dump a list of the already well-known bugs...
Posted by: robricc
Re: V3 alpha bugs - 25/09/2003 14:10
- Uploading with emplode 2.00-final often results in early termination causing a messed-up database (for me at least).
- Emplode provided with v3a3 is unstable.
- Crossfade kicks ass
- The player usually stops responding after playing a short (5-10 second) track when crossfade is enabled. (not tested without crossfade enabled)
- Reversing (possibly fast forward or both) past a track boundry crashes the player (I think).
- Crossfade rules
- Hard drives seem to not spin-down after the ignition is cut. It is possible the hard drives are always spun-up.
- Hitting fast forward quickly through 5-10 tracks will cause the player to stop playing.
I think those are pretty accurate.
Posted by: mtempsch
Re: V3 alpha bugs - 25/09/2003 14:13
Low bitrate files tend to stop playback (player will still take commands, but no output): step to another track and reboot.
/Michael
Posted by: Daria
Re: V3 alpha bugs - 25/09/2003 17:11
Low bitrate files tend to stop playback (player will still take commands, but no output): step to another track and reboot.
I noticed this. Anyone experimentally determined what "low" is?
Posted by: tanstaafl.
Re: V3 alpha bugs - 25/09/2003 21:07
Anyone experimentally determined what "low" is?
I've had it happen at 64 KBPS.
I also noticed that when I installed 3.0 and tried to run it with the Emplode 3.0 the results were not good, as has been reported above. 2.0 Emplode seems to work OK. I don't know if it was my adventure with 3.0 emplode, or if this will happen to everyone who tries it... but I went from 2.0 player software to 3.0 player software and reverted back to 2.0 player software because of the low bitrate problems (audioboooks) and in the process, my play counts got destroyed. According to the info in my player, I had only listened to La Villa Strangiato a total of two times, and I had actually played it more times than that just on that very day!
tanstaafl.
Posted by: robricc
Re: V3 alpha bugs - 25/09/2003 21:43
my play counts got destroyed
This was known before the "leak" and has happened to others.
Posted by: tanstaafl.
Re: V3 alpha bugs - 25/09/2003 21:50
This was known before the "leak" and has happened to others.
Ah, good. I'm glad to know it wasn't because I did something dumb.
It wouldn't matter to me, really, except that I have a custom shuffle set up in my player, shuffled in order of most often played. This lets me do a down-down-down keypress and have an instant "favorites" playlist.
In another few months I will have played my favorites enough that they will once again be back on top of the play count list, and my favorites playlist will work again.
Is there any way to hasten this? Is there a way to just reset all my play counts to zero?
tanstaafl.
Posted by: tfabris
Re: V3 alpha bugs - 25/09/2003 22:12
Is there a way to just reset all my play counts to zero?
Yes, right
here.
However, this brings up a very important question for the Cambridge folks...
The instructions linked above were for version 2.0. Which should be fine for you, Doug, since that's what you're running. But now that 3.0 is out, do those instructions still count?
Anyone?
Posted by: drakino
Re: V3 alpha bugs - 26/09/2003 00:02
I wouldn't recommend someone running that command until we get the new info on the dynamic partition. Based on experiences of moving from 2.0 to 3.0 and back, things have changed out there quite a bit.
Posted by: Diznario
Re: V3 alpha bugs - 26/09/2003 00:26
Crossfade does indeed kick some serious bootay, but I just found an issue with it.
It doesn't work with ogg files. Well, not completely anyway...
You can fade out of an ogg, but you can't fade into one.
Let me explain.
If you're playing an ogg file, and then an mp3 comes on, the crossfade works just fine.
But If you're playing an mp3 file (or an ogg), and an ogg file comes up next, then there's no crossfade.
Anyone else seen this?
Posted by: Diznario
Re: V3 alpha bugs - 26/09/2003 00:33
Oh yeah, one other thing I noticed...
Sometimes, when I first turn on the player, the fade in takes hella days... like 30 seconds or so. I'm guessing it's not supposed to do that.
But it doesn't seem to happen every time.
Also note that the last time it happened, it was playing an ogg file... so that may be realated.
Posted by: Diznario
Re: V3 alpha bugs - 26/09/2003 00:38
Speaking of play counts... Is there any way to get rid of that counter in 3.0?
I had removed it before with 2.0, but I can't remember how I did it now... (Was there an option in Emplode before...?)
Posted by: Diznario
Re: V3 alpha bugs - 26/09/2003 00:43
b0rked avatar fixed. yay.
Hey, at least this is the bug section...
Posted by: tfabris
Re: V3 alpha bugs - 26/09/2003 00:56
Yeah, play counts on the track screen was an option in 2.0 final.
Note that you guys are going to find a lot of little things like that... Features that aren't in 3.0 because they were implemented late in 2.0, bugs that were fixed late in 2.0 that aren't fixed in 3.0, etc.
The reason is that 3.0 is from a branch earlier up the tree than 2.0 final. So there's a lot of rollup work to do.
If they ever get time to do it...
Posted by: JeffS
Re: V3 alpha bugs - 26/09/2003 07:11
Anyone else seen this?
Yeah, but with my wma files. I noted it in the other thread and then realized I should have stuck it here instead.
Same behavior as you're describing, only with wma files. mp3s work fine.
This threw me for a loop at first because the cross fading seemed to only be working intermittently. In fact, the first few files I tried were wmas, so I really thought the cross fading wasn't that great (since the effect I was getting was a fade out and an abrupt entrance in). Finally I hit my mp3s (the bulk of my collection) and started hearing true cross fading. It took me a while to figure out exactly what was going on. Since my wma's comprise < 1% of my collection it shouldn't be too much of a problem to re-encode them if that's necessary.
Posted by: mlord
Re: V3 alpha bugs - 26/09/2003 09:24
The PrevVisual function doesn't work -- cannot seek backwards when cycling through the Visuals. If I recall correclty, this was implemented via a serial port command.
Cheers
Posted by: CHiP
Re: V3 alpha bugs - 26/09/2003 16:23
Some bugs i found are:
on reverse seek, the cross fading seems to crash the player.
when looking at the seek tool and holding the seek buttons, if you go past the end of the song and into the next, it crashes the player.
When listening to a track, I put it in pause mode, and then click to the next track. But then when i unpause, insted of starting fresh at the beginning of the track, it plays part of the last track while starting the new track. They need to make it so when you click to the next track, it clears the crossfading buffer (of whatever its called, you know what i mean).
Simple wish list:
Fade on pause and resume, or give the option, so you can at least fade back in from pause.
when i say crash the player, the screen still looks ok, but you get no sound, and the time doens't count up, just sits at zero.
Bedies that, its quite stable. I was expecting it to be a lot worse!
Posted by: mlord
Re: V3 alpha bugs - 26/09/2003 17:03
Actually, PrevVisual was a virtual button code in v2final, not a serial command.
Hijack v342 now includes a temporary work-around for this issue, requiring either a Tuner or "fake_tuner=1" in config.ini.
Cheers
Posted by: tanstaafl.
Re: V3 alpha bugs - 29/09/2003 02:57
tanstaafl: Is there a way to just reset all my play counts to zero?
tfabris: Yes, right here.
FAQ: ... shell prompt to run the following command: dd if=/dev/zero bs=512 skip=4096 count=28672 of=/dev/hda3
This should erase the per-song dynamic data without harming the player settings such as the tuner and EQ presets.
I don't promise that this will happen to everybody (don't know why it wouldn't) but the above step did erase my EQ presets and bookmarks, as well as zeroing out my play counters.
tanstaafl.
Posted by: Roger
Re: V3 alpha bugs - 29/09/2003 03:23
The dynamic data partition hasn't changed much from v2 yet. I will change by 3.0 final, I'm sure.
Posted by: tfabris
Re: V3 alpha bugs - 29/09/2003 10:20
but the above step did erase my EQ presets and bookmarks, as well as zeroing out my play counters.
Anyone know why this happened? It wasn't supposed to erase anything but his song statistics, according to the source that supplied us with the command.
Posted by: tanstaafl.
Re: V3 alpha bugs - 29/09/2003 15:19
Anyone know why this happened?
Could it have anything to do with the fact that I went from 2.0 Final to 3.0 Alpha and back to 2.0 Final? (This is what wrecked my play counters in the first place...)
tanstaafl.
Posted by: Daria
Re: V3 alpha bugs - 29/09/2003 16:36
The song counts really use 28672*512 bytes? Wow, that sounds inefficient.
Posted by: genixia
Re: V3 alpha bugs - 29/09/2003 17:04
This should erase the per-song dynamic data without harming the player settings such as the tuner and EQ presets.
I imagine that includes the data used to visualise tracks in seek mode.
Posted by: tman
Re: V3 alpha bugs - 29/09/2003 19:15
Each song doesn't use up the entire 512 bytes that it's allocated. I think there has been mention of splitting it up further and allowing more track metadata to be stored so you can have more tracks. This would be one of the post 3.0 things which would break the dynamic data partition format.
Posted by: Daria
Re: V3 alpha bugs - 29/09/2003 20:00
I'll have to find my notes before I can comment intelligently, but it should be possible to determine if it will clobber those. I'll look in a bit.
Posted by: foxtrot_xray
Re: V3 alpha bugs - 01/10/2003 20:31
I will change by 3.0 final, I'm sure.
...Yeah, but will
It??
Sorry.
Posted by: boxer
Re: V3 alpha bugs - 06/10/2003 04:17
My issues with the 3.00alpha are as follows:
1. Stops dead on MP2's
2. Stops dead - I've now established that it's not just on low bitrate, it did it on a VBR, yesterday.
3. Forgets filters on re-boot.
4. I've given up trying to figure out whether the RDS issues are the Empeg, or the transmitted signal - it was never a great piece of technology! Since installing 3.00 I haven't had a single traffic announcement, but I seldom got them on 2.00.
5. Seldom syncs correctly.
Posted by: Chimaera
Re: V3 alpha bugs - 30/10/2003 11:44
If you do a tweak by artist, and get the "no matching artist found" message then the current song cannot be changed, pressing the skip buttons on the front panel causes the title information to change, but it doesn't change what is playing. Also when the playing song reaches the end you just get silence, even though it is not the end of the playlist.
Posted by: russmeister
Re: V3 alpha7 bugs - 16/02/2004 12:24
Just downloaded the new alpha 7 and noticed a few things:
I hope these haven't been reported before but here goes:
1-If you do a long button press on the number 2 it gives you the "found matching artist" popup but it pulls a random artist and immediately advances to that song. I can't find a pattern to it.
2-The player always boots up paused. Is this intentional?
3-When trying to go to a previous track with crossfade on, it will not advance back. It just goes to the beginning of the current song and no matter how many times I press the previous button, it won't go back. If you press it twice you can see the previous song come up (depending on your info mode, of course) but then it skips back forward to the current song.
Only been playin' with it for about 10 minutes and I've found these so far.
Running version 3.0 alpha7
Posted by: tfabris
Re: V3 alpha7 bugs - 16/02/2004 12:54
1-If you do a long button press on the number 2 it gives you the "found matching artist" popup but it pulls a random artist and immediately advances to that song. I can't find a pattern to it.
No, that's not what it does. It's doing the correct thing, the same thing it does on V2 software. Please
click here.
Posted by: russmeister
Re: V3 alpha7 bugs - 16/02/2004 13:07
I never knew about that feature. I stand corrected. Thx.
I'm sure I'll be using that from time to time now.
Posted by: Elite M3
Re: V3 alpha bugs - 16/02/2004 13:28
1) I was using the long press on the bottom button of the empeg (to cycle through the visuals that display the current song, list of upcoming, or visual) and it first goes to the visual with the song listed at the bottom of the screen (but no visual), then the next one goes to a completely blank screen. The song still plays, but nothing on the screen. Pressing it again yields NO results. The only way to get it back is to manually reboot the machine. I am running v3 Alpha7.
2) My crossfade only works when I manually press the track foward button. I would like it to be on all the time to automatically fade when the next song is about to start.
Thanks.
Posted by: russmeister
Re: V3 alpha7 bugs - 16/02/2004 21:10
I also noticed that the screen isn't as responsive when advancing through a song. It just seems slower than the 2.0 final. Is this a bug or is it my imagination? Anyone else experiencing this?
Posted by: brendanhoar
Re: V3 alpha7 bugs - 17/02/2004 00:57
I concur: fast-forward seems lagged.
-brendan
Posted by: Taym
Re: V3 alpha7 bugs - 18/02/2004 05:16
I'll post it here too for the sake of clarity.
I always forgot to mention this: all alpha releases (including alpha7) have a bug so that when you switch back from Tuner ro Player, the currently played sond is marked ( !! ).
Has anyone noticed?
Posted by: russmeister
Re: V3 alpha7 bugs - 18/02/2004 08:10
I noticed two other things this morning:
1-When the player is paused, you can't go to a previous track. It does nothing.
2-When looking at the track info screen, the bitrate is no longer there so you have no way of telling what the bitrate is of a specific song. I found this when my player froze on a song and I was trying to see what the bitrate was b/c I remember that low bitrates were causing the player to crash.
Posted by: Taym
Re: V3 alpha7 bugs - 18/02/2004 08:30
The bitrate problem occurred to me too, but not consistently. Most times it is there.
Posted by: drakino
Re: V3 alpha bugs - 18/02/2004 19:48
Not sure if this is an empeg bug or jEmplode.
empeg 3.0 Alpha 7
jEmplode v54
HiJack 374
Did a sync to the unit, while the screen was asleep. Hit the top button to wake the empeg, and the sync continued, but, the screen showed my last track that was playing. Pressing the top button again would cause the player to show the pause logo. Once more, it goes away, and the player shows 0:00 on the track, but never advances. Not sure if this is the basic RMM protocal being implemented behind the scenes, or a glitch in either the player or jEmplode.
edit - Sync finished, files all seemed to be ok, but jEmplode hung on rebuilding database. Oddly, closing it then reopening it showed the songs in the proper playlist. I did a minor change to force a database reload just in case.
Posted by: jbradshw
Re: V3 alpha bugs - 19/02/2004 11:40
v3 a7, Hijack 374
I read somewhere that sometimes the player locks on when switching visuals (or something like that), but I can't watch any visuals on mine. No matter what visual is selected or what Info screen (that has a visual showing) I select my player immediately reboots upon switching to that. The weird thing is, after I first went to v3a7 I had no problem with the visuals, then all of a sudden this started.
I'm assuming this is a known bug so it's not really a big deal for me, plus I know its an alpha but it would be nice to be able to see visuals again.
Posted by: Micman2b
Re: V3 alpha bugs - 19/02/2004 22:44
I found a funky bug last eve with 3.0a7. When I upload either Béla Fleck or Björk the names become scrambled with random characters on the empeg after synchronizing. I was using jEmplode. The Rio Central using jEmplode does not scramble the names on the Central during sync.
Sean in NC
Posted by: tfabris
Re: V3 alpha bugs - 20/02/2004 00:46
Béla Fleck
How many Béla Fleck fans on the board?
<raises hand>
Posted by: peter
Re: V3 alpha bugs - 20/02/2004 04:19
I found a funky bug last eve with 3.0a7. When I upload either Béla Fleck or Björk the names become scrambled with random characters on the empeg after synchronizing. I was using jEmplode. The Rio Central using jEmplode does not scramble the names on the Central during sync.
Is this the latest Jemplode? Rio Central and car-player v2 use ISO Latin 1, car-player v3 and Karma use UTF-8.
Peter
Posted by: Micman2b
Re: V3 alpha bugs - 20/02/2004 07:52
Peter, you know, I have not installed either band to the Karma yet, let me check...
BRB..
Also, yes I am using the latest jEmplode
Sean in NC
Posted by: Micman2b
Re: V3 alpha bugs - 20/02/2004 07:54
<raises hand>
I have most all albums..
Sean in NC
Posted by: Gleep
Re: V3 alpha bugs - 20/02/2004 08:01
How many Béla Fleck fans on the board?
Was that a cosmic hippo I saw?
Hand Raised!
Posted by: crazymelki
Re: V3 alpha bugs - 20/02/2004 11:26
Hi,
I can confirm this bug....The rebooting procedure does't stop after this visual changing. I was going down to 2.0 to fix the problem. After upgrading to V3a7, the player works again..ufff..
bye
Posted by: tonyc
Re: V3 alpha bugs - 21/02/2004 13:07
I could have sworn the Clock visual had the date on it in previous releases, but in v3a7, I don't see it.
Posted by: mlord
Re: V3 alpha bugs - 21/02/2004 17:34
Mmm.. The Hijack "Clock" function has day-of-week, time, and date.
Cheers
Posted by: genixia
Re: V3 alpha7 bugs - 21/02/2004 20:02
v3a7 - Gap removal isn't quite perfect yet. I don't know whether this us bitrate dependant or not, but it appears that a little too much 'gap' is being removed on my 192kbits/s tracks. Is there any parameter that could be tweaked through config.ini?
Posted by: tonyc
Re: V3 alpha bugs - 21/02/2004 21:24
Of course, but the clock visual is always on when I'm in tuner mode. I just thought it was worth pointing out that it seems to have disappeared from the visual (intentional or not.)
Posted by: Micman2b
Re: V3 alpha bugs - 21/02/2004 21:46
Peter,
The Karma reads these bands fine... Oh well, I downgraded to 2.0 anyway as the drives do not seem to spin down...
Sean McManus
Posted by: mlord
Re: V3 alpha bugs - 21/02/2004 21:52
With Hijack installed, the drives should *always* spin down. It may take as long as 60 seconds (from last access; configurable), but they should spin down.
Cheers
Posted by: msaeger
Re: V3 alpha bugs - 21/02/2004 23:50
Does anyone else get a messed up info screen when using the aux input. I kind of looks like the tuner screen.
Also if I put the player in standby where I get the pulsing led with the screen off if I turn off the car and the player totally shuts down then when I restart the car the player still looks like it is in standby but the music starts playing.
Posted by: Daria
Re: V3 alpha bugs - 22/02/2004 00:51
Aux in screen: what happens if you change info modes?
Posted by: msaeger
Re: V3 alpha bugs - 22/02/2004 01:01
If I do info off the screen goes blank like normal. If I do info line I just get the counter in the lower right corner I believe that is the normal behavior for that too. The only mode with a problem is the regular info mode.
Posted by: russmeister
Re: V3 alpha bugs - 25/02/2004 13:02
Here's a new one....
I just deleted all of my songs off my player b/c I have fixed some of them and reordered them on my computer. After deleting them all, the playlist shows "none" but the interesting thing is that I can still use the advance button and it scrolls through songs that use to exist. Actually, I just noticed something... I unpaused it and it's still playing the songs so they must still be there! Odd, very odd. Shouldn't they be completely deleted from the player and unplayable after "deleting" them?
v3a7 and the latest version of jemplode, whatever that is.
EDIT: Emplode 2.10 is also showing nothing for my playlists but the player still plays songs.
Posted by: tms13
Re: V3 alpha bugs - 25/02/2004 13:31
That sounds normal, if you've removed all your playlists, but not removed the tunes.
If I'm right, you should see tunes in soup views, or with an advanced search for refs="0".
Posted by: russmeister
Re: V3 alpha bugs - 25/02/2004 13:37
But I told it to remove the tunes, too.
EDIT: When you are deleting playlists, there's a checkbox to delete the song as well, right? I checked that box and it's my understanding that not only the playlists will be deleted but also the songs. Am I wrong?
Posted by: tms13
Re: V3 alpha bugs - 25/02/2004 15:52
In reply to:
When you are deleting playlists, there's a checkbox to delete the song as well, right?
That's not how it works in JEmplode, IIRC. There's a checkbox for "Remove completely" which kills all references to the playlist or tune, but I believe that the children will be orphaned when you remove their last containing playlist.
You can do a search on refs=0 to find your orphans.
Posted by: tfabris
Re: V3 alpha bugs - 25/02/2004 15:59
No, remove completely is supposed to remove the tune itself, just like Emplode.
Posted by: image
Re: V3 alpha bugs - 25/02/2004 21:39
couple of bugs:
first, before i've complained about OGG files making the load up to the 7s, making it practically impossible to do anything after (slow menus, song load, etc). I finally isolated it to VISUALS. i turned the selected visual to OFF, and its at around 1.0 - 1.5 load at -q7. now, here's the kicker. INFO mode didn't have to be showing visuals for it to be eating up cpu time. I could have it at the Track Info screen, and it would be at such a high load, until i change it to off. this by design? I mean, does the player have to be processing the visual even if nothing is showing? can't you autoswitch it to OFF if its a non-visual INFO screen? how come i never noticed this until i played with OGGs?
secondly, i have some audio books that i compressed on -q0 mono, which turned out to be 19kbps. these OGG files do not seek whatsoever in v3a7. not sure if they did in any other alpha.
Posted by: pupvogel
Re: V3 alpha7 bugs - 26/02/2004 05:46
I'm just noticing the same effect: alpha7 is 'too gapless', a very short part of music is missing between tracks.
Which of course is still much better than a gap...
Also, as somebody mentioned before, special characters like in Bj
rk are not handled correctly in emplode (which is pretty bad as I have those all over the place..lots of german stuff..).
When adding new tracks everything seems to be right, but after emplode (2.00 and 2.10) downloads the database from the empeg those characters go nuts somehow.
I noticed this behaviour in v3alpha3 already.
Posted by: tms13
Re: V3 alpha bugs - 26/02/2004 08:26
I thought we were talking about removing playlists here, not tunes?
Posted by: mlord
Re: V3 alpha bugs - 26/02/2004 08:33
first, before i've complained about OGG files making the load up to the 7s, making it practically impossible to do anything after (slow menus, song load, etc). I finally isolated it to VISUALS. i turned the selected visual to OFF, and its at around 1.0 - 1.5 load at -q7.
Have you tried the latest Hijack with this? Any better?
Cheers
Posted by: genixia
Re: V3 alpha7 bugs - 26/02/2004 16:04
In reply to:
Also, as somebody mentioned before, special characters like in Bj rk are not handled correctly in emplode
Or in the BBS apparantly
Posted by: wfaulk
Re: V3 alpha7 bugs - 26/02/2004 18:50
I thought it was a particularly apt transliteration.
Posted by: tfabris
Re: V3 alpha7 bugs - 27/02/2004 01:22
You know, you're right, that little icon does kinda look like her.
Posted by: image
Re: V3 alpha bugs - 27/02/2004 01:29
Have you tried the latest Hijack with this? Any better?
nope, the one i have on my empeg is 374. been pretty hectic, and haven't been able to just recompile a new ext3 kernel in the last week. will try tommorow.
Posted by: genixia
Re: V3 alpha7 bugs - 27/02/2004 16:03
LOL. Although true, I think that it's due to some strange codebase effect. No matter how I tried, I couldn't get the BBS to convert :
o to
without spacing between the "j" and ":", whereas the original post has no spacing.
Posted by: drakino
Re: V3 alpha7 bugs - 28/02/2004 12:50
Testing:
Björk
Posted by: genixia
Re: V3 alpha7 bugs - 28/02/2004 16:02
Hmm. Maybe not then. So how did he do it??
Bj:ork
Posted by: tman
Re: V3 alpha7 bugs - 28/02/2004 16:09
Bj
rk? If you intentionally put in the image tag then you can do it without the space.
Posted by: drakino
Re: V3 alpha7 bugs - 28/02/2004 16:14
I typed this out:
Shift-B
j
Option-U
o
r
k
Looks like my browser is in ISO-Latin-1 encoding mode. This being on OS X. I'm not sure what the ALT-code equivalent is on the PC.
Posted by: genixia
Re: V3 alpha7 bugs - 28/02/2004 16:59
Doh! Overlooking the bloody obvious again.
Posted by: image
Re: V3 alpha bugs - 02/03/2004 01:37
Have you tried the latest Hijack with this? Any better?
nope, just tried 379 and its the same behavior. on the same ogg file, it rockets to 7 if i'm showing the SpectroLog 128 visual, 4 if its on the visual but track mode, and 1.5 when track + visual off.
Posted by: AndrewT
Re: V3 alpha bugs - 14/07/2004 21:27
Quote:
4. I've given up trying to figure out whether the RDS issues are the Empeg, or the transmitted signal - it was never a great piece of technology! Since installing 3.00 I haven't had a single traffic announcement, but I seldom got them on 2.00.
Boxer: I remember the meticulous investigations you made previously on this subject.. Can you, or perhaps anyone else with v3alpha8, comment upon whether this (TA) and the AF and the right/left-buttom freq searching problems have been resolved in the new release(s)?
I understand that the freq searching was an acknowleged bug but the AF and TA problems, and more importantly to me the AF, were considered by the Cambridge team to be working properly in previous releases?