Skip to content
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

Do you recommend to replace Surge with Surge XT? #5836

Closed
yurivict opened this issue Jan 29, 2022 · 8 comments
Closed

Do you recommend to replace Surge with Surge XT? #5836

yurivict opened this issue Jan 29, 2022 · 8 comments

Comments

@yurivict
Copy link

I maintain the FreeBSD port for Surge.

Now Surge XT is out. Should the Surge port be renamed into Surge XT, or they should exist in parallel?

@yurivict yurivict added the Bug Report Item submitted using the Bug Report template label Jan 29, 2022
@baconpaul
Copy link
Collaborator

We recommend they exist in parallel, and set up homebrew and our binary installers that way

@mkruselj
Copy link
Collaborator

They are installed in parallel and have different plugin IDs. Old Surge 1.9 branch won't be updated anymore.

@mkruselj mkruselj added Discussion and removed Bug Report Item submitted using the Bug Report template labels Jan 29, 2022
@mkruselj mkruselj changed the title [question] Do you recommend to replace Surge with Surge XT? Do you recommend to replace Surge with Surge XT? Jan 29, 2022
@yurivict
Copy link
Author

But if Surge XT is a complete replacement, why keep Surge 1,9 ?

@K0rrid0r
Copy link
Collaborator

K0rrid0r commented Jan 29, 2022

sometimes its nice to keep track of how changes were made, and old projects was maybe done with older version of surge

here is an example how all versions of surge can coexist
image

@baconpaul
Copy link
Collaborator

Yeah exactly surge is a renderer for projects in daws. Almost everyone (including me) keeps the old and new version around so they can render and edit older projects

@baconpaul
Copy link
Collaborator

(And surge 16-19 were drop in compatible in daws but xt is not for a variety of reasons, hence the separate I’d and so on)

@baconpaul
Copy link
Collaborator

Oh just fyi @yurivict we plan a 1.0.1 release in next 48 hours to fix some bugs found after release if that adjusts your packaging plans

@yurivict
Copy link
Author

[...] we plan a 1.0.1 release in next 48 hours to fix some bugs found after release if that adjusts your packaging plans

Thanks for the heads up. I'll package it then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants