Hey guys, thanks for testing this thing wtih me... Riley, interesting thing about the 19 seconds...
Well, what now? Is it time to talk to Archos and battle with tech support to see if we can make them understand what's going on here, or should we do a little more testing first?
YES, definitely. I've been calling them and emailing them, with no real results. it takes a few days for them to answer each email, and I don't think the same person is reading and responding to my emails. and the phone conversations I've had with them don't seem to help either. They'd like to write me off as an isolated case. I think it would be great if everyone who is testing this thing calls and emails them and bring to their attention the deficiencies that currently exist, and that could probably be fixed with firmware updates...
I think the first priority is to get it to reliably record at 16/44.1 and 16/48. once it does that, maybe we can get them to record 24/48 and 24/96...
if anyone has any more test results to post, keep them coming. and also, please post if you have any positive (or negative feedback from archos)
I ran another quick test last night. I generated a 5 second 440Hz wav, put it on repeat, and played it analog out of my computer, into the V3, then digi into the Gmini. I recorded this for just over 10 minutes. I wasn't testing for bit-accuracy, but simply the glitches. I had the same results, although I didn't take the time to note exactly where the glitches occur. sometimes the glitches were just one sample, but I've seen errors up to 6 samples in a row. usually happens in both channels, but, again, I've seen it in just one channel as well.
I may take it out tonight, because, hey, what do I have to lose? if anything, it will be a good test for the battery.
and +t for everyone else who's also testing this
> Jason