Posts: 31
Threads: 11
Joined: Feb 2015
Reputation:
0
(L)ubuntu 16.04 64B, fresh install.
When I try to create a new session I get this "Could not create session in(...)"
Hints?
TIA
Posts: 32
Threads: 7
Joined: Jan 2016
Reputation:
0
Likely a jack issue. Is jack running?
Posts: 31
Threads: 11
Joined: Feb 2015
Reputation:
0
Solved!
For unknown reasons I was not added to the audio group. I saw that info when re-installing Mixbus from scratch via Terminal message.
A simple "sudo adduser username audio" fixed it.
Posts: 6
Threads: 1
Joined: Oct 2016
Reputation:
0
So I changed the ownership on the whole home folder, but it doesn't solve my problem :/
I don't get it.
Posts: 55
Threads: 6
Joined: Sep 2016
Reputation:
2
10-06-2016, 03:09 AM
(This post was last modified: 10-06-2016, 03:19 AM by micksedan.)
/home should be owned by root
/home/Clark (and it's contents) should be owned by Clark
mixbus installs in /opt owned by root.
I made a link to launch mixbus:
# ln -s /opt/Mixbus-3.6.0/bin/mixbus3 /home/me
and type mixbus3 in a terminal to launch
I would fix your permissions, rename your current mixbus folder,
and do a fresh install of mixbus
Cheers
Posts: 659
Threads: 57
Joined: Jan 2014
Reputation:
43
Another thing to check...
Recall that you can specify the name of the folder where Mixbus will create all
-default- sessions. Additionally, you can specify the name the folder where you might
want to create other (non-default) sessions. For example, I specify my default
session folder to be: "/home/pburyk/studio/default_sessions". This allows me to
quickly startup or continue a scratch or test session. For my "real" sessions, I specify:
"/home/pburyk/studio/projects/projectname/sessions/songs/songname"
As you can see, this is more complicated than simply using my default session folder,
but it is done in the name of organization. The whole point of this is to help explain
that there are numerous areas in the specified path that Mixbus will need access to.
So, in my case, I assure that Mixbus has read/write/execute permission to -every-
folder and file that exist under my "studio" folder. This can be done by group
association or using the chown & chmod commands (topics for further discussion).
Additionally, some of us have chosen to locate our session areas out on an external
HDD or separate file system. This helps protect our project areas from inadvertent
harm or being run out of space by non-studio related work on the computer. Both of
these cases require that these "detached" areas be "mounted" prior to asking Mixbus to work with them.
So... As you can see, there are a number of potential causes (even more beyond
what I've provided here) for getting the "can't create" message. All of them are
pretty straight forward to trouble shoot and resolve if you know just the basics of
Linux. If not, there are many others here who can help you get past this issue.
Cheers!
Patrick