My dream is a netbook with very low cpu time of OS and much more cpu time for Renoise - this is the xsession in my opinion. I did the steps in the FAQ and everything works well, except the error of native startup which says Renoise can’t initialize the ALSA driver. However if I click down the message and Renoise continues the startup, I go to preferences -> audio and pickup the ALSA driver from the list - it initializes without problem, and everything works well.
How can I force the starting session to load ALSA driver BEFORE starting Renoise?
Not to cut off Brian, but I’m having some serious issues on 64-bit Ubuntu. Version 2.5.1 worked like a charm, despite having to punch ESD in the nuts before launching in order to get the sound to work (and without that, really, what’s the point); however, Version 2.6.0 won’t even start.
Without sudo permissions, the terminal output is ```
bash: /usr/local/bin/renoise: cannot execute binary file
And with it, we get ```
/usr/local/bin/renoise: 1: Syntax error: "(" unexpected
I kinda feel responsible since I didn’t participate in the beta. Does anybody know what causes this? It’s not a particularly enlightening error either way.
I am also trying to get Renoise 2.6.1 running on Ubuntu correctly. I am using UbuntuStudio 10.10 Maverick on a 64bit Intel i5 laptop. My normal setup is Renoise in Win7 on the same laptop, however I wanted to learn JACK and linux audio and am looking for a comfort zone in Renoise.
I first tried to simply extract my 2.6.1 x86_64 tar and run renoise out of the box. (like it says it should work)
As Rainfly_x said, using either $ renoise or $ ./renoise without sudo returns “cannot execute binary file”.
using $ sudo renoise returns /usr/local/bin/renoise: 3: Syntax Error: Unterminated quoted string
I also repeated the above steps after having run the system installation script; to no avail. However the installation completes successfully. further yet, ldd renoise returns “not a dynamic executable”;
I have tried to download the other linux version of 2.6.1, and even 2.5.0; both did the same thing. Because of this I am guessing it is a problem on my end. I’m basically a linux noob, so I have no idea where to go from here. Any help would be appreciated.
To anyone using Ubuntu, and this has probably been mentioned elsewhere, you will have a far better experience using a light window manager like X11 intead of KDE or metacity… I use LXDE for this reason… vast improvement on an old laptop
As general information, I tested all WMs with Renoise and on my systems (Mandriva 32bit and 64bit) Renoise runs best with XFCE.
XFCE is far smaller than KDE or Gnome and a bit bigger but easier than LXDE (LXDE is quite new and not yet 100% stable).
It even gives me less XRUNS with QJackCtl then LXDE, but I use Rneoise mostly as ALSA-Standalone DAW.
yeah i was asking because i wondered how it compared to the others. i went for #! linux with openbox and am loving it, but i never tried the others. i use openbox (an #!) because it is fast, small and lightweight, so should be good for making music. i also asked because i did not find Openbox buggy, as you said LXDE was. i’m sure its a matter of taste though. i use tint2 instead of lxpanel, works pretty smooth.
No program can use ALSA in shared mode. I believe there was a trick using OSS compatability layer but i think this no longer works in the newest Linux distributions. But frankly Alsa gains exclusive access to the sound-device that you are using and only allows one program to access Alsa.
Soundbridges like Jack or PulseAudio use Alsa and on their term, allow multiple programs to use their sound architecture.
PulseAudio is the least time-efficient soundbridge, yet the majority of applications nowadays use PulseAudio.
When Renoise was ported to Linux, PulseAudio didn’t existed yet hence Renoise supports either Alsa or Jack.
I’m not familiar if Pulseaudio could be configured to use Jack as its audiosource instead of Alsa, but i suspect that if you can, your problem is solved.
It looks like you are right about me being wrong, i based my interpretations on found forum and knowledgebase questions where developers come up with questions about ALSA’s exclusive claiming of audio devices and they get simply answered that Alsa doesn’t share the sound-device. But i think i misinterpreted the idea where developers wanted to claim the audio device directly rather than use Alsa at all.
This snippet does explain Alsa should be capable to share audio among multiple applications (because OSS was exactly lacking that)
It does also explains this about the Alsa driver:
I suspect for the latter, exclusive mode is required as Renoise aims for low latency. I’m not sure if adding an Alsa shared mode is easily done, but performance wise this is really not a good idea at all, it beats the purpose of serious music production.
Besides, once Renoise would run in shared mode, i am not sure either if Alsa can be claimed strictly again if other applications already have access to Alsa.
You can select them to use alsa backend and not jack or pulseaudio, I know that I have no user land sound server.
I don’t understand how jack being a user land sound server could provide a better “real time” mixing than ALSA being a kernel land sound server. But on the other hand I can understand that exclusive mode can improve performances, but here we need numbers, and without them it means nothing. I think we have to try how it goes with ALSA + shared mode, eventually add both ALSA exclusive and ALSA shared mode avalaible.
I used wine + reaper using the new windows sound driver which is marked experimental on reaper, in shared mode. I had no issue at all, and excellent settings: 5ms at 96khz.
I wasn’t mentioning Jack in that piece you quoted anywhere so this means i wasn’t speaking about Jack regarding low latency and exclusivity, that was still about Alsa.
Jack offers audio and midi patching between audio applications, which is usually a warm welcome if you want to route the audio and midi of multiple audio applications among each other.
