Os-x yosemite driver?

[PeterC]

No, I have misled you then.  I changed it only in HQP; the change is reflected in AudiMidi without me touching that directly.

I have check again and same situation...only touching upsample rate in HQP, which is changed automatically in AudioMidi.  705 does not work; 768 works but 10% slow.

[PeterSt]

705 does not work

What do you mean "does not work" ?

Please try explicitly and report :
16/44.1 file, output in HQP to 705.6 (2-wire active) : What do you perceive ?
(Switch#5 in NOS1a down)

[PeterSt]

OK, something else - and about not enough juice (perhap) :

Try to find a small track like 1 minute or so. This could matter. Maybe Beatles get you there easily (or close).

[PeterC]

Exactly what I have been trying just as you specify..."does not work" means, drop outs, noise, stops completely for long periods (and I perceive voice sounds high pitched).

Then try 16/44.1 file, output in HQP to 768 (2-wire active); (Switch#5 in NOS1a down)...now plays without dropouts, noise, stops...but plays 10% slow but timing vs. stop watch.

All above change sample rate only in HQP.

[PeterSt]

Stoooooooooooooooooooooooooooooooooooooooop
and
F*****************************************CK

Because I too much believe what you guys are telling, I now found my own mistake. And you sure will believe how stupid I myself can be and how much I can waste my own time, including yours ...

Yesterday I did not feel like taking out my own NOS1a from the cabinet (want to preserve the perfect SQ I have these days) and grabbed another one. And what did I do ?
I took one which is not upgraded to the "a" yet.
Very nice, but in there no special clock-change treatment is required. So that always works (about the wrong speed).

How do you say "I apologise" ?

[PeterSt]

Now trying with an "a" ...

This has brought me so many surprises that I don't know where to begin to make logic out of it ...

Generally, indeed, no output of 705.6 (16x) plays without super distortion. 8x 2-wire same thing. 8x 1-wire same thing.

But something new (meaning you guys did not report this) : No speed is correct anywhere. It is or too slow or too high. Counts for the 44.1 based (as long as I can see the signal) and counts for 48 just the same.
I can't even find the logic in when too high or when too low, but what I seem to have seen of it, it's the difference between the output rates (so input (file) is not important for this.

Now very coincidentally I am super glad I saw this working yesterday with the "non-a" because otherwise for 100% sure I would have blamed the player.

It will be outside of your scope, but to me it feels that the sampling rate is changed all right, but that next internally something else is reported to the OS. Say like : first tell Audio Midi about the sampling rate, and only next do it for real and then something back fires.
Do notice that I did this for Windows myself and that this works fine to next tell a couple of other guys to apply it like this for Apple, and assumed they did that, this now does not work at all.

Also, I will be mad most probably, but while I told earlier that I saw the sampling rate change in Audio Midi after changing it in HQP, I now only see it change in Audio Midi when I press Play. Was I wrong in observing yesterday ? maybe. But I sure see how such a change relates to what I now see happening.

Maybe I need to apply some more checks ...

[PeterSt]

Also, I will be mad most probably, but while I told earlier that I saw the sampling rate change in Audio Midi after changing it in HQP, I now only see it change in Audio Midi when I press Play. Was I wrong in observing yesterday ? maybe.

Yes I was; just re-checked it with the non-a.

[CoenP]

Also this is not completely repeatable with A+, where -only- my 192 files play perfect with -only- 1x oversampling (OS).

I was wrong. The music sounded normal, but compared to the laptop's audio out it is definitely to slow.

I'm glad that our findings are repeated by Peter.

regards, Coen

[PeterSt]

But Coen, this still doesn't tell me about too slow in absolute sense. Probably you are saying this but can you confirm ?

Peter

[Bob Stern]

One more hint to drivers which won't install hence leave the old stuff be :

First off you won't notice this. The green OK tells you all is fine, while nothing happened (thank you Apple). One of the (totally stupid) reasons is this (and please correct when better data is available) :

The increment of a version number is tracked by OSX. This - and this seems to be new - means that no "newer" version like 2.0.1 can be installed over a 2.0.8 already running. Really so, and this is reason #1 as it seems to me that you can't revert (to 2.0.7.). But delete mentioned files and all looks to be good, while *still* something is in there knowing about this.
In the end I could not fully track this because these kind of issues I ran into on 10.7, at that time not knowing yet that things so much changed that 10.8 is required for minimum.

When you replace an extension by simple Finder copy (drag-and-drop) rather than running the Apple Installer program, I do not believe OS X cares whether the new extension is a higher or lower version number.  (Although I have to admit that I am not using Yosemite.) 

The usual cause of an extension update being ignored is that the old extension remains in cache.  OS X does not notice that you installed a different version of an extension if you merely copied it in the Finder instead of using the Apple Installer program.

The solution is to clear the extensions cache in one of two ways:

1. The "touch" command in my previous reply #36.  However, I made a mistake: I specified the Extensions folder for OS X 10.8 and earlier, not the new one for Mavericks and Yosemite.  The "touch" command for the latter is:
sudo touch /Library/Extensions/

2. A completely foolproof method, although extra steps, is to restart the Mac in "Safe" mode by holding down the Shift key after you hear the startup chime until you see a horizontal thermometer icon (representing the progress of the fsck operation).  Login in Safe mode, then restart again normally.

Side note: I can't upgrade my 10.7 to anywhere because of a perceived non-GUID partition I don't know anything about (that particular iMac was just bought running from an Apple Shop but with the notice that I installed Bootcam on it later).

GUID versus AFS is a property of the entire hard drive, not of an individual partition.  To convert a drive to GUID you must completely erase the drive, recreate the desired partitions, then restore the data from a backup.  Instructions at:

http://support.apple.com/HT201723
or
http://bombich.com/kb/ccc4/preparing-your-backup-disk-backup-os-x

[PeterSt]

And again Thank You Bob. Not sure where your help in here springs from, but for me as a Mac NooB it is really really appreciated.

The GUID thing ... yeah, that kind of answers I read everywhere. Assuming you have that Backup ready etc.
But what I never read is how the heck such a thing can emerge. So again, I didn't partition that disk and if I would have it would have been GUID in the first place.

Might you like to provide one more little sentense of help :
What is reliable for making a backup of an iMac ? One which was little later provided with Bootcamp ? One which extends the Bootcamp partition with a FAT USB disk (which requires tweaks under Windows I could do (and are not readily available) but which makes me reluctant to say the least to go the backup and restore route in the first place).

Thank you Bob ...
Peter

[Bob Stern]

Thank You Bob. Not sure where your help in here springs from ...

1. Although I don't own a NOS1a, it does greatly interest me as a clever design that I'd like to audition eventually.

2. I've been a Mac user for 24 years, and I've developed AppleScripts, etc for managing my music library, so I like to do what I can to facilitate the Mac as a platform for computer audio.

What is reliable for making a backup of an iMac ? One which was little later provided with Bootcamp ? One which extends the Bootcamp partition with a FAT USB disk (which requires tweaks under Windows I could do (and are not readily available) but which makes me reluctant to say the least to go the backup and restore route in the first place).

Bombich "Carbon Copy Cloner" is the backup program I use.  It is the highest regarded program for carefully preserving all the hidden files, permissions, Bootcamp partition, recovery partition, etc.  It has a fully functioning 30-day free trial.

http://bombich.com

The help in the Help menu is the same as the online help, so it probably is easier to view the instructions online.  I believe there are instructions in Nederlandse, too.

http://bombich.com/kb/ccc4/how-set-up-your-first-backup

[PeterSt]

That is super Bob. Thanks a lot.

[CoenP]

But Coen, this still doesn't tell me about too slow in absolute sense. Probably you are saying this but can you confirm ?

Peter

I'd estimate about 10% which makes perfect sense: 48khz consistently too slow and 44.1khz consistently to fast.

Iow 48 played back with 44.1 clock and 44.1 played back with 48 clock. Clocks differ in the order of 10%.

Regards, Coen

[PeterSt]

Hey Coen,

Yes, I have been thinking about something like that. And could well be a most logical explanation of something which consistently goes wrong; It would only be a matter of some programmer switching around the code concerned (have the If / Else (content) the other way around).

Now I am going to make a few phone calls ...

Thanks !
Peter