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

Save and restore mixer state (fader / mute / solo...) #377

Closed
newlaurent62 opened this issue Jun 20, 2020 · 11 comments
Closed

Save and restore mixer state (fader / mute / solo...) #377

newlaurent62 opened this issue Jun 20, 2020 · 11 comments
Labels
feature request Feature request

Comments

@newlaurent62
Copy link
Contributor

newlaurent62 commented Jun 20, 2020

Hello,

To stream web concert with Jamulus and several band, it would be nice to let the user save and restore the mixer state (fader, mute, solo,... )

Each musician would have a unique and same channel name or a channel uuid across connections. If a musician is disconnected then when reconnected, the level, mute and solo should be the one of the current preset for that channel or the default.

BR,
Laurent

@corrados
Copy link
Contributor

This is already supported in the Jamulus software.

@newlaurent62
Copy link
Contributor Author

Can we name the presets ? Like first song mixer, second song mixer ...

@corrados
Copy link
Contributor

corrados commented Jun 20, 2020

Yes, you can do this. Start Jamulus with Jamulus --inifile "c:\temp\jamulussetup1.ini".
Just do your session, than disconnect and close the Jamulus software. Then all fader settings are stored in the ini-file. If you then want to store another session, simply copy the file jamulussetup1.ini to jmulussetup2.ini and start with --inifile "c:\temp\jamulussetup2.ini". If you are then done with the storage and want to recover the first session, then simply start Jamulus with the first file again.

@newlaurent62
Copy link
Contributor Author

I will try that but it would be easier to have a preset handling in the gui (preset save/load button)

@gilgongo
Copy link
Member

I've added this to the Tips & Tricks

@pljones
Copy link
Collaborator

pljones commented Jun 20, 2020

I have a client and server ini file overhaul sitting here on a branch... It's actually quite a large task to get it right... (At the moment, the ini file is handled on start up / shut down; it needs to change to be more dynamic to get this to work, which means a lot of changes.) This is related to #294 and #347.

I need to finish the jam recorder changes, though...

@melcon
Copy link
Contributor

melcon commented Jun 22, 2020

Yes, you can do this. Start Jamulus with Jamulus --inifile "c:\temp\jamulussetup1.ini".

What's the equivalent for Mac?

@gilgongo
Copy link
Member

Open a Terminal window, type:

/Applications/Jamulus.app/Contents/MacOS/Jamulus --inifile /path/to/somewhere/jamulussetup1.ini

Hit return key.

@newlaurent62
Copy link
Contributor Author

Considering a concert streaming : Each musician is connected to Jamulus and an additionnal Jamulus client (called "Streamer") will handle the output streaming mix of the musician playing and will be send to a social network or icecast2 using OBS.

The store/load of fader/pan mixers is intended to help handling the streaming of a Jamulus concert. This would allow to prepare each song settings before the concert begins and recall them as needed during the concert. An easy and fast action to store/load would be preferable. Closing the Jamulus client should not be needed.

May be, it would be better to let the user dispose of a jack client with a port for each channel from the server or a special client to the server with an output jack port for each channel. This would allow to put some VST/LV2 on channels and making sub groups for a more complex mix in a DAW that otherwise would be impossible.

@corrados
Copy link
Contributor

corrados commented Jul 8, 2020

See my comment #347 (comment) and the following discussion.

@corrados
Copy link
Contributor

This is implemented now. It is available on Git master -> closed

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

No branches or pull requests

5 participants