Subject:List of known bugs in AP6

Posted by: frogman06

Date:4/14/2006 12:57:30 AM

Be nice if there was a on going list so we could all know what to expect.

Subject:RE: List of known bugs in AP6

Reply by: Spheris

Date:4/14/2006 5:40:44 AM

1. Guru VSTi does not init properly
2. Virus external midi/audio routing is not reliable
3. Waves S360 does not insert to surround setups

That's about it from this side.

Most everything else I've seen so far is procedural (end user) errors - including a few real winners of my own (careful with those catalyst drivers). Comes with a near complete overhaul.

Subject:RE: List of known bugs in AP6

Reply by: pwppch

Date:4/14/2006 9:24:37 AM

2. Can you be specific. Please, provide details.

3. ACID 6 does not support Surround plugins.

Peter

Subject:RE: List of known bugs in AP6

Reply by: LittleStudios

Date:4/14/2006 12:36:53 PM

when both AP5 and AP6 are installed on the same machine there are problems. the biggest problem i've seen is when using AP6 the audio bus effects get bypassed. in order to have the audio bus effects not to be bypasses you need to delete each bus. reinsert a new bus and re add the effects back on. then reroute everything.

to fix this bug i've uninstalled AP5. that has seemed to fix the issues. But when both AP5 and AP6 are installed, the problem returns.

Subject:RE: List of known bugs in AP6

Reply by: Spheris

Date:4/14/2006 6:25:20 PM

2. Any change in channel or preset select in the virus vst/hardware rack combo resets the defaults in the preset select and channel select

I reported it last week, probably just in the shuffle right now

3. Damn. I repeat...damn

Well can't always have it all..

Subject:RE: List of known bugs in AP6

Reply by: pwppch

Date:4/14/2006 6:36:27 PM

What version of Virus to you have?

Peter

Subject:RE: List of known bugs in AP6

Reply by: miquel

Date:4/15/2006 12:20:56 AM

copied from another thread:

I've experienced that AcidPro6 doesn't manage properly the Vstplugins which have its own sequencer.

DK+, Phrazor, Microtonic, energyXT, ...

Out of sync a bug?

Subject:RE: List of known bugs in AP6

Reply by: alltheseworlds

Date:4/15/2006 12:34:16 AM

I've experienced this several times: If I leave a project open for a long time (overnight) sometimes the cursor position and zoom functions will be "dead" when I return. I need to reload the project to reactivate them. Maybe just me...

Subject:RE: List of known bugs in AP6

Reply by: gjn

Date:4/15/2006 3:47:49 AM

problem with kontakt 2.
crash of acid 6 .
problem with DFD option.

no problem with acid5 pro.

Subject:RE: List of known bugs in AP6

Reply by: miquel

Date:4/15/2006 4:21:29 AM

Sorry to say that here K2 runs flawlessly

Subject:RE: List of known bugs in AP6

Reply by: Spheris

Date:4/15/2006 7:59:23 AM

Polar version. It's not mine though. It's Jim Youngs. He went with acid on my recommendation and unfortunately the polar is biting him on it.
Any change in the channel at all seems to randomly reset the preset and controller data sent to it.

about the s360 - I'll say damn again..any chance of future support?

Subject:RE: List of known bugs in AP6

Reply by: gjn

Date:4/15/2006 8:23:35 AM

For kontakt2, it is the "dfd" which rests problem with acid6.

It is necessary to lower the polyphony;
Otherwise...crhashhhhh

Subject:RE: List of known bugs in AP6

Reply by: jyoung50

Date:4/15/2006 5:11:32 PM

I'm the one with the TI Polar. Acid 6 is showing this strange behavior in conjunction with the TI. Although the TI is an external synth it installs a VST that acts as a control for the TI. Through the VST you can load up to 16 instruments that can be triggered through separate channels from ACID. The problem is that if I setup a track and point it to a channel in the TI VST and then change the channel number from the track side, the instrument in the TI VST (for that channel) gets reset to an arbitrary default instrument, which completely messes up any instrument setups I may have had on the TI.

Subject:RE: List of known bugs in AP6

Reply by: klyon

Date:4/15/2006 7:59:29 PM

Loading a large Reason file with autosave turned on in Acid hangs it up. (Tried it several times to be sure; deselecting "autosave" solves the problem.)
Midi loops glitch at the loop point (using rewired Reason).

Subject:RE: List of known bugs in AP6

Reply by: pwppch

Date:4/15/2006 8:17:45 PM

Good find on the autosave. Definitely hanging inside of Reason. Will have to contact the Propheads on this one.

What version of Reason are you using?


The loop glitch is a known issue and will be resolved for the update.

Thanks,
Peter

Subject:RE: List of known bugs in AP6

Reply by: klyon

Date:4/15/2006 8:28:23 PM

3.03. I know there's a newer one (3.04). I don't know if that will make a difference; I read the small list of fixes and they didn't seem to apply (I think they were OSX-centric) so I never took the time to install it as 3.03 was working fine and it would require digging in my closet for the original disks. If I have time I'll do that tomorrow and see if it makes a difference.
Cheers.
kL

Subject:RE: List of known bugs in AP6

Reply by: miquel

