Sony NWZ-E370

Rockbox Development > New Ports

Sony NWZ-E370

<< < (15/23) > >>

pamaury:
@mxyzptlk: that's a very interesting finding. Could you send me the file so I have a try on my device please ?

mxyzptlk:

--- Quote from: pamaury on May 08, 2016, 01:28:17 PM ---@mxyzptlk: that's a very interesting finding. Could you send me the file so I have a try on my device please ?

--- End quote ---

First, I've found some other similar issues on older sites, but they didn't have anything to do with Rockbox (or the Walkman). Looks like it was an issue for some who use Mac applications -- I think Quicktime -- to record/mix something. (What I saw was related to music, but the same issue applied.) So maybe this stems from places that use certain Mac tech to record their content?

Second, since my last post, I've tried converting with ffmpeg, avconv, and Audacity, and it doesn't make much of a difference.

Third, though, is that this has since happened with files that were originally recorded at a standard bitrate (128, 96). The thing is, though, the files that cause issues have to be one of two or three in a playlist (so Files >> Podcasts >> Name of Podcast >> multiple files in that directory). It doesn't make a difference if the playlist is automatically generated from what's in a directory or if I make it -- the same problem occurs if I'm listening to a single file from a single directory and add another file to the dynamic playlist -- if there's two or three in that dynamic playlist, the pausing/slow wps issue occurs.

For whatever reason, when there's a load of files in a playlist (like a bunch of stories from NPR or BBC), the pausing/slow wps doesn't happen. But if it does happen, it's with files in a playlist of 2 or 3, and if the file was originally recorded at 127 bitrate, then it's pretty much guaranteed.

So that leads me to believe this is all down to how Rockbox is handling files in a playlist, particularly when there's only 2 or 3 files in that playlist.

Here's a file that was recorded at 127 -- a rugby league podcast from a radio station in Australia:
19/05/2016 Rush Hour Podcast

And here's one that wasn't recorded at 127, but still threw the pause/slow wps problem when in a playlist of two (Rockbox shows this as 96 kbps):
Rationally Speaking #115 - Maarten Boudry and Massimo On the Difference Between Science and Pseudoscience
(That file was in a single directory with one other file, so two files in the playlist, and it caused the same issue.)

--------------
EDIT
--------------

Yeah, so the pause/slow wps problem definitely a playlist issue, and occurs whenever there is more than one but less than four files in a directory or in a dynamic playlist. This always occurs with files that are being read by Rockbox as 127 kbps, and almost never occurs any other time (but has at least once with the file above).

I did some experimenting, and put four files in a dynamic playlist. All were files that Rockbox shows as having a 127 kbps bitrate. All of them have given problems in the past, locking up the device and necessitating a hard reset (the file still plays, but the device becomes unusable until a hard reset or the file ends). Three of them come down as three separate 1-hour files in a 3-hour show, and the other was a different podcast.

The three have always given be trouble since I put Rockbox on the device. Always. But when I added all three to a dynamic playlist along with the fourth 127 kbps file, there were no issues.

And as noted above, this also occurred at least once with files that have a normal kbps. I've just rarely had occasion to have only 2 or 3 normal kbps files in a directory/playlist, so didn't notice it until recently, and thought it was only an issue with the 127 kbps files. (And to be clear, it doesn't always happen with normal files -- I have a two-file playlist going now, the two files are 64 kbps, and there are never any pausing/slow wps issues with them.)

So that seems to narrow it down to the way this spin of Rockbox on this device is dealing with playlists: If either the number of files in a directory or the number of files in a dynamic playlist is only 2 or 3, that seems to trigger the random pausing/slow wps issue that locks up the device, especially if Rockbox reads those files as 127 kbps instead of the standard 128 kbps.

pamaury:
Hi mxyzptlk,
I have been trying to reproduce the play/pause issue on the NZE-E380 with your files but no success so far... I tried to put your two files in a directory and play them, I have try to add them one by one to a dynamic playlist, but didn't trigger the bug. Do you have any specific procedure that triggers the bugs reliably and quickly ?

mxyzptlk:

--- Quote from: pamaury on May 31, 2016, 06:55:50 PM ---Hi mxyzptlk,
I have been trying to reproduce the play/pause issue on the NZE-E380 with your files but no success so far... I tried to put your two files in a directory and play them, I have try to add them one by one to a dynamic playlist, but didn't trigger the bug. Do you have any specific procedure that triggers the bugs reliably and quickly ?

--- End quote ---

Just the files that are read by Rockbox as 127 kbps when there are 2 or 3 in a playlist -- those always trigger the problem, every time. Those same files are always read as 128 kbps on the computer, but Rockbox reads them as 127.

The times are also screwy on those files: When the time reads 0:00 at the end of a file, the file isn't actually done and the time will go negative, so like -0:30, -2:10, etc. And if you skip ahead on those files, it'll actually go backwards first and then start skipping forward on repeated skips.

Normal files generally don't have that pause/slow wps issue, but on a couple of occasions, I've experienced the same problem with files at 128 kbps and with 96 kbps, and always when there were 2 or three files in a playlist -- never with 1, not with more than 3.

If I reset the device as mentioned above (in the settings, not the hard reset), then that issue doesn't happen for a short while, but always starts again after a few days use. But it's been a long time since I've done that, so I haven't reset the device and then tried deliberately triggering the playlist issue.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version