Software help archive

A read-only archive of old serato.com help threads.

CPU consumpion of 2.1 vs 2.0 my computer is running harder and hotter

Product
Scratch Live
Version
2.1
Hardware
Rane TTM 57SL
Computer
Mac
OS
Platform
-
the_black_one 2:10 AM - 17 August, 2010
Product: scratchlive
Version: 2.1
Hardware: rane-ttm57sl
Computer: mac
OS Version: 10.6.4
---

i'm going to start another help discussion about the CPU consumption of 2.1. The jump of CPU consumption jumps quite a bit from 2.0 to 2.1 . It makes my laptop run hotter because the CPU is getting pushed harder. The Normal temp wile running 2.0 is around 55 degrees, when i run 2.1 the average temp is 70 to 72 degrees. BIG JUMP if you ask me.


Macbook pro unibody 2.66 ghz 320 HD (music is internal)
4 gigs of memory
256 memory video card (not shared)
DJ Stoyvo 4:32 AM - 17 August, 2010
since running 2.1, i have to bring an external laptop cooler with me. I dont know the specs, but dang it's hot
DjWoody 6:43 AM - 17 August, 2010
Having the same issue. Laptop gets a lot hotter with 2.1.
DJ MisterG 9:19 PM - 17 August, 2010
Same here! Released version of 2.1 has high cpu load with large playlist (CRATES). I tried it with less crates and it ran better. The has been an ongoing issue and it was previously fixed.
Serato, Forum Moderator
Matt-C 10:45 PM - 17 August, 2010
Hi the_black_one.

Can you please see if tags are being written to the file when you eject the track?

Also if you turn off the 'Autofill Overviews' function in the Setup screen, does that lighten the CPU load?

Cheers.
the_black_one 12:00 AM - 18 August, 2010
yes, it will right over the tag on some songs, not all. I have an open help discussion on that issue.

Will try the "autofill overviews" un check as soon as i get home and will let you know the findings asap
victor_M 12:21 AM - 18 August, 2010
Quote:
Hi the_black_one.

Can you please see if tags are being written to the file when you eject the track?

Also if you turn off the 'Autofill Overviews' function in the Setup screen, does that lighten the CPU load?

Cheers.

Hey Matt

Tried this to no avail. Still writing tags and still getting hot. It's getting like VSL and 1.92 hot.
Javier drada 3:07 AM - 18 August, 2010
How do we revert to 2.0?
the_black_one 3:10 AM - 18 August, 2010
auto fill unchecked does not make the cpu consumption change
Serato, Forum Moderator
Matt-C 3:14 AM - 18 August, 2010
What is the exact CPU value for each version?
Can you please take screen shots of each and attach to this thread.
Cheers.
the_black_one 3:15 AM - 18 August, 2010
I'm at work. as soon as i get home i will.
Serato, Forum Moderator
Matt-C 3:16 AM - 18 August, 2010
Cheers man. We'll try and get to the bottom of this asap for you guys :D
the_black_one 3:17 AM - 18 August, 2010
thanx homie!
Serato, Forum Moderator
Matt-C 3:23 AM - 18 August, 2010
Anytime :D
LJ_WOOLSEY 2:02 PM - 18 August, 2010
OK 2.0.0 max CPU Load when loading tracks 55%

2.1.1 (21110) max CPU Load when loading tracks 77%

im on a Dell inspiron 1545 4gb ram 2.2ghz Intel core duo
win 7 home 64bit.
Javier drada 7:13 PM - 18 August, 2010
If you need to download the previous version
serato.com
Serato, Forum Moderator
Matt-C 12:12 AM - 19 August, 2010
Can you please re-analyze a few files in the latest beta of 2.1.1 and then play them.
What happens now?
If the CPU is still spiking, how long does the spike last?
the_black_one 10:11 PM - 23 August, 2010
2.1.1 is still making the computer run hot even after re analyzing
LJ_WOOLSEY 10:13 PM - 23 August, 2010
With version of 2.1.1 are you using? The CPU fix came out today. What's the 5 digit build number?
the_black_one 10:14 PM - 23 August, 2010
do you have a link?
LJ_WOOLSEY 10:22 PM - 23 August, 2010
Serato, Forum Moderator
Matt-C 10:32 PM - 23 August, 2010
Can everyone let me know how they are going with this latest build? (21110)
the_black_one 10:53 PM - 23 August, 2010
Quote:
Can everyone let me know how they are going with this latest build? (21110)

downloading now, will post after testing
LJ_WOOLSEY 11:03 PM - 23 August, 2010
Quote:
Can everyone let me know how they are going with this latest build? (21110)


You mean PB2 - 2.1.1 (21111) ;-)
the_black_one 11:16 PM - 23 August, 2010
(21111)

in 2.0 , one particular song, i analyze it in 2.0, Not corrupted
in 2.1.1 (21111) same song, i analyze it in 2.1.1 (21111) and it's corrupted


2.0 not corrupted
2.1 corrupted

why is it that the song is not corrupted in 2.0 and then it is corrupted in 2.1.1 (21111)
11:20 PM, 23 Aug 2010
the_black_one attached a file: Zookey (Lift Your Leg Up) (Bob Sinclair Africanism Remix).mp3
Download· Permalink
LJ_WOOLSEY 11:22 PM - 23 August, 2010
OK THIS IS A TEST WITH NO HARDWARE! have to wait till wed for that test.

Load track in offline player. CPU MAX LOAD 9% Goes back down to 0-3%

now load a track with NO bpm or just delete the bpm from the track you just tried.
CPU MAX LOAD 85% Goes back down to 45-60% WOW so if you dont want to have bpms your computer is guna fry!

will test with me sl-3 on wed. hope that not to late for you.

cheers.
Quote:
(21111)

in 2.0 , one particular song, i analyze it in 2.0, Not corrupted
in 2.1.1 (21111) same song, i analyze it in 2.1.1 (21111) and it's corrupted


2.0 not corrupted
2.1 corrupted

why is it that the song is not corrupted in 2.0 and then it is corrupted in 2.1.1 (21111)


yep analyze the track twice and its currupt. N-O-T G-O-O-D!!!!

Cheers
the_black_one 11:25 PM - 23 August, 2010
i attached a file that was giving me the issue.
LJ_WOOLSEY 11:27 PM - 23 August, 2010
i will do the same but in the beta area,
LJ_WOOLSEY 11:59 PM - 23 August, 2010
Following up the currupt issue here ----> www.serato.com
the_black_one 12:12 AM - 24 August, 2010
On going bugs!
dj tuffy 1:05 AM - 24 August, 2010
Hey Guy's since i downloaded the new version 2.1 been having serious usb dropouts... never had them before... running -- a toshiba satellite-a205 Duo core -- 2gb mem.. using external harddrive.
Mighty Dragon Sounds 1:12 AM - 24 August, 2010
Nothing so far while running on MacBook Pro 2gig Ram 2.26mhz.......... So far about 20 hours of play time.
Serato, Forum Moderator
Matt-C 2:20 AM - 24 August, 2010
Hey guys.
Can we please keep this thread on point.
Which is diagnosing increased CPU usage from Scratch Live 2.0 to the new 2.1 version.

Can all other users please start a new help thread, I can see this thread getting cluttered real fast. Cheers.
Serato, Forum Moderator
Matt-C 2:22 AM - 24 August, 2010
Quote:
Load track in offline player. CPU MAX LOAD 9% Goes back down to 0-3%

now load a track with NO bpm or just delete the bpm from the track you just tried.
CPU MAX LOAD 85% Goes back down to 45-60% WOW so if you dont want to have bpms your computer is guna fry!

This is normal, analyzing files is meant to take as much of the CPU as possible, this won't fry a computer at all unless your computer is broken. Many computer functions do this. However this is one reason why we suggest analyzing your library before playing out :D
Serato, Forum Moderator
Matt-C 2:23 AM - 24 August, 2010
We'll keep discussing file corruption here: www.serato.com
Doomz 2:26 AM - 24 August, 2010
Man I thought I was the only one having these problems. At my last gig, several of my songs slowed down my PC. The screen became really choppy and the wave bars were choppy too. I though my PC was going to crash. All the songs have worked fine with 2.0, but the 2.1 version is the problem. But it only happens to a few songs.... I noticed it was writing tags after almost every song was played. I analized my files again and I also ran the tags too. So should I revert to 2.0... and when will this bug be fixed.
Serato, Forum Moderator
Matt-C 3:46 AM - 24 August, 2010
This tag problem has been fixed with the new builds of 2.1.1 - go to the new beta area for this and give it a go: www.serato.com
Doomz 4:45 AM - 24 August, 2010
Is beta stable? Or should I wait like a month before installing it, you never know, a new bug might pop up. I already went back to 2.0.
Serato, Forum Moderator
Matt-C 4:57 AM - 24 August, 2010
Well, if your issue is resolved it will most likely be more stable for you than the current version.
There will be tweaks to the beta until we feel it's ready, but you can easily have more than one version of Scratch Live on your computer at once (the information on how to do this is in the beta area I linked to above your post).

However if you are happy with using 2.0 until the beta period is done and the final release is out then feel free to do that.
Serato
James 2:35 AM - 25 August, 2010
Has anybody had a chance to try the latest 2.1.1 yet?

You don't need to worry about the corrupting issue - it is just giving false positives (and will be fixed in the next beta)
the_black_one 2:50 AM - 25 August, 2010
Quote:
Has anybody had a chance to try the latest 2.1.1 yet?

You don't need to worry about the corrupting issue - it is just giving false positives (and will be fixed in the next beta)

good thing serato does not make pregnancy test!
Doomz 1:44 AM - 26 August, 2010
lol
BriChi 1:57 AM - 26 August, 2010
Quote:
Quote:
Has anybody had a chance to try the latest 2.1.1 yet?

You don't need to worry about the corrupting issue - it is just giving false positives (and will be fixed in the next beta)

good thing serato does not make pregnancy test!



HAHAHAHAHAHAHA, that was good
Seegweed 11:54 PM - 26 August, 2010
I had the same problem with high CPU consumption in 2.1, switched to 2.1.1 beta which I used yesterday at a 6 hour gig without problem. With a few songs the waveforms did short stops and didn't move smoothly but there was no audio dropouts.
victor_M 1:16 PM - 27 August, 2010
Quote:
Has anybody had a chance to try the latest 2.1.1 yet?

You don't need to worry about the corrupting issue - it is just giving false positives (and will be fixed in the next beta)

James
I did notice a big difference between 2.1.1 and 2.1.0. It's running really nice temperature is down. It seill get's a little hot when running VSL but that has always been the case. I do notice that a couple of tracks are still writing tags but that's for another thread. 2.1.1 almost making me wanna leave 1.9.2. Almost ;-)
Serato
James 12:18 AM - 30 August, 2010
Cool thanks for the feedback guys. A combination of overviews being recalculated in the background and writing tags was the culprit.