Date:4/16/2006 2:46:14 AM

I've found that AcidPro6 inline midi cursor doesn't follow the midi events accurately with VSampler.

I don't know if this happens with other samplers.

I'll check ...

Subject:RE: List of known bugs in AP6

Reply by: miquel

Date:4/16/2006 3:32:26 AM

I think this is not an VSampler issue.

It could be an EMU ASIO driver issue because MS Mapper doesn't produce this malfunction.

Subject:RE: List of known bugs in AP6

Reply by: gihanjay

Date:4/16/2006 8:31:12 AM

Acid Pro has number of issues. To begin, when you replace a loop with a existing loop on the Folder, the file name of the file is never replaced with the new name but the wav form display changes its name to the new name.

I just lost a entire file I was working on for over 2 weeks. I had a VST plug in that Acid reported as a "problem' but nothing more info is provided, and because of this, I can rename the file to a new one nor can I save the file with the current name.

My Scroll bars are completely gone from the screen I have no idea how this happened.

Subject:RE: List of known bugs in AP6

Reply by: porkjelly

Date:4/16/2006 11:51:45 AM

Every clip I load has "Preserve pitch when stretching" selected by default. A bug?

Subject:RE: List of known bugs in AP6

Reply by: Djipy

Date:4/17/2006 8:31:47 AM

Chopper bug here.

Subject:RE: List of known bugs in AP6

Reply by: porkjelly

Date:4/17/2006 9:47:17 AM

>> Every clip I load has "Preserve pitch when stretching" selected by default. A bug?

Nevermind. I believe I have corrected this problem.

Subject:RE: List of known bugs in AP6

Reply by: slr

Date:4/18/2006 12:15:48 AM

Encountered two minor bugs tonight while exploring:

1 - When working on surround project and bus tracks displayed, clicking on automation for surround mixer (on the surround bus track) works fine, but I cannot click again to turn off. Clicking the automation button on the surround mixer panel does not clear out the surround master bus track automation button state. My workaround was to change to a stereo project, click the bus automation off, then switch back to a surround project.

2 - When fully zoomed out on horizontal axis, mouse wheel up would not zoom in unless spun very fast. As long as zoomed in one notch, it would work as expected (one click up or down would zoom in or out one level). If I zoom out all the way, then zoom in would require fast spin again. Also, + button next to horizontal scroll bar would not zoom in at all from full zoom out. Created new project and odd behavior disappeared.

-Steve

Subject:RE: List of known bugs in AP6

Reply by: J Psycle

Date:4/19/2006 3:03:04 PM

Although a lot of the VST plugin problems I've been having with AP5 seem to be solved in AP6 (particularly with T.C. Electronic plugs), I've been having problems with certain VST plugins in AP6 that still work perfectly fine in AP5. For instance, the Nomad Factory Blue Tubes bundle works perfectly fine in AP5, but they won't even load in AP6. It gives me an error message that those plugins are not properly installed, yet they show up in the VST plugins list. I have tried both reinstalling AP6 and reinstalling the Blue Tubes plugs on both my PC and Laptop to no avail.

Here is a copy of the specific message it gives me whenever I try to load a Blue Tubes plug:

"The plug-in could not be run. One or more components required to run this plug-in may be missing.

If a hardware key (dongle) is required to operate this plug-in, ensure that it is properly installed.

The COM object failed to initialize."

When I click on the details tab, it says:

"The Plug-in 'BT BrickWall BW2S' failed to load. Please make sure the plug-in is properly installed."

I hope this gets resolved, because the Blue Tubes plugs are some of my favorites.

Subject:RE: List of known bugs in AP6

Reply by: Weevil

Date:4/21/2006 4:06:35 AM

I haven’t had enough time to really put the program through its paces. :( I have however noticed the below behaviour:

When you drop a file from the File Explorer to the Track List a new track is created with no events in it.

When you drop a file from the File Explorer to the Track View the new track is created and the track is populated with the file you dropped.

When you drag multiple files to the Track List multiple empty tracks are created as expected.

...But...when you drag multiple files to the Time Line all the tracks are created but only the first track is populated. This seems a little strange.

If you are creating a new project from already recorded tracks you want to be able to quickly populate the project by dragging and dropping all the files at once. Rather than having drop or having to draw them all out individually.

Subject:RE: List of known bugs in AP6

Reply by: AxEast

Date:4/26/2006 6:10:30 AM

... possible bug with multiple wave editors usage.

I have both Wavelab and SoundForge.
After specifying them in the "Options>Preferences>Editing",
- when accessing with r.click on the explorer window both editors appear for use ...
- when accessing from the r.click on track>paint clip>.. only the first one and appears twice.

Subject:RE: List of known bugs in AP6

Reply by: drew_

Date:8/24/2006 10:47:41 AM

I found Undo when using Inline MIDI Editing to be buggy...

Sometimes I play a MIDI part, then stop, draw an extra note or two in - if I undo it deletes the recording but leaves the drawn notes... undoes the penultimate step only.

Also I find that sometimes I undo (using Ctrl-Z) and nothing changes on screen, yet the undo menu item will suggest it has been performed (eg. the Redo option for Record or Draw will now be showing)

Has anyone else experienced this?