-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty Template #2202
Comments
A - Yes, Good idea! I'll look into it. |
This one is so easy to solve: |
Silly -i read that different, i thought he meant creating a template from a project 8| -but ofcause he wrote 'default'. |
I understand what you mean and agree on that, but @mamins1376 is asking for 'a "Clean" or "Empty" template' - his own words -. |
it is useful a lot for working faster. but i have an idea: create a "platform" like VBA in Office apps, a script system to automate some processes, e.g. a special configuration for triple osc, or making some standard tricks like sidechaining or developing a 'Riff machine' using a small script. I know that wants lots of time and programming but can be a nice feature to create a special ability to making musics.Sent from K-9 Mail. |
This is similar to the concept of an FX preset (#1680), but a bit more specific. For now, a screen reader may be a better stop-gap. You may also find a quick way to perform these using XML manipulators against our project file format. Edit: @mamins1376 either way, this is probably suited for its own bug report, rather than in the template bug report. |
oh, sorry! I will open a new issue about that. On ۲۹ ژوئیهٔ ۲۰۱۵ ۲۳:۵۴:۲۴ (GMT+04:30), Tres Finocchiaro notifications@github.com wrote:
Sent from K-9 Mail. |
Ya, i know :p Thats where the first word Silly comes from 8] |
Hello. i think it is a little boring to remove and clean up the default track, automation, triple osc and baseline at start, it is better to have a "Clean" or "Empty" template like FL Studio. can it be included in the default templates that coming with project?
The text was updated successfully, but these errors were encountered: