Giter Site home page Giter Site logo

surge-synthesizer / surge-synthesizer.github.io Goto Github PK

View Code? Open in Web Editor NEW
122.0 122.0 37.0 388.24 MB

Surge synthesizer website @ https://surge-synthesizer.github.io

Home Page: https://surge-synthesizer.github.io

License: GNU General Public License v3.0

CSS 0.41% JavaScript 0.08% TypeScript 0.43% Astro 7.53% MDX 81.74% HTML 9.80%

surge-synthesizer.github.io's Introduction

Built with Astro & Tailwind CSS

  1. Install node.js
    • (Optional) Install pnpm
  2. npm install/pnpm install to install dependencies
  3. npm run dev/pnpm dev to run the development server

Adding and editing pages

To make changes, all you need to is fork the project. Once you have done that you can create a branch on your fork make changes and then open a PR. This git document for the OSS Surge-Synthesizer project outlines a suggested way of doing work and then creating PRs.

Once you have created a branch in your fork you can then just click the edit button (upper right corner) to edit a post in the src/content/pages folder. Because the posts are markdown documents you can just edit stuff in place in the GitHub editor.

To add a page, open the src/content/pages folder in your fork and click the create new file button.

A post has a frontmatter section and a body section. The frontmatter section is metadata about the post, such as which image to use and what categories it belongs to. A new post would have frontmatter that looks something like:

---
slug: surge-xt
title: Surge XT
summary: Surge XT is an open source hybrid synthesizer, and the synth which started the Surge Synth Team project!
order: 1
thumbnail: /screenshots/surge-xt.png
categories: [Synth]
url: https://surge-synthesizer.github.io
issue_tracker: https://github.com/surge-synthesizer/surge/issues
---

The title is the display name for the post, the summary is the text in the card on the main page, the thumbnail is an image for the project, and the categories are a comma-separated list of any appropriate categories (look at the other projects for categories that already exist). The order determines which position a post appears in on the main page.

The body section of a post is where you can write a description of the project in markdown. It is everything after the frontmatter section.

Editor setup

Official guides

VS Code Setup

Set Prettier as your default formatter

{
    "editor.defaultFormatter": "esbenp.prettier-vscode",
    "[astro]": {
        "editor.defaultFormatter": "esbenp.prettier-vscode"
    },
    "[yaml]": {
        "editor.defaultFormatter": "esbenp.prettier-vscode"
    },
    "prettier.documentSelectors": ["**/*.astro"]
}

Format on paste, save & type

{
    "editor.formatOnPaste": true,
    "editor.formatOnSave": true,
    "editor.formatOnType": true
}

Associate CSS files with tailwind

{
    "files.associations": {
        "*.css": "tailwindcss"
    }
}

surge-synthesizer.github.io's People

Contributors

andreya-autumn avatar artyfunk avatar aryoungblood avatar baconpaul avatar bgins avatar bradlylanducci avatar brendanxboyd avatar cyanit avatar dependabot[bot] avatar erroreyes avatar esaruoho avatar gitsmol avatar haenkel avatar itsmedavep avatar j5v avatar jangler avatar jatinchowdhury18 avatar kzantow avatar menketechnologies avatar mkruselj avatar mortfell avatar mthierman avatar mx avatar pgrimaud avatar pitermach avatar sirlich avatar surge-build-bot avatar theredwaxpolice avatar vincyzed avatar zakcodes avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

surge-synthesizer.github.io's Issues

Update website images after skin changes are finished

There have been many changes happening with the Surge skin. Once that process is all finished up, we should go back through the images on the site and update them to be reflective of the finished skin.

Basically, we need to retake the screen shots and update the site with the new look. Putting this here so that I don't forget.

Binary Linux VST Release

I would love to test/use this and contribute with bug reports, but I am not running a Debian-based distribution. Would it be possible to release a version of the binary Linux VST, so that it can be run without requiring .deb installation?

Links page

We could maintain a pretty quick and dirty linkpage for Surge-related things (like Surge KVR forums, Surge preset pack links and the mystery islands link for a commercial Surge preset pack by Gokosoul).

and maybe some videos embeds?

Wavetables

Hi,
I don't know if this is the right place to post this, but closes I could thing of..

I followed the guide Creating-Wavetables-For-Surge to create a wavetable from a sample of a saw I have.

My starting point is pretty much a perfect one-cycle saw waveform. When playing it in loop in Audacity, it sound nice deep and crisp.

> soxi test.wav          

Input File     : 'test.wav'
Channels       : 1
Sample Rate    : 44100
Precision      : 16-bit
Duration       : 00:00:00.05 = 2048 samples = 3.48299 CDDA sectors
File Size      : 4.14k
Bit Rate       : 713k
Sample Encoding: 16-bit Signed Integer PCM

image

The problem is that when importing this in Surge it sounds "dull", not so crisp, almost like there is a lowpass filter stripping away the high frequencies.

Is this a something that rings a bell? I seem to have done everything by the book, but cannot get the same sound..
(yes, I'm sure there are no filters on in Surge. Used the Init Saw patch as a starting point and just switched the waveform)

Converting it

> mkdir test
> cp test.wav test/
> wt-tool.py -d test -f test.wt -a create -n half   
Creating 'test.wt' with 1 tables of length 2048
Normalizing by half

..I also tried without -n half and also tried with a wavetable for length 1024 samples, same result.

Thanks for any hints on what the heck is going on here :)

I attached test.wav and test.wt in a zip file

test-wavetable-files.zip

UPDATE

I tried to make the one-cycle waveform from another offset, also touching the "zero line". That actually helped quite a lot! Still not 100% as bright, but that could be fixed with eq I guess.

  • Green: Works
  • Red: Cuts the high tones

image

Installation issue... forgot "browse" button

Just installed this software, 'cause I'm curious.
I have tons of stuff in my Program Files folder, from Auddict, to XLN Audio... that's just VST lol
So where exactly does this thing install itself???

make licenses into a separate page, and link to it from the manual

like an addendum..some paste from discussions:

baconpaul [2:07 PM]
The licenses ask us to put them “in the documentation”
at least the vstgui license does
We have lots of leeway but we should meet the spirit and letter of that ask I think.
They could be on a separate page and the licenses section could have links for instance
So like keep this bit but then have links to the text of the license.
Screen Shot 2019-02-15 at 7.08.23 AM.png 


esaruoho [2:09 PM]
k
maybe i need to tweak the manual so it feels like 90% manual and 10% licenses.. instead of 20% manual 80% licenses :wink:

baconpaul [2:10 PM]
Well if you move the text of the licenses to a separate file then that section is literally 3 lines with links
that’s perfectly fine with me

esaruoho [2:11 PM]
yeah like a linked addendum

baconpaul [2:11 PM]
(And then change “below Steinberg license” to “<a href…>the SteinbergMedia VSTGUI License</a>” and “GPL3” to “<a >The Gnu General Public License version 3 (GPL3)</a>”
But in the main manual I really want the three lines I screenshotted to appear
Link to text of license fine
Name of licences with link in the manual required please

screen shot 2019-02-15 at 7 08 23 am

Website typos/corrections

Italics - current state. Normal text - suggested fix.

If you have used it in the past it will be like welcoming an old friend back into your life. If you are new to Surge, welcome to the party. Come on in the water is fine.
If you have used it in the past, it will be like welcoming an old friend back into your life. If you are new to Surge, welcome to the party. Come on in, the water is fine.

Quick category-based patch-browser
I'd remove the dash in patch-browser there.

Future proof, comes as both a 32 & 64-bit VST plugin (Windows PC coming soon)
Doesn't this usually have a dash there, future-proof? Also, "a" article is not necessary there. Maybe also remove "Windows PC coming soon" because it's already there, isn't it?

3 oscillators/voice
May be nicer to write "3 oscillators per voice" instead

and Audio-input
No dash

/dualsaw
/dual saw

The FM2/FM3 oscillators consists of a 1 carrier with 2/3 modulators and various options.
The FM2/FM3 oscillators consists of a carrier and 2 or 3 modulators and various options.

Oscillator FM/ringmodulation
Space between "ring" and "modulation"

Most oscillator algorithms (except FM2/FM3) are strictly band-limited yet still cover...
Most oscillator algorithms (except FM2/FM3) are strictly band-limited, yet still cover...

Filterblock
I'd add a space there, but then the manual will also need updating. Which it should anyways, eventually. :)

Two filter-units with arrangeable in 8 different configurations
Two filter units in 8 different configurations

Available filter-algorithms: LP12 (3), LP24 (3), LP24L (1-4 poles), HP12 (3), HP24 (3), BP (4), Notch (2), Comb (4), S&H
Available filter algorithms: LP12 (3 variations), LP24 (3 variations), LP Ladder (1-4 poles), HP12 (3 variations), HP24 (3 variations), BP (4 variations), Notch (2 variations), Comb (4 variations), S&H

12 LFO-units available to each voice (6 are running on each voice and 6 are shared for the scene)
12 LFO units available, 6 are per voice and 6 are global for the whole scene

7 deformable LFO-waveforms + 1 drawable/step-sequencer waveform
7 deformable LFO waveforms + drawable/step sequencer waveform

LFO1 allows envelope retriggering when used as stepsequencer
LFO 1 allows envelope retriggering when used as step sequencer

2 inserts/scene
2 inserts per scene

(EQ, stereo-image control & limiter)
(EQ, stereo image control and limiter)

System requirements:
Instead of using "an" and "a" articles all the time, I would suggest using bullet points instead.

Manual improvements

TOC button should be moved to header and margins should be fixed when TOC is collapsed

Spacing is not even example:

Screenshot 2022-08-05 213941

Reorder entries in Menu

To me, it makes a lot more sense to have "About" last in the menu, and "Zoom" probably first. So, I suggest just inverting the order of entries in the Menu. Perhaps add a separator. Like this:

Zoom       >
------------
Surge Manual
About Surge

Surge doesn't remember delay FX tempo sync

Hi,

I've tried Surge today and I've created a patch that uses a delay FX with tempo sync. Every time I reload the patch, tempo sync is disabled and I have to enable it manually. Also happens after loading in my DAW (Reaper) any project with any Surge instance that had tempo sync enabled.

Steps to reproduce the bug:

  • Add delay FX to any patch (choose any delay preset, seems that all of them use tempo sync)
  • In the delay FX options, right click the slider labeled as "right" and check that "Temposync" is enabled in the context menu.
  • Repeat the same for the slider labeled as "left".
  • Save the patch using the store button.
  • Reload the patch using the patch browser | Or save/reload the project using the DAW.
  • "Temposync" is disabled for both left and right channels (and the delay doesn't sound synced anymore)

System where the bug was experienced:
OS: Windows 10 x64
Surge version: 1.6.4.1 (VST x64)
DAW: Reaper 5.984 x64

Feel free to ask me any additional information.
Keep up the good work, It's a great synth with an amazing sound and tons of versatility.

Thank you in advance.

wrong github link in the footer

<a class="github-button" href="https://github.com/{{ site.github_username }}/{{ site.github_repo }}" data-icon="octicon-star" data-count-href="{{ site.github_username }}/{{ github_repo }}/stargazers" data-count-api="/repos/{{ site.github_username }}/{{ github_repo }}#stargazers_count" data-count-aria-label="# stargazers on GitHub" aria-label="Star {{ site.github_username }}/{{ github_repo }} on GitHub">Star</a>

The "Star" button in the footer is giving me a https://github.com// link (yes, with two slashes).

VST2 64 bit .dll not recognised by FL Studio

The VST2 64 bit version of Surge is not being detected by FL Studio 20.1.1 in Windows 10 when scanning for new plugins. Yes, I have configured the search to look in the correct folder. The VST3 version is detected.

Add TOC for Manual

At least for now, lets add some links to the various sections. That way at the top we can add in a way for people to jump to a section that interests them.

Right now if you are looking for something you can try ctrl-f but thats it.

So something like:

Topic.......pg.24

Add in section for dev's and link to main project to website

From the Slack convo on this topic in the #design channel:

From @baconpaul
screen shot 2019-01-29 at 8 22 53 am <-- Image can be used for this. Thanks for the screen!

Secondly I think the main page should hve something for developers. Like another section with a screenshot of developer workflow with some copy like “Developers Welcome” and then “Surge is supported by a community of volunteer open source developers. If you are interested in contributing, we welcome developers who know or want to learn C++, git, and graphic and web design. There’s plenty of open issues and our slack channel can help you find a good first one if you want. Hope over to the , and for more!”

Or some such?

Oh I woudl definitely add something to that copy about “help with testing, replicating bugs, and working with multiple hosts is also welcome. There’s more than enough work!”
And maybe finally something like “a positive upbeat community of volunteer…”
but I’m not a copywriter. I just realized the web page was a good opportunity to share that message!

esaruoho [7:30 AM]
this would definitely be crucial
and if someone is still using 1.52, they can be of enormous help telling us where surgeOpenSource version is at
zvenx for instance has been of enormous help, telling us where things are at with 1.52

baconpaul [7:31 AM]
I’m wondering if we also want to make an open call for peopel to send us tracks which use only surge or almost only surge which are released under (say) cc-4.0-nc-sa or similar (cc-4.0-nc-sa is roughly gpl3-ish but we don’t have to be that uptight)

Add Info on WaveTable Oscillator to manual

“Its a feature not a bug”

What that oscillator is doing is essentially simulating a variable-rate D/A converter running at the rate of the original wavetable. The convolute method is generating a band-limited impulse with a sub-sample time localization precision, which is then integrated to provide the stepped function.

This means that it basically doesn't produce any inharmonic aliasing (which make stuff sound messy). But it does produce harmonic aliasing, ie the waveform spectrum will continue indefinitely as opposed to other interpolation methods. It similar to very early pre-interpolation samplers that had a dedicated D/A converter per-voice (and analog filters) instead. But yeah, its not the right choice if you want a triangle wave without any additional overtones.

Feature Request

Possibility of adding a "Show Presets Folder" option in the right click menu of the presets? Make it easier to Add and Share presets for people.

LV2: Patch changes randomly when reooening the GUI or reloading the session

Today I've tried the LV2 build in Linux and I've had my patch change randomly during work.

The oscillators seemed to be reverted back to Sawtooth when I closed and opened again the UI.

I ended up replacing Surge with something else, to finish the project.

Anybody had similar issues? I'm running Manjaro, used Surge LV2 in Ardour 5.12.
I've installed Surge LV2 from AUR.

about.md tweaks

Like it would be great if instead of saying claes 
is too busy, say he contributed it to the
 community and a community flourished
or some such

so a rewrite

dropdown for manual(s)

since i don't know how to jeckyll (have not looked into it yet)
i drop idea here for now:

  • make drop-down menu for manual(s) in page header
  • call it "Manual" and the sub categories English, Deutsch, Français etc. (sorted alphabetical(?))
  • (no national flags ... please)

so it takes same space in header menu for the hundreds of translations that may soon come in...

Manual Translators Please Subscribe to this Issue

Hi!

First, thanks for kindly translating the manual. If you are a manual translator please subscribe to this GitHub issue and we will use it (plus the #documentation channel in discord) to notify folks if there are big changes or so on.

Best practices for a manual translation are

  1. Please call it Surge-XX.md where XX is the standard 2 letter code for your language (DE, FR, JP, etc...)
  2. Please make the permalink manual-XX
  3. If possible, put near the top of your manual that "this manual was translated as of ..." - but we are still working on that
  4. Please ask on this issue and we will link to the translated manual from the top of the english manual

In SurgeXT we may be able to internationalize more fully - things like link to a german manual from the menu if your computer has a german language region. If so we may occasionally hit up this issue for some testing or changes there too.

And finally, thanks for working to translate the manual!

Pre-tagging @mkruselj @VincyZed @mynameismuhl

Releases/Downloads -page

As discussed on #design ,

D/L Page, contains links to nightly builds (preferably with dates!)
The current "release" build

a changes log

and .. maybe .. known issues list

objective of the page is to encourage people to contribute.

Clean up styles and Jekyll"ify" page content

As well as the page works now, the home.html page is getting to be a bit complex. I would like to break the HTML down a bit and make it easier to work with.

Jekyll works by injecting HTML fragments into a page. By way of providing an example:

home.html should only include references to these fragments of a page like so:

<div class="container mx-auto px-2 py-4">
        {% for post in site.posts %}
          {% include post_block.html %}
        {% endfor %}
      </div>

I didnt do that when I made the site. It gets much easier to manage content and you end up dealing with smaller html documents that are easier to understand if you follow the pattern.

Work to be done

In our context:
Take home.html
Take each section and move them into their own fragment and add to _includes
Update home.html to reference all fragments

Additionally, clean up of the CSS is needed in all kinds of spots. Ive been a bit sloppy with things. I would like to take the time to fix this stuff up before it gets further out of hand.

The effort will make my life easier. It will make future dev's life easier if they were to work on it.

Add a section to the manual on "upgrading to surge 1.6"

EvilDragon [10:15 AM]
I was doing a thought experiment from the perspective of an old Surge user (edited) 

baconpaul [10:15 AM]
Right a 1.5.2 32 bit user

EvilDragon [10:15 AM]
yep

baconpaul [10:15 AM]
Yeah

EvilDragon [10:16 AM]
so that user, when installing the current builds, would have his 32-bit overwritten with 64-bit
because of the same filename

EvilDragon [10:16 AM]
and if that user used a 32-bit DAW, that'd essentially screw his projects up

baconpaul [10:16 AM]
yeah she may be upset in that situation. I certainly hope people with production critical surge dependencies keep backups of 1.5.2 if they download nightlies tho.

EvilDragon [10:17 AM]
right
it was just a thought. nothing NEEDS to be done regarding it if you deem it unnecessary

baconpaul [10:18 AM]
I think when we approach a stable 1.6 we want to think at least about documenting it clearly
It is trivial to rename Surge.dll as Surge64.dll

EvilDragon [10:18 AM]
yes, good idea

Surge crashes Renoise - Debian 10

Hi,

I compiled surge in Debian 10 and use it together with Renoise. It frequently crashes with this window:

https://i.imgur.com/Z835J1v.png

Last lines I see in the terminal are below. I just copied the .so file into my home user folder and the presets in /Documents/Surge.

BTW: Is it possible to deactivate the warning that no presets are found in /usr/ ... ?

Cheers
Marco

renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. ^CRenoise LOG> Application: Caught signal:2 - Terminating... Renoise LOG> Application: Saving a backup... renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
Renoise LOG> VstWindow: Closing the Editor...
Renoise LOG> VstWindow: Editor was closed
Renoise LOG> Application: Exit...
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed.
renoise: src/common/thread/CriticalSection.h:33: void Surge::CriticalSection::enter(): Assertion !(refcount > 10)' failed. Renoise LOG> Shut down: Stopped the Player Renoise LOG> MIDI: Shut down: Closing all acquired MIDI devices... Renoise LOG> MIDI: Shutting down MIDI server... Renoise LOG> MIDI-IO: Closing MIDI in device 'MPK Mini Mk II MIDI 1'... Renoise LOG> MIDI-IO: Shutting down the MIDI sequencers... Renoise LOG> Shut down: Stopped and released all MIDI-Devices Renoise LOG> Jack: Deactivate... Renoise LOG> Jack: Releasing port 'renoise:input_01_left' Renoise LOG> Jack: Releasing port 'renoise:input_01_right' Renoise LOG> Jack: Releasing port 'renoise:output_01_left' Renoise LOG> Jack: Releasing port 'renoise:output_01_right' Renoise LOG> Jack: Close... ^CRenoise LOG> Application: Caught signal:2 - Terminating... Renoise LOG> Jack: Jack was released Renoise LOG> Shut down: Stopped and released the active Audio-Device Renoise LOG> Shut down: Destroyed the Player Renoise LOG> Shut down: Destroyed the Document Renoise LOG> Shut down: Destroyed the GraphPort Renoise LOG> Shut down: Saving the Preferences Renoise LOG> Shut down: Destroyed the Preferences Renoise LOG> Shut down: App is down Renoise LOG> Application: Exit OK

Audio Input Wiki Host info is out of date

Hi - I hope this is the right way to report this.

The Audio Input page of the Wiki[1] has a couple of entries that are now out-of-date.

In the known compatible audio software section, it currently says the only version of Cubase that will work for this is Cubase Pro, and that Elements doesn't work.

Since version 11, Cubase Pro, Artist and Elements all support sidechain input, and work fine with Surge's Audio Input mode.
Cubase Pro has indeed offered sidechain since V4.1, so I'm not sure how to mark this differentiation cleanly, but I'd suggest something like this:

Cubase Pro (Version > 4.1), Cubase Artist, Elements (Version > 11)

Also, in the last section - the list of known issues, the following is present:

CUBASE ESSENTIALS AND ELEMENTS: No support for sidechains

I think now the versions this would apply to are Cubase AI and Cubase LE (both of which I'm unable to test, but I'm fairly sure neither support sidechain).

Sorry if this isn't the right arena to report this.

[1]- https://github.com/surge-synthesizer/surge-synthesizer.github.io/wiki/Using-Surge-as-an-effect-(and-vocoder)

Surge FXP presets are not showing up in Bitwig

  • macOS 10.14.6
  • Bitwig 3.1.2
  • Surge 1.6.6

Despite having standard FXP format presets, the Surge presets are not showing up in Bitwig's file browser despite my having added /Library/Application Support/Surge (where the FXPs are located), to Bitwig's Locations in Settings.

Any ideas why?

Testimonials and sourcing of testimonials

Suggestion:

We could definitely have testimonials for Surge on a page somewhere. Posted about it on #design and @itsmedavep seemed to agree.

I'll start by asking if Inigo Kennedy would be interested in providing a testimonial - and send him the one he wrote on KVR.

@itsmedavep is correct that there should be 3-5 of them. Will be posting them when I get permission from the wordy culprits!!

Feature Request: keybindings

One of the most annoying things with software based synths is their dependency on the mouse when navigating through banks/patches. Right now, the work flow appears to be:

  1. Click on the patch browser
  2. Locate a patch
  3. Trigger via MIDI controller
  4. Repeat (meaning you have to start from scratch)

One simple fix would be to keep the menu open. This would allow the end user to avoid having to start at the beginning each and every time they wanted to select another option.

Better still would be to design the GUI in such a way so that a keyboard's arrow keys could be used to cycle around throughout the Patch Browser. Again, the trick is to avoid closing the menu each time something is selected forcing the user to start the process from the beginning each time.

Looking forward to digging deeper into this seemingly awesome software.

Topbar: "System Requirements" "Downloads" "Contributors"

Suggested on general - add System Requirements, Downloads and Contributors to the top-bar-menu.

They would, in this case, be:

http://surge-synthesizer.github.io/#contributors
http://surge-synthesizer.github.io/#downloads
http://surge-synthesizer.github.io/#systemrequirements

i'm not sure which things from the frontpage could be anchored and added to the topbar.

i guess eventually the Downloads page will be a separate page. but i think there's a ticket about that, too, somewhere.

Cannot find the Surge wavetable browser

Hello,
it seemed to me that we could open the Surge browser before it's open source ( or before 1.6.0 betas )
I searched on the Surge manual, on the KVR forum for answer and I saw that someone who has bought Surge in the past and has kept this version and he can use the browser as well.
Please update Surge so we can browse the wavetable without changing it one by one with the arrows .
Thanks in advance.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.