FL Studio 7
-
- KVRAF
- 6478 posts since 16 Dec, 2002
oh damn the funny stuff got deleted. I had a personalised crack made ready for that AgentNo1 fella!
Last edited by Kingston on Fri Jan 05, 2007 10:11 am, edited 1 time in total.
-
Reverse Engineer Reverse Engineer https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=9129
- KVRAF
- 4968 posts since 23 Sep, 2003 from Glasgow
Awwww....you didn't even get the chance to send him a 'system cleansing crack' for retroband. 
Edit: Seems you had the same idea.
Edit: Seems you had the same idea.
-
- KVRAF
- 6478 posts since 16 Dec, 2002
well I'm not that hostile, but I had a little gif present wrapped for him in a .zip that looked like the real thing.Reverse Engineer wrote:Awwww....you didn't even get the chance to send him a 'system cleansing crack' for retroband.
Edit: Seems you had the same idea.
-
- KVRer
- 3 posts since 5 Jan, 2007 from Boston
-
- KVRer
- 3 posts since 5 Jan, 2007 from Boston
-
- KVRAF
- 6478 posts since 16 Dec, 2002
and yet another suburban hero is out of his depth. somewhere, they only breed idiots.montro809 wrote:i got the crack too, if u wanna it let me know
-
- KVRian
- 1141 posts since 29 May, 2005
FL 7 RC5 is out, bugfix release.
i've spent more time with it now,
and i have to say it is alot more cpu hungry
than the previous 6x version.
all demo tracks / cool stuff tracks etc.
go up to 89% with crackles and some freeze
the only track that runs smooth is that
little rap track - even that one uses already close to 50%
would be nice to see a less hungry final version,
otherwhise i'm forced to use 6x until i get a new PC.
i've spent more time with it now,
and i have to say it is alot more cpu hungry
than the previous 6x version.
all demo tracks / cool stuff tracks etc.
go up to 89% with crackles and some freeze
the only track that runs smooth is that
little rap track - even that one uses already close to 50%
would be nice to see a less hungry final version,
otherwhise i'm forced to use 6x until i get a new PC.
-
- KVRer
- 3 posts since 6 Jan, 2007
The workflow of pattern clips is still really really basic. The same as automation clips and audio clips were in v6. Sadly they didn't touch that yet.
I usually steer clear off betas but pattern clips had me tickled, still far from really useable. What we need now is the flatten/merge functionality and some more editing tools to be added to the 'clips' portion of playlist. Too basic for smooth workflow as it is.
I usually steer clear off betas but pattern clips had me tickled, still far from really useable. What we need now is the flatten/merge functionality and some more editing tools to be added to the 'clips' portion of playlist. Too basic for smooth workflow as it is.
-
- KVRer
- 3 posts since 6 Jan, 2007
Few things the clips section needs IMO:
Clip grouping / ungrouping
Much like graphic programs. Select multiple clips, group them and then whichever clip in the group I grab for movement or shift-movement (copying) I move/copy the whole group. When I want to edit contents I can ungroup them, edit and then select and group them again.
Another usefull tool with grouping would be ability to 'squeeze' the group on one lane of the clips playlist stacking all the group elements on the topmost lane (usefull if the user is confident he will not edit the group in near time and wants to preserve screen estate as changing lanes has no effect on anything soundwyse).
Merge for pattern and audioclips
For pattern clips it should be simmiliar to the merge operation for patterns -- one selects multiple pattern clips and clicks merge -- the clips are all merged into one new clip and replaced by that new clip on the playlist respecting their slicing and positions. Additionally, step sequences are sent to piano roll (standard FLS behaviour).
For audioclips it's a matter of creating a new 32-bit wave file and mixing down the original audio clips respecting their slicing, relative volumes and time positions, the resulting wave routed to master.
And finally, the killer feature:
Bouncing clips
By bouncing I mean rendering all selected clips (and disregarding the ones not selected despite being in the same time on the arrangement), of any type, routing through all active effects and executing all selected pattern and automation clips, and then placing the newly rendered wave into proper place in the playlist. Removing original clips should be optional.
The new wave should be routed to master, since the recording point should be the input point of the master chanel. This also removes all isues that such bouncing would cause with sends.
These features would round up the new features form last few versions and finally make Fruity perfect.
Clip grouping / ungrouping
Much like graphic programs. Select multiple clips, group them and then whichever clip in the group I grab for movement or shift-movement (copying) I move/copy the whole group. When I want to edit contents I can ungroup them, edit and then select and group them again.
Another usefull tool with grouping would be ability to 'squeeze' the group on one lane of the clips playlist stacking all the group elements on the topmost lane (usefull if the user is confident he will not edit the group in near time and wants to preserve screen estate as changing lanes has no effect on anything soundwyse).
Merge for pattern and audioclips
For pattern clips it should be simmiliar to the merge operation for patterns -- one selects multiple pattern clips and clicks merge -- the clips are all merged into one new clip and replaced by that new clip on the playlist respecting their slicing and positions. Additionally, step sequences are sent to piano roll (standard FLS behaviour).
For audioclips it's a matter of creating a new 32-bit wave file and mixing down the original audio clips respecting their slicing, relative volumes and time positions, the resulting wave routed to master.
And finally, the killer feature:
Bouncing clips
By bouncing I mean rendering all selected clips (and disregarding the ones not selected despite being in the same time on the arrangement), of any type, routing through all active effects and executing all selected pattern and automation clips, and then placing the newly rendered wave into proper place in the playlist. Removing original clips should be optional.
The new wave should be routed to master, since the recording point should be the input point of the master chanel. This also removes all isues that such bouncing would cause with sends.
These features would round up the new features form last few versions and finally make Fruity perfect.
-
- KVRAF
- 3378 posts since 27 Feb, 2004 from Paris (france)
mind_deja_vu wrote:well i'm kinda looking for crack of fl studio 7. just wanna crack the new genrator pluging toxic n poizone please reply - mind_deja_vu@yahoo.com
i encourage eveybody to spam him with porn sites
Organising a protest march this Friday Schlesische Strasse 28 ,10997 Berlin, Germany
-
- KVRian
- 852 posts since 3 Aug, 2001 from Belgium
He's been banned.
-
- KVRAF
- 3378 posts since 27 Feb, 2004 from Paris (france)
well that's was quick 
Organising a protest march this Friday Schlesische Strasse 28 ,10997 Berlin, Germany
-
- KVRAF
- 2187 posts since 25 Jan, 2007 from the back room, away from his wife's sight (or so he thinks)
Huh? FL7 works just as fast as FL6 for me, if not a bit faster evenbambooman wrote:FL 7 RC5 is out, bugfix release.
i've spent more time with it now,
and i have to say it is alot more cpu hungry
than the previous 6x version.
all demo tracks / cool stuff tracks etc.
go up to 89% with crackles and some freeze
the only track that runs smooth is that
little rap track - even that one uses already close to 50%
would be nice to see a less hungry final version,
otherwhise i'm forced to use 6x until i get a new PC.
