bangraman

It's not so much a Vista issue as an A80x issue. A straight UMS file transfer of a 150Mb file takes 1 minute 45 seconds on the A808. It takes 29 seconds on the Cowon D2... ... In XP. And the D2 is definitely not the fastest-transferring 'real' USB2.0 MP3 player out there. And an update - on Vista Business 32 on another PC (a laptop), its 1 minute 47 seconds and 32 seconds respectively. Chronicstage definitely adds it's own delay, but in this case it's just adding a minor insult to major injury. After even going to the length of building a purpose-specific PC to sync Sony devices and suffering with Chronicstage, I finally had enough of all the hoops that are placed in your way by Sony because of incompetence and a general lack of smelling the coffee. I'm keeping the A808 purely as a mini iPod-format video podcast player (since I can't be bothered to transcode them for the D2) only until the new iPods turn up, and the RH1 just in case. Everything else has already been given the boot, and the purpose built Chronicstation has had Chronicstage exorcised from it recently. Good riddance to (good looking) bad rubbish which also doesn't deliver in the sound quality (i.e. not how much bass it produces) stakes. I'll return to the Sony fold when... or if... they ever get their act together.

Among the other issues listed, Chronicstage also has problems with larger libraries. I accidentally came upon this by trying to figure out why some forum members had no problems and why others (like me) had terminal problems. The upshot of that was that Chronicstage can only successfully manage around 8,000 tracks before performance starts rapidly tailing off. I'd first check that you don't have more than this, then work with other possibilities.

Just wondering if this would make Chronic go any faster for larger libraries.

I don't think so - at least, not in the case of the iPod. They have enough flexibility in their players to be a viable proposition even along with an MP3-phone (especially one not made by Apple) in a way that for example a Sony player isn't.

No they don't. Sole reason that the EX90's are total deal-killers for me is the lack of any isolation. Other than that, a pretty decent sounding pair of in-ears and I found them extremely comfortable.

Yes.

Well, I have some sort of resolution to my issues. Thanks to a couple of posters on Head-Fi, who I worked out had similar library sizes, I figured out the maximum practical library size of Chronicstage. It's about 8,000 tracks, which at a typical 160-192K ends up about 40Gb. Having thrown in different bitrates, it's clearly the number of tracks that is the issue, not their sizes. Below this level, I have to say Chronicstage is not so Chronic - if you disregard it's inherently inelegant and rudimentary nature - and does what little it does quite smoothly, provided you don't have other compatibility issues. Other compatibility issues included additional codecs and media splitters being present on your system, but those issues are already covered and known. I'm not sure if the ~8K track soft limit (by soft limit, I mean that Chronic will continue to work beyond this point but gets slower and slower) has been discussed before, but this is my finding so far. I'm now assuming everyone who has no major issues basically has less than 700 or so albums in their Chronicstage implementation. The count may be tied to your disk / processing power too, so I am not 100% sure that the ~8K limit applies to everyone else. Library management in Chronic is still unwieldy though, so I would hesitate to call this beyond 'barely usable' as far as the industry state of the art is concerned. However I have now discovered that the terminal slowdowns are avoidable, which is good news.

Some updates: The 8800GTX has been replaced by a 7900GS. Much more stable in sleeping. In fact, I'd probably say fully stable as I've not had a display-related issue since putting in the 7900. Clearly overkill was a bad idea. I did not install the X-Fi, but rather have put a spare Fireface 800 on here for the occasions that I may want to listen directly from this PC. Once again, seemingly no driver issues. The prognosis for general everyday usage: Very slow. This is with a 14,000 track library, a subset of my main library. I can imagine that if I put my full library on here, Chronic will probably choke. iTunes and j.River have no issues with my main library but that's beside the point at this stage. The slowness is not so much in the library listing, it's the pauses between doing anything at all that gets me. Significantly less than the Dells I had it running on for sure, but just the accumulation of these pauses when navigating folders, loading the player, unloading it, etc is really starting to get to me at the moment. I'm a bit incredulous of comments made in forums saying they're perfectly happy with this kind of response. For MD users it's unsurprising since the speed of their transport has to catch up with even Chronic, but for flash/HDD player users who have apparently used other machines, I find it hard to believe that this is acceptable if you have more than a handful of albums in your library and you refresh them on a regular basis. If anyone has speeding up tips, please post'em.

My vote is for the A80x. There's more subtle detailing in the design over the boringly 'old Sony' HD1/3 and the cool looks extend to the UI as well as the casing.

There have been some bulbously ugly MD's from Sony, but I don't think there's been anything NW which I've hated in terms of how they looked. Even the Bean. The HD1/2 were the most silly to use though.

Er... my view seems to have gone all weird, I can't see the replies....?!? Right, if anyone's answered this before sorry for the dupe, but for one of the easiest solutions you can use Autoplay Repair (http://www-stud.uni-essen.de/~sddabacz/prog.php?id=apr) which will allow you to add to the Autoplay dialog.

No. Unless he uses Boot Camp / Parallels to run Chronicsh*tage which will be pretty painful, especially so for a Mac user.

Not 100% sure about this but does Image Converter need additional codecs to translate iPod Video podcasts? I could swear that stuff I could transfer on my non-Chronicstation to the A808 now can't be transferred. Specifically, the dl.tv podcast using the iPod Video/PSP feed. EDIT: July 1st 07: I'll answer this myself. The answer is yes. Absolutely moronic then that they don't bundle Quicktime or a Windows codec for codecs that are supported natively on the A80x with the Chronicstage disc. Just... morons.

What, just like you had inside info to get the beta gapless firmware for the Zen Vision M? Bwahahaha, happy Photoshopping On a related note to this thread, I think I should have a countdown thread: "Countdown to bangraman having a Chronicstage-induced aneurism". This is the first time I've seriously used Chronic day in, day out in about two years and it really is still a remarkably crappy piece of software. The one thing it really succeeds in is to kill off a significant percentage of the musical enjoyment to be had resulting from the convenience of having your music digitally and centrally stored. However, it is helping my diet as I'm sick of doughnuts, seeing it all the time on Vista + Chronic.

I'm curious where you get all this from.

I'd go against the grain here (of course) and say that the latest iPods have slightly better sound quality, but notably inferior flavour (adjusted tonality). Whether your ears are sufficiently tuned to be able to - or choose to - separate the two is something else. For me, as I almost never touch the EQ on a player unless I'm trying to compensate for tonally flawed phones such as the E3/4 Shures or Etymotics for example, the former is more important. Neither player features what could be called 'bad' or even 'mediocre' SQ however.

I received the Elite Pro today so will fit it and hope that nothing goes kaput. The 8800 in Vista is not good. Fails to come out from sleep about half the time. I'm going to have to buy another card after all.

If you saw my home office computer layout you probably wouldn't be saying that :-p Seriously though the main problem with a 24+ monitor at the moment is the lack of space for yet another wide monitor on my desk arrangement and more seriously, I was not intending to spend any more than this on something that will do practically nothing else but sync portables (or more specifically, Sony portables since other players are pretty happy coexisting on any of my other systems). iTunes is perfectly usable without additional aggravations on a 17", ditto for j.River, it's just Chronic spoiling the show... yet again. I guess I'll have to live with this until I think of something else, or if someone figures it out before I do.

Well yes, having temporarily tried it on 20, 24 and 30" widescreens the problem is that Chronic only shows the display I want for the Library in the Transfer screen *as default* at resolutions of 1920 horizontal or better. i.e. ~24". I must say I wasn't planning to dedicate this much resources to the Chronicstation...

I asked Sony whether this was possible a while back, when I came across this problem on a laptop. I was told no. By split location, I mean the split ratio between the library and the player area in the Transfer window. As you probably know, you can drag this across to favour the library or the player display... but it doesn't 'stick'. You may have read my other post in this subforum regarding putting together a machine specifically for Chronicstage. The PC is running with a Dell 1708FP monitor at the moment, and the library details in the Transfer window that is visible as default on a 17" screen isn't wide enough. Convenience is paramount to me and I am not moving the slider over every time I boot Chronicstage. The easiest way to solve this would be to buy a 24" or over monitor for the 'Chronicstation' which will show up the information I want, but I'd rather not do this as it's otherwise not necessary. Is there a way to get the split location to save? Thanks.

So... the Chronicstation is up and running. Slight problem with the chosen PSU as it happened to be dead, so I cracked open a spare new Tagan 800W supply. After a brief struggle with NVidia's finest (but not in terms of driver support) and after a pang of regret that I should have actually bought something more basic and better-Vista-supported, it seems to be a stable build. The issue that is left is indeed entirely down to the 8800GTX and I may elect to buy something else. Response of Chronicstage is... acceptable. No more, no less. It does definitely feel sluggish, but it is not unacceptably slow as on the Dell H2C and the Precision 690. So clearly it's a software compatibility issue with whatever I have already on the Dells. However, it is merely on the 'man it's slow' side of acceptable even in absolute terms, and since totting up the spec of this machine it sits comfortably alongside that of $2500-class gaming machines from Velocity Micro / etc. that strikes me as rather ridiculous as far as the performance of Chronic goes. However, it does actually achieve what I set out to do which is to make Chronicstage usable (from my point of view, not necessarily yours) so I think we can cautiously call the Chronicstation a success. From now, I'm going to play around with how much and of what subsystems Chronic is actually making demands on this machine to see if I can speed up any element of how it works. One problem with the P5B is that the onboard 'high definition' sound is, like most other Intel HD implementations, quite mediocre even for casual use - they may have respectable codec specifications but somehow the analog side ends up 'meh'. I'm tempted to stick an X-Fi in here but would it muck up Chronicstage? I don't see why not but... well, I never know with Chronic. What do you reckon?

As I alluded to in a roundabout way, the way to go which appears logical to everyone else who actually uses their wares and the way that Sony goes is not always the same direction. We can but hope otherwise. Chronicstage is not a bad tool for absolute beginners as I've said before, but the vast majority of people outgrow it's hand-holding, which is in reality only a mask for it's slowness and inefficiency, very quickly. It's not actually impossible to salvage it and to at least put it on a par with other library managers in terms of everyday usage, but it needs someone with a clear vision to lead the project... someone they don't seem to have at this time.

It isn't for me. What do you do? Dip them in yoghurt?

Yeah... lack of joined-up thinking yet again regarding Image Converter. Build a halfway usable RSS reader/loader, and limit it to movies. Great. Autohotkey doesn't look like a bad way to go, if only Chronic didn't take so long to do that particular task. I could actually do the same thing in Winbatch, only it would probably spoil my 'Chronicstage only' setup since I was too cheap to pay for the compiler. I'm going to give it a go after I put together the Chronicstation and see just how bad the startup time will be with my cut-down library. The 'no new files' error is one of those absolutely moronic things that just serves to illustrate the hopelessness of the Chronicstage programmers...

i duno den. o, lrn 2 spel & punkchu8 az wel