Subject:suggestion for next upgrade or patch (APro5.0)

Posted by: esotheric

Date:11/21/2004 9:36:50 AM

Put in a function to where you can switch out a loop without removing the corresponding track


Example:

Tag Track

Loop A ** * *** ** * ** ***

switched to:

Loop B ** * *** ** * ** ***

---------------------------------------------------------------------------
the track would already be setup with the new loop; would make it easier to preview how loops would sound in the current project without having to delete and redraw

Subject:RE: suggestion for next upgrade or patch (APro5.0)

Reply by: bryanhughes

Date:11/21/2004 2:15:26 PM

Another suggestion.

Set up a series of SYSEX events that can be sent to the MIDI devices so that you can set up the appropriate banks and programs BEFORE the project starts playing.

Subject:RE: suggestion for next upgrade or patch (APro5.0)

Reply by: jumbuk

Date:11/21/2004 2:19:02 PM

I am pretty sure this feature was already there in Acid Pro 4.0. If I understand you correctly, you can drop a loop onto an existing track, and it will replace the existing loop. Check the manual.

Subject:RE: suggestion for next upgrade or patch (APro5.0)

Reply by: JohnnyRoy

Date:11/21/2004 4:30:07 PM

Yep, Just drag a new loop onto the header of an existing track and it replaces that loop.

~jr

Subject:RE: suggestion for next upgrade or patch (APro5.0)

Reply by: esotheric

Date:11/22/2004 6:43:57 AM

didn't know that... will give it a whirl

Subject:RE: suggestion for next upgrade or patch (APro5.0)

Reply by: Dark_Matter

Date:11/22/2004 11:06:29 AM

I suggest to make some changes in a process of recording MIDI.
1. Some soft-synth (such as Edirol Super Quartet, RM4, etc.) have multiple outputs (they are looks like rack mount). Acid 5 open each output as different synth with appropriate number, etc. Each of synths modules have their own midi channel. But when you record MIDI recorded data transfered as CHANNEL 1, and if you for example trying to record via module on channel 3 you will hear only sound from module on channel 1. Of course you can fix it later in Global option of midi track, but all this is very annoying. Can you give as abilty to chose between default record channel?
2. I suggest to limit number of synth displayed in mixer window in that case (when soft-synth have muptiple outputs). For example, when i open Linplug RM4 (drum module), in mixer windows 5 or 6 additional installations of RM4 also opened. And they are absolutely useless. You can't record anything via it. They are like garbage. In ACID 4 everything worked fine and rm4 opened as one instance. Can you fix it? Or make it usefull?

Subject:RE: suggestion for next upgrade or patch (APro5.0)

Reply by: JohnnyRoy

Date:11/22/2004 11:57:46 AM

> I suggest to limit number of synth displayed

You need to adjust the number of outputs that are exposed to ACID from within the VSTi. ACID is only showing you what the VSTi exposes. Some VSTi's, like Kontakt, allow you to adjust the number of outputs and then ACID will only show the ones you asked for. I agree it might be nice to have an option like the one SONAR does to expose either the first stereo pair or all outputs.

~jr

Subject:RE: suggestion for next upgrade or patch (APro5.0)

Reply by: pwppch

Date:11/22/2004 12:23:25 PM

We have tested with both the Edirol and RMIV synths. They work in ACID exactly how they were intended to work (and how they work in Cubase/Nuendo.)

1. ACID does not open a different synth for each bus. Only one instance is created with a single MIDI port of 16 channels (since this is all VSTi defines) VSTi has a single 16 channel MIDI port exposed. This is what ACID exposes on a track. If the VSTi maps each MIDI channel to a bus, then this is what ACID exposes.

2. ACID does not create multiple instances. I just exposed all the buses that the VSTi tells it are available. Only a single VSTi "MIDI port" is created.

What behavior are you seeing that is not consistent with this?

Peter

Subject:RE: suggestion for next upgrade or patch (APro5.0)

Reply by: Dark_Matter

Date:11/23/2004 8:16:58 AM

Ok, Peter. Thank you for your answer. I solved this problem. In Acid 4 as i understand was no multiple-out support. Acid 5 opens each multi-out as section of the same plug-in in mixer windows. Am i right? That was new for me and i thought that it was wrong behavior of ACID. After your explanation everything looks fine. I carefully read infos for every plug-in and now i can control it. :0). Thank you very much for your patience. That was just new feature of Acid 5.
P.S. The downside of this feature is overcrowded mixer window. And also it's really hard to record for each independent module of the same plug-in without appropriate control of recodring proccess (i described it also in previous post).