Your system reads like the ideal MIR-setup, so it takes me by surprise that you have any problems at all. I will do a test later today on my system (which has less RAM, though).

Just to be sure - you experience these glitches as soon as you switch from the Instrument Channel to the Output Channel view? As long as you see the Instrument Channel, the same project is doing fine? Does it help when you increase either the system-wide latency settings of the RME Control Panle, or MIR's dedicated Buffer Multiplier?

Does this happen with less instruments, too?

And you are sure that this happend with older builds, too?

BTW  - what is the graphics card of your system?

@Ramu said:

[...] Hope this could help you, First Officer! ;)

;-D ... at least _one_ person who read the manual from cover to cover!

Ok...Time to give you some weird behaviour I've experienced today...

First of all, concerning the OUTPUT button. If I don't touch it on the MIR Panel the project works perfectly. If I change the latency while I'm having a session loaded it gets completly crazy...so, close application...reload...or reboot..

I've haven't tried with less instruments...I should when I could :)

My gfx is NVIDIA GF8400

Now the fun part!

I've launched the MIR today thinking it would work as yesterday...it didn't. I've started to have lots of CPU cracks as soon as I have lots of VI playing together...Sometimes this happens, mainly if I load a new session over a big one...so I close the app and reload (and sometimes reboot because it still don't work..). But today, nothing I did could help the system to feel not overloaded...Yesterday the session worked perfectly and today...no.

So I've tried to change the latency (why???!) and it was even worse (going from 512 to 1024). I switched it back to 512 and then : a miracle, It sounded without any glitches...[My bad, the DAW was the issue for the balance...I want to cry!!]

So, I don't know why this happens since I don't touch anything on my system. It's a very sane and dedicated configuration I did for MIR...

Now cracks appear randomly...I can play once the whole cue without any issue and the second pass won't reach the half before getting cracks...

I really don't understand...I thought it could come from the HDD but I doubt it as cracks are not dependent on which instrument is playing...

[EDIT]

I've figured...The mainboard took the OC back to normal settings without warning me...I was at 2.8 GHZ instead of 3.8..sometimes I just feel technology has a great sense of humor. Sorry for the flood :)

[EDIT 2]

back to 3.8 still have cracks...I'm lost..

Hmmmm ... it really looks like there's a specific flaw with your system, harware- or driver-wise - much like a conflict between two components. Most likely, something similar would happen in other application, too, but MIR is especially susceptible for those problems as it taxes the system more than most other programs.

I will ask our local hardware-gurus what they think.

I have to admit that I was almost expecting it - but I can't reproduce this behaviour on a system that is not too different from yours (using even the same audio device). The biggest difference is that this system has a an ATI Radeon 3800 HD graphics card, and only 12 GB RAM.

We'll have to look into this a bit deeper, I'm sorry to say so.

ramu, i'm asking myself what has been done to your system that you can run an i7 930 with 3.8 GHZ ... the processor is specified for a maximum of 3.06 GHz (including the possible 2 overclocking steps) ... additionally please consider the 930 has the *slow* QPI interface of 4.8 GT/s (our *little* i7 MIR machines all have the 6.4 GT/s QPI with the 965 or 975 and are running at 1333 MHz memory bus speed)

also we had to notice nVidia cards are always troublesome when it comes to openGL implementation, this is the reason why VSL certifies only machines with ATI until we can get the proof nVidia caught up.

what about your harddisks - maybe we should look for the bottleneck here ... MIR _is_ a demanding application and needs good hardware - any bottleneck in the chain can decrease the overall performance significantly.

something additional caught my attention: you wrote to had changed your latency - where exactly has this been done, what about the multiplyer and did you stop the engine when doing so?

EDIT: i didn't read what audio interface you are actually using ... is this ok and up to date with drivers? if USB then don't expect too much or at least free your USB bus from other devices ... 16 GB RAM ... this is an unusual number for an i7 motherboard (doesn't spread data across the 3 memory channels evenly)

Thanks for chiming in, Chris.

@cm said:

[....] EDIT: i didn't read what audio interface you are actually using ... is this ok and up to date with drivers? if USB then don't expect too much or at least free your USB bus from other devices ... [...]

Ramu is using a RME DigiFace (PCIe, I suppose). He wrote this in his first message.

@Dietz said:

Ramu is using a RME DigiFace (PCIe, I suppose). He wrote this in his first message

sorry, must have overlooked this info - so IMO we can exclude this component from our considerations

Just to let you know where I am right now

1. Although yesterday I did checkdisk my hard drives and got no errors, this morning W7 started a checkdisk prior to boot and found errors on one of my velociraptor (I love computers). So I did re-install the brass library that were on the velociraptor on another HDD (7200 rpm). After I did this I player the session and everything went good. The proc is at 2.8 with no OC (performance peak at 63% with no cracks)

2. Output Button is still acting weird. When I click on it the proc works (up to 25%) then go back to normal and when I play the sound is different...

3. I'm buying today an ATI Gfx, 8 gigs RAM and some new HDD. Hoping this will help...

One other thing is that despite the HDD situation (that could be the cause of the cracks) it was working perfectly (output button included) before. So maybe the session got too big...or there is a big mystery.

I'll keep you in touch with the new setup,

Really appreciate your help and support

Sorry to flood the forum

Last update

I did not touch anything...just reboot and now lots of cracks...

[EDIT]

and I changed the latency from 512 to 1024 and back again to 512 : no more cracks

[Update]

OUTPUT Button is no more an issue with ATI Radeon. As a matter of fact Nvidia is not for MIR.

Still testing the rest

I used to have lots of little dumb errors and video issues etc when I used a 256MB Nvidia card.  I ended up buying a 1GB ATI card and they all dissappeared.  Even my Remote desktop issues went away.

It definitely doesn't like NVidia at the moment.

Maestro2be

I don't have any problems with my Nvidia Geforce GTX 285 here. Perhaps the cheaper range of Nvidia cards have crappy OpenGL drivers.