Posted by: schofiel
Bugs in V3 A10 - 14/07/2005 18:31
Please post them in this thread ONLY.
When hammering on the s/w, please look specifically at the tuner.
When hammering on the s/w, please look specifically at the tuner.
Bugs in V3 A10
Posted by: pim
Re: Bugs in V3 A10 - 14/07/2005 18:34
Bugs new to v3a10?
Or v3a bugs still not fixed in 10?
Pim
Or v3a bugs still not fixed in 10?
Pim
Posted by: schofiel
Re: Bugs in V3 A10 - 18/07/2005 17:20
Any bugs you find in A10, regardless of how long they've been there.
Posted by: SE_Sport_Driver
Re: Bugs in V3 A10 - 18/07/2005 18:59
After installing over 2.00final, my screen did this.
I'm now doing my first reboot and it's Building the database. BTW, I love the progress % for the database build! Great feature!
I might have the record (?) for the most mp3s on an alpha player after this.
I'm now doing my first reboot and it's Building the database. BTW, I love the progress % for the database build! Great feature!
I might have the record (?) for the most mp3s on an alpha player after this.
Posted by: SE_Sport_Driver
Re: Bugs in V3 A10 - 18/07/2005 19:06
Upon reboot, without any sync, I queued up the root playlist of 23,000 songs and the first track began to play in "Slow motion" and a bit of scratching. No response from the front panel.
No error messages via Serial.
No hijack. No player hack for larger fid counts. Only fidsift at this point.
64mb memory board. Memory passes test during bootup.
EDIT:
After 2nd reboot, noticed this via serial
Code:
EDIT2:
Dang it. Emplode crashed. The only thing I could grab from the windows error report was this.
No error messages via Serial.
No hijack. No player hack for larger fid counts. Only fidsift at this point.
64mb memory board. Memory passes test during bootup.
EDIT:
After 2nd reboot, noticed this via serial
Code:
Starting player
Using non-standard cache size 820 (bonus 48Mb, adjustment 0)
player.cpp : 579:empeg-car 3.00-alpha10 2005/07/09.
! tunedb_disk.cpp :1192:Database size mismatch error.
no room for private writable mapping
error: -12
serial_notify_thread.cpp: 170:@@ S0
EDIT2:
Dang it. Emplode crashed. The only thing I could grab from the windows error report was this.
Posted by: peter
Re: Bugs in V3 A10 - 18/07/2005 19:35
Quote:
no room for private writable mapping
Your player is running out of memory. I never tested the alphas (or 2.01 for that matter) on players as big as 48Mb, and it may be that the policy of giving the entire difference in memory over to the music cache, is not ideal. (Perhaps the kernel needs more memory to keep its pagetables for such a big system, or perhaps things such as TCP/IP award themselves bigger buffer sizes if run on 48Mb players.)
See whether adding a "reservecache=20" line, or something similar, in config.ini makes any difference. This leaves 20 cache chunks (or 1280K) unallocated, so any greedy TCP/IP or pagetable that comes along, is welcome to use it.
Peter
Posted by: SE_Sport_Driver
Re: Bugs in V3 A10 - 18/07/2005 19:39
I'm not sure if it either needed one more try for emplode (this time just connecting because the prior database build took even though I never sync'd) or the installation of HiJack fixed it...
But it's working now. Sorry to clutter the thread. I'll wait until the end of the night at least before posting again!
But if anyone runs into a similar situation, maybe this will give them hope! 
But it's working now. Sorry to clutter the thread. I'll wait until the end of the night at least before posting again!
But if anyone runs into a similar situation, maybe this will give them hope!
Posted by: mlord
Re: Bugs in V3 A10 - 18/07/2005 19:46
Hijack includes code to try and counter the stuttering/unresponsive display at startup on high-memory machines. Not perfect, but much better than without hijack.
-ml
-ml
Posted by: SE_Sport_Driver
Re: Bugs in V3 A10 - 18/07/2005 19:52
I'm getting some error message pop up on the screen, but it's so lightning quick I can't read it....
Serial output=
VM: do_try_to_free_pages failed for kswapd...
VM: do_try_to_free_pages failed for kswapd..
no room for private writable mapping
error: -12
Low memory error right? It's at least working. Kinda. Error message pops up a LOT, "Line" info mode c r a w l s ss as do the menus.
But hey, at least my database in in good shape!
Serial output=
VM: do_try_to_free_pages failed for kswapd...
VM: do_try_to_free_pages failed for kswapd..
no room for private writable mapping
error: -12
Low memory error right? It's at least working. Kinda. Error message pops up a LOT, "Line" info mode c r a w l s ss as do the menus.
But hey, at least my database in in good shape!
Posted by: mlord
Re: Bugs in V3 A10 - 18/07/2005 22:00
Looks like low memory.
Try a nice big fat ReserveCache=50 or something.
The kernel needs about 5% overhead on physical memory. So on a 48MB player, one should consider doing ReserveCache=xx to tell the player s/w not to use at least 5% of the added RAM, which works out to 25 or so (each ReserveCache increment represents 64KB of RAM).
I'd give about double that, myself, which will help things like the web access and any third party apps you might install (or have installed).
Cheers
Try a nice big fat ReserveCache=50 or something.
The kernel needs about 5% overhead on physical memory. So on a 48MB player, one should consider doing ReserveCache=xx to tell the player s/w not to use at least 5% of the added RAM, which works out to 25 or so (each ReserveCache increment represents 64KB of RAM).
I'd give about double that, myself, which will help things like the web access and any third party apps you might install (or have installed).
Cheers
Posted by: Roger
Re: Bugs in V3 A10 - 19/07/2005 06:13
Quote:
BTW, I love the progress % for the database build! Great feature!
Is that a v3-only feature? Wow. It's been so long since I added that: I thought it was in v2.x as well...
Posted by: Roger
Re: Bugs in V3 A10 - 19/07/2005 06:17
(Note: this is a v3a8 bug, and I've not tried v3a10 yet, but since Dave was focussed on the tuner code, I don't think he'll have fixed it. If someone gets the chance to reproduce it before I install v3a10, please post your results here)
Using Tweak Order can confuse/crash the player:
If you have the player shuffled, and you decide you'd like more of the current artist, you hit the tweak button on the remote. If you decide you'd like lots more, you keep hitting it until it says "no match found".
At this point, if you hit track skip, it doesn't -- the screen changes to the next song (and the next song), but it never actually skips track.
You need to reboot the player to fix it.
If the position in the first track is past the end of the next track (IYSWIM), this action can also cause the player to reboot.
Using Tweak Order can confuse/crash the player:
If you have the player shuffled, and you decide you'd like more of the current artist, you hit the tweak button on the remote. If you decide you'd like lots more, you keep hitting it until it says "no match found".
At this point, if you hit track skip, it doesn't -- the screen changes to the next song (and the next song), but it never actually skips track.
You need to reboot the player to fix it.
If the position in the first track is past the end of the next track (IYSWIM), this action can also cause the player to reboot.
Posted by: webroach
Re: Bugs in V3 A10 - 19/07/2005 06:24
Quote:
You need to reboot the player to fix it.
Actually, if you, upon experiencing this error, back up two tracks, then skip forward, all will be well. At least it's been working for me (I tend to use tweak order a LOT).
YMMV
Posted by: schofiel
Re: Bugs in V3 A10 - 19/07/2005 16:59
Guys, could we keep the discussions to a minimum and keep a concise list of bugs posted here. If you want to discuss the behaviour, problems, or whatever, start another thread. Don't just sit here spinning gas about observations: at some point, someone is going to have to pick through a bug list and if this thread is populated by 10,000 pointless observations then it's going to be a bit difficult, no?
So from now on: concise bug descriptions of confirmed bugs ONLY, with a description of the stimulus, and the symptoms, with an indication of repeatability. The areas of interest are focussed around the tuner functionality.
So from now on: concise bug descriptions of confirmed bugs ONLY, with a description of the stimulus, and the symptoms, with an indication of repeatability. The areas of interest are focussed around the tuner functionality.
Posted by: AndrewT
Re: Bugs in V3 A10 - 19/07/2005 19:31
1. Unable to perform station searches using the L & R buttons (remote & front panel).
2. Impossible to disable AF. The AF display symbol reflects the menu selection but AF is still always active.
3. AF changes frequency to 98.0MHz every few minutes. This appears to happen while tuned to BBCR1 (99.1MHz) and BBCR4 (93.9MHz), I haven't observed this behaviour on independent stations.
I mostly listen to radio in the middle of the south-central area shown here - see the light blue 99.1MHz patch. With BBCR1 for example, it always switches from 99.1MHz to 98.0MHz within a few minutes. Meanwhile, the AF debug display permanently displays the "WAIT" screen. Changing the preset station away and back again corrects it for anything up to 2 minutes, rinse and repeat.
I cannot 100% confirm this but I think that in areas of weak reception, the 98.0MHz switching tends not to happen.
2. Impossible to disable AF. The AF display symbol reflects the menu selection but AF is still always active.
3. AF changes frequency to 98.0MHz every few minutes. This appears to happen while tuned to BBCR1 (99.1MHz) and BBCR4 (93.9MHz), I haven't observed this behaviour on independent stations.
I mostly listen to radio in the middle of the south-central area shown here - see the light blue 99.1MHz patch. With BBCR1 for example, it always switches from 99.1MHz to 98.0MHz within a few minutes. Meanwhile, the AF debug display permanently displays the "WAIT" screen. Changing the preset station away and back again corrects it for anything up to 2 minutes, rinse and repeat.
I cannot 100% confirm this but I think that in areas of weak reception, the 98.0MHz switching tends not to happen.
Posted by: pim
Re: Bugs in V3 A10 - 21/07/2005 21:29
Seeking in ogg files is broken.
If you fast-forward ogg tunes, the player does not resume playing after releasing the button. Usually, it will only stop after completing the current tune.
Pim
If you fast-forward ogg tunes, the player does not resume playing after releasing the button. Usually, it will only stop after completing the current tune.
Pim
Posted by: pim
Re: Bugs in V3 A10 - 21/07/2005 21:32
Tunes are marked unintentionally, randomly.
Pim
Pim
Posted by: pim
Re: Bugs in V3 A10 - 21/07/2005 21:35
Database loading is suboptimal.
/drive0/var/database3 is read with 512 bytes per read() system call.
A larger buffer would speed up the database load.
Pim
/drive0/var/database3 is read with 512 bytes per read() system call.
A larger buffer would speed up the database load.
Pim
Posted by: pim
Re: Bugs in V3 A10 - 21/07/2005 22:33
Japanese tags do not display right.
Version 3 of the player uses utf-8 internally, but the
used fonts lack japanese glyphs.
Pim
Version 3 of the player uses utf-8 internally, but the
used fonts lack japanese glyphs.
Pim
Posted by: pim
Re: Bugs in V3 A10 - 21/07/2005 22:35
Play count display cannot be suppressed.
This used to be possible in player v2
Pim
This used to be possible in player v2
Pim
Posted by: pim
Re: Bugs in V3 A10 - 21/07/2005 22:40
Playlists cannot be accessed immediately.
Pressing Playlists->Down shows an hourglass before the playlists appear.
Player v2 would show playlists immediately.
Pim
Pressing Playlists->Down shows an hourglass before the playlists appear.
Player v2 would show playlists immediately.
Pim
Posted by: AndrewT
Re: Bugs in V3 A10 - 21/07/2005 22:54
AF occasionally causes the empeg to jump to a different station.
Perhaps this is caused by interference from a local station or possibly this is because TA is always enabled (it is currently set to 'Off' on my player) regardless of the menu selection (just like AF) - I'm not sure? Local radio stations have a bad habit of leaving their TA beacon active both before and after the TA to sucker you into listening to their ad's.
I'm struggling to think of any useful data that I can provide here to backup my claims in this thread, please feel free to ask if there's anything worthwhile that I should add.
Perhaps this is caused by interference from a local station or possibly this is because TA is always enabled (it is currently set to 'Off' on my player) regardless of the menu selection (just like AF) - I'm not sure? Local radio stations have a bad habit of leaving their TA beacon active both before and after the TA to sucker you into listening to their ad's.
I'm struggling to think of any useful data that I can provide here to backup my claims in this thread, please feel free to ask if there's anything worthwhile that I should add.
Posted by: peter
Re: Bugs in V3 A10 - 22/07/2005 11:44
Quote:
Tunes are marked unintentionally, randomly.
This is a feature, not a bug, but it's clearly unpopular enough to remove. The markings are not random, they indicate when the track ended earlier than it indicated it would; often, this is the result of a corrupt MP3. However, if the marking is as overzealous as some claim, perhaps there are bugs in its determination of early ending. FITNR.
Quote:
/drive0/var/database3 is read with 512 bytes per read() system call. A larger buffer would speed up the database load.
The actual problem was the dynamic data partition, not database3 (which is read with a single system call). FITNR.
Quote:
Version 3 of the player uses utf-8 internally, but the used fonts lack japanese glyphs.
FITNR (for the larger font; it's not really possible to display Japanese in the smaller font).
Quote:
Play count display cannot be suppressed.
FITNR.
Quote:
Unable to perform station searches using the L & R buttons (remote & front panel).
FITNR.
Peter
Posted by: Roger
Re: Bugs in V3 A10 - 22/07/2005 12:10
Quote:
...they indicate when the track ended earlier than it indicated it would; often, this is the result of a corrupt MP3...
I always suspected that -- more often -- this is the result of whichever version of emplode had a rounding error when calculating the length of the track. Theoretically, if you recalculate the length tag, it'd go away.
The problem is that the "marked" flag should be reserved for the user, or should differentiate between the user setting it, or the player setting it.
Posted by: peter
Re: Bugs in V3 A10 - 22/07/2005 12:23
Quote:
The problem is that the "marked" flag should be reserved for the user, or should differentiate between the user setting it, or the player setting it.
On the car-player, certainly. This was really another product's feature, which kind of leaked over.
Peter
Posted by: peter
Re: Bugs in V3 A10 - 22/07/2005 13:41
Quote:
you keep hitting it until it says "no match found". At this point, if you hit track skip, it doesn't
How sucky. FITNR.
Peter
Posted by: pgrzelak
Re: Bugs in V3 A10 - 22/07/2005 13:42
WITNR?
Posted by: mlord
Re: Bugs in V3 A10 - 22/07/2005 13:43
While you're in there..
The "Previous Visual" virtual button code vanished a while back.. I don't think any of the v3alpha's have it.
This is a fake button code (0x0020df18) first introduced in v2-rc1. Hijack is then used to remap it to a real button/menu as needed.
Cheers
The "Previous Visual" virtual button code vanished a while back.. I don't think any of the v3alpha's have it.
This is a fake button code (0x0020df18) first introduced in v2-rc1. Hijack is then used to remap it to a real button/menu as needed.
Cheers
Posted by: JBjorgen
Re: Bugs in V3 A10 - 22/07/2005 13:46
No bug to report, but Peter is my hero.
Posted by: peter
Re: Bugs in V3 A10 - 22/07/2005 14:11
Quote:
The "Previous Visual" virtual button code vanished a while back.
FITPR -- it was in alpha 10, but you're right that it wasn't in previous alphas. Dave did a (manual) v2 to v3 merge for the alpha10 release, and in the bits of code that haven't changed much in the interim (such as the input handling) the merge went in fairly smoothly.
Peter
Posted by: pim
Re: Bugs in V3 A10 - 22/07/2005 15:00
Quote:Quote:
Version 3 of the player uses utf-8 internally, but the used fonts lack japanese glyphs.
FITNR (for the larger font; it's not really possible to display Japanese in the smaller font).
Cool! Don't forget to claim the $350 reward!
Pim
Posted by: pim
Re: Bugs in V3 A10 - 22/07/2005 15:08
Quote:Quote:
...they indicate when the track ended earlier than it indicated it would; often, this is the result of a corrupt MP3...
I always suspected that -- more often -- this is the result of whichever version of emplode had a rounding error when calculating the length of the track
Now it makes sence to me. My length tags are calculated by mp3tofid using madlib or libogg, and can be slightly different from the ones emplode would have calculated.
Pim
Posted by: peter
Re: Bugs in V3 A10 - 22/07/2005 15:38
Quote:
Cool! Don't forget to claim the $350 reward!
There's no need for a $350 reward. If anyone desparately wanted to rid themselves of $350 after downloading the next release, I'm sure either these folks or maybe this lot could find something useful to do with it.
Peter
Posted by: alex25
Re: Bugs in V3 A10 - 22/07/2005 15:46
While you are fixing bugs. Here are my comment, previously reported in another thread:
In tuner mode there is a very short pop (nearly not audibly) each time the software tries to search for a stronger signal. This happens about twice per second. It’s the same as it was in 2.0 final.
Manually setting a tuner frequency using the remote control crashes the player. Hijack displays a sigseg error and the player reboots (same behaviour as in alpha8) This somehow only seems to occur in the car and not in the docking station?!?
In tuner mode there is a very short pop (nearly not audibly) each time the software tries to search for a stronger signal. This happens about twice per second. It’s the same as it was in 2.0 final.
Manually setting a tuner frequency using the remote control crashes the player. Hijack displays a sigseg error and the player reboots (same behaviour as in alpha8) This somehow only seems to occur in the car and not in the docking station?!?
Posted by: tman
Re: Bugs in V3 A10 - 22/07/2005 15:56
Quote:Quote:
Cool! Don't forget to claim the $350 reward!
There's no need for a $350 reward. If anyone desparately wanted to rid themselves of $350 after downloading the next release, I'm sure either these folks or maybe this lot could find something useful to do with it.
Both good causes but how about for the beer/curry fund?
Posted by: peter
Re: Bugs in V3 A10 - 22/07/2005 16:10
Quote:
Both good causes but how about for the beer/curry fund?
It should go to charity. In particular, people shouldn't attempt to put it behind the bar at the Wrestlers: our new office is on the other side of town and we don't even go to the Wrestlers any more.
Peter
Posted by: tman
Re: Bugs in V3 A10 - 22/07/2005 16:26
Quote:
It should go to charity.
Okie dokie
Posted by: peter
Re: Bugs in V3 A10 - 22/07/2005 16:46
Quote:
WITNR?
This coming Monday, 25th July. Or Tuesday morning UK time at the latest. Everyone is urged to download alpha 10 if they haven't already done so, and test it over this weekend, reporting bugs in this thread by Sunday evening US time if possible.
Peter
Posted by: pgrzelak
Re: Bugs in V3 A10 - 22/07/2005 17:02
!!! Wow! I was just asking, not expecting anything in the near future...
Posted by: bonzi
Re: Bugs in V3 A10 - 22/07/2005 17:26
Let me just reiterate: guys@empeg are absolutely amazing!
Posted by: SE_Sport_Driver
Re: Bugs in V3 A10 - 22/07/2005 17:33
This is so awesome of you guys!
Posted by: alex25
Re: Bugs in V3 A10 - 22/07/2005 18:18
Another bug: beeps do not work in alpha10
Many thanks for releasing a new player version and we all hope to see a new karma with tuner soon.
Many thanks for releasing a new player version and we all hope to see a new karma with tuner soon.
Posted by: matthew_k
Re: Bugs in V3 A10 - 22/07/2005 18:54
Quote:
FITNR
That's an amazing acronym to read. Peter is also my hero. I havn't looked forward to the next release in years.
Matthew
Posted by: elperepat
Re: Bugs in V3 A10 - 22/07/2005 19:44
Here are my observations. As nobody else seems to have problems with that, maybe it's just me...
Riocar V3.0 alpha 10 Dev, 32Meg memory, Hijack 435, ReserveCache=50
Playlist is not remembered between reboots
(Every time unplug/plug the empeg, it starts with an empty playlist)
Bookmarks are not saved.
(When I Set, then Goto bookmark, it comes to an empty playlist.)
Menu scrolling is sluggish during caching
(Just after changing songs with skip, more of an annoyance than a bug...)
Riocar V3.0 alpha 10 Dev, 32Meg memory, Hijack 435, ReserveCache=50
Playlist is not remembered between reboots
(Every time unplug/plug the empeg, it starts with an empty playlist)
Bookmarks are not saved.
(When I Set, then Goto bookmark, it comes to an empty playlist.)
Menu scrolling is sluggish during caching
(Just after changing songs with skip, more of an annoyance than a bug...)
Posted by: wfaulk
Re: Bugs in V3 A10 - 22/07/2005 20:13
Quote:
Playlist is not remembered between reboots
(Every time unplug/plug the empeg, it starts with an empty playlist)
Bookmarks are not saved.
(When I Set, then Goto bookmark, it comes to an empty playlist.)
Assuming you have a very large playlist, that's a known problem fixed by this hack.
Posted by: elperepat
Re: Bugs in V3 A10 - 22/07/2005 21:19
Not having the empeg near me, if I remember correctly, I have about 6000 items in down-down-down playlist, and no more than 20-30% of the fids are in more than one playlist.
Posted by: SE_Sport_Driver
Re: Bugs in V3 A10 - 22/07/2005 21:52
That empeg_set_max_fid_v7 hack is a great one though. Give it a shot.
Posted by: Defiler
Re: Bugs in V3 A10 - 23/07/2005 02:09
The 'scan frequency' (press and hold the left or right button) feature isn't working in the tuner for me.
Other than that, all systems go so far. Seeking and track-switching for FLACs seems to be much improved, and I can finally seek cleanly in Ogg Vorbis files.
Still not as fast as MP3, but acceptable.
I also had some problems with the post-upload stages (rebuild, reboot, etc.) of jEmplode, but not much worse than usual, so that might just be a coincidence: only about one sync in five is error free for me in jEmplode, on either of my empeg units.
Single HDD, Hijack v435 with ext3 filesystem.
Other than that, all systems go so far. Seeking and track-switching for FLACs seems to be much improved, and I can finally seek cleanly in Ogg Vorbis files.
Still not as fast as MP3, but acceptable.
I also had some problems with the post-upload stages (rebuild, reboot, etc.) of jEmplode, but not much worse than usual, so that might just be a coincidence: only about one sync in five is error free for me in jEmplode, on either of my empeg units.
Single HDD, Hijack v435 with ext3 filesystem.
Posted by: mlord
Hijack v436 -- removed v3a hacks, modifed i2c fan control logic - 23/07/2005 12:59
Great news, Peter!
I wonder if the functionality of empeg_set_max_fid_v7 should go in.. or not. I suppose it's easy enough to run once after upgrading.
Meanwhile, Hijack v436 is out. The major changes are:
(1) Slightly cleaned up i2c code (internal protocol for DSP and fan controller).
(2) Fan control logic now continues with setup regardless of errors, and also prints out (serial console) current temperature reading at startup.
(2) Removed "lavatory floor" visual recovery code, since that visual is no longer present as of v3a10.
(3) Removed "previous visual" workaround code for the v3alphas, since this function is now present again as of v3a10 (works great!).
Cheers
I wonder if the functionality of empeg_set_max_fid_v7 should go in.. or not. I suppose it's easy enough to run once after upgrading.
Meanwhile, Hijack v436 is out. The major changes are:
(1) Slightly cleaned up i2c code (internal protocol for DSP and fan controller).
(2) Fan control logic now continues with setup regardless of errors, and also prints out (serial console) current temperature reading at startup.
(2) Removed "lavatory floor" visual recovery code, since that visual is no longer present as of v3a10.
(3) Removed "previous visual" workaround code for the v3alphas, since this function is now present again as of v3a10 (works great!).
Cheers
Posted by: larry818
Re: Bugs in V3 A10 - 23/07/2005 13:07
Quote:Quote:
Version 3 of the player uses utf-8 internally, but the used fonts lack japanese glyphs.
FITNR (for the larger font; it's not really possible to display Japanese in the smaller font).
Will there be traditional Chinese font in the next release?
Posted by: alex25
Re: Bugs in V3 A10 - 23/07/2005 14:28
Here is more input from my trip today (about two hours)
The player was in tuner mode all the time. I had four spontaneous reboots during that time. Hijack displayed a message sigkill or something like that. Maybe it is the same problem as mentioned earlier: Selecting a frequency by the remote control let my empeg reboot.
Switching between alternative frequency (AF) works pretty good! Sometimes the software changes to an alternative frequency every 5 seconds. But because the interruption is that short this is no problem at all. It never switched to a wrong station during my trip.
But I think there is at least one AF bug. Every time the player changes to another AF the RDS information is deleted (RDS text, RDS station id, PTY). In my opinion this should stay what it is, because it should be the same for all AF of a radio station.
I have not tested the traffic announcement (TA). I think earlier versions of the software had a problem that the AF is not working if in mp3 mode. I you can make sure that the AF works the same in mp3 mode as in tuner mode than everything should be ok.
Hardware: MK2, 64MB RAM, original tuner, 2 drives
Software:V3alpha10, Hijack 435, no other software running
The player was in tuner mode all the time. I had four spontaneous reboots during that time. Hijack displayed a message sigkill or something like that. Maybe it is the same problem as mentioned earlier: Selecting a frequency by the remote control let my empeg reboot.
Switching between alternative frequency (AF) works pretty good! Sometimes the software changes to an alternative frequency every 5 seconds. But because the interruption is that short this is no problem at all. It never switched to a wrong station during my trip.
But I think there is at least one AF bug. Every time the player changes to another AF the RDS information is deleted (RDS text, RDS station id, PTY). In my opinion this should stay what it is, because it should be the same for all AF of a radio station.
I have not tested the traffic announcement (TA). I think earlier versions of the software had a problem that the AF is not working if in mp3 mode. I you can make sure that the AF works the same in mp3 mode as in tuner mode than everything should be ok.
Hardware: MK2, 64MB RAM, original tuner, 2 drives
Software:V3alpha10, Hijack 435, no other software running
Posted by: FireFox31
Re: Bugs in V3 A10 - 23/07/2005 18:41
Quote:
reporting bugs in this thread by Sunday evening
Low priority, not really a bug: Entering the Visuals and Shuffle menus doesn't show the currently selected mode. /me runs.
You guys are great! Thanks for supporting us.
Posted by: JBjorgen
Re: Bugs in V3 A10 - 24/07/2005 12:19
Quote:
Menu scrolling is sluggish during caching
(Just after changing songs with skip, more of an annoyance than a bug...)
It may just be my player, but on my 32mb MK2a (stacked method), all visuals and scrolling text are very sluggish while caching. Playlist of maybe 300 fids. Let me know if I can get you any debug info.
Posted by: Shonky
Re: Bugs in V3 A10 - 25/07/2005 06:19
Quote:Quote:
Menu scrolling is sluggish during caching
(Just after changing songs with skip, more of an annoyance than a bug...)
It may just be my player, but on my 32mb MK2a (stacked method), all visuals and scrolling text are very sluggish while caching. Playlist of maybe 300 fids. Let me know if I can get you any debug info.
Menus sluggish is "normal" (in the sense that everyone has it I think). The play software temporarily froze everything while caching. Mark did some kernel magic in Hijack to make the caching part yield so the rest of the system was more (relatively) responsive.
For my report:
When using the search feature I can't "queue" up letters. If I enter letter while it's narrowing down the list of matches it seems to get lost. So I have to keep looking at it to see when it's ready for the next letter. Appeared in v3 it would seem but I couldn't say when.
Posted by: JBjorgen
Re: Bugs in V3 A10 - 25/07/2005 10:52
Quote:
Menus sluggish is "normal" (in the sense that everyone has it I think). The play software temporarily froze everything while caching....
Yeah, but this is different...my visuals and scrolling info slow down to like 1 or 2fps until (I assume) it's done caching, then everything runs at normal speeds. It may not be the caching though, many times it goes through an entire song like that.
Posted by: mlord
Re: Bugs in V3 A10 - 25/07/2005 11:12
That sounds like the caching issue.
Without Hijack, the player basically locks up until it finishes the read-ahead. With Hijack, it is very slow as described, but at least it does respond to button presses.
Cheers
Without Hijack, the player basically locks up until it finishes the read-ahead. With Hijack, it is very slow as described, but at least it does respond to button presses.
Cheers
Posted by: peter
Re: Bugs in V3 A10 - 25/07/2005 14:49
Quote:
Will there be traditional Chinese font in the next release?
No. We looked a while ago, but couldn't find a free one in a small enough size. (Some Chinese characters will work in the Japanese Edition -- the ones which happen to be shared with JIS X0208 -- but many common Chinese characters will be absent.)
Quote:
beeps do not work in alpha10
FITNR.
Quote:
When using the search feature I can't "queue" up letters.
FITNR.
Quote:
Impossible to disable AF.
Believed FITNR.
Quote:
That's an amazing acronym to read.
I can assure you that writing it is even more amazing than reading it...
Peter
Posted by: wfaulk
Re: Bugs in V3 A10 - 25/07/2005 15:20
Quote:Quote:
That's an amazing acronym to read.
I can assure you that writing it is even more amazing than reading it...
Good, because I was getting a bad feeling about what it meant, honestly.
Posted by: mlord
Re: Bugs in V3 A10 - 25/07/2005 17:30
v3a10 & v3a11: The Anna-VU visual (and possibly all others, as well) is "muted" when in FM tuner mode. It rarely, if ever, bounces beyond 1/3 scale. Earlier v2 releases had much more animated visuals for tuner mode.
I wonder if this can be fixed in Hijack, by adjusting the gain on the sampling input that drives the visuals ?
Cheers
I wonder if this can be fixed in Hijack, by adjusting the gain on the sampling input that drives the visuals ?
Cheers
Posted by: larry818
Re: Bugs in V3 A10 - 30/07/2005 13:05
Quote:
No. We looked a while ago, but couldn't find a free one in a small enough size. (Some Chinese characters will work in the Japanese Edition -- the ones which happen to be shared with JIS X0208 -- but many common Chinese characters will be absent.)
If you give me the spec, I may be able to find a font. At least I'd be willing to do all the legwork.
Thanks,
Larry
Posted by: peter
Re: Bugs in V3 A10 - 30/07/2005 13:44
Quote:
If you give me the spec, I may be able to find a font. At least I'd be willing to do all the legwork.
Eight pixels high (in a nine-pixel cell). If you found a pan-Asian one, that would be even better, as now that we're Sigmatel we won't be able to make any more car-player releases with that Japanese font, for licensing reasons.
Peter
Posted by: webroach
Re: Bugs in V3 A10 - 30/07/2005 18:49
Would this font be a possible solution for the Japanese end of things? I've used a version of it on my Palm for years. I'm also looking for a Chinese font.
Posted by: Major_Sarcasm
Re: Bugs in V3 A10 - 08/09/2005 18:24
Quote:
beeps do not work in alpha10
Quote:
FITNR.
And you did! Thanks
Posted by: JonnyGee
Re: Bugs in V3 A10 - 26/01/2007 13:51
I keep seeing these kinds of issues with ffd/rew. All the seeking (jumping around) is loading the CPU to 100% and there's none left for the UI thread to handle the button-up message.
Maybe Peter or one of the other staffers on here could try adjusting the settings near the top of LACF, to increase the time between seeks. Maybe also increase the initial jump size so the "effective velocity" is the same.
The timings I picked were based on what sounded best, but if the CPU ain't fast enough - tough luck!
Cheers, John
Maybe Peter or one of the other staffers on here could try adjusting the settings near the top of LACF, to increase the time between seeks. Maybe also increase the initial jump size so the "effective velocity" is the same.
The timings I picked were based on what sounded best, but if the CPU ain't fast enough - tough luck!
Cheers, John
Posted by: pim
Re: Bugs in V3 A10 - 26/01/2007 14:51
Never mind, since then, I have re-ripped my entire collection to flac+mp3 and deleted my oggs. The mp3's play (and seek) just fine on my player.
Pim
Pim