Collaborative project!
-
@ustk @lalalandsynth do you think we are good for a free version already? or should we keep adding stuff? chorus. vibratos. IRs. etc?
-
@hisefilo I see, so I will re-implement mine, but a lighter version... It's too much work adding a ramp for transition, split, woofer and horn behaviour... So I'll just use the same than before, but lighten the filtering stuff
Can't help pressing F5 in the forum...
-
@ustk awesome!!! yes.
-
@hisefilo I think it's good for a collaborative project for the moment.
I wouldn't have (it's my opinion at least) a free/open plugin that infringes on people who try to make a living (on the same forum moreover) ;) -
@ustk ohhh. well. ok. I guess we are good to go then. you are right
-
So, should I finalize the GUI ?
What do I download specifically to work on , GIT noob. -
@lalalandsynth I think you can finalise around what we already have
You need to pull/fetch (or clone if you haven't already) the last commit. Tell if you're stuck somewhere so we can help you ;) -
@lalalandsynth :) yeeeeeah!!!
-
@lalalandsynth @hisefilo Ok guys, I just pushed the Leslie (no res, phase, freq cut...) just doppler effect and basic level changes
Tell me if it sounds ok enough- still have a proper bypass to implement
- Also when I remove or replace the frame for a fix_16 block, I get a crash... I'll check tomorrow again, but seeing the actually broken scriptnode, I can't promise to be gentle on CPU this time
-
@ustk WOW did you just made the engine start-stop????? U rock man
I thing the effect is doing the right thing, but like too much! Can doppler detunes be smoothed?
-
@hisefilo Thanks ;)
Yes, that's what I thought, like if the pitch is too much... But I have no reference and never used an organ, even less a Leslie
I'll smooth that out. I will use the B3 in Pro Tools as a reference, that should help me a lot... -
@ustk GarageBand Vintage B3 is in my opinion one of the best emulations ever made. And it's free and is already on your Mac. Just open GarageBand
-
@hisefilo or Logic
-
@hisefilo Ok, I know literally nothing about GIT , how can I make sure I am working on the latest version , also , how to deliver properly ?
I probably need to understand this git thing to be usable in this context :) -
@lalalandsynth Ok, let's start at the beginning...
I strongly recommend to use GitHub Desktop, it's less complete but enough, compared to command lines in the terminal. The less I put my hands on the terminal, the happier I am :)
Once you have it, you just have to clone the repository and that's all:
When you have modified the project, just push a new commit
name your commit properly and push each time you made a working mod
If you work on two different things, it is advised to push once for each. In short, never wait for 10 mods before pushing...
If, on our sides, we've made new commits, you'll need to fetch them so you always work on an updated version. -
@ustk ok, so what I am working on now is a clone of the project right?
What if you make changes to the original and I need to incorporate that commit into what I am working on , or do I consider the latest commit as a final version for me to work on ?And do I save as archive and then do a commit ?
-
Any comments or things I should be aware of before I make the GUI?
- Will it be standalone as well
- Keyboard ?
- Resizable ?
- Size of interface ?
-
I just pushed a new commit with a refined Leslie (doppler and stereo)
Tell me guys if it sounds betterCan't help pressing F5 in the forum...
-
@ustk So if you push a new commit , how can I make sure I am working on that ?
And what happens if I am already working on the gui and up pops a new commit ? -
So if you push a new commit , how can I make sure I am working on that ?
Git pull to get the latest version before you start work.
what happens if I am already working on the gui and up pops a new commit ?
Before you start work make a new branch. Once you've finished your work you can merge it into the working branch and fix any conflicts.
