Just posted this to tech support -ACID Product Family

Subject:Just posted this to tech support Posted by: ibliss Date:8/27/2002 8:25:29 PM Any comments/ideas/similar bugs? Bugs: Bug 1) When playing back a project, undo/re-doing causes a momentary pause in playback, and you can see the time display briefly reset to zero in the period of silence. This is not so much a bug, but it is irritating. Bug 2) with the supplied demo song playing, do the following: -a) mute all three DLS synth BUSSES. -b) solo one of the DLS busses -c) un-solo the DLS -d) un-mute the other DLS busses - they don't unmute (you have to hit Solo button twice on the busses stuck in mute mode) Bug 3) Open up MIDI or Audio in the chopper, or open up a Track Properties box for and audio track. Click on one of the time selection boxes as if you were going to type in a new value. Hit return, or click outside of the box and Acid crashes. Bug 4) Acid won't save some plugin automation data from the Buss tracks; only the first plugin in a Bus/Master/Synth fx chain will have it's automation data saved - if placed 2nd or later in the chain, no automation data will be saved. (to clarify - the automation can be input, and will playback, but when you reload the project it will not be there). Track fx chains do not seem to suffer from this problem. Bug 5) This doesn't seem to happen all the time: when vector automation has a Node 'off-screen' to the left, the line between the off-screen and first on-screen Node dissapears. This means that if you have not added Nodes and are half way along the timeline it will seem as if there is no enveleope at all - although the mouse pointer will still change to the 'hand' when over the invisible vector line. Then, as soon as you add a Node the vecotor line appears. Bug6) When I play back a project from start to finish, Acid playback stutters slightly at the points where VSTi synths are first triggered from a MIDI track. If I then play back from a point closer to the VSTi entry point, the stutter does not occur. The stutter does not show up in renders of the poject (ie renders are fine!) Bug 7) FX sends from tracks are still active when the tracks are muted. Bug 8) When rendering, reverb tails at the end of a song will be cut of UNLESS the user creates a loop region that goes beyond the end of the media in the project on the timeline, and then chooses 'render loop region only;' in the Render As... save box. Suggestions: No.1) On the subject of soloing - it doesn't work properly. The point of soloing (as I'm sure you all know) is primarily to hear a single source. Soloing a DLS synth buss doesn't mute the audio tracks. Now, I realise you can solo the MIDI track that is feeding the DLS synth to hear it in isolation, but given that you can have muliple MIDI tracks feeding a single DLS, the DLS buss solo should (IMO) work as a normal solo. Please ask questions if this doesn't make sense :) This is also important for setting up plugin FX on the DLS synths. No2) 4) It is a personal gripe that when a track/buss is muted, it's plugins are hidden from view (this is the same in Vegas). Also if another track is solo'd, the remaining tracks have their plugs hidden. Can you explain the reasoning behind this to me? I think it is useful to know that the plug-in being shown isn't actually doing anything (ie if another track is being solo'd) but I'd much prefer it to be indicated in a less 'destructive' way - this would allow you to still copy plugin settings from a muted track, for example. No3) 5) There seems to be no way to adjust all of the 5.1 faders at the same time. I know that you can use the Surround Master track with a Volume envelope, but I would have thought there would be a way to adjust the faders together directly. Not really high priority this one! No4) Can we not have plug-ins on the 5.1 bus?? :( Thinking in terms of limiting/comps/eq. I guess this plus the above suggestion would then lead to the need for seperate buss tracks for Centre, Front Pair, Back Pair & Sub.... (for automation). No5) Could Auto-scroll work in the buss tracks window too? No6) It would be really nice to see the surround pan 'diamond' moving on indiviual tracks as the track played. Extra CPU cycles, I know - perhaps as a switchable option? Certainly if nothing else it would be useful to see it move in the Surround Panner Window. No7) I quite like vector automation, but touch automation can be a little more musical at times - one for a more major revision perhaps? No8) The OPT Midi editor - would it be possible to implement vector automation here to control cc data - either as a fourth tab, or directly over the existing MIDI notes (blocks!) in the same way automation is displayed over events in the main Acid timeline. Thanks for your work so far, Mike K
Subject:RE: Just posted this to tech support Reply by: SonySteveS Date:8/28/2002 5:27:22 PM Thanks a lot for the feedback, Mike. Here are some comments on a couple of your bugs. The rest I'll get to later. Bug 2) Repro'ed and bugged. Should be fixed in the next update. Bug 3) Already bugged and fixed. Should be working fine in the next update. Bug 5) I can't reproduce this. Do you see this in bus tracks, regular tracks, or both? Does this happen with all fade types, or just certain ones? Also, what type of video card are you using? Bug 7) Is your FX send pre or post volume? If it's pre then this is by design. If it's post I can't repro your problem. Thanks, Steve
Subject:RE: Just posted this to tech support Reply by: ibliss Date:8/29/2002 9:33:46 AM Hi Steve, Quick update: >>Bug 5) I can't reproduce this. Do you see this in bus tracks, regular tracks, or >>both? Does this happen with all fade types, or just certain ones? Also, what type >>of video card are you using? Okay, I was having the problem on my laptop (integrated graphics controller on a Sis630 chipset), but couldn't repro it on my desktop (geforce3). I went to Windows' 'Display Properties>Advanced>Troubleshoot' and turned down the graphics acceleration slider by one notch (from the default 'Full' position). This cured the problem - now the Vectors always display properly. >>Bug 7) Is your FX send pre or post volume? If it's pre then this is by design. If >>it's post I can't repro your problem. Yes, it is set to Pre-volume - so I guess this is a design flaw more than a bug. Mute's should totally mute any output from a track. If I want to pre-fader send a track to an FX buss without the track output being heard, then I can either turn the volume control all the way down, or use a volume envelope set to -inf on the track. This failure to correctly (in the logical sense, rather than the way it's been designed) mute tracks means that when you solo a track, you can still hear the signals from other tracks which are going (via pre-fade send) through a bus. This requires the user to mute fx buss too - but this is less than ideal if you are trying to adjust send levels from the solo'd track to same buss you are muting to hear what you are doing! :) So, IMHO: Mute should Mute all output of the track/buss/synth that it relates to. Thanks for listening Mike K

Any comments/ideas/similar bugs?

Bugs:

Bug 1) When playing back a project, undo/re-doing causes a momentary pause in playback, and you can see the time display briefly reset to zero in the period of silence. This is not so much a bug, but it is irritating.

Bug 2) with the supplied demo song playing, do the following:
-a) mute all three DLS synth BUSSES.
-b) solo one of the DLS busses
-c) un-solo the DLS
-d) un-mute the other DLS busses - they don't unmute (you have to hit Solo button twice on the busses stuck in mute mode)

Bug 3) Open up MIDI or Audio in the chopper, or open up a Track Properties box for and audio track. Click on one of the time selection boxes as if you were going to type in a new value. Hit return, or click outside of the box and Acid crashes.

Bug 4) Acid won't save some plugin automation data from the Buss tracks; only the first plugin in a Bus/Master/Synth fx chain will have it's automation data saved - if placed 2nd or later in the chain, no automation data will be saved. (to clarify - the automation can be input, and will playback, but when you reload the project it will not be there). Track fx chains do not seem to suffer from this problem.

Bug 5) This doesn't seem to happen all the time: when vector automation has a Node 'off-screen' to the left, the line between the off-screen and first on-screen Node dissapears. This means that if you have not added Nodes and are half way along the timeline it will seem as if there is no enveleope at all - although the mouse pointer will still change to the 'hand' when over the invisible vector line. Then, as soon as you add a Node the vecotor line appears.

Bug6) When I play back a project from start to finish, Acid playback stutters slightly at the points where VSTi synths are first triggered from a MIDI track. If I then play back from a point closer to the VSTi entry point, the stutter does not occur. The stutter does not show up in renders of the poject (ie renders are fine!)

Bug 7) FX sends from tracks are still active when the tracks are muted.

Bug 8) When rendering, reverb tails at the end of a song will be cut of UNLESS the user creates a loop region that goes beyond the end of the media in the project on the timeline, and then chooses 'render loop region only;' in the Render As... save box.

Suggestions:

No.1)
On the subject of soloing - it doesn't work properly. The point of soloing (as I'm sure you all know) is primarily to hear a single source. Soloing a DLS synth buss doesn't mute the audio tracks. Now, I realise you can solo the MIDI track that is feeding the DLS synth to hear it in isolation, but given that you can have muliple MIDI tracks feeding a single DLS, the DLS buss solo should (IMO) work as a normal solo.
Please ask questions if this doesn't make sense :)
This is also important for setting up plugin FX on the DLS synths.

No2) 4) It is a personal gripe that when a track/buss is muted, it's plugins are hidden from view (this is the same in Vegas). Also if another track is solo'd, the remaining tracks have their plugs hidden. Can you explain the reasoning behind this to me? I think it is useful to know that the plug-in being shown isn't actually doing anything (ie if another track is being solo'd) but I'd much prefer it to be indicated in a less 'destructive' way - this would allow you to still copy plugin settings from a muted track, for example.

No3) 5) There seems to be no way to adjust all of the 5.1 faders at the same time. I know that you can use the Surround Master track with a Volume envelope, but I would have thought there would be a way to adjust the faders together directly. Not really high priority this one!

No4) Can we not have plug-ins on the 5.1 bus?? :( Thinking in terms of limiting/comps/eq. I guess this plus the above suggestion would then lead to the need for seperate buss tracks for Centre, Front Pair, Back Pair & Sub.... (for automation).

No5) Could Auto-scroll work in the buss tracks window too?

No6) It would be really nice to see the surround pan 'diamond' moving on indiviual tracks as the track played. Extra CPU cycles, I know - perhaps as a switchable option? Certainly if nothing else it would be useful to see it move in the Surround Panner Window.

No7) I quite like vector automation, but touch automation can be a little more musical at times - one for a more major revision perhaps?

No8) The OPT Midi editor - would it be possible to implement vector automation here to control cc data - either as a fourth tab, or directly over the existing MIDI notes (blocks!) in the same way automation is displayed over events in the main Acid timeline.

Thanks for your work so far,
Mike K