The FLStudio 6.1 beta looks to have great features!!!

[experimental.crow]

so ...
nobody appears to be using the 'project bones' function , to save
automation, channels, effects, mixer and scores ?...

or perhaps you just haven't mentioned it ...

i find it quite handy ...

I use project bones all the time. Instead of a one click freeze I think this is even better because it is more flexible.Export project bones, render the high cpu track (disc arm,ctrl+r),delete the channel.Now if I need to make a change just open the browser and drag over what you need from project bones make my changes ,rinse,repeat.

The entire project bones part of the software is REALLY dated and needs to be entirely re-worked. Even worse, it can be REALLY difficult to even figure what part is what when going through there.
Another thing that bothers me is the archiving of projects within FLS. It doesn't archive everything (think audio). This is another part of the program that needs to be reworked AFAIC.

Overall though, this program keeps getting better and better though.

--Sean

i agree w/ this , up to a point ...

if you set out knowing you are going to use this function , it is imperative that you take the time to 'name' your channels with enough information to provide the clues you may need for identification ...

clunky , perhaps ...
but it does work ...

[experimental.crow]

yeah but theres not just a "channel all" bone --- like one thing you drop into the channel window that recreates the vsti, preset, mixer channel, and scores at once....

that would be a very nice addition ...
it would certainly simplify the process ...

all in all though , it does work ...

[Jason Brian Merrill]

i think there are enough challenges and things to be concerned with instead of trying to figure out workarounds for software --

I used to do work on a radioshack karaoke machine...

http://jasonbrianmerrill.googlepages.com/music

And i dont find that not having those challenges has made me worse as a musician. I am still a one-take guy -- sometimes to my detriment -- that is the one thing i think some people forget and dont retain when going to a software DAW that has it all...

[audiojunkie]

grymm, when you unclick the green light for a channel, i belive MOST vstis do not use cpu.

however, RAM hungry vstis will certainly still take up the RAM they originally had if they are not uloaded completely.

According to Gol, "Muting" the generator (unclikking the green light for a channel) uses almost no CPU. However, there still IS a little usage from the generator, even when muted. The same goes for muting effects.

Also,

I know this is just a stupid workaround, but I believe that RAM can be saved by writing my soundfonts, that I use in SFZ, down in the fruity notepad, and then removing them from SFZ's memory and then muting the SFZ plug works for removing the RAM. If the soundfont (or whatever RAM intensive thing is needed again, simply refer to the notepad, and reload it.) Then again, as I said, it's just a stupid workaround.

By the way, the ability to use mono audio channels will definately save resources. The 6.1 manual is a little hazy as to whether this is implemented or not. Some parts of the manual seem to say that mono loading and saving is implemented (as it mentions in the parts about the sampler), and other parts seem to indicate that there has been no change. Does anyone know what's what with this situation?

--Sean

you are assuming that the people who want freeze would want to use this 'notepad' method. it's a neat tip, and i use trackpad myself in tracktion but never used fl notepad much for whatever reason. i'm more of an external text editor kind of guy i guess ultraedit or notepad for notes and junk.

Nah, I wasn't assuming anything. I was just thinking of a way to save RAM with the system as it currently is. I don't like the method that I just mentioned either.

--Sean

[audiojunkie]

so ...
nobody appears to be using the 'project bones' function , to save
automation, channels, effects, mixer and scores ?...

or perhaps you just haven't mentioned it ...

i find it quite handy ...

I use project bones all the time. Instead of a one click freeze I think this is even better because it is more flexible.Export project bones, render the high cpu track (disc arm,ctrl+r),delete the channel.Now if I need to make a change just open the browser and drag over what you need from project bones make my changes ,rinse,repeat.

The entire project bones part of the software is REALLY dated and needs to be entirely re-worked. Even worse, it can be REALLY difficult to even figure what part is what when going through there.

Another thing that bothers me is the archiving of projects within FLS. It doesn't archive everything (think audio). This is another part of the program that needs to be reworked AFAIC.

Overall though, this program keeps getting better and better though.

--Sean

for archiving audio, save as a zip. it includes the external dependencies too.

Hmmm.... I could have sworn that some things were left out. Does it include the samples used in the sampler as well? Does it list the names and patches of any missing VSTs? I can't remember, but I seem to remember discussions on looptalk where there were things not included in the zipped flp, and that the best method was to create a folder and put all of the recordings and samples and the flp and such into it, and then zip that. Does anyone remember any of those conversations? The conversations took place during the FLS 5.x era. Nothing has changed in the FLP zipping since then.....

--Sean

--Sean

[audiojunkie]

so ...
nobody appears to be using the 'project bones' function , to save
automation, channels, effects, mixer and scores ?...

or perhaps you just haven't mentioned it ...

i find it quite handy ...

