Subject:How's the 5.0a update coming along?

Posted by: mcseay

Date:2/11/2005 9:30:42 AM

Just curious. Its been almost 4 months since the initial release. Version 5 is so buggy, I can't use it. I have gone back to using version 4.

Subject:RE: How's the 5.0a update coming along?

Reply by: porkjelly

Date:2/15/2005 10:10:05 AM

You might be waiting for a while. It took Sony almost a year to release the Sound Forge 7.0b update.

Subject:RE: How's the 5.0a update coming along?

Reply by: JohnnyRoy

Date:2/15/2005 12:36:19 PM

This is a double edged sword. I remember Pinnacle Systems releasing patch after patch after patch to their software breaking almost as many things as they fix with each one just because customers were clamoring for fixes. It is much better to wait until a stable update is ready than to continually release patches that cause other problems. Sony is working on an update. I’m sure as soon as they feel it’s stable, they will release it. I’m waiting for a few things to be fixed myself.

~jr

Subject:RE: How's the 5.0a update coming along?

Reply by: SonyJennL

Date:2/15/2005 6:17:30 PM

By the way, to those of you who are complaining about ACID being so buggy.

You will highly increase your chances of getting bugs that bother you fixed if you tell us what is the problem. And I don't mean "ACID crashes". Tell us what you were doing when it crashes.

As for "how's the 5.0a update coming along"... nicely, thanks. Lots of fixes so far. It will be out when it's ready.

Subject:RE: How's the 5.0a update coming along?

Reply by: Zacchino

Date:2/15/2005 9:27:20 PM

That's a good thing. But I'm wondering if all clients of AP5 goes in this forum. Do you guys have had a lot of bug reporting from your US Hotline ?

Cuz I was thinking about how the forum users' reports are really significant (in a quantity level).

I hope there's not too much work left for this update so far !

Subject:RE: How's the 5.0a update coming along?

Reply by: PHLENDO

Date:2/16/2005 6:39:05 AM

If you are having trouble with Acid Pro 5, you need to check out this website regarding tuning/configuring your (XP) machine for music applications.

Most computers are not geared for music. Priority is usually given to the XP background apps which suck up all of your available memory, causing your audio apps to freak out. Go to this site: http://www.musicxp.net/tuning_tips.php. READ carefully. Disregard tip #10: You WANT to map through your soundcard, so that you can use the "render to new track" feature.

The only drawback making these changes is that you are left with a dedicated DAW, so anyone else who needs to use it for business, etc. may not like the changes.

Hope this helps.

Subject:RE: How's the 5.0a update coming along?

Reply by: H2000

Date:2/16/2005 12:14:15 PM

Glad to hear the update is coming along.

