To Sofo regarding Fruityloops by Imagline -ACID Product Family

Subject:To Sofo regarding Fruityloops by Imagline Posted by: Jacose Date:9/4/2002 12:55:36 PM Hey, I know you guys are working on getting these programs together, but I was also wondering, you should talk to reflex or gol about their scheme for 3.7, as far as there "piano roll playlist" is concerned. Eseentialy, Fruityloops can only stay in ONE time sig throughout a whole fruityloops arrangement. They are changing that very soon with what I mentioned above, the piano roll playlist. You dont just do loops in fruity of course, you do whole songs as well. How you do this is by using the playlist. each track on the playlist represents a certain loop, and you arrange them together. (just like Acid's track view, in a way.) the problem is, you cant trim the blocks up or slice them, and they all have to follow the songs Pattern length (basically tim sig), which cannot be changed. I hope there is away to sync these two up with tim sigs as well because I am looking foward to some freaky shiz wit deeez two programs
Subject:RE: To Sofo regarding Fruityloops by Imagline Reply by: SonyNateM Date:9/4/2002 1:07:04 PM I just checked on this, and FruityLoops will just ignore the time signature change and "free wheel" after that. Tempo sync will still occur, but the measures are thrown off. FruityLoops remains in it's previous time signature. If FruityLoops is limited to a single time signature per project, then I'm pretty positive there will be no way that ACID could affect this, or "extend" FruityLoops' capabilities. I'm not sure if this will change when they release their new version. Time signature changes may not be part of the tempo sync/start position addition to VSTi that we are adding support for.
Subject:RE: To Sofo regarding Fruityloops by Imagline Reply by: pwppch Date:9/4/2002 1:47:49 PM VSTi supports both time sig change info and tempo info, and ACID will transmit this information to any VSTi that asks for it. If FL follows this information, then it can track tempo and meter changes. There is a limitation in how VSTi defines the changes though. There is no mechanism to indicate exactly when tempo and/or time sig change within the specific sample frame being processed. gol has never mentioned anything about this to me in our previous emails, so I guess it must be sometime off. Peter
Subject:RE: To Sofo regarding Fruityloops by Imagline Reply by: pwppch Date:9/4/2002 1:49:44 PM ACID will report its current time sig to a VSTi. It is up to the VSTi to deal with this. The limitation is that VSTi does not define a mechanism to tell the plug "when" the time sig change has occured relative to the current sample frame that the plugin is processing/rendering. This is suppose to be part of VST 3.0. Peter
Subject:RE: To Sofo regarding Fruityloops by Imagline Reply by: Jacose Date:9/4/2002 3:11:35 PM hmmmm... maybe something could be hooked up later on....

Subject:To Sofo regarding Fruityloops by Imagline

Posted by: Jacose

Date:9/4/2002 12:55:36 PM

Hey, I know you guys are working on getting these programs together,
but I was also wondering, you should talk to reflex or gol about their scheme for 3.7, as far as there "piano roll playlist" is concerned.
Eseentialy, Fruityloops can only stay in ONE time sig throughout a whole fruityloops arrangement.
They are changing that very soon with what I mentioned above, the piano roll playlist.

You dont just do loops in fruity of course, you do whole songs as well.

How you do this is by using the playlist.

each track on the playlist represents a certain loop, and you arrange them together.
(just like Acid's track view, in a way.)

the problem is, you cant trim the blocks up or slice them, and they all have to follow the songs Pattern length (basically tim sig), which cannot be changed.

I hope there is away to sync these two up with tim sigs as well because I am looking foward to some freaky shiz wit deeez two programs

Subject:RE: To Sofo regarding Fruityloops by Imagline

Reply by: SonyNateM

Date:9/4/2002 1:07:04 PM

I just checked on this, and FruityLoops will just ignore the time signature change and "free wheel" after that. Tempo sync will still occur, but the measures are thrown off. FruityLoops remains in it's previous time signature.

If FruityLoops is limited to a single time signature per project, then I'm pretty positive there will be no way that ACID could affect this, or "extend" FruityLoops' capabilities.

I'm not sure if this will change when they release their new version. Time signature changes may not be part of the tempo sync/start position addition to VSTi that we are adding support for.

Subject:RE: To Sofo regarding Fruityloops by Imagline

Reply by: pwppch

Date:9/4/2002 1:47:49 PM

VSTi supports both time sig change info and tempo info, and ACID will transmit this information to any VSTi that asks for it. If FL follows this information, then it can track tempo and meter changes.

There is a limitation in how VSTi defines the changes though. There is no mechanism to indicate exactly when tempo and/or time sig change within the specific sample frame being processed.

gol has never mentioned anything about this to me in our previous emails, so I guess it must be sometime off.

Peter

Subject:RE: To Sofo regarding Fruityloops by Imagline

Reply by: pwppch

Date:9/4/2002 1:49:44 PM

ACID will report its current time sig to a VSTi. It is up to the VSTi to deal with this.

The limitation is that VSTi does not define a mechanism to tell the plug "when" the time sig change has occured relative to the current sample frame that the plugin is processing/rendering. This is suppose to be part of VST 3.0.

Peter

Subject:RE: To Sofo regarding Fruityloops by Imagline

Reply by: Jacose

Date:9/4/2002 3:11:35 PM

hmmmm... maybe something could be hooked up later on....