Well ... what a coincidence ...
Yesterday evening I closed *my* GoogleDesktop because I estimated that it could lock files I couldn't read from the Vista machine (which is a big misery anyway), and today it is still closed *and* I could upload the testfile.
I will try it again with GoogleDesktop running ...

Another thing : during the download (so, your track08) all the time the server seems to hang. So, still things to do ...

Now I will listen to your track. 

It works with me (at a download speed of 3000kbs or so (and upload overthere is 1000)).

It took 5 minutes or so.

Marco, do you recall the message om the screen ? or did it just stop ?

It should work now though ...
I go home in a few minutes, and then I will try again myself.

And while I'm writing in this thread anyway ...

Yesterday I achieved the most important "thing" for more or less convenient playback with #3. So for that matter it's ready to go. But :

What is left to do, is stripping the development environment as much as possible into a clean runtime environment, in order for "you" not needing stuff you wouldn't even be able to get. I'm not sure yet what it takes to do so, but I can imagine that it's done before the weekend, or otherwise in the next coming weekend.

 

Haha Chris, that's okay.

But please let's workout the major stuff first with Tor, Jack and Bert. This won't be a case of "me helping you", but merely "you help yourself, and with that me hence everyone".
I'll use you to finetune !! Haha. But if all is okay, you will get it right after the "tests" and my ability to write down what to do.

Hi Marco,

Could you please try it once more ?
Currently I can't because I'm too near to that server, and 20MB goes in 1 second ...

If you can do it before 5 hours from now (watch the posting time), we can adjust things before people go home here (and otherwise it will be tomorrow, which is okay with me).
Thank you !

All those combinations ... 

Well Chris, I don't think I even ever tried #2 on Vista. Possibly that is because (for me) theoretically it shouldn't differ for quality from #1 (but I know it does), while it has less functionality once Doubling is not applicable (like with Vista).
But another thing is : what did you set your sounddevice samplerate to in Vista ? Remember, properties of the device (after click on the loudspeaker icon in the taskbar tray), the rightmost tab and the combobox in there.
Set that to 96 and it really will be different again.

Note that you can check what it's really doing by means of the Fireface properties form (yellow icon).
In Vista you should get used to always doing that checking (with #1 & #2) because it's really the Vista setting determining it (mentioned above).


Now what comes to my mind for the first time ...
People like Klaus reported better quality with 48KHz (and offline resampling). This can be true for theories easily, once you know that the DAC's clock itself runs on a (MHz range) rate that suits the samplerate ... or not. For 44K1 it might be more not ...
Now, since I am used to 96K on Vista anyway, I might just as well resample to 48K ... uhmm ... *you* might just as well Chris.

I myself am always listening to #3 lately and I really need my time for that.

Uh-oh ...
Today I tested it with a high speed connection ... wrong.
Now it times out.

This just isn't made for this. Must find something else.

Uhhm ... the Fireface should be shut off (10 secs or so) and on. That is, for the firmware.
For the driver it's the PC.

That sure is so Chris. But : where did you get the old drivers from ? from the withgoing CD I suppose ...
Those are way old ! (and indeed cause the problem you describe).

Go to this page : http://www.rme-audio.de/en_downloads.php?page=content/downloads/en_downloads_driver&subpage=content/downloads/en_downloads_driver_fireface

Look whether you need new firmware first before you actually upgrade; If you download the driver there will be a readme where (usually) the needed firmware is shown.
Think about a structure to keep the old versions for future needs, because it may happen that a new driver doesn't sound good.
Note : I'm on 2.63a for the 800 and I don't have problems with it.

Okay ... there was some internal limit of 2MB. If everything is allright you can do 25MB now (but you should do not more than some 20MB ).

Hi Werner,

So did you do the things in here : http://www.phasure.com/index.php?topic=11.0 ?

Peter

Haha, this was merely about rooms, not about systems.
The only "system" for that matter where I found it working just the same (and others weren't tested) were my own Infinity R90's.
No difference ...


Oh, the cable thing was just an I think well known example, and I compared it with the other stuff ...
I think your (and anyone's) cables are unrelated to *this* matter.


You can always try it, with having in mind that (apparantly) before you didn't like it anymore and switched.
It's no matter of life and death, and long as you are "able" to decide for yourself what to use when.

Maybe you find it of interest that I use my two subwoofers all the time (upper cutoff is equalized with the bottom of the BD15s), and I too have a processor (for room correction) for the subs which I used before ... I just don't need it anymore. Not even with the 2 subwoofers.
Btw, you may have read that (out of all  ) Bert activated his subwoofer as well (which is a rather huge one), and the only thing he does is getting the xover right by means of a processor.

When the DAC you used is the same (or better : when the whole chain after the PC is the same as that after the CDP), then, yes, I would dedicate that to more dynamics (and you probably read my descriptions about that). But *was* the chain the same ? I can imagine that with the CDP you at least didn't use the Fireface ...

Then, at using the Fireface, be careful dat the sliders are at the 0dB position. You can easily get them there by means of ctrl-click on them.
Higher is dead-wrong, and lower is not good also !


Remember that there's nothing explicit in there, and all (my theories) is bound to "when it's good you don't need external corrections".
Since this, so far, works everywhere, and I don't expect you to reside in a concrete bunker (where it wasn't tested yet your conclusion should be : then there's other things in my system not optimally working.
And Chris, I don't say this to be right or for a whatever unreal reason, I say it because it works everywhere, and when it didn't it was always solved by searching for the culprit as long as it took to get rid of the room anomalies.
I *know* that your TacT will do it better in the case there's something going on, just like the TacT will get rid of the anomalies at using Foobar. So the real message is : don't use filtering cables to get rid of harsh highs and find the culprit instead, which would be in the same leage as saying : don't use your TacT and find the real culprit instead (no matter how unbelieveable it comes to you).

Of course you remember the nos-DAC thing (as a prerequisite to let it all work(out)), so here is reason #1.
But of course again, in your situation it would be a rather awkward solution, because the first thing you'd have to do is get rid of the TacT as well. That is, you'd be only allowed to let it pass through everything 100%.
Also, do note that squeezing out the peaks is different -and not as bad- as pulling up the dips, and that dips of 0dB SPL exist which just can't be amplified (1000 x 0 = ... ?).
Might you be able to get hold of an nos DAC loaner, don't hesitate to try whether I could be right ... 
If I am, it would be worth it. You know that ... 

Thank you for this information Chris.

The read cross can happen, and currently I am not sure what it exactly need to let it do that. I had it myself for three or four times.

When you start XX and it is minimized to the taskbar, this usually is the result from minimizing XX and then close it (rightclick on the icon and X). Now, since the player remembers its location and size, it redoes that at the next startup. And there you go ...
I really must fix that, because its very inconvenient (though rather standard Windows behaviour). I think I can fix that anyway.

In the end it is sure not needed to do as you did : reinstall so many things;
The unobvious thing to do is maximize XX (rightclick - Maximize), followed by "redo previous size" (which just would be clicking the square box in between the minus and the X at the right top of the form), followed by dragging the form to a convenient position.

The rapid ticks as you described are, as far as my experience goes, due to Fireface anomalies. It can't have all the stuff fed we feed it with, and sometimes it goes bananas of it. Not that far more dangerous is the situation that just no sound comes from it, so you don't get on the path of switching it off and on. But that too can happen.
What remains is what caused it in your situation, and which well can be a derived situation from you leaving the player sit for 60 minutes, while before that it should have timed out because of the demo version. However, I did not explicitly anticipate on it quitting from the situation it's not playing anything, while you incurred for that. I will look into it.

Maybe superfluosly : never start to get back to restore points because of something you think was caused by XX. It just cannot, and I never experienced it. It can look like it though, but then better try to ask the question here first, in order to save you all the troubles.

Thanks again,
Peter