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

Full Stereo Processing #174

Closed
harryhaaren opened this issue Mar 7, 2017 · 18 comments
Closed

Full Stereo Processing #174

harryhaaren opened this issue Mar 7, 2017 · 18 comments

Comments

@harryhaaren
Copy link
Member

Implement stereo audio processing from source to end of the audio chain

@harryhaaren harryhaaren added this to the future release milestone Mar 7, 2017
@georgkrause
Copy link
Member

This would need a pretty well designed concept, since some users (including me) may mostly work with mono sources (gits, mics, even some (most?) synths) and i think the new panning is pretty handy. Would this get lost? Can i choose between mono and stereo? Maybe per channel? (you know, i love configuration possibilities :D)

@coderkun
Copy link
Contributor

coderkun commented Mar 7, 2017

I mostly work with a stereo keyboard input and would love to see stereo support in luppp. But @georgkrause is right that a mono workflow must not suffer from this.

@georgkrause
Copy link
Member

@coderkun sure its real stereo and not two times the same signal? i have some softsynths and one hardware synthesizer which simply output two times the same...

@sub26nico
Copy link
Contributor

+1, I'd like to see it too

@coderkun
Copy link
Contributor

coderkun commented Mar 8, 2017

@georgkrause, I am sure: The source is a Nord Electro 5 which hase some stereo effects etc. – it is a true stereo signal.

@coderkun
Copy link
Contributor

coderkun commented Mar 8, 2017

Two options I can currently think of:

  1. Provide a configuration option for each channel to be either mono or stereo and adjust the inputs on the fly
  2. Provide mono and stereo input for each channel at the same time and map the mono input to the stereo input internally (using panning), using the stereo part for further processing

@harryhaaren
Copy link
Member Author

harryhaaren commented Mar 8, 2017 via email

@coderkun
Copy link
Contributor

Is there any documentation about the signal flow? I would like to see when the mono inputs get converted into a stereo signal, when send, return and fx are applied etc.
I think it would be best to see how it is currently done and line out how it will be done using (optional) stereo signals.

@georgkrause
Copy link
Member

@harryhaaren i didnt missed the panning when it wasnt there but now i dont want to live without. so if connecting a mono source with the two stereo inputs still allows me to pan, i am fine with it!

@harryhaaren
Copy link
Member Author

@coderkun nope no docs, just code, sorry. Currently, its like this:

(mono) input -> looper -> sends (Rev + JACK) -> ***pan dial / stereo convert volume/ *** => Master fader
(stereo) input => looper => sends (Rev + JACK) => pan (stereo panner, amp / delay dunno which yet) => master

Aka; stereo the whole way trough.

We can discuss this more, but really its about just getting into the code and reworking it to be stereo. Tweaking details of exactly how mono -> stereo works at the start of the chain is the icing on the cake :)

@coderkun
Copy link
Contributor

coderkun commented Mar 18, 2017

Hey @harryhaaren, which data structure do you suggest to pass a stereo signal around (e. g. sample)? The mono signals are just one float but we would need two floats for stereo …

@harryhaaren
Copy link
Member Author

Hi @coderkun, there are two options for dealing with stereo, either A) pass two buffers of floats (aka, one per channel), B) interleave the samples, so a single buffer is passed in, with channel A and B mixed like so : ABABABABA

@coderkun
Copy link
Contributor

I have a full stereo chain working locally, just need fix the panning and make sure stereo files are read and written.

@harryhaaren
Copy link
Member Author

Sounds good - file a PR when you have something you want me to look at :) Cheers

@harryhaaren
Copy link
Member Author

Hey @coderkun - this can be marked closed right? Your PR adding stereo to the audio pipeline, so I'll close this?

@coderkun
Copy link
Contributor

@harryhaaren, yes, please close it.

I cannot close it myself, can I?

@harryhaaren
Copy link
Member Author

Just wanted to make sure there was no remaining "thing" you had in mind as part of this PR. Thanks again!

@harryhaaren harryhaaren modified the milestones: Release 1.1.1, future release Apr 22, 2017
@coderkun
Copy link
Contributor

Yeah, sorry, I could have been more clear on this. Thanks for merging.

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