Unfortunately, my time is limited, so I do not have time to chase down every single crash I have with Acid5. I do report when I find repeatable bugs if I have a chance, but to be honest, there are many, many times where Acid just hangs or crashes with all different error messages (exception errors, rewire errors(which I'm not using), etc.). Usually this happens when I am working, so fo me I just restart and move on. I don't really have the time to document every crash. There are too many. And, if you want to talk systems, I have been using Acid Pro 4 on my Audio only optimized PC, and it does not have the same stability issues.

I will mention that several VST plugs cause the program to hang. And, when I tried the wrapped DX versions (which work fine in Acid4), it hangs also. I also have Acid4 files that open in Acid5, but when you hit play it hangs.

I general, I find the program to have many stability issues which hopefully you will work out. To suggest to buyers of your programs that they report them all is tough. I'm sure people try when they can, but for many people they might just throw up their hands and forget it.

I think further testing before release would have helped (although v5 wasn't nearly as bad as v4 first release - which was horrendously unacceptable).

Subject:RE: How's the 5.0a update coming along?

Reply by: mnickolas

Date:2/16/2005 1:26:05 PM

>If you are having trouble with Acid Pro 5, you need to check out this website regarding tuning/configuring your (XP) machine for music applications. <

Sorry, but I'll have to disagree with this. I've been using computers since the Apple IIE days to make music (okay, I'm an old man <grin>), and I work full time from my own studio. I once had a tech support job for a major music software manufacturer and my opinion is the Acid Pro 5 problems are not correctable by simply tweaking your system. My install of Acid 5 really bit me on the a$$. So much so that I plan to test the update on a copy of my C drive, before actually committing to it on my working setup.

Michael Nickolas
www.studionineproductions.

Subject:RE: How's the 5.0a update coming along?

Reply by: SonyJennL

Date:2/16/2005 1:56:53 PM

H2000,

You mention that several VST plugs cause the program to hang.

What plug-ins are you seeing this with? Realize that there are many plug-ins available and it is simply impossible to extensively test every single one. If you have a plug-in with a problem, tell us what one.

thanks,
Jenn

Subject:RE: How's the 5.0a update coming along?

Reply by: H2000

Date:2/16/2005 3:22:54 PM

Hi Jenn,
I had trouble with Voxengo Stereo Touch, PSP Stereo Enhancer and PSP PseudoStereo. I posted the error below.

But, since I had the problem, I didn't want to waste a lot of time so I went and set it up with the DX Wrapped (DirectiXer) Version in Acid4 and it worked fine. Now here is the clincher - if I load the Acid4 project into Acid5 it works/plays just fine. But, if I then try to load up the plugins again in Acid5, I get the error again. Also, another bizarre thing is that I tried the plugs on another project in Acid5 and did not have the problem. So, it is sometimes hard to keep track of these kinds of bugs as they are hard to pin down. In fact, I'm not entirely sure it would have mattered which plugin it was.

------------------------------------------------------------------------------------------------------
Sony ACID Pro 5.0
Version 5.0 (Build 265)
Exception 0xC0000094 (integer divide by zero) IP:0x876781B
In Module 'sfvstwrap.dll' at Address 0x86B0000 + 0xB781B
Thread: GUI ID=0x3B0 Stack=0x12F000-0x130000
Registers:
EAX=00000000 CS=001b EIP=0876781b EFLGS=00010246
EBX=00000000 SS=0023 ESP=0012f218 EBP=00000000
ECX=00000000 DS=0023 ESI=00000000 FS=003b
EDX=00000000 ES=0023 EDI=001c15a8 GS=0000
Bytes at CS:EIP:
0876781B: F7 FE 5E 5B 8B C2 83 C4 ..^[....
08767823: 08 C2 04 00 CC CC CC CC ........
Stack Dump:
0012F218: 001C1318 00130000 + 91318
0012F21C: 00000001
0012F220: 00000000
0012F224: 00000004
0012F228: 08767F04 086B0000 + B7F04 (sfvstwrap.dll)
0012F22C: 00000002
0012F230: 0C777B08 0C690000 + E7B08
0012F234: 001C11F8 00130000 + 911F8
0012F238: 0012F310 00030000 + FF310
0012F23C: 00000800
0012F240: 00000000
0012F244: 00002D50
0012F248: 00000004
0012F24C: 00000002
0012F250: 00000000
0012F254: 00000000
> 0012F274: 086B1D89 086B0000 + 1D89 (sfvstwrap.dll)
0012F278: 00000001
0012F27C: 000000B5
0012F280: 00000001
0012F284: 00000000
> 0012F290: 00623E2E 00400000 + 223E2E (acid50.exe)
0012F294: 0000AC44
0012F298: 0000E2C2
> 0012F29C: 00623EA7 00400000 + 223EA7 (acid50.exe)
0012F2A0: 00000000
0012F2A4: 060E6EE0 05F00000 + 1E6EE0
0012F2A8: 00020003 00020000 + 3
0012F2AC: 0000AC44
> 0012F314: 08763540 086B0000 + B3540 (sfvstwrap.dll)
0012F318: 00000000
0012F31C: 00000000
0012F320: 05F32B90 05F00000 + 32B90
0012F324: 0000E2C2
> 0012F330: 0876AE18 086B0000 + BAE18 (sfvstwrap.dll)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 00637390 00400000 + 237390 (acid50.exe)
0012FFFC: 00000000

Subject:RE: How's the 5.0a update coming along?

Reply by: coolout

Date:2/17/2005 3:15:19 AM

"By the way, to those of you who are complaining about ACID being so buggy.

You will highly increase your chances of getting bugs that bother you fixed if you tell us what is the problem. And I don't mean "ACID crashes". Tell us what you were doing when it crashes.

As for "how's the 5.0a update coming along"... nicely, thanks. Lots of fixes so far. It will be out when it's ready."

Jenn thanks...you're the best.

i have some issues and i'm curious if they've been addressed.

1. UAD-1 cpu munching

2. occasional stuck notes on some vsti

3. scanning for plugins at startup causes AP5 to load much slower than AP4

4. will live triggering of one-shots ever be immediate (where you can hear what you're playing everytime), polyphonic (where you can assign different tracks to different keys), or triggered through midi?

5. i also noticed that if record in 24-bit using the microsoft sound mapper driver i get crackles all over my recording, but if i use asio it's fine. this is strange considering my asio latency is way lower and using more cpu.

6. i can get AP5 to crash everytime if i start a new project and attempt to render to a new track and i haven't named and saved the whole project yet.

7. this is a silly one, but why doesn't acid remember how i open files? everytime i open a saved project i have to reselect the file type (acid project files), change the view back to "details" and then hit the sort by "date modified" field just to find what i'm looking for. every other windows app can remember how i last opened a file.

that's all for me...

Subject:RE: How's the 5.0a update coming along?

Reply by: Lavoll

Date:2/17/2005 3:59:56 AM

Here's the one bug that has happened to me with ACID. (It has never crashed on my system, which I am very happy about)


When recording midi, alot of notes are stuck in the beginnin gof the midi track. notes that i havent played after i've hit record.
My theory: there's a full buffer or something somewhere of midi notes, and they are dumped into the track. I'm guessing this because they are notes that i have played at some point... but not meant to record.

does that make sense?

It's happening on a M-AUDIO RPC-1 audio card.

Subject:RE: How's the 5.0a update coming along?

Reply by: JohnnyRoy

Date:2/17/2005 8:20:38 AM

> When recording midi, alot of notes are stuck in the beginnin gof the midi track. notes that i havent played after i've hit record.

I’ve seen this too. It’s very strange. I had notes in a section that I never even touched the keyboard.

~jr

Subject:RE: How's the 5.0a update coming along?

Reply by: MyST

Date:2/17/2005 1:43:15 PM

Coolout, I tried you're number 6.

I opened a new project.
I selected a loop.
Painted the loop .
Selected Render to New Track.
Rendered it.

No problems. Worked great.
Did I miss a step that maybe makes your machine crash?

Mario

Subject:RE: How's the 5.0a update coming along?

Reply by: mcseay

Date:2/17/2005 4:49:35 PM

SonyJennL,

I am not trying to start a pissing match here, but...

I submitted an error report on November 11, 2004 (with a full description of the problems I was having). My frustration is that I have paid for something that I can not use yet. I have been a faithful Acid user since its inception, purchasing every upgrade and a fair amount of loop libraries along the way. If is wasn't so passionate about Acid, I would not be here in this forum. I am optimistic that an update will solve an problems I was experiencing.

Subject:RE: How's the 5.0a update coming along?

Reply by: MyST

Date:2/17/2005 4:54:32 PM

Post your error here. You never know, maybe we've encountered the same thing.
Maybe someone has a workaround/solution.

Mario

Subject:RE: How's the 5.0a update coming along?

Reply by: coolout

Date:2/17/2005 6:36:32 PM

"Coolout, I tried you're number 6.

I opened a new project.
I selected a loop.
Painted the loop .
Selected Render to New Track.
Rendered it.

No problems. Worked great.
Did I miss a step that maybe makes your machine crash?

Mario"


it crashes acid everytime on my PC. Here's the error:

Sony ACID Pro 5.0
Version 5.0 (Build 265)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x47100A
In Module 'acid50.exe' at Address 0x400000 + 0x7100A
Thread: GUI ID=0xBB4 Stack=0x129000-0x130000
Registers:
EAX=00000000 CS=001b EIP=0047100a EFLGS=00010216
EBX=00129c90 SS=0023 ESP=00129800 EBP=0012a7c8
ECX=00000000 DS=0023 ESI=0012a7d4 FS=003b
EDX=0012a9e4 ES=0023 EDI=0012a9dc GS=0000
Bytes at CS:EIP:
0047100A: 8B 08 50 FF 51 04 8B 83 ..P.Q...
00471012: 18 02 00 00 8B 10 50 FF ......P.
Stack Dump:
00129800: 0012B588 00030000 + FB588
00129804: 00000000
00129808: 0012B58C 00030000 + FB58C
0012980C: 00000000
00129810: 00000000
00129814: 00000000
00129818: 00000000
0012981C: 00000000
00129820: 00000000
00129824: 00000000
00129828: 00000000
0012982C: 00000000
00129830: 00000000
00129834: 00000000
00129838: 00000000
0012983C: 00000000
> 0012985C: 0185000F 017E0000 + 7000F (sfpublish.dll)
00129860: F8010531
00129864: 0000005C
00129868: 00000000
0012986C: 00000370
> 00129880: 006AB518 00400000 + 2AB518 (acid50.exe)
00129884: 00000343
00129888: 00000000
0012988C: 0000035B
00129890: 00000016
> 00129898: 7195B532 71950000 + B532 (COMCTL32.dll)
> 001298A8: 7195A8E1 71950000 + A8E1 (COMCTL32.dll)
> 001298B8: 018A0021 01870000 + 30021 (sfnetmedia.dll)
001298BC: 00000383
001298C0: 00000002
001298C4: 00000386
001298C8: 00000016
> 001298D0: 77D45306 77D40000 + 5306 (USER32.dll)
> 001298D4: 0041A213 00400000 + 1A213 (acid50.exe)
001298D8: 0004029A 00030000 + 1029A
001298DC: 001298EC 00030000 + F98EC
001298E0: 0012999C 00030000 + F999C
> 001298E4: 0041A150 00400000 + 1A150 (acid50.exe)
001298E8: 00000000
> 001298EC: 0101005B 01000000 + 1005B (acid50k.dll)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 00637390 00400000 + 237390 (acid50.exe)
0012FFFC: 00000000

Subject:RE: How's the 5.0a update coming along?

Reply by: Weevil

Date:2/18/2005 6:56:25 PM

You will highly increase your chances of getting bugs that bother you fixed if you tell us what is the problem. And I don't mean "ACID crashes". Tell us what you were doing when it crashes.

...I reckon I have more chance of getting hit by lightning than having one of my bug reports / enhancement requests stomped on...

But what the hell, haven’t been kicked in the guts for ages, who knows it might be fun this time. ...Gosh I sound a little cynical don’t I... :-)

Hows about the old ‘right-click-and-drag drops events in the wrong spot’ bug???

Been around for eons...Same bug that used to be in the big V, got stomped on over there but still kicking on strong in A5.

To reproduce: turn snapping on, right-click-and-drag an event to copy it to a new location. Event snaps correctly to grid position ***until*** you let go of right button. Then its position goes all funky town.

...Also while we are in the right-click-and-drag neck of the woods...

You can’t right-click-and-drag to move or copy events while using the Selection Tool (like you can with the Draw Tool). Don’t know if that is a bug or just an oversight. But it’s really annoying being forced to swap tools to perform a simple edit.

...And finally to wrap up the whole right-click-and-drag saga, a wee feature request:

Currently when right clicking and dragging you receive ‘Move Here’ and ‘Copy Here’ as menu options. ‘Twould be lovely if in addition to those you had a ‘Copy Repeat Here’ menu item.

Subject:RE: How's the 5.0a update coming along?

Reply by: Weevil

Date:2/18/2005 8:48:05 PM

...Got me thinking about editing annoyances now...

One thing that has irritated me for a long time is the lack of ability to simply and quickly move/copy events while at the same time retaining their relative positions within measures.

The program has no problems doing this if one of the events being copied falls on beat one of a measure. But very often this is not the case:

...Say I have two one shot snare drum events, drawn in on beat 2 and 4 of a measure.

So to copy them I select both of them and Ctrl-drag them to the next bar. Unfortunately (for example) I have snapping on and set to measures so the snare that is supposed to be on beat 2 is now insisting on snapping to beat 1.

999 times out of 1000 all you want to do is grab the events in one measure (or measures) and drop them in the same spots in another measure.

It would be ideal if you could just get on with it and not have to worry about what snapping was set to, or what beats the events were on or anything like that.

A simple solution would be to have a ‘relative to measures’ snapping override mode.

It could work in the same way that holding down Shift already overrides snapping while dragging.

So if you hold down Alt while dragging it overrides normal snapping, and the selected events snap ‘relative to measures’ instead.

A much more ‘musical’ workflow than the present situation.

Subject:RE: How's the 5.0a update coming along?

Reply by: H2000

Date:2/18/2005 9:51:00 PM

That's a great one - I seem to have that issue alot. Not really a bug, but an annoyance as you said.

Subject:RE: How's the 5.0a update coming along?

Reply by: mortalengines

Date:2/19/2005 12:20:39 PM

I crashed acid a couple of times when trying to open up the express f/x dynamics & an express fx eq while the program was in "play mode". This wasn't a problem if I stopped playback before adding effects to my chain.

Subject:RE: How's the 5.0a update coming along?

Reply by: Zacchino

Date:2/22/2005 5:50:18 AM

That's a great solution !

What about a Group/ungroup function ala Reason (the best Reason sequencer function after the shuffle knob).

That would also easy up the "organizing" process for a song (with color-schemed groups). Wouldn't it ?

Subject:RE: How's the 5.0a update coming along?

Reply by: SonyJennL

Date:2/22/2005 8:18:10 AM

(working my way down the list to respond to everyone who posted a complaint... may take a little time but keep checking back...)

H2000,

I can't reproduce any crashing with Voxengo Stereo Touch with either the release version or the later versions we've been working on. I've tried multiple system w/ various hardware and can't find any problems.

As for the PSP plug-ins... Those absolutely do crash ACID. They also crash Sonar and won't even open in Cubase. That points to a problem with the plug-in itself, rather than our software. We're contacting the plug-in manufacturer. (you also might want to do the same.)

-Jenn