I use project bones all the time. Instead of a one click freeze I think this is even better because it is more flexible.Export project bones, render the high cpu track (disc arm,ctrl+r),delete the channel.Now if I need to make a change just open the browser and drag over what you need from project bones make my changes ,rinse,repeat.

The entire project bones part of the software is REALLY dated and needs to be entirely re-worked. Even worse, it can be REALLY difficult to even figure what part is what when going through there.
Another thing that bothers me is the archiving of projects within FLS. It doesn't archive everything (think audio). This is another part of the program that needs to be reworked AFAIC.

Overall though, this program keeps getting better and better though.

--Sean

i agree w/ this , up to a point ...

if you set out knowing you are going to use this function , it is imperative that you take the time to 'name' your channels with enough information to provide the clues you may need for identification ...

clunky , perhaps ...
but it does work ...

Hmmm.... Good point (naming of channels). I'm going to have to keep this in mind and try it again to see if this helps me out. However, unless I'm mistaken, project bones doesn't even save piano-roll data (it was either this or step sequencer data -I can't remember for sure). Surely that would be considered an essential "bone" for the project bones area. Also, I agree with the earlier post that a "save entire channel" bone would be a great addition.

Overall though, I still think it is hard to find exactly what you are looking for, without a lot of searching, and that needs to be made easier for the user in order to get me (and probably others) to use it more. So I still think that Project bones needs a rework job.

--Sean

[grymmjack]

so ...
nobody appears to be using the 'project bones' function , to save
automation, channels, effects, mixer and scores ?...

or perhaps you just haven't mentioned it ...

i find it quite handy ...

I use project bones all the time. Instead of a one click freeze I think this is even better because it is more flexible.Export project bones, render the high cpu track (disc arm,ctrl+r),delete the channel.Now if I need to make a change just open the browser and drag over what you need from project bones make my changes ,rinse,repeat.

The entire project bones part of the software is REALLY dated and needs to be entirely re-worked. Even worse, it can be REALLY difficult to even figure what part is what when going through there.

Another thing that bothers me is the archiving of projects within FLS. It doesn't archive everything (think audio). This is another part of the program that needs to be reworked AFAIC.

Overall though, this program keeps getting better and better though.

--Sean

for archiving audio, save as a zip. it includes the external dependencies too.

Hmmm.... I could have sworn that some things were left out. Does it include the samples used in the sampler as well? Does it list the names and patches of any missing VSTs? I can't remember, but I seem to remember discussions on looptalk where there were things not included in the zipped flp, and that the best method was to create a folder and put all of the recordings and samples and the flp and such into it, and then zip that. Does anyone remember any of those conversations? The conversations took place during the FLS 5.x era. Nothing has changed in the FLP zipping since then.....

--Sean

--Sean

It should include the samples from the sampler. It always has everytime I've done it. The names of the patches of missing VSTs? Not sure what you mean -- if you move a plugin or dont have the same one installed the channel name will be the name of the plugin unless you change it yourself by default when you insert it, for the name of the preset, it would have to have a copy of the plugin atleast that's most logical ... so no, it probably wouldn't but I wouldn't expect it to either, considering that presets are parts of plugins and not a separate thing. It's not unreasonable for FL to be unable to recall this information if the plugin is missing? I dunno.

Everytime I've saved as zip it's worked ok. But my projects aren't very complex. So perhaps there is something I don't know (wouldn't be the first time) regarding save as zip. Does it save the audio tracks or reference them? I would hope it would just reference them instead of saving them into the archive itself. For the obvious reason of diskspace..

Project organization can be a tricky thing, it's best to have a plan going in and do some organization on your own I find.

[hitman8081]

hitman tell us what version you are using ok?

i use the producer edition. i thought the xxl edition only has a bunch of bloated outdated synths. i didnt know you can emulate freeze in the xxl edition and i didnt know you can emulate a freezeing a synth and fx together. i recently started trying to learn fl studio inside and out. so theres things alot of things that i didnt know before that i do now. like changing the colour of grids, adding icons, shortcuts ect. so take my comments or complaints with a grain of salt as i admit i cant back up my mouth right now as far as advanced fl studio use goes

[justified]

On saving zips: unfortunately files that are loaded by vsti's are not zipped (eg sfz's sf2) but probably there's no way to do this?

[experimental.crow]

so ...
nobody appears to be using the 'project bones' function , to save
automation, channels, effects, mixer and scores ?...

or perhaps you just haven't mentioned it ...

i find it quite handy ...

I use project bones all the time. Instead of a one click freeze I think this is even better because it is more flexible.Export project bones, render the high cpu track (disc arm,ctrl+r),delete the channel.Now if I need to make a change just open the browser and drag over what you need from project bones make my changes ,rinse,repeat.

The entire project bones part of the software is REALLY dated and needs to be entirely re-worked. Even worse, it can be REALLY difficult to even figure what part is what when going through there.
Another thing that bothers me is the archiving of projects within FLS. It doesn't archive everything (think audio). This is another part of the program that needs to be reworked AFAIC.

Overall though, this program keeps getting better and better though.

--Sean

i agree w/ this , up to a point ...

if you set out knowing you are going to use this function , it is imperative that you take the time to 'name' your channels with enough information to provide the clues you may need for identification ...

clunky , perhaps ...
but it does work ...

Hmmm.... Good point (naming of channels). I'm going to have to keep this in mind and try it again to see if this helps me out. However, unless I'm mistaken, project bones doesn't even save piano-roll data (it was either this or step sequencer data -I can't remember for sure). Surely that would be considered an essential "bone" for the project bones area. Also, I agree with the earlier post that a "save entire channel" bone would be a great addition.

Overall though, I still think it is hard to find exactly what you are looking for, without a lot of searching, and that needs to be made easier for the user in order to get me (and probably others) to use it more. So I still think that Project bones needs a rework job.

--Sean

it does save piano roll data ...
under ' scores ' ...

create some midi , in a piano roll channel ...
export it as a project bones ...
open a new project ...
insert a piano roll channel , in the new project ...
open the project bones > scores ...
drag & drop the score on the new piano roll channel ...

voila ...

i can't comment on the step sequencer , as i never use it ...

[audiojunkie]

so ...
nobody appears to be using the 'project bones' function , to save
automation, channels, effects, mixer and scores ?...

or perhaps you just haven't mentioned it ...

i find it quite handy ...

I use project bones all the time. Instead of a one click freeze I think this is even better because it is more flexible.Export project bones, render the high cpu track (disc arm,ctrl+r),delete the channel.Now if I need to make a change just open the browser and drag over what you need from project bones make my changes ,rinse,repeat.

The entire project bones part of the software is REALLY dated and needs to be entirely re-worked. Even worse, it can be REALLY difficult to even figure what part is what when going through there.

Another thing that bothers me is the archiving of projects within FLS. It doesn't archive everything (think audio). This is another part of the program that needs to be reworked AFAIC.

Overall though, this program keeps getting better and better though.

--Sean

for archiving audio, save as a zip. it includes the external dependencies too.

Hmmm.... I could have sworn that some things were left out. Does it include the samples used in the sampler as well? Does it list the names and patches of any missing VSTs? I can't remember, but I seem to remember discussions on looptalk where there were things not included in the zipped flp, and that the best method was to create a folder and put all of the recordings and samples and the flp and such into it, and then zip that. Does anyone remember any of those conversations? The conversations took place during the FLS 5.x era. Nothing has changed in the FLP zipping since then.....

--Sean

--Sean

Does it save the audio tracks or reference them? I would hope it would just reference them instead of saving them into the archive itself. For the obvious reason of diskspace..

I can't say I agree here. What's the point of archiving your stuff, if the audio tracks (part of the song) aren't archived with it? No, I don't agree at all on this one.

--Sean

[hitman8081]

heres one for you guys. im working on a project right now cant say what its about or called but the person is part owner of a popular remix site. he wants me to do some remix work for him and in
return hell do vocals for me. heres the kicker though. he says i need cubase because ill be more happier with the end results but tbh i hate cubases workflow and prefer fl studios way of doing multiouts, the pianoroll, mixer ect. this is all to common for people to say you need cubase to make good music. while the inbuilt effects are decent as is the features, fl studios just has it right as far as workflow goes. im often a critic of fl studio due to its lack of more expensive daw
features but i would never say fl studio sucks or is unprofessional but its slowly growing into a great daw and imo how fast fl studio grows is going to determine whether better competiton makes or breaks fl studio.

[audiojunkie]

If everything isn't archived, then it's not a complete archive. Think of Cakewalk's Sonar archive function. You can zip your entire archive, and then burn it to disk when you are done. In 6 months, if you decide you want to go back and remaster things, you just unzip the archive. However, right now, you can't do that.

--Sean

[audiojunkie]

hitman tell us what version you are using ok?

i use the producer edition. i thought the xxl edition only has a bunch of bloated outdated synths. i didnt know you can emulate freeze in the xxl edition and i didnt know you can emulate a freezeing a synth and fx together. i recently started trying to learn fl studio inside and out. so theres things alot of things that i didnt know before that i do now. like changing the colour of grids, adding icons, shortcuts ect. so take my comments or complaints with a grain of salt as i admit i cant back up my mouth right now as far as advanced fl studio use goes

The producer edition is the 'exact' version of the software that the xxl 'bundle' contains. The xxl 'version' is just a price-reduced marketing 'bundle' that includes the extra synths that are available at the time of the xxl bundle purchase.

You have the exact capabilities in your FLStudio that everyone with the FLStudio xxl bundle has.

--Sean

[diverdee]

Yep - same thing in live - save as 'self contained', what I always do.