Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
GIT - Help ! please :)
I’m just getting into GIT for source control, have come from a long time of SourceSafe, VisualSourceSafe, TFS...I have recently switched to GIT, and I have some dumb questions 🙂
The reason for the switch is a move from in-house servers running a Winforms application, to Azure VM’s, after that converting to containers, they are being managed in dev ops.
In GIT what does what ? 1 repository per project ? How in DevOps do you span Kanban’s across multiple GIT projects ?
Comments
I’m so excited for you! My god, VSS still haunts me and I haven’t used it in 10+ years.
Ask more specific questions as they come. Or just search stack overflow like the rest of us.
One thing that might be hard to grok coming from other VCS is that there is no “main” repository with git. Every person/machine who clones a repo has the full repo. Services like github or bitbucket can act like the “central” repository but it’s important to understand that this is entirely down to convention/team acceptance.
Associating something like a kanban board with one or more repositories is going to come down to your kanban software. Jira can do this, for instance, but it leans toward one repo per board/project as do most others that I’m aware of.
Thanks for the info, Kanban is provided by DevOps, and it looks like that is on a project only basis, no project spanning
And also within DevOps I can only seem to add a single repository to a DevOps project, I’m using GIT for the repository.
With GIT I now need to get my head around branching/merging and handling conflicts.
Are you talking about the product Azure DevOps ?
Branches in git are different from VSS or older SVN versions in that branches in git don’t make a new copy of the entire repo. They’re really just snapshots of whatever the current state of the repo is. In SVN and VSS, we very very rarely made branches because they were a giant pain. In git, you’re making new branches pretty much constantly.
https://www.atlassian.com/git/tutorials are all really well written. Probably best to start from the top but https://www.atlassian.com/git/tutorials/using-branches might help.
https://www.atlassian.com/git/tutorials/comparing-workflows Is also a really worthwhile read with regard to branching and merging. Git is soooo flexible that team conventions are key. There are lots of ways to collaborate and lots of reasons to make branches. Understanding the different workflows will help you and your team understand those reasons.
Yes 🙂
@syrupcore Awesome, thanks 🙂