Subject:6.0c Bogged Down Issues

Posted by: LittleStudios

Date:11/5/2006 7:13:36 PM

what's up with 6.0c. i installed it along with FrameNetwork 2.0 and i was pumped to start using it. well, it sucked up my CPU resources and it was choppy and slow. it had similar issues like if you had your latency set to 1.0 mil sec and didn't have a powerful enough computer. so basically i did a system restore to yesterday before i installed the new update to 6.0c. basically back to 6.0b.

how come there's this issue.

p.s. now that i'm back to 6.0b, i'm running as smooth as can be.

Subject:RE: 6.0c Bogged Down Issues

Reply by: SonyMLogan

Date:11/6/2006 9:53:11 AM

little guy,

Could you give me a general idea of what the project contained? (track count, synth count, fx count on tracks vs busses, ratio of midi/audio tracks)

I will be looking into this today.

- Matt Logan

Subject:RE: 6.0c Bogged Down Issues

Reply by: LittleStudios

Date:11/6/2006 11:56:16 AM

i'll give you all that information as soon as i return home from work.

Subject:RE: 6.0c Bogged Down Issues

Reply by: SonyMLogan

Date:11/6/2006 2:19:46 PM

little guy,

Great. Thanks a lot for your help.

- Matt Logan

Subject:RE: 6.0c Bogged Down Issues

Reply by: LittleStudios

Date:11/7/2006 7:19:25 PM

matt,

i did the acid zip, my file is HUGE!! 715,506 KB = 715 MB.

do you still want me to upload it to that ftp site??

Like i said before. this project has never had any problems when using 6.0b, as soon as i made the switch to 6.0c, the stuttering began. i rolled back to 6.0b and everything is working fine.

Subject:RE: 6.0c Bogged Down Issues

Reply by: jtprime

Date:11/8/2006 9:39:50 AM

I have the same issue with my setup (posted 11/5/06).
I've updated my profile and the particulars of the session.
Any ideas

Subject:RE: 6.0c Bogged Down Issues

Reply by: LittleStudios

Date:11/8/2006 7:55:15 PM

hey matt,

well i'm attempting to post it as i'm typing this. the file name is `Better Time Than Ever.acd-zip'

the part where the stuttering and bogged down behavior would start towards the end of the project, right when the clapping comes in. i also noticed that with the framenetwork 2.0 installed, other programs acted all wierd and boggy, such as winamp. as soon as i did a system restore to the day prior the installation, everything worked fine.

Subject:RE: 6.0c Bogged Down Issues

Reply by: SonyMLogan

Date:11/9/2006 9:56:48 AM

our FTP server can handle that load if you are willing to Upload it.

Alternatively, you could cut the project down to a more managable size, as long as it still demonstrates the problem.

- Matt Logan

Subject:RE: 6.0c Bogged Down Issues

Reply by: LittleStudios

Date:11/11/2006 10:10:05 AM

hey matt,

well i ran some of my own tests, and it took a while. first i installed .net framework 2.0 directly from microsoft's site. then i did the acid 6.0c upgrade. i opened the project that was giving problems. the problems were still there. there are no softsynths in the project and i disable all track effects and vst's. it made absolutely no difference. so i continued to check other projects, all of the same problems were present on every single project no matter what the size was. i was also monitoring my cpu usage, it was at 100% every single time. now knowing that 6.0c requires .net framework 2.0 and sound forge 8.0d doesn't. i checked out sound forge to see if there were any issues. no issues were present.

so seeing that it didn't matter what project was used, and also that it didn't matter whether or not any vst's, soft synths or any other effect were being used, i don't see the point in attempting once again to post a project on to the ftp site.

so, as i did before, i will roll back my computer to version 6.0b without the .net framework 2.0 installed.

i really appreciate your help and effort, but i'm at a completely lost as to why my cpu is being sucked up the way it is.

oh also, i tried all the audio drivers i have and that didn't change anything.

this is the first time i've ever had any issues with a sony upgrade, i'm going to roll back for now because i have about five songs i need to mix and get ready for mastering and i'm pressed for time.

so, matt, if you could continue to try and help / fix my issue, that would be greatly appreciated.

Chris

Subject:RE: 6.0c Bogged Down Issues

Reply by: LittleStudios

Date:11/11/2006 10:26:11 AM

i just rolled back to 6.0b, i checked my cpu usage on the same projects, on average i was at about 43%, unlike 6.0c where i was maxed out at 100%.

Chris

Subject:RE: 6.0c Bogged Down Issues

Reply by: Ranger Bob

Date:11/11/2006 3:44:49 PM

I had already learned to live with 6.0b was quite used to working around the minor bugs but I went against my better judgement and upgraded to 6.0c. What a mess that was, I've since rolled back to 60.b and have learned my lesson (yeah, sure). I also thought the unexpected .net framework 2.0 upgrade was quite rude.

Subject:RE: 6.0c Bogged Down Issues

Reply by: Zacchino

Date:11/12/2006 1:32:14 AM

RangerBob, Little guy, can you guys be more specific with the issues you're having with 6.0c ?

I had no issues at all with this Framework 2.0 upgrade. So maybe that it is system-related. Can you list all the programs that are running while you're using Acid Pro ?

Get this little handy tool that tells you what programs start with your Windows, and keep me up :

http://download.sysinternals.com/Files/Autoruns.zip

(wow just realized Sysinternals has been acquired by Microsoft... They'll eat us all lol)

HTH

Subject:RE: 6.0c Bogged Down Issues

Reply by: SonyMLogan

Date:11/13/2006 3:41:50 PM

little guy,

It sounds like Acid might be having a problem with something particular to your system – since your problems are so wide-spread I would expect a lot of other users to be reporting this, but they are not.

I don’t believe .NET 2.0 would be the cause of this. There are a couple other possibilities I’d like to explore:

#1: if you remove (not just disable) all plug-ins and synths from your setup, do you still notice the problem?

#2: What does your total memory usage look like in the task manager? Does this problem exist if you play a simple one-track project with no FX?

#3: Does this problem occur no matter what device driver you use? (Asio, mapper, etc?) Is track buffering enabled? What is your playback buffering setting?

- Matt Logan

Subject:RE: 6.0c Bogged Down Issues

Reply by: LittleStudios

Date:11/15/2006 9:12:20 AM

well,

i removed the vst's (not just disabled)

my total cpu usage is maxed out

and the problem exists no matter what device driver i use

track buffering is enabled, i believe, i can't remember the setting. it's what ever the default is.

i've played projects with one simple track.

when acid is not playing the cpu usage is way down, which is cool.
as soon as i press play, WHAM! it's maxed out.

i'm just really confused why this problem doesn't exist with 6.0b, this stuff only happens with 6.0c.

i'm in no way angry. just confused. all my computer settings and acid settings are the same as they've always been and i never had problems before.

Subject:RE: 6.0c Bogged Down Issues

Reply by: jackn2mpu

Date:11/19/2006 8:07:42 AM

This .NET2.0 business - is this a new requirement for 6.0c? I know the .NET is needed for previous versions of Acid, but I'm asking about the specific version level of .NET. My DAW runs XP Service Pack 1 which MS no longer supports and I do not want to update to SP2 if I can reasonably help it.
Jack

Subject:RE: 6.0c Bogged Down Issues

Reply by: miquel

Date:11/19/2006 11:14:53 AM

By the way, The .NET Framework 3.0 has been released!

Subject:RE: 6.0c Bogged Down Issues

Reply by: randygo

Date:11/19/2006 12:15:37 PM

>By the way, The .NET Framework 3.0 has been released!

Fantastic. Another few hundred megabytes of sh*t that needs to be downloaded just to run the next version of Media Manager...

Cheers,

Randy

Subject:RE: 6.0c Bogged Down Issues

Reply by: jtprime

Date:11/20/2006 10:09:13 PM

I (jtprime) reported this same issue about 2 weeks ago. Almost identicial symptoms. Not sure about little guy's config, but I posted mine and info on very very small project that came witht PLP loop set I purchased.

BTW, the issue seems associated with ASIO. If I switch to WDM device, all seems well. It does not matter which ASIO device (i.e., kx, EMU-0404).

Also, recenlty AP6.0c began stalling (not repsonding) when updating VST effects - I can clear stall without killing AP or restarting system it by killing a cpu hogging rundll spawned program task manager process view.