Hi Glynn,

We seem to be out of luck a bit;

Just sent you an email (two attempts) but now I am rejected as being spam by your side somewhere. The things seems mutual.
So, sent you a PM by means of the forum again.

Sorry for the inconvenience ...

Peter

Answer No to that question, set one or two of your settings, quit and restart and see if the question comes up again.
If not, you're good, although you have to set all of your settings as how you are used to.

It looks like reverting back to an old version just confuses B. Gates beautiful thoughts.
And mine ...

Anyway, does that solve the issue ?

Peter

Hi again Don,

What you describe doesn't seem logic to me.

In the Settings Area, your DAC Is should be set to 24 bits 96KHz. But I suppose you did that.
Then the radio buttons thereunder should be set to 32 bits (so not at 24). I think you did that too.

Now, since your MADI will be able to play at 16 bits and 44.1KHz, I would not know why it can't work. Also, if you mean "upsampling by XX" (see the checkboxes at the left side of the player), you will be outputting at 32 bits and 88.2 KHz. So this is the least that just should work.

The only thing I can imagine (though still not completely logical to me) is that you fixed the sample rate in the driver interface from the RME somehow. So, this sure should *not* be so. That is, I assume the MADI will pick up the samplerate etc. it is fed with.

If after the above "knowledge" things still don't work at 44.1/16, please examine whether the DAD can handle less than 24 bits. But then again there is no logic regarding the upsampling issue.

Let me know what happens.

Peter

Glynn,

I never saw anything back from you after my PM (My Messages at the top in here).
Are you ok ?

Peter

Hi, and welcome !

For Engine#3 you should make the MADI device the primary device (hence the default device); then it should just work ...
Or do I understand you wrongly ?

Engine#1 (and #2) were never explicitly made for other samplerates and bitdepths than 44.100/16. If other combinations work it is by accident.

Do you have the 384K version of the DAD ? that would be great ...

Peter

Hi Glynn,

I just sent you a PM.

Thanks,
Peter

I was just thinking ...

Core Appointent can not be done for drivers (actually I wish it could -> with registry hacks it can I think). Now what if your system allows for this (one is enough) while it actually "can't" (or conflicts) ...

I don't think you can do much with this information, but it might be a reason.

GerardA,

1. I can't judge about problems in earlier versions because ... well ... there are newer versions. That we currently want to listen to an older version is bad luck for a while.

2. Please don't use Core Appointment for a while, so you can prove it is just that (but maybe you already know). But whatever you can prove, I'm afraid I can't help with it, or solve it. Of course, when more people have problems like this I must get cautious.

Peter

Nah, there's too much functionality in running two instances, mainly in the area of copying on one, and checking (what to copy etc.) on the other, but also in having setup something in the one (not wanting to destroy that) and checking something else on the other.
Of course you must know that the one who closes down as the last one, saves the -whatever it is- (the first one does too, but it will be overridden by the second (just the last one)).

Of course this should not be done with two different versions ! (when the Data folder is the same).

Whether this impeeds for JohanZ's problem with the Favorites.txt file is something I will investigate.

Peter

Hi Kjell,

Uh-ohh, these kind of things usually are nasty ...
Do you have an infrared keyboard ? switch off the IR feature and try again.
Do you have a wireless connection somehow (or an accesspoint connected to the PC) ? switch it off an try again.
Other means of "through the air" ? same ...
And for now : make sure the Split Lare Files setting (Settings area) is at 2500 (when the clicks have gone you can do what you want with it).

You are not the first with a (Dell) notebook and these kind of problems ...


Look here : Vista Users ... prepare yourselves ...

I sure hope you can solve it !
(but let me know when not)
Peter

With v7 you mean ? (during typing of your post ?)

The UnicodeTrack0001 thing I recognize from 0.9v-2a or something (it was an intermediate version).
Please tell me as exact as possible what you play in this case (MP3 etc., AA box ticked or not and whether it's repeatable).


Like completely unrecognizeable ?

At which version this wasn't happening ? (0.9-w1 ? earlier ? -> just your experience, you don't need to explicitly try)

And can it be related to A few questions about Vista behaviour to you ? otherwise it seems quite some coincidence ...

All,

Background : In the development environment I have a setup which is not equal to yours. Therefore a few of the below things I cannot test (that is, not all the time, and it would be very time consuming), but when I want to test an older XX version I most probably bump into the same anomalies ... as you might have always at installing a new version. However, I never heard anyone complain, so now I wonder ... do you have similar and must I try to do something about that, or are the below things unique to my environment anyway ?

Vista SP0 (which *will* matter) and UAC is off, all as advised by myself hehe (Vista Users ... prepare yourselves ...).

1. Can you ever Restore to you Old Settings ?

Yesterday I installed 0.9-v6a in a new folder, and received the message (at first startup) that not all setting could be restored;
The message says "no problem" but the only way to avoid the message the next times at startup (and loose the settings AGAIN) is to answer the question with "No, I don't want to Restore the Old Settings".
For a new XX folder this seems logic to me. However :
Today I downloaded 0.9v-7 over the files in the 0.9v-6a folder (but I renamed the folder to 0.9v-7 !) and the sequence was the same.

This is obviously not the intention of the Restore function, and now at each new version you have to set the settings all over.

Is this common behaviour for you to ? (hence the most inconvenient)

2. Things can get stuck within ChangeWP (the Wallpaper feature) ?

I changed OS disks; this should go unnoticed (by the OS itself) because it is a literal copy, and only the disks are different.
However, together with the procedure described under 1 above, today I noticed that the Wallpaper wouldn't change, *and* by kind of accidence I noticed that ChangeWP.exe kept on running with XX and everything closed (no XXEngine3 running either).

I got smart and thought it would be rights related. Started XX as administrator (but all of which is arranged for already), and after that it appeared that ChangeWP was waiting for the confirmation to "Run this (unsigned) program", hence now the message appeared which apparently was there under the hood before, just the same.
One time starting XX as Administrator was enough to solve the problem for the next times.
But yes, since I applied a new icon to the new XX folder, most probably this is logic. But again the most inconvenient.

Do you experience similar ?

3. Again in the context of the above, I suddenly may receive a message from ChangeWP that a .cue file does not exist

The .cue file sure does exist, and I am 100% sure this is somehow related to files coming over (via Ethernet) from another PC in the network.
When renaming the .cue file to some other name, and rename it back, the problem has gone.
I never noticed something like this before, so I am fairly sure it is related to the install in the new folder.
Also, I think it is related to the necessity of starting XX once as administrator, although I can't be sure.
Note that I don't see the relation to which .cue files do, and which don't "exist" as it is reported.


All 'n all I am afraid that nobody tells about these quite annoying "features" while everybody is confronted with them all the time.
Are you ?

Peter

I can't tell why this doesn't work for you (or for Gerard for that matter). Note that it mind be kind of importantish though, because what's left for me (see 2nd picture of first post in this topic) stays away between 6-12 minutes. I don't know (anymore) about the frequency of things you got left. Could be each 10 seconds ... (but you can look for yourself with the resource monitor).

No, I don't shut off anything manually.
I'm stuck with the 5 showing in the very first post of this topic. I just don't know what to stop and how to stop it. Not by some hack and not even manually.