Messed up track numbers using dBpowerAMP

[Unregistered]

hey, i recently downloaded the newest version of dBpowerAMP and decided to convert some of my larger sized songs into 64kbs wma format. this worked fine, although when i open my Rio Music Manager, i look at the track numbers and they are in the original order; although the numbers are no longer 1, 2, 3 etc. They are high numbers (for instance, 3145778 is a track # for one of my songs). if there is an update or fix it would be much appreciated.

-max

[Spoon]

Re: Messed up track numbers using dBpowerAMP

Probabbly a bug in Rio Music Manager, try adding those WMA files to Windows Media Player, I bet they are ok.

[Boxall]

Re: Messed up track numbers using dBpowerAMP

Same problem. Many apps are not setting the WMA track numbers correctly including this one.

When you dump these files to a Nomad Zen the tracks play in the wrong order as well.

[boxall]

Re: Messed up track numbers using dBpowerAMP

I have noticed WMA tags get messed up in LOTS of apps. But in the end I have been using MediaMoney and mp3tag to correct them.

Hopefully the music rippers will get it right soon.

If the track numbers appear wrong in MediaMonkey and MusicMatch then I know they will be wrong on my Nomad ZEN.

[figster]

Re: Messed up track numbers using dBpowerAMP

I had the same problem after downloading and purchasing Sveta and using it with my Nike audio player. The program screwed up all the tracks, screwing up the ordering.

The program also corrupted my existing song list and it hogs the memory on my memory sticks, gobbling up huge amounts of RAM, preventing it from being accessed or writtent to correctly with updated songs.

The only way around this has been to format both the internal and the external memory/media and then go back and use the original software the MP3 player came with: Rioport Audio Manager. This program compresses the songs and keeps them in the right order and allows all the songs that were downloaded to be played, without skipping tracks.

Solutions?

[Spoon]

Re: Messed up track numbers using dBpowerAMP

2 different things here, the WMA track number is going to be looked at soon.

For the Nike a new WMDM driver is going to be created.

[figster]

Re: Messed up track numbers using dBpowerAMP

That's great news for the Nike Player. Please remember to include the one I have: it's the PSA[120 that was made about 3-4 years ago. I still prefer the Nike to a brand new mini disc recorder I bought because the Nike/Rio device sounds the best..extremely loud, crisp, sharp with full bandwidth. I even compared it to other brands on the market and the Rio products came out way ahead in overall quality of sound output.

I cannot wait for the new fixes. I just recently upgraded my memory media to 512 MB; it costed me a fortune but I managed to get it to work in that it reads the full stick but the player will only play 4 out of all the tracks (potentially up to 180+ tracks plus the existing 30 in the internal memory). Thinking about those numbers makes me realize that this amount should be sufficient to keep me from having to invest a fortune in an IPOD or any other player. I generally don't really like to listen to more than a dozen or more tracks anyways.

It'd be great if you can write the updates to allow better file handling for the Nike. I have noticed these problems 1) the song list is screwed up when using Sveta, 2) the file format that's transferred is not in the same format that the Nike/RioPort Audio Manager generates (the file types are different: mp3 vs. unknown Nike format), and 3) my player will recognize all the 500 MB on the new stick but will only play 4 (about 12 MB) of the tracks on the new stick. To me the latter sounds like a software bug that is affecting the transfer of the tracks to the unit.

I hope you can take a look at this. I still like my Nike player despite so many of the other options on the market because I can go running with it and throw it around in my backpack or pockets without worrying about it getting damaged and it sounds simply awesome.