|
Subject:The bug list (ATTN: SOFO)
Posted by: waynegee
Date:8/19/2002 1:33:57 PM
You guys need a bug list page/form for your stuff, so we can keep this stuff private. Anyway, here is the bug list(so far) 1) Acid 4 not keeping environment settings. Meaning, every time I launch the program it is like the very first time...toolbar is back to virgin, no last project opened, have to set up all the preferences agains, have to scan my PC for vsti's again, etc. 2)First press of the spacebar results in a .ms start and stop. Requires another spacebar press to resume playback. 3) The volume of MIDI drops 3db after about a minute. It jumps back to the original setting if I restart the program. 4) Acid crashes repeatedly each time I use VSTi's, especially FM7, Battery, Fruity 3.5 and Phat Pro. 5) If I have VSTi's checked in the Preferences dialog box, the performance becomes EXTREMELY SLOW and CHOPPY. If I kick the audio buffer settings up to 1.00, this helps a bit. Do the VSTi's sit in memory? (i.e.; are the .dll's instansiated but not called). I love it for the most part so far...I'll keep hammering at it. Thanks. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: hermanakos
Date:8/19/2002 3:44:57 PM
Here's my log: Sonic Foundry ACID Pro 4.0 Version 4.0 (Build 215) Exception 0xC0000005 (access violation) READ:0x0 IP:0x2B87B33 In Module 'sfvstisynth.dll' at Address 0x2B80000 + 0x7B33 Thread: GUI ID=0xD78 Stack=0x12F000-0x130000 Registers: EAX=00000000 CS=001b EIP=02b87b33 EFLGS=00010287 EBX=06e98e0c SS=0023 ESP=0012f80c EBP=00000008 ECX=0012fb1c DS=0023 ESI=06e98848 FS=003b EDX=02c8a878 ES=0023 EDI=06e988e4 GS=0000 Bytes at CS:EIP: 02B87B33: 8B 10 6A 00 6A 00 50 FF ..j.j.P. 02B87B3B: 52 18 8B 96 8C 01 00 00 R....... Stack Dump: 0012F80C: 00169AD8 00140000 + 29AD8 0012F810: 00000001 0012F814: 00000000 0012F818: 02CA3718 02C00000 + A3718 0012F81C: 011AFE53 01000000 + 1AFE53 (acid40k.dll) 0012F820: 06E9880C 06CC0000 + 1D880C 0012F824: 00169AD8 00140000 + 29AD8 0012F828: 0119175B 01000000 + 19175B (acid40k.dll) 0012F82C: 02CA3718 02C00000 + A3718 0012F830: 00000001 0012F834: 011919ED 01000000 + 1919ED (acid40k.dll) 0012F838: 011E2A20 01000000 + 1E2A20 (acid40k.dll) 0012F83C: 00169AD8 00140000 + 29AD8 0012F840: 00000000 0012F844: 01191AD3 01000000 + 191AD3 (acid40k.dll) 0012F848: 00169AD8 00140000 + 29AD8 > 0012F84C: 011E2A20 01000000 + 1E2A20 (acid40k.dll) - - - 0012FFF0: 00000000 0012FFF4: 00000000 0012FFF8: 005E9074 00400000 + 1E9074 (acid40.exe) 0012FFFC: 00000000 |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: Ted_H
Date:8/19/2002 4:39:06 PM
An error message without more info isn't much help :-) What were you doing when this happened? Can you reproduce it under a specific set of circumstances? What version of Windows? Ted |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: hermanakos
Date:8/19/2002 4:44:42 PM
XP Pro (completely up-to-date). Other progs running at the same time: Norton AV 2002 and ZoneAlarm Pro. It happened while editing Model E in de Midi-roll (replacing several notes at the same time). I've reproduced it once sofar. The first time it happened it was just Model E (one midichannel only in the project), the second time I also had Battery and FM7 running together with two wav-files. Ted, is there an emailaddress I can send my errorlogs with description to, instead of putting it here on the forum? Thx |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: slcrz
Date:8/19/2002 7:38:32 PM
Hi everyone... Ok there it is,I 've been trying ACID 4 for an entire day(I intented to update but I'll wait a bit to see if SOFO is fixing that App a bit) I've been an ACID fan and using it since it first came out ... (best Intuitive GUI) So... 1.during the test day ,The app crashed several times on me with the Same kind of LOG than Hermanakos(see thread above) That happen using 2 vsti MAX and not more than 10 tracks of loops and audio recording(erff bad start ) 2.the app itself seems to be So heavy compared to before (acid 3.0g)Where I could play up to 80 audio tracks and loop + Few FX in direct with no trouble... I get Slow downs,Audio glitch when I move the interface, and the worst ,REndering give me Noises and Glitch (all of that with 8 audio tarcks and 2 VSTi) I dont see how u can finish a project in those conditions... 3.From time to time when I mute or solo a track my mouse Is jumping straight to the propertie Window...(it doesnt happen all the time just in certain config - didnt figure that one out yet but I'll try to understand)anyway pretty annoying... 4.I still can't figure out how to monitor External Midi Out(besides from press record and then hear something) but that maybe me ;) 5.That weird feeling of instability :{ (funny when SOFO products are usually really Stable) Conclusion so far: I have to say that I was dying to test it,and I'm a bit disapointed... I was Hoping for a bit more worked Midi integration (this one doesnt really make u want to use it)even if I know that basically ACID is a LOOP based program,I'm sure I'm not the only one that uses it as a "ALMOST all in ONE Studio"(I record most Of my tracks "accoustically")So midi integration was definitly awaited to complete the picture... If SOFO does not intend to MORPH Acid into that dream Studio,then u should definitly think about a New APP that does (maybe integrate Some of acid features in Vegas...) anyway,we'll see what the future has plan for us till then ,Keep Up the good work. JAY p.s. Sorry for the spelling but English ain't my first language ;) |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: SHTUNOT
Date:8/19/2002 7:57:51 PM
Hermanakos...Dude I'm not sure how much help your going to get when you have "Other progs running at the same time: Norton AV 2002 and ZoneAlarm Pro." I'm not sure what kind of hardware your running+soundcard but I'd say that if you got rid of those two issues you"ll have better luck running ANYTHING. Apps like Vegas,acid,etc...run best in a enviroment dedicated to just ONE purpose. In other words only install what is necessary to get the job done. If you want to go and "chat" online I recommend you do what I do. Make two "partitions" of XP Pro[I have the same set up as standard PC mode=1cpu]. One for vegas,acid,etc...audio/video partition obviously;and one for fun[online,et...] I download my updates to a hd that BOTH partitions can see and voila. Do you have ALL your GUI enhancements disabled? Waynegee...I can't reproduce numbers 1+2. Everythings fine here with XP Pro. I don't have any Vsti's so I can't test that. Maybe you need a reformat+reinstallation? Hope not. Later. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: waynegee
Date:8/19/2002 8:30:59 PM
Once I registered, numbers 1 & 2 seemed to go away. I been having NO crashes or problems until now. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: buffalosnout
Date:8/19/2002 9:39:43 PM
I can't get it to stay in sync with SONAR 2 XL, using MTC, with ACID as the Master. Acid 3.0 locked in tight for me. I get bad drift and stutters in 4.0. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: Studio_de_Lara
Date:8/19/2002 9:57:23 PM
Well, I am having alot of problems. Mostly with Midi. I had a crash when trying to record a midi track, just locked and gave an error report similar to the one in a previous post. Had a crash when openning the piano roll editor while playing back a midi file I did successfully record. I had a crash when I selected the ASIO drivers and configured the card (Delta R-Bus). After the crash, I restarted ACID 4.0 and the ASIO wasn't listed anymore. I had to restart my machine in order to get the ASIO option to display again. Which leads to my nest question, anyone using ASIO successfully. IS ASIO the way to go with ACID 4? I haven't tested my VST instruments yet, still trying to test regular midi . ACID did not save a song correctly and re-loaded a song screwy (all the VST I's in the demo song got screwed up. Had to reload manually. One last thing, how do you monitor VST Instruments when recording midi? TED, help would be appreciated. My system: Athlon 1800 XP+ MSI mobo with 1 gig PC133 SDRAM Ultra SCSI2 Adaptec 2940UW2 card with separate SCSI drives (7200 rpm minimum) Matrox G450 dual head video card Windows SP Pro M Audio Delta R-Bus Emagic Unitor 8 Midi Interface Rich |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: Jessariah
Date:8/19/2002 10:50:57 PM
James, What's "MTC?" |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: hermanakos
Date:8/20/2002 12:32:44 AM
I have three partitions on this computer; one dedicated to XP Pro + plus AV/Firewall, one dedicated to audio and video progs and one for my audio/video-tracks. The computer on which I'm running ACID Pro 4.0 now is a PIII 600Mhz, 128MB with a simple Creative PCI-soundcard. In a week I'll be back home where I run a P4 1.7, 768MB DDR, so then the real test begins. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: Spirit
Date:8/20/2002 3:44:47 AM
I haven't tested it myself, but over at KvR they're saying that VSTi CANNOT sync bpm to Acid tempo. Given the amount of inbuilt tempo based LFOs and effects these days I'd say this was a MAJOR bug, not just a missing feature. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: buffalosnout
Date:8/20/2002 9:32:59 AM
Jessariah: I was abbreviating "MIDI Time Code," when referring to MTC. In 3.0, I was able to sync SONAR 2 with ACID. ACID was the master and was sending out SMPTE (non-drop 30) time code for SONAR to follow. Unfortunately, this has not worked reliably for me in 4.0. I am certain, however, that Sonicfoundry will have this and many of the other apparent bugs fixed with a maintenance release before long. I believe they are taking note of the issues on this forum and are tweaking the code as we speak. They want it to be right. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: pwppch
Date:8/20/2002 11:07:24 AM
What are the specifics of the ACID as MTC master problem that you are seeing? Thanks Peter |
|
Subject:RE: The bug list (ATTN: SOFO) ---> Wami Box
Reply by: antistar
Date:8/20/2002 3:24:51 PM
I work on a notebook with WinME, PIII 1GHz, 256MB, with 2 sound cards: ALi Audio WDM, Wami Box - which is a PCMCIA card with a break out box, installed drivers for Win98 supporting MME, DirectSound. After installing my purchased ACIDPro4.0 starts without problems, and works very well with my Wami Box. MIDI, tons of WAV-tracks... all these are no problems, but after quitting the program and starting again it crashes and i am never again able to start. It is just strange for the reson, that why the hell works ACIDPro4.0 for the first time (when it probably scans for availeable sound cards), and then never again. Are there any possibilities to make ACIDPro4.0 to start like the very first time after installing except the registration procedure? Like setting some registry keys? Or do i have to wait until the next patch, which maybe fixes this problem. Before ACIDPro4.0 i have been using ACIDMusic3.0 which was really stable and needed only a small CPU-performance. antistar |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: SonicBC
Date:8/20/2002 3:44:32 PM
I can't say for certain, but I would bet many of your problems would go away with a memory upgrade. WinXP asks for 128 just for itself as a minimum requirement. Add in ZoneAlarm, a huge resource sucker and NAV, known for this too. You're stretched thin. Throw a resource intense Audio app on top, then use VSTi's that love to use as much as they can, your ram usage is gonna be super intesne and eventually something is going to break. I hate to tell you to shell out more money, but maybe borrow an extra 128 from another machine for a bit and see if that helps. I've seen huge increases in performance in WinXP by bumping up to 256. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: hermanakos
Date:8/20/2002 3:50:02 PM
You certainly have a point there, but I even had a crash when ZA and NAV were disabled and only once VSTi was open (Steinberg's Model E). Next week - when I'm back in my studio - I'll install it in my normal computer (P4 1.7/768MB DRAM, WinXP) and I'll test everything again. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: pwppch
Date:8/20/2002 5:14:14 PM
It is most likely the Delta ASIO drivers. There is a know problem with the Delta series ASIO drivers. MIDIMan is working on a fix. The problem manifests itself in most of the ways you decribe. The reason you don't see the ASIO devices after the crash is because due to the driver bug, the driver is nolonger loadable/usable. The only way to recover the driver is to restart Windows. As soon as we are made aware of updated ASIO drivers for the Delta Series cards, we will post the information here. Peter |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: Spirit
Date:8/20/2002 6:29:46 PM
I tried the sync problem myself, and I find the same thing: I can't get VSTi parameters to sync to the Acid Project tempo. For example the Linplug Delta-III synth run fine in Acid, I can create MIDI tracks, run it in a window etc, but all its onboard effects and its four LFOs all naturally want to sync to host tempo. But they don't. I've gone to the sync and audio preferences but there just doesn't seem to be anything there to select. At KvR one of the Fruity developers seems most frustrated at this lack, and also that with Fruity as a VSTi there is no song position transferred either. I'm thinking maybe the ability to sync to host tempo is there somewhere since the promo shots of AcidPro4 show Absynth running as a VSTi. Since Absynth creates a lot of its effects as rhythmic pulses from LFOs and envelopes, it would be a huge loss if these couldn't be synced to the host tempo. Anyone have better luck ? |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: pwppch
Date:8/20/2002 6:55:35 PM
We are aware of this limitation and will be providing a solution. Peter |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: dlcham
Date:8/20/2002 8:56:14 PM
Is there a way to assign different channels from a single instance of a VSTi (I'm using Sampletank, with 16 channels per instance) to different midi tracks? It looks like I'd need to create a new instance of Sampletank for each midi track, and use only one of the VSTi's channels per track. Thanks - |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: pwppch
Date:8/20/2002 9:55:59 PM
You should be able to play multiple ACID tracks to a single VSTi. ACID "looks" at the VSTi as if it were an external MIDI port. If the VSTi is multitimbral (or can have one voice on MIDI channel 1, another on MIDI chan2, etc etc) then you can have as many ACID tracks routed to a single synth as you want. NOTE: You can change a channel on a MIDI track very easily from the MIDI track properties General tab page. Peter |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: dlcham
Date:8/21/2002 12:06:25 AM
Sure enough! Thanks, Peter. |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: fuzzy
Date:8/21/2002 1:35:38 AM
We are aware of this limitation and will be providing a solution. Is this limmitation the cause of ACID PRO 4 not working with Fruityloops VSTi? fuzzy |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: pwppch
Date:8/21/2002 8:20:05 AM
Yes. Peter |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: antistar
Date:8/21/2002 4:47:53 PM
Rendering Error... I've just tried to render (into wav) an ACIDMusic3.0 Project with my new ACIDPro4.0 but is repeatedly allocates to much virtual memory, so that ACIDPro4.0 seems to hang. PIII,1GHz,WinME,2 partitions (1st: 1.6 GB free RAM, 2nd 3.2Gb free RAM) In the other hand i had no problems to render a 700MB Divx4 movie. Any suggestions? antistar |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: pwppch
Date:8/21/2002 5:07:25 PM
This sounds like a bug to me. Will get it on the list... Peter |
|
Subject:RE: The bug list (ATTN: SOFO)
Reply by: aress
Date:8/21/2002 5:53:42 PM
i am getting crashs when i rezise the window with my mouse wheel.... also some stuttering on segmented [4 bar] regions that are drawn & chopped from long wav files.... |