Subject:Acid 4.0 Demo

Posted by: NeoN

Date:8/28/2002 3:38:19 AM

Hi,
1)in settings i have insert a folder in witch there are a lot of vst plugins...
but down in list of plugins there aren't no plugins....(if i press refresh button plugins are olways 0...)
2)Hov i can chage the insrtument for a midi in piano roll??
3)can you tell me some name of vst instruments to use with piano roll??
4) Acid 4 is Wonderfull!!!!!!!!

Subject:RE: Acid 4.0 Demo

Reply by: jsv

Date:8/28/2002 6:30:57 AM

1)Acid 4.0 doesn't support vst plugins, only directx
3)HALion, model-E, absynth...

Subject:RE: Acid 4.0 Demo

Reply by: Spirit

Date:8/28/2002 7:06:17 AM

To hange MIDI instruments click the little icon in the middle of the track info area. A drop down menu shows what VSTis are available.

Subject:RE: Acid 4.0 Demo

Reply by: NeoN

Date:8/29/2002 3:45:49 AM

dosn't work..
I insert a new midi channel , write the song in piano roll , then
i insert a soft synth and in the window i insert SonicFoundry's soft synth...
then i link the midi channel with the soft synth (in with there are a lot of instruments) but changing the instrument i can listen only a piano...
if i'd like tu use a flaute for exemple what i must do??
Bye!

Subject:RE: Acid 4.0 Demo

Reply by: SonyNateM

Date:8/29/2002 10:18:19 AM

Currently you must use a patch change to access the different voices available through the DLS soft synth. Either insert one manually in the List Editor OPT plug-in, or you can send patch changes via a controller during live preview. This may change in a future update.

Subject:RE: Acid 4.0 Demo

Reply by: TeeCee

Date:8/29/2002 12:33:21 PM

Nate:
I was experimenting with Hybrid.acd that comes with Acid 4.0. It seems that the biggest tool we all have and maybe some of us can't figure out is the DLS synth. I was using patch change messages to choose some of the other patches in the DLS synth, but they don't all seem to be readily selectable, mainly the drum patches. Three patches are readily available, why aren't the rest? Could one of you guys whip up an Acid 4.0 DLS demo where you select alternate patches as the track plays back (around working on bugs)?

TeeCee

Subject:RE: Acid 4.0 Demo

Reply by: NeoN

Date:8/30/2002 2:10:22 AM

ha.....oky...

Subject:RE: Acid 4.0 Demo

Reply by: chaircrusher

Date:8/30/2002 7:46:36 AM

> Currently you must use a patch change to access the different voices available
> through the DLS soft synth. Either insert one manually in the List Editor OPT
> plug-in, or you can send patch changes via a controller during live preview.
> This may change in a future update.

As I have noted in other messages, the patch change thing doesn't seem to work very well, particularly for trying to select and use different GS drum kits. I'm
hoping that this is being looked at for updates.

And every other software sequencer I know has a field in a track's properties to select a MIDI patch number. This is sent as a program change every time you start the track. You can also insert patch changes if you like, but for 90% of the time, you want to select an instrument for a track and leave it.

Subject:RE: Acid 4.0 Demo

Reply by: pwppch

Date:8/30/2002 3:14:46 PM

>>And every other software sequencer I know has a field in a track's properties to select a MIDI patch number. This is sent as a program change every time you start the track. You can also insert patch changes if you like, but for 90% of the time, you want to select an instrument for a track and leave it.
<<
ACID not "every other software sequencer". You cannot do this on the ACID MIDI track, since and ACID MIDI track can have any number of possible channels played from it, each with a different patch or patches.

Remember, you are editing the MIDI file you are painting with, not the ACID MIDI Track. Just like audio.

What I could see us doing is permiting a simple patch change in the Track properties general page on each individual MIDI track with in the larger sequence.

Peter

Subject:RE: Acid 4.0 Demo

Reply by: TeeCee

Date:9/2/2002 4:45:41 PM

Peter:
As it would be ludicrous to recommend that you change the way that Acid deals with MIDI at this time, what you are offering hardly seems worthwile. If an Acid MIDI track can play back 16 channels of MIDI, a single patch change in the track properties would be nice, but only slightly effective.

-But-

Doesn't this sound ludicrous? Set a patch change in your MIDI loop. As it loops, won't it send this patch change every time? My Prophecy will reset everytime it is sent a patch change. This will result in a few seconds of silence followed by all the missed notes played with any controllers reset.

If it were possible to change the way Acid works with MIDI files, and you were to change Acid so that each MIDI track was just that, a single MIDI track with a single MIDI channel set initially to a single patch, it would certainly change the usability of ACID. Maybe an imported MIDI file would be split across tracks by the channels involved. Better for some, worse for others. Probably a ton of work for you guys.

TeeCee

Subject:RE: Acid 4.0 Demo

Reply by: pwppch

Date:9/3/2002 9:28:11 AM

Yes, the idea of sending out the patch change on every loop iteration is bad with external hardware. In the general page of the MIDI track props there is a filter that was intended to prevent the chasing of program changes. We have discovered that a bug is preventing this filter from working. This will be fixed in the next rev.

The idea of having a single ACID track represent a single "MIDI track/channel" would change ACID significantly, and it would be a ton of work for ACID. It would make ACID a sequencer more than a media looping tool. Again, you are editing and painting a file in ACID. To change MIDI to have this behavior in ACID would be a different paradigm.

Peter

Subject:RE: Acid 4.0 Demo

Reply by: thenoizzbox

Date:9/3/2002 9:50:11 AM

Another crazy idea might then be to have 2 kinds of MIDI tracks: MIDI loop tracks ((like we have now) and MIDI sequencer tracks that would work more like "ordinary" sequencers. It would be just like having audio loops, and Beatmapped or one shot sounds. That'd be more work but would probably make ACID a very attractive replacement for full fledged (and expensive) sequencer/audio applications like Sonar. I myself much prefer SoFo's user interfaces. Would that be doable? Maybe in ACID PRO 4.5? ;-)

Stéphane

Subject:RE: Acid 4.0 Demo

Reply by: TeeCee

Date:9/3/2002 12:12:12 PM

Peter:
"Yes, the idea of sending out the patch change on every loop iteration is bad with external hardware. In the general page of the MIDI track props there is a filter that was intended to prevent the chasing of program changes. We have discovered that a bug is preventing this filter from working. This will be fixed in the next rev."

If you filter patch change, how will Acid ever set your keyboard's patch? I guess the answer is to set up a measure before your song with all of your patch changes in MIDI.

Looking into SF's DLS files, I got a tip that you guys use or the creator of the DLS files used AWave Studio. It's a lot easier to get a DLS sound if you create a new DLS file with just your instrument in it. There's still some magic to Leo Cavallo's DLS files though, such as why his files containing only one instrument actually allow you to select any of the other DLS instruments. DLS seems like it has some power. A mention of Microsoft's DirectMusic Producer wouldn't hurt. It's a licensed but no cost DLS editor. A tutorial or a link to a good DLS guide would be helpful. DLS looks as powerful as any basic urtle Beach sampler on a sound card, not that anyone here has ever used such a thing.

TeeCee

Subject:RE: Acid 4.0 Demo

Reply by: pwppch

Date:9/3/2002 12:31:24 PM

>>If you filter patch change, how will Acid ever set your keyboard's patch? I guess the answer is to set up a measure before your song with all of your patch changes in MIDI.
<<

Correct, but we would only filter the patch/bank information on chase scenarios. We would send it once, and then never again. Not a complete filter, but a "smart" filter. Keeping track of the last sent patch and if a loop point occurs, only resend a patch if it has changed. For the simple scenario of a single patch/bank change at time 1.1.000, the patch would only be sent once on intial playback. For the more complex scenario of many patch changes on a single channel that occur over time - your typically GM authored uber sequence - then we would only send patch changes when required to.

Peter

Subject:RE: Acid 4.0 Demo

Reply by: pwppch

Date:9/3/2002 12:34:47 PM

That would complicate ACID's simple interface. You would now get into two modes of operation. One for MIDI to be treated like loops and one to treat MIDI like a traditional sequencer. The UI would have to change to accomidate this and things would/could get ugly very fast.

The approach we are taking is that our OPT editor interfaces will provide more and more traditional sequencer like functionality and provide a sequencer as an editor. This permits us to maintain ACID's paint model for dealing with all media types.

Peter

Subject:RE: Acid 4.0 Demo

Reply by: TeeCee

Date:9/3/2002 3:57:01 PM

A smart filter would be nice. But it might complicate dumb users. Does everyone else view this in threaded mode? I view it in "flat" mode or whatever this bulletin board calls it but I noticed Peter answers things threaded.

TeeCee