XXHighEnd

Hi Peter,
Yesterday evening I replaced the standard 1 meter USB cabel for the new short Clairixa USB to connect to the Intona Isolator. During the listening sessions i clearly hear some sound disturbances in the music. When checking NOS1a interface (driver v1.0.4b) i see that there were a lot of Fifo and USB errors. Restarts of the PC and NOS1a and reconnecting the USB to the silverstone did not helped. I will replace this evening the short Clairixa for the standard USB cable to see if this helps. Any suggestions for me what caused this errors en solutions? Thanks.

Best regards

Johan

Hi Johan,


Not yet, but a very strict advice :
Write down the current value of each (!!) setting you are going to change. If you don't do that I will predict the next issue : with the old cable it also does not want to work any more.

Now first a question or hint - if not a suggestion :
Is this Windows 8 ?
Coincidentally, when I was testing a few of the last fabriqued cables I was running Windows 8 and it was may more difficult to get it right. I needed to set the SFS to 4.00 because under that it showed what you describe ...
Do notice that I tested all the short cables as intended : with Intona in the chain and a longer Clairixa at the other end.

If you have laying around a W10 install (for the info to others - you don't have the RAM-OS), you can test that and I guess you will see the difference.
Anyway, and of course still assumed this is W8, you can test with the higher SFS (like 4.00).

If from this comes that the Intona somehow can't bear the Clairixa under Windows 8, then we must see how to proceed. But I am fairly sure that Daniel from Intona will be willing to help out.

Btw, are you talking about the Industrial version of the Intona ? because remember, that is the one I advised (read : tested and technically approved).

I hope you can answer upon all the questions and that I was not toooo specalutive ...

Regards,
Peter

Hi Peter,

I'm using Build 10074 of Windows 10.

Yes the industrial version.

Johan

Hmm ...
Clearly I did not expect this.

Another attempt :
Already for some longer, it has become quite difficult to work with 16ms for NOS1 Driver (Control Panel) buffer. So I have that at 4ms. That this should not be 16ms (I recall that this is since Windows 10) was discussed but is very easy to miss and forget. With all the testing I mostly forgot since the default at installing is 16ms.

Can that be the culprit ?

Peter

I'm using the 4 ms for NOS1a control panel.

Hi Peter,
Same issue here, I highly suspect the short Clairixa. Without it no problems!
But SQ is super.....
Regards, Arjan

Hi Arjan,
For me the Fifi errors are audible. This evening I have changed the Clairixa connection from the Silverstone USB port to the the computer USB port. So far no errors and strange disturbances in the sound anymore. I never installed the drivers for the Silverstone card in W10. I don't know if thats the solution for this problem. I have the impression that the sound via the Silverstone is better.

Someone a download link to the Silverstone driver for a W10?

Regards

Johan

Hi Johan,
Audible for me as well, but with a cheap cable no problems.
I will try the other usb port tomorrow.
Regards, Arjan

Hi I woke up this morning and no sound whatsoever. I have just received the Intona and blamed that initially.

The software for the Silverstone was not working.

I downloaded the latest W8 drivers from the Silverstone Web site and all working again. I installed both the firmware and driver and restarted, it all worked. Don't use the driver from the install disk its a problem I believe for W10 although it did work but stopped so not sure what happened.

Here is the Silverstone ECO4-P driver link under downloads for anyone: http://www.silverstonetek.com/product.php?pid=364

Robert

Guys,

Something is going on here and Robert, thank you for your post because it only adds more of it.

With the explicit notice that we should not see ghosts (as we say it over here), I am now at the count of 5 with sudden strange problems. The common denominator is the Intona.

The common denominator is also that it seems that things "break" and can't be reversed. Well, technically and very far sought that may (electrically) be possible, but so far I can't believe that. This is how Robert's post is crucial, assumed he did not see ghosts (from another angle coming in). Point seems to be :

It is the most easy to draw wrong conclusions as the problems are not logical (or don't seem to be as long as we don't understand). But example : At testing the cables I myself had once all out of order and could only get it right after a reboot of the PC (after switching off/on the remainder). To me this tells that things also can work halfly, like in too many errors (FYI this is not far-sought at all).

This is only a lead-in, as I had some more prepared already, but Robert's post must let me re-think a bit first. Anyway I will be having some questions, and I hope you can deal with them precisely.  No matter what, write down your previous settings and I say this because of seemingly irreversable problems I run into just the same (remember, count is 5). Again see the importance of Robert's post ...

Thanks for now,
Peter

Both feet back on the ground, first another observation :

I know from 10074 that there will be many USB or FiFo errors for sure. Notice though that I never checked that so I can only know for real if I start looking at it, which I sure could.

In between the lines I reported about this like "it needs 30 seconds at least to stabilize and then still audible anomalies might occur once in a while".
This has been there right from the (10074) start and all it takes is a lower SFS (I forgot how low but say under 4.00).
The sound of this is a sort of scratching DC-ppplop and people not familiar with the music or even the system (but know the music) may not notice.
Mind you, already this I read about exactly in Johan's post. Also, the fact that you now hear these things can theoretically imply that things are better audible. This really is so.

Then, at writing the very last sentence above I realize that Johan *is* using 10074 (I really did not think about it). So for this (his) situation I can already turn it upside down : Johan, if you can proove to me any setup WITHOUT errors and an SFS of say 0.2 or lower ... be my guest.
Keep in mind : I listened to that for months myself, as it slowly goes away after pressing Play.

That is 10074;
With the others I don't think such a thing is in order, but this very well can be about the sound it exhibits and which is a kind of special with 10074. The anomaly smears there and therefore makes it audible easily. But look :

I already told about my W8 experience and how we had to set the SFS to 4.00 in order not to see errors. Yeah ?
Well, not quite, because with 10586.0 I had to set the SFS to 1.00 in order to not see errors. Mind you, see; I don't hear them anyway (oh, maybe if I want to hear them, but that is not me).

So the danger is - and about seeing ghosts - that if we now all start to measure the USB/FiFo errors, we indeed see them and think things are flawed, while they have been there all the time. But I must be careful with such expressions just the same, because "all the time" for myself would be since 10074 which has been with Clairixa right from the start, and with W8 not because I used an SFS of 4.00 because lower did not sound right.
Do we get the message ?

Sadly you both (Johan and Arjan) see that with a normal USB cable the errors are not there.

Ready for the first question ?
What happens with either of your situations when you set the SFS to 4.00 ?

And Arjan, which OS and how (RAM, Unattended etc.) are you using ?

Peter

Question #2 :

What happens to either of you when you swap your both Clairixa's ? Thus, the long one coming from the PC, the short one going into the DAC ?

I see this. But changed bugger from 4 ms to 2 ms and they where gone.

Just now going back to 4 ms and no errors apear :prankster:

SFS 0.10

 :)

Thank you Gerard.

Another question I have (and it relates to Gerard's post) is :

How long does it take before you see things stabilize ?
So remember, I talked about that for "audibly and 10074" but I am also confident that this happens to you (Johan, Arjan) and everywhere (OSes). Example :

You press Play and right away a pile of Streaming errors pop up. A few 100 more after a second, more afer 5 seconds, maybe a handful after 10 seconds and then it is quiet.

Or :
You press Play and right away a pile of Streaming errors pop up, and that's it.
In this case, think of an audible tick when you press Play. Regard this a Driver error (and virtually my bad but no issue).

Or:
Right away a few dozen USB Stream and FiFO errors show, and that's it.

These situations per definition happen. Here they do and I have to regard them normal.
Still they can stay away just the same, and the higher SFS will "cause" that, usually.

I hope it doesn't need explicit telling that the errors don't automatically reset when you press Play. So keep track of the last score at pressing Play for a next attempt.
Otherwise changing the sampling rate (in the Control Panel)  will reset the count, but always change to a multiple of the sampling rate you play with (like to 88200 (and not 96000) if you use 176400). Otherwise for 100% sure errors will emerge right after pressing Play.

Well,

I got back to buffer 4 ms. Other buffer size give usb and fifo errors too.

But i played a song right now.

1 track no errors

going to the second track first second 742 error counts and the next second 1198 errors.

From second track to the third in the first second 2400 errors.

So in my situation it only happens in the first seconds of the track. max 2 seconds.

 :)

No really,

The 5 track there were some USB and Fifo errors during playback. Really random. But only a few and only one time 2/3 of the track.

If we think back (years), we recognize ticks and such at track boundaries. Well, Unattended assumed (so that is the prerequisite !) :

The sound engine doesn't know about track boundaries; all is concatenated as one super large file (or stream if you want). Still a tick ? then something can not cope with the knowledge that for the sound engine it is one large stream all right, but for the PC it is not as it needs to do more things.

All we can say is that if you'd observe the errors, you can trust your ears when you heard a tick or glitch at a track boundary.

But set the SFS higher and undoubtely you will see a different behavior because you wil stress the PC less.

Also let's keep in mind my own observation about (or thinkering about) a very low SFS : we lose samples. This works so since the before last 1.xx version and the Q3,4,5 at 1 thing (at first it was Q5 only as I recall). So that also allows for the crazy low SFS while things keep on playing - and now instead we may observe lost samples.
But the errors will be all over the place ...

So I say it once again :
At least for 10074 I am 100% positive about the errors because I always heard them, but, it stabilizes (say it requires a minute max).
And in addition to this the crazy thing : no, I never looked at the errors because whatfore; I know they are there (because I hear them).

Peter

Btw :

I already see one "mistake" I make when talking my own observed errors at testing the cables :

We do this with Hires material (24/96) which really matters a lot for stressing the PC. Think 3 times more (compared with 16/44.1).
And it is already known that with Hires the SFS can not be that low ...

Anyway, where I told that I need to set the SFS to 1.00 because otherwise I see errors anyway, this is always with 24/96. I don't even know about 16/44.1 ...

N.b.: I use the 96 because of implying the highest sampling rate over the USB interface (768000).

Peter

Hi Peter,
Updated silverstone driver and firmware, but errors are still there and I always hear them. I now use a normal, but isolated silverstone.
Both in ram or not I get these errors and ticks. Also with sfs on 4. But I now use 0.10 again.
I use 10586, unattended and attended.

Switched the usb cables, short on the dac, but that seems even a bit worse.

Changed the short usb on dac side for cheap usb cable, so long Clairixa on pc, still errors and ticks.
Next cheap usb from pc to Intona, no more errors and ticks!

Final test to be done, use of mobo USB ports, but I have to make them active first....

I think Intona is also part of the issue.....combination pc - Clairixa - Intona.
Regards, Arjan

Arjan, thank you for all this work !

So we need to focus on Clairixa on the PC-Intona side. Hmm ...

I am going to test a few things now.

Thanks,
Peter

Btw :


Would that be ours ? (shipped with the NOS1a)

My PC currently runs at 500MHz.
10586.0 from RAM.
16/44100 upsampled to 32/705600

I can play up to SFS=0.05 without errors (but can be one time a few, fairly quickly after pressing Play).
With SFS=0.04 it goes wrong and Kernel Streaming errors are continuous.

Meanwhile someone is making a 30cm for me ...

Btw, you guys have "Copy To XX-Drive by standard" activated, right ?
Without that it is errors all over the place because of the Network being too slow to pump the SFS trunks fast enough.

The OSes were shipped with that active, but if you deactivated it ...

Yes Peter, the usb cable shipped with the NOS1.
regards, Arjan

Yes, immediate ticks, no sound at all with deactivated Copy To XX... Just dddddddddddddd. If you say this you know.

But the errors are on Kernel streaming/WASAPI and not on USB stream and Fifo...
So different behavior.
regards, Arjan

Correct.

If you have a hint on what could be special (different) between you and me, don't hesitate.
I don't mean our glasses. :)

So I am trying to let it go wrong, but not, so far.

Is that 10074 at your side ?
I will try that now.

My PC currently runs at 430MHz.
10586.0 from RAM.
16/44100 upsampled to 32/705600

I can play up to SFS=0.05 without errors.
With SFS=0.04 it goes wrong and Kernel Streaming errors are continuous.

This is in unattended!

Similar behavior.

regards, Arjan

I can't do a thing actually (I missed the delivery yesterday arrrrggg), but has someone tried to increase slow down the ClockRes or bring back the processor speed at its nominal value (3.2GHZ) ?

Just a thought...

Alain

10074 is not easy for me at this moment because at creating the RAM-OS disks I destroyed something in there (in my own !) and I don't even recall what. :swoon:
But doesn't matter since you use 10586.0 just the same, Arjan.

Anyway, maybe I learned something ...
I went back to 10586.0 but now the BASE boot; I just thought it could be more convenient. Now :

Especially in 10586.0 this is utterly more slow (but PC at 500MHz only of course) but actually so slow that it was the reason to change my PC from 430MHz to 500MHz.
So starting up XXHighEnd takes maybe 4 times longer than when booted from RAM (strange in itself).
And now I really can't provoke any error ... (ok, not in 5 minutes of time).
Not finished yet and possibly premature, but maybe there is a relation.

No, this is unreliable;
Now I have the Kernel Streaming errors randomly, which is logic (for me) because the SFS of 0.12 is too low for the reading of the file which is on disk now. You could say : Oh, this can work with that low SFS but now it requires a normal RAMDisk first.
So never mind.

What we can learn from this is that Kernel Streaming errors are "source" ((slow)provision) errors. So a too slow PC so to speak.

I have been playing around with my new 30cm cable, but I can't let it fail.
Of course it must burn-in or maybe burn-down :) but ...

Generally we can do two things :

1. I send you both a new cable to see whether that helps.

2. Arjan comes over with his Intona and Clairixa (maybe even both) to see whether it's the Intona.

Ad 1.
Not much helpful if it doesn't help.
Unlikely to help.

Ad 2 (a).
Always the most helpful because it can be combined with a new cable just the same, if the Intona appears to be OK.
The latter is unlikely, because the former already is (see 1.).

Ad 2 (b).
Not helpful at all if it appears to be the combination of PC and Intona and cable.
Likely.

---

I wasn't trying to make fun, but reason out chances. And it is not so easy ...
What I suspect is that the Intona is not equal for everybody. Reaons for that are :

a. There is timing involved which is at the nano-second level.
b. Intona is improving firmware because many others (not our group) have issues (can't get it running at all). So what if you received new firmware which now for "us" doesn't work out the best.
c. It is already clear that it is impedance or whatever cable related.

Ad a.
With the knowledge of the galvanic isolation of the NOS1a in similar fashion (but in another (i2s) domain, we know that this is also "external chip" related. So if a delay of say 2ns is required somewhere, then another chip or even resistor etc. can make this a required 4ns delay.

Ad c.
This has been proven by many (in unsollicited fashion) and not even at the high speed we NOS1(a) users use. Read : not all USB cables work (more not than do) which actually testifies about #a. Notice that this is also how the length can matter.

Then we have this as a kind of facts :
- Clairixa-"long" works for everybody;
- Intona with $1 or whatever cable, also works for everybody (so far), except for maybe one that I know of.
- My first Intona didn't work for long, dedicated (by me) to "heat" problems (just a little warm up and the timing changes (too much)).
- All short Clarixa's were tested over here, in a chain similar to your daily use if not 100% the same for many.
- It is only two that don't work but with not too many others around yet claiming that it does work (we sent out 30 short Clairixa's, so that many Intona's should be around too, in our group).

:scratching:

I am just thinking ...
I am pretty sure that everybody with an Intona from our group (so 30 at least) used it for at least a few days by now (if not a few weeks) with his Clairixa at the DAC Side. But I now wonder ... If these same people would have used the Clairixa at the PC side, whether not all (or many) would have had problems ...

Peter

Hi Peter,
Not sure i was clear enough but long Clairixa between pc and intona also gives errors and ticks.
Yes, might be the Intona, but the Clairixa is also involved.

Will try to do a test later tonight with mobo usb. And maybe some other USB cables?

Regards, Arjan

Yes, that was clear Arjan.
I suggested that this might have happened to more people *if* they only had tried (which I guess nobody did).

Peter

Did someone try without the Intona ?

Alain

First there was Clairixa and then Itona. Only Clarixa no fifo and usb errors. The sound of these errors are very audible!

Johan

Not NOS1a but using Intona too. I switched the short standard USB cable and the Clairixia USB cable and compared the transmission errors counted in the USB receiver of the DAC. In both cases roughly the same error count is shown: 250.000 KS transmission packets and 400 KS error packets (should be syncronization). The plugs of the USB cables are isolated with sticky tape to cut the screening reliably and I'm using a standard Intona.

Georg 

I did some tests with W8 (not the OS ramdrive), with and without the Intona. I have a Clairixa USB about 1.5m and a iFi USB cable that came with the iFi iUSB (bought two years ago).

When not using the Intona, I connect PC and NOS1 (not NOS1a) with Clairixa.
With Intona, I connect PC > iFi USB cable > Intona > Clairixa > NOS1.

In the two cases there were errors at the end of the playlist with KS. So for me the Intona is not necessarily the culprit.

But I realized something else. I needed to elevate the SFS and slow down the ClockRes to eliminate some other errors (USB and Fifo). At this point, I still have to compare with and without the Intona though.

Alain

I Have tried all of the mentioned scenarioes, with supra,  entreq and a common usb cable, on one side, and clarixa on the other side. Switched cables from and to DAC and pc-side. I had the same distortion as you. But I gave up trying. Switching between cables and adjusting sfs value. I played with sfs 0,06 and 4 ms.   and I have no distortion anymore.

I tried the mobo usb instead of silverstone with the short clairixa to intona and that works without errors and ticks. So for my setup also the Silverstone is part of the issue.

But I still prefer the Silverstone.... so back to cheap cable between pc and intona.

But oh boy getting into bios to activate the mobo usb was difficult. PS/2 mouse and keyboard do not work..... I first had to reset the bios and boot without hdd attached. With hdd it was for me impossible to get into the bios. But this is another subject.

regards, Arjan

I received the package with RAM-OS disk and short Clairixa cable yesterday.  Spent some time today listening with my standard setup (see signature) and short Clairixa cable between PC and Intona.  No problems, in fact better SQ than using the cheap, longer USB cable I had before.  Not sure this helps anyone, but just some input.

Ah you encounter problems too with the PS2. I think ill buy a new USB card with 4. So I can connect mouse, keyboard and HDD dock. Than the MB USB can turned off again. I also got in when I removed HDD-RAM.

Thanx

People, there is a topic in the Chatter board about a perceived BIOS and PS/2 connection problem. It was named "boot menu" and I just renamed it to "Problems getting into the BIOS (with RAM-OS ?). Here :
Problems getting into the BIOS (with RAM-OS ?) (http://www.phasure.com/index.php?topic=3494.msg37373#msg37373).
Feel free to add to that !

Peter

But of course this helps, because it testifies (or sould do that) that things can work.

Thanks,
Peter

All,

During my testing yesterday, I definitely found that - at least in my situation - the Buffer of the NOS1 Driver Control Panel can not be at 16ms. That is errors all over the place.
Disclaimer in favor of Intona : I did not sort out whether this is "caused" by the Intona and I vaguely recall that this is since the "a" of the NOS1. Anyway that can not work while the install of the Driver defaults it to that.
Side note : the ClockRes appears to be involved in this, as it being at 2.5ms the errors are almost away. So Driver at 16ms and ClockRes at 2.5ms could be an acceptable combination - for me over here at least.

Peter

Hey Arnt,

First off, thank you for sharing, bbbut ... it is not so clear to me what your conclusion and final setup is.
Also, you have the short Clairixa and seem to avoid mentioning that you used that together with your long one.

Is it possible to briefly tell it in a somewhat better fashion ?
Thanks !
Peter

I had the impression that you adviced to avoid the 16ms?

Last evening i Test the following route: silverstone usb>clairixa 1.2m>itona>Clairixa 0.3m>Nos1a and only streaming errors. For me not audible. This was not in unattended mode. I did not switch the voltage off. Order of connecting from pc to nos1a. This morning switching all on still no fifo an usb errors. At this moments not even streaming errors. I red on the site computeraudiophile.com a lot of discussions about the itona and connection problems with different cabels. Someone wrote the connection order and the short cabel on the dac site. Others wrote succes with the $1 usb cables.

I hope i can keep this situation. Today back to unattended playback.

Regards
Johan

Last track of the first cd i had a small hickup and 2496 streaming errors but no fifo and usb errors.

First off, thank you for sharing, bbbut ... it is not so clear to me what your conclusion and final setup is.
Also, you have the short Clairixa and seem to avoid mentioning that you used that together with your long one.

Is it possible to briefly tell it in a somewhat better fashion ?
Thanks !
Peter

Sorry for that, I saw i now that this could be misunderstood.
Conclution is that I continued playing With The Entreq usb to the NOS1a from the Intona, and the long Clarixa from PC to Intona. And did nothing more, after a while, just listening to different Music, the distortion was gone, and has been away since.
The reason I did not mention the short Clarixa, is because It has not arrived yet.

Arnt

Hi Arnt,

So I registered something wrongly or something *is* wrong. But it is a bit tough to find out now for me.
At this moment 4 have not arrived at customers yet and you are not in that list. Maybe it is no big deal for you to forward me your last UPS email (so I know your tracking number and can follow myself). But if all is right that email shows that it arrived ? (otherwise clearly my bad).

Otherwise thank you for the explanation.
Peter

Hi Johan

That is a matter of following the sequence. I mean, if I first say that the 16ms should be avoided indeed because of audible anomalies - which I already said months (if not a year) ago - and if I next only yesterday start to combine with the ClockRes and see that 2.5ms looks to be acceptable (still a few errors, but acceptable) then ...
Then I don't think nothing much is wrong with that.

Something else - or actually not ...
I asked a few questions (in bold) trying to solve your problem and you never answered upon one of them.
Now you don't have no errors but forget to mention how you did that or what you have changed.

This makes me a bit dizzy - as usual.
And if you don't know what happened you can always explicitly tell THAT. Now I still don't know while I still try to help.
(and this takes time)
:)

Regards,
Peter

Peter, the shipping has been in the same destination for 3 days, this is about POSTEN NORGE.
it will arrive tomorrow.
Arnt

Hi Peter

Shoot me, but currently I am listening to the both clairixa's and intona in the chain........

Johans remarks gave me some new ideas. Also now I have the short clairixa on the dac. (I had it running already between the intona and dac for some hours, maybe burning in needed?) I put a separate linear psu on the Silverstone AND I only can use the lower Silverstone connection!!
Also my CPU is now at 1200 because of my bios issues last night. I use 10586.0 in RAM. sfs 0.05 and clockres 1 ms and usb buffer size 2 ms.

To much variables....... do not know what did it, seems a lucky shot to me.

regards, Arjan

The least I should do is tell you both is that I am the most happy that you solved  it.
If you did !!!

 :) :) :)

Qustion: Driver at 16ms, what driver are you talking about?

Something went wrong yesterday in the answering. I wrote two reactions, but they did not arive on the forum. Arjan's reaction was very fast. saterday is a bussy day for me. I did some teste in the night.

I wrote my answer in the same reaction on this forum playback. "Last evening i Test the following route: silverstone usb>clairixa 1.2m>itona>Clairixa 0.3m>Nos1a and only streaming errors. For me not audible. This was not in unattended mode. I did not switch the voltage off. Order of connecting from pc to nos1a. This morning switching all on still no fifo an usb errors. At this moments not even streaming errors. I red on the site computeraudiophile.com a lot of discussions about the itona and connection problems with different cabels. Someone wrote the connection order and the short cabel on the dac site. Others wrote succes with the $1 usb cables.

I hope i can keep this situation. Today back to unattended"

"I asked a few questions (in bold) trying to solve your problem "

Still fifo and USB errors

That was what i have done in the late night. See my answer before. No fifo or usb errors anymore only sometimes streaming errors.

I have the impression that it also something has to do with the Silverstone USB card. In an configuration with first the short and then the long Clairixa with the PC USB port the fifo errors don't exist anymore.

Long post but Peter I appreciate especially your efforts in your work and solving this problems. But sometimes we have some communication problems. XXHighend is difficult software with a lot of parameters. The understanding of this parameters is not always easy.

Do I forget something to answer? :(

Best Regards,

Johan
 

Haha, all ok !
But of course, if posts disappear then it gets a bit difficult.

Thank you for your extensive answer !

Regards,
Peter

Hi Peter,

after reading all the posts I feel that one aspect isn't be under consideration: The Intona is powered via PC. Could there be any dependency on the PC with different power supplies, different USB ports or the used USB cable?

Georg

Hi Georg,

You probably are very right. But how to "control" that ...

Peter

Strange, I  had the same problem. Before the HDD from Peter. Now it is ok.



 :)

I had ticks with 1.03 on W8.

I changed the USB port (3.0 to 2.0) and the USB/FIFO errors stopped.
I suspect powers supply issues.

Short Clarixia on the PC side.

VJ

Another question: Do all NOS1a users with silverstone card problems have connected the power via molex plug?

Georg

My memory is that the molex supplies 5V to the usb port, so you will need it connected if you want to handshake the NOS1 or Intona.  That is what I remember anyway, I might be wrong.

Anthony

I do not use the molex plug. I wil test it in the comming days.

Johan

Yes I do use the Molex. Its using the standard computer lead from a separate power output terminal on main power supply. Only powers the Silverstone.

Since upgrading Silverstone software no problems. I have not changed USB leads around yet on the Intona. Certainly don't have ticks/clicks but then my DAC is probably not up to it.

In regards to SFS I'm running .5 on 16/44 but have to increase to 1 for some 24/96 and 192 files. These stop playing after two tracks off an album.

Robert

Does that read as a virtue or what !?
haha

Interesting !
... as my Silverstone won't run (the NOS1a won't) without it ...

Peter

Ah, only now I understand ...
So it just arrived, for that reason I now received the email about your shipment and only now I can see that there wasn't any "hold up" message about it. This in itself did not make me see (anything of) it.

I now recall that there's always something with your shipments. Haha.
I always blame you for living on a nice island. :secret:

Regards,
Peter

And now I just tested With the short Clarixa on the DAC-side. It Works fine, With no ticks at all.
I have not "upgraded" to RAM-OS yet.

Regards
Arnt

Indeed it was already connected, sorry. :(

Hi Guys,

Since 2 days I have been using the RAM OS disk & booting with RAM OS 10586, there is no issues related to audible errors. Short Clarixa on PC & long one on DAC. Silverstone usb port without isolation.

Maybe I am one of the lucky ones.

Best regards,

Arvind

Now in RAM-OS With the short Clarixa on the dac side and no errors.

Regards
Arnt

The RAM-OS disk turned up today along with two Clairixa USB cables.  Followed the tutorial, plugged everything in, everything worked first time.  I have isolated Silverstone > short Clairixa > Intona > longer Clairixa > NOS1 and all seems quite good.

Interestingly, this is the first time that I have ever successfully had coverart working, which is nice, and I never set a thing, I just went with Peters settings in the RAM-OS 10586.

Good stuff!

Anthony, good that you mentioned it because I wasn't (email) notified of it.

One more to arrive, as far as I can see and it is Canadian.

Regards,
Peter

Canadian, crikey!  My package went through the US to get to me in Australia...surely Canada would be onto it, but I suppose there may be a bit of snow that way delaying things.

I am not sure if this is related to me, but I have yet to get my OS-ramdrive since I missed the first delivery even if I got earlier home last Friday... I should get it this morning to close the case ;) I should change the address to have something delivered at the office... Sorry !

Alain
PS: We did not get anything from that big storm in the US, thanks to the jet stream that "protected" Canada Eastern from that...

Alain,

From Mani I heard (or actually saw) that he had to collect his package from the UPS Store - after he missed the delivery at first.
Can't this be your case as well ?

Peter

Yes it is. Since I missed the first delivery, I asked them to leave it at their delivery warehouse.

I should get two packages at the same time, since I ordered a "toaster" to allow me to swap drives a lot easier than to remove my OS drive from an external enclosure.

"toaster": a docking station to allow either 2.5 or 3.5 drives. Very handy :) Have USB 3 and Esata connections. I use Esata. I can also power it with linear power supply, even if I do not think it will be really important with RAM OS usage, but...

Alain

Hi All,
My errors are gone! I think main reason was the 5V supply of the Silverstone USB card. (As someone mentioned,,,)
I used a picopsu feeded by an linear psu. That gave the errors.
Next I tried a direct 5V linear psu feed, no errors, but I had to restart the NOS1a dac everytime to get USB connected after PC restart.
Now I use an HDPLEX kind of picopsu (250W Hi-Fi DC-ATX) feeded with the same linear psu. No errors and instant connection of the USB.
regards, Arjan

Hi Arjan,

Well, nice (not); so those linear PSU's are so good that they actually don't work ?
Better wonder what you are doing this for !

Regards,
Peter