Benefits to FL6 audio file handling?2006-06-02T11:17:32+00:00I seldom use loops are put a wave file directly into my hosts but when I do in Live, I just drop or draw it and work on it anyway I want. With FL6, it seems I have to work in 2 different windows to do the same thing. Is there a benefit to this that I'm missing? right now it seems like un-needed extra steps.
Thanks for any enlightenment.
Riley riley4reasonhttps://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8712
I seldom use loops are put a wave file directly into my hosts but when I do in Live, I just drop or draw it and work on it anyway I want. With FL6, it seems I have to work in 2 different windows to do the same thing. Is there a benefit to this that I'm missing? right now it seems like un-needed extra steps.
I think ( I am sure someone will correct me if this is not fully right) FL was not originally thought to take onboard audio - later as gol progressed and other developers components and code was integrated into FL - audio was considered - however the original design did not allow the audio to be integrated into the playlist - as it's a playlist for what was originally a step sequencer - if or not audio could be integrated within the step itself like the midi, I don't know, who knows what the future is with any app. At least where the audio is, there is also the automation curves etc. I don't know what the benefit is for the way its integrated, other than audio could now be added to an application where audio could only be added within a sample channel or slicer or tool.
The playlist is designed as a pattern sequencer, where there is a one-to-one correspondence between pattern and track. So, dropping in arbitrary audio clips to the pattern playlist does not really fit the current paradigm.
One can imagine that the playlist could be redesigned to support better mingling of the pattern tracks with the audio/automation tracks, for example have track1 be a pattern track, track2 be an audio track, track3 be another pattern track, etc., but who knows what plans Image-Line have in store.
Acid had a somewhat similar challenge to transition from a one-clip per track paradigm. Rather than introducing a new track type Sony decided to support multiple clips per track, which is an equally valid approach, but might not be suitable for the FL Studio pattern model.