XXHighEnd

When I play back 16/44 files albums all goes perfectly.

When I playback one Hires(24/96) album all goes well.

When I mix it up say 2 x 16/44 albums then a 24/44/96/192 album XXhighend will stop playing and a box comes up Playback file is full.

I have to hit ctr alt x to bring screen back.

It almost appears that the playback drive is not clearing of former played tracks creating the full warning. I'm unable to check ram drive volume in Min OS playback.

I've tried hitting X and closing XXh and restarting still the same thing happens. The only solution is to reboot computer.

I've set Ram drives to 5g. I've also split some hires albums into 2. But often XXhigh stops after 2 tracks anyway.

This is annoying but not a major problem.

Robert

Hey Robert,

I don't see why you would not be able to check the RAMDisk volumes when in MinOS. Just click PC or MyComputer or however it is called in Explorer, and then rightclick on the volumes you see in the right pane. Then choose properties and there it will show how full it is (assumed it is that what you wanted to know).

What happens (about the necessary reboot) is that some process is killed where it should not, and now the file which was worked with is kept open. In my view this can only be XXEngine3.exe, thus kill that (blue led in the right hand border of XXHighEnd). Otherwise I think when you manually (Explorer) shift-delete the files in there, it will go (out).

Since a RAMDisk won't know about CD vs Hires and such, I suspect that you still manage to have the RAMDisk(s) full. Notice that this is still quite easy with one 24/192 album alone. And then you try to add two 16/44.1's. Forget it.
With 24/96 you may have more luck but still will be critical.
So I'm almost sure you just try to put in too much in there. Just look at the contents when you loaded (play a little in Unattended of a full one in the Playlist Area) a 24/192 and I think you will agree ...

Regards,
Peter

I should add :

Once you are able to let overflow your RAMDisk, you are in deep trouble because now you are writing to used memory elsewhere. I have talked about this before, as IMDisk - or the way we implemented it - does not protect well against that. So *if* you allow to let it overflow, then indeed it can be so that you must reboot to get all working decently again. Take this as your last option though, because XXHighEnd itself is quite protective in this (tries to look ahead whether the RAMDisk will overflow to next prevent that).

Peter