Load player slowdown and Audio Cracks

[rhopkins]

As an experiment I set the virtual memory to a minimum of 2gb and a maximum of 4gb. Just did a 30 minute practice with reduced hanging on player load.

reduced hanging on player load
actual time it takes to load the player and is it still glitching

I mean loading a track into player a or player b.

A little freeze still but I'm never expecting it to be instant. I'm not that demanding! No audio glitch experienced.

[daniel clark]

keep playing around with your setup and try to increase the usage levels too see when the auddio /gui glitches occure ,

[rhopkins]

:cool: keep playing around with your setup and try to increase the usage levels too see when the auddio /gui glitches occure ,

Had a mix session last night and whilst I had one of those nights where nothing sounded any good together (!) the performance was better. Slight freezes on pressing play on the Pro 2, more so compared when just pressing the play button using my laptop, but no audio glitches. Some improvement!

Latency set to 5.2ms.

[rhopkins]

Another practice last night. I reduced the laency to just under 5ms and at the start of the session I had a few clicks and breaks in sound. For the rest of the session things were fine and in terms of freezes I had nothing like the hangs I was experiencing when I started this thread.

I do notice a click if I load a new track to a player whilst FX are on for that particular deck, even when the amount knob is at 0.

[MusicMeister]

Ok... just read through this entire thread....

Can we drop back and punt?
First, are you still having the analyzing issue where every track is analyzed upon load regardless of whether it's been analyzed previously or not? This part is a bit unclear and knowing if it's still an issue may help identify the problem.


While I know you made a lot of changes, here's a few I'd recommend:
- First, defrag the hard drive. It may not be very defragged, but I recommend doing it anyway before the next step.

- Set your virtual memory to 1.5 times the amount of memory in the system and set the min and max to the same amount. This cases windows to not increase/decrease the size on the fly and there is a slight performance gain.

It appears the DPC Latency shouldn't be an issue, but can we double check? Try using the DPC Latency checker from:
http://www.thesycon.de/deu/latency_check.shtml

It's real easy to read with regards to whether you have an issue with DPC Latency or not.


I'm also curious - does your processor 'peg' when you load a new track? I didn't notice anyone asking nor it being mentioned. What sort of utilization are you getting during the loading of a track?

Once we get through these items, I have a couple areas to look at next, but it depends on the results.

[rhopkins]

Ok... just read through this entire thread....

Can we drop back and punt?
First, are you still having the analyzing issue where every track is analyzed upon load regardless of whether it's been analyzed previously or not? This part is a bit unclear and knowing if it's still an issue may help identify the problem.


While I know you made a lot of changes, here's a few I'd recommend:
- First, defrag the hard drive. It may not be very defragged, but I recommend doing it anyway before the next step.

- Set your virtual memory to 1.5 times the amount of memory in the system and set the min and max to the same amount. This cases windows to not increase/decrease the size on the fly and there is a slight performance gain.

It appears the DPC Latency shouldn't be an issue, but can we double check? Try using the DPC Latency checker from:
http://www.thesycon.de/deu/latency_check.shtml

It's real easy to read with regards to whether you have an issue with DPC Latency or not.


I'm also curious - does your processor 'peg' when you load a new track? I didn't notice anyone asking nor it being mentioned. What sort of utilization are you getting during the loading of a track?

Once we get through these items, I have a couple areas to look at next, but it depends on the results.

Wow, excellent suggestions. I'm away this weekend but will go through this all soon and come back to you.

Still having issues. Re-enabled the battery in device manager, re-enabled theme etc to see if performance was worse - it isn't, it's exactly the same.

[rhopkins]

Let me start by summarising what my two issue are, as I think that's been lost in this thread, probably down to me using it as a bit of a dumping ground for all the issues I've had:

1) When I load a track into a player, UMCP2 connected or not, I see Cross freeze.

2) Whilst 1) is happening or whilst I'm applying effects or navigating around my collection, cracks, pops and cutouts occur. If I'm recording a mix on playing back the recording I DO NOT HEAR these. Nonetheless, it's offputting and whilst I don't proclaim to be good enough and I've never been asked, one day I might want to perform for a crowd and this would be unacceptable. Trying to learn with all this going on is frustrating.

To clarify as well, audio is being played out of outputs 1 and 2 of the UMCP2 straight into my speakers.

Now to your questions.

Ok... just read through this entire thread....

Can we drop back and punt?
First, are you still having the analyzing issue where every track is analyzed upon load regardless of whether it's been analyzed previously or not? This part is a bit unclear and knowing if it's still an issue may help identify the problem.

This seems to be fine now. I have a side issue that I've reported before, in that if I edit the beatgrid with just my laptop as opposed to having the UMCP2 attached, I'll come back later and connect the controller and find that my changes have been lost. I was told this is impossible, but I see it over and over again. If I edit a beatgrid with just laptop connected, come back the next day just with the laptop, changes stick. Next day, connect the UMCP2 and the changes will go and default beatgrid/analysing will take place again.

Strange, but I can live with this - the audio cutouts and cracks are more troubling.

While I know you made a lot of changes, here's a few I'd recommend:
- First, defrag the hard drive. It may not be very defragged, but I recommend doing it anyway before the next step.

I've done this. I must confess that it had been a while and whilst all round laptop performance seems to have been given a slight boost, audio cutouts and slow player loading is still an issue.

- Set your virtual memory to 1.5 times the amount of memory in the system and set the min and max to the same amount. This cases windows to not increase/decrease the size on the fly and there is a slight performance gain.

Done. Not tested yet. I found that when I set the VM to half my RAM (4GB of 8GB) that the load player freeze was shorter but still there.

It appears the DPC Latency shouldn't be an issue, but can we double check? Try using the DPC Latency checker from:
http://www.thesycon.de/deu/latency_check.shtml

It's real easy to read with regards to whether you have an issue with DPC Latency or not.

Not tested with the UMCP2 yet but just on my laptop I see obvious problems when my wiresless adaptor is enabled. Disabled, I don't see anything above green, but slight jumps up to (a guess) 300 when I load a track or apply an effect. Laptop idle, the current latency ranges between 99 and 130 us. As I'm switching between windows now I can see that something makes it jump up to 1800 us (another estimation) every now and again. That's a bit concerning. Display driver? This has been mentioned a couple of times. It's just an Intel display driver; could I get an alternative generic driver?

I'm also curious - does your processor 'peg' when you load a new track? I didn't notice anyone asking nor it being mentioned. What sort of utilization are you getting during the loading of a track?

I haven't ever noticed that it does. It's frustrating that I can't see this! I was expecting to, it'd make it easier to track down the problem!

Once we get through these items, I have a couple areas to look at next, but it depends on the results.

Next!

[Support@MixVibes]

1) When I load a track into a player, UMCP2 connected or not, I see Cross freeze.

Computer related for me. What format are you using ? mp3.flac,m4a.wav.ogg ?

2) Whilst 1) is happening or whilst I'm applying effects or navigating around my collection, cracks, pops and cutouts occur.

Your computer is having a hard time...

If I'm recording a mix on playing back the recording I DO NOT HEAR these. Nonetheless, it's offputting and whilst I don't proclaim to be good enough and I've never been asked, one day I might want to perform for a crowd and this would be unacceptable. Trying to learn with all this going on is frustrating.

To clarify as well, audio is being played out of outputs 1 and 2 of the UMCP2 straight into my speakers.

Now let's move on and say it is not the computer.
This could be the soundcard, or its drivers. So if you can try with another soundcard (internal one) and/or alternative drivers (asio4all).

This seems to be fine now. I have a side issue that I've reported before, in that if I edit the beatgrid with just my laptop as opposed to having the UMCP2 attached, I'll come back later and connect the controller and find that my changes have been lost. I was told this is impossible, but I see it over and over again. If I edit a beatgrid with just laptop connected, come back the next day just with the laptop, changes stick. Next day, connect the UMCP2 and the changes will go and default beatgrid/analysing will take place again.

Let me try to keep in clear :
Nor the computer, the collection (the database) or the file have somewhere a value where it is written "beatgrid done with controler (or not)". So nothing in the system can tell this.
If default beatgrid/analyse happen again, it is because the file generated into the peak folder cannot be found.
It has not be written for any reason, but it is not there anymore.
Did Cross forgot to write it down ? is it a security option on your system ?

Done. Not tested yet. I found that when I set the VM to half my RAM (4GB of 8GB) that the load player freeze was shorter but still there.

I'm pretty shure something is wrong with your computer, most of the time, these are weak motherboard, integrated component drivers using generic windows one instead of custom oem ones.

Not tested with the UMCP2 yet but just on my laptop I see obvious problems when my wiresless adaptor is enabled. Disabled, I don't see anything above green, but slight jumps up to (a guess) 300 when I load a track or apply an effect. Laptop idle, the current latency ranges between 99 and 130 us. As I'm switching between windows now I can see that something makes it jump up to 1800 us (another estimation) every now and again. That's a bit concerning. Display driver? This has been mentioned a couple of times. It's just an Intel display driver; could I get an alternative generic driver?

May be the latest one, or try the Windows one (generic in this case).

Give me the exact brand, model name, series and trim you have.

[rhopkins]

So these problems started to happen with the release of 2.1. Would you expect a laptop that handled 2.0 ok would struggle with that upgrade?

[daniel clark]

Kinda siding with support , have had and run all versions since 1.25 ,, keep my system same and noticed the emerging pattern with useage and system coping ,, that why sitting on the side lines ,,, my system has become underpowered to run the last version with out freezes and audio glitches,, also even running media player has same issues ,, so i am trying to bat with a weak and underpowered base ball bat ,,,,,,new year might give oppunity to upgrade and come into the win7 era