19 Dec
2011
19 Dec
'11
5:11 p.m.
Hi,
After fixing the jack 32bit/64bit issue, now finally I can run kontakt5
1. As standalone exe, using WINE / WineASIO
2. As a VST instrument, using WINE / WineASIO / SAVIHost
3. As a VST instrument, using Festige / FST.
All approaches can show the GUI, and play some sound.
Great!
I can see the following differences:
- While approach 1 and 2 give me 2 output channels, approach 3 gives me
8, 16 or 64 output channels (depending on which DLL I pick). I only need
2 for stereo..
- I would think that approach 1 and 2 involve emulating more stuff than
strictly necessary, so I would like to stick to approach 3, if possible.
- Only approach 3 gives me direct JACK midi input. (But I guess I can
solve this with a2jmidid for the other two approaches, too.)
* * *
Anyway, what comes next now is to
1. Set this up in a networked way: host1 has the physical midi input and
audio HW, host2 is running the VST. (I have already done this with
jack2, but now I have to re-do this for jack1.)
2. Tune the system to decent latency/performance; currently I get a lot
of xruns...
* * *
Is there an up-to-date guide somewhere explaining
- how should I choose my kernel version ,
- what to compile into my kernel,
- how to configure my kernel run-time,
- how to patch / configure wine,
- how to configure jack
- etc
.... to get the best possible audio performance?
(I know this gets talked about all the time, but everything is changing
so fast, and half of the info I find the net is already obsolete;
I am not asking you to repeat what is is already stated, but to point me
to the relevant and current docs.)
Thank you for your help:
Kristof
19 Dec
19 Dec
6:16 p.m.
On Mon, 19 Dec 2011 17:11:48 +0100
Csillag Kristof <csillag.kristof(a)gmail.com> wrote:
* * *
Is there an up-to-date guide somewhere explaining
- how should I choose my kernel version ,
- what to compile into my kernel,
- how to configure my kernel run-time,
- how to patch / configure wine,
- how to configure jack
- etc
Hi, probably the fastest way is running this script:
http://code.google.com/p/realtimeconfigquickscan/
which AFAIK is up to date. It will tell you various info on your system.
Then there's this written by Jeremy IIRC:
http://wiki.linuxmusicians.com/doku.php?id=system_configuration
and I've just found this page on the wiki, where on the bottom are
collected various links if you want to dig further:
http://apps.linuxaudio.org/wiki/real_time_info
now you've got something to read ;)
best wishes,
renato
20 Dec
20 Dec
9:07 a.m.
On 12/19/11 18:14, Renato wrote:
Then there's this written by Jeremy IIRC:
http://wiki.linuxmusicians.com/doku.php?id=system_configuration
The original article is not written by me. I did edit it heavily. I
should take a look at it, especially now we have the threaded IRQ's and
new real-time patchsets for 3.0 and 3.2.
Best,
Jeremy
19 Dec
19 Dec
6:33 p.m.
On 12/19/2011 05:11 PM, Csillag Kristof wrote:
Hi,
After fixing the jack 32bit/64bit issue, now finally I can run kontakt5
1. As standalone exe, using WINE / WineASIO
2. As a VST instrument, using WINE / WineASIO / SAVIHost
3. As a VST instrument, using Festige / FST.
All approaches can show the GUI, and play some sound.
Great!
Indeed. Congrats.
Are you using the free-of-charge Kontakt player or the full K5 version?
I can see the following differences:
- While approach 1 and 2 give me 2 output channels, approach 3 gives me
8, 16 or 64 output channels (depending on which DLL I pick). I only need
2 for stereo..
- I would think that approach 1 and 2 involve emulating more stuff than
strictly necessary, so I would like to stick to approach 3, if possible.
There'll be performance differences when it comes to low latency.
running it under wine will require an extra context-switch. I don't know
if WineASIO works around this, but I think it does not.
Not too long ago there was an email on LAD by Paul Davis who explained
ardour's native VST/wine strategy. IIRC the whole app was run in the
context of wine to forego the extra context-switch; but I don't know the
details. He may chime in.
http://old.nabble.com/Kontakt-Spikes-td32614159.html
May actually have some insight as well..
- Only approach 3 gives me direct JACK midi input.
(But I guess I can
solve this with a2jmidid for the other two approaches, too.)
Where there's a will, there's a way :)
* * *
Anyway, what comes next now is to
1. Set this up in a networked way: host1 has the physical midi input and
audio HW, host2 is running the VST. (I have already done this with
jack2, but now I have to re-do this for jack1.)
2. Tune the system to decent latency/performance; currently I get a lot
of xruns...
It'd be great if you could document this setup or write a blog-post when
you're done.
Well, most of it is already there scattered over the last couple of
emails so it should not be much work.
* * *
Is there an up-to-date guide somewhere explaining
2 months out of business and I lost track of those :)
- how should I choose my kernel version ,
For a professional studio setup you'll want a realtime-kernel for
reliability (it must be the time of the year again, I wrote this two
times today already).
http://www.kernel.org/pub/linux/kernel/projects/rt/
I have good stable experience with 3.0.6-rt17 on 64bit; there were some
b0rked versions after that and I have not yet tried 3.0.12-rt30 nor
3.2-rc5-rt8.
- what to compile into my kernel,
Maybe you can get away with some stock kernel, from Arch or AVLinux;
otherwise:
CONFIG_TREE_PREEMPT_RCU=y
CONFIG_PREEMPT_RCU=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_RT_FULL=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_HPET_TIMER=y
disable CONFIG_RT_GROUP_SCHED
or walk through http://trac.jackaudio.org/wiki/Cgroups
Avoid *_TRACE and *DEBUG* and *_ACCOUNTING options in general; although
many of those e.g. CONFIG_LATENCYTOP=y or CONFIG_PM_DEBUG=y don't have
negative impact unless you explictly enable them during runtime; this is
usually documented in the help for the option.
http://old.nabble.com/IO-scheduler-for-realtime-audio--td30624684.html
might be helpful as well.
- how to configure my kernel run-time,
boot option 'threadirqs'; and Rui's rtirq: http://alsa.opensrc.org/Rtirq
debian already takes are of /etc/security/limits.d/audio.conf
CPU frequency scaling works fine on most systems these days - even on
low latency systems. But PCI-bus or FSB freq. scaling is still often an
issue. Chipsets vary a lot WRT to that. In doubt: disable it in the BIOS
(look for sth like 'C1E halt state' and/or 'EIST' and disable them).
- how to patch / configure wine,
- how to configure jack
Should work fine OOTB.
- etc
.... to get the best possible audio performance?
"best" is somewhat ambiguous in that context. I assumed you meant a
reliable low-latency system.
(I know this gets talked about all the time, but
everything is changing
so fast, and half of the info I find the net is already obsolete;
indeed.
I am not asking you to repeat what is is already
stated, but to point me
to the relevant and current docs.)
too late :)
Cheers!
robin
Thank you for your help:
Kristof
6:59 p.m.
On 12/19/2011 06:33 PM, Robin Gareus wrote:
On 12/19/2011 05:11 PM, Csillag Kristof wrote:
Oh my, time flies and my memory is not getting better:
http://linuxaudio.org/mailarchive/lad/2010/11/10/175294
long story short: use FST.
robin
> - I would think that approach 1 and 2
involve emulating more stuff than
> strictly necessary, so I would like to stick to approach 3, if possible.
>
There'll be performance differences when it comes to low latency.
running it under wine will require an extra context-switch. I don't know
if WineASIO works around this, but I think it does not.
Not too long ago there was an email on LAD by Paul Davis who explained
ardour's native VST/wine strategy. IIRC the whole app was run in the
context of wine to forego the extra context-switch; but I don't know the
details. He may chime in. 
20 Dec
20 Dec
2:59 a.m.
On 12/19/2011 12:33 PM, Robin Gareus wrote:
Are you using the free-of-charge Kontakt player or the full K5 version?
The only free Kontact player I've found only runs for 15 minutes after
installation. (NOT 15 minutes of run time, but 15 minutes which start
the minute you install it!!)
3:10 a.m.
On Mon, Dec 19, 2011 at 8:59 PM, Al Thompson <althompson58(a)gmail.com> wrote:
On 12/19/2011 12:33 PM, Robin Gareus wrote:
You must be running the demo or the player with unlicensed content.
The Kontakt player can only play libraries licensed for the player,
else it goes into demo mode. You need the full app for loading any
random samples or libraries for editing.
--
Brett W. McCoy -- http://www.brettwmccoy.com
------------------------------------------------------------------------
"In the rhythm of music a secret is hidden; If I were to divulge it,
it would overturn the world."
-- Jelaleddin Rumi
Are you using the free-of-charge Kontakt player or the full K5 version?
The only free Kontact player I've found only runs for 15 minutes after
installation. (NOT 15 minutes of run time, but 15 minutes which start
the minute you install it!!)
21 Dec
21 Dec
5 p.m.
On 12/19/2011 09:09 PM, Brett McCoy wrote:
Actually, I think it was a demo. It was the only one I found on the NI
site, and only played the demo sample library, which was really limited.
I had only tried it because I've had virtually no luck getting
Linuxsampler working in Windows. It requires the ASIO drivers, and the
only one of those I have is a free one called something like ASIO4ALL or
something equally silly, and it kind of works, but has HORRIBLE latency
and takes a ton of CPU when it's loaded.
The only free Kontact player I've found only
runs for 15 minutes after
installation. (NOT 15 minutes of run time, but 15 minutes which start
the minute you install it!!)
You must be running the demo or the player with
unlicensed content.
The Kontakt player can only play libraries licensed for the player,
else it goes into demo mode. You need the full app for loading any
random samples or libraries for editing.
5:04 p.m.
2011-12-19 18:33 keltezéssel, Robin Gareus írta:
On 12/19/2011 05:11 PM, Csillag Kristof wrote:
Fol experimenting, I am using the free-of-charge Kontakt Player, with
the factory library selection.
(Which is quite limited, but the technology is equivalent with all other
kontakt-based instruments.)
What I have a satisfactory setup, I intend to buy (one of the) Galaxy
Pianos,
which is also powered by Kontakt Player.
Kristof
> Hi,
>
> After fixing the jack 32bit/64bit issue, now finally I can run kontakt5
>
> 1. As standalone exe, using WINE / WineASIO
> 2. As a VST instrument, using WINE / WineASIO / SAVIHost
> 3. As a VST instrument, using Festige / FST.
>
> All approaches can show the GUI, and play some sound.
>
> Great!
Indeed. Congrats.
Are you using the free-of-charge Kontakt player or the full K5 version?
5:50 p.m.
On 12/21/11, Csillag Kristof <csillag.kristof(a)gmail.com> wrote:
2011-12-19 18:33 keltezéssel, Robin Gareus írta:
If you want a good piano on Linux I think you would be better off
looking at Pianoteq, or using LinuxSampler with one of the giga pianos
from the confusingly similarly named sampletekk -
http://www.sampletekk.com/ (they have a 50% discount at present!)
Windows-based VSTi are never going to be the way to go IMHO - likely
to be much more unstable and frustrating!
James
On 12/19/2011 05:11 PM, Csillag Kristof wrote:
Fol experimenting, I am using the free-of-charge Kontakt Player, with
the factory library selection.
(Which is quite limited, but the technology is equivalent with all other
kontakt-based instruments.)
What I have a satisfactory setup, I intend to buy (one of the) Galaxy
Pianos,
which is also powered by Kontakt Player.
> Hi,
>
> After fixing the jack 32bit/64bit issue, now finally I can run
> kontakt5
>
> 1. As standalone exe, using WINE / WineASIO
> 2. As a VST instrument, using WINE / WineASIO / SAVIHost
> 3. As a VST instrument, using Festige / FST.
>
> All approaches can show the GUI, and play some sound.
>
> Great!
Indeed. Congrats.
Are you using the free-of-charge Kontakt player or the full K5 version?
19 Dec
19 Dec
9:33 p.m.
Il 19/12/2011 17:11, Csillag Kristof ha scritto:
1. As standalone exe, using WINE / WineASIO
2. As a VST instrument, using WINE / WineASIO / SAVIHost
3. As a VST instrument, using Festige / FST.
- how to patch / configure wine,
Hi, based on my personal experience with NI Battery 3, I achieved the
best performances using FeSTige by falkTX. With FeSTige, rtirq, and Wine
with RT support, you can manage the priority of the ".exe" process, so I
made some experiment and found a good setup.
I also wrote about some experiments I made with Wine and Battery here:
http://forum.winehq.org/viewtopic.php?p=56810&sid=28c71399324b7399dd643…
This is the command I used to launch it from terminal:
env WINEDEBUG=-all WINE_RT=15 WINE_SRV_RT=10 wine
.wine/drive_c/Programmi/Native\ Instruments/Battery\ 3/Battery\ 3.exe
But, In the end, IMHO I found more reliable to use a native sampler, so
I switch to LinuxSampler :-)
--
Nicola Pandini
http://www.cassandraweb.it/nicolapandini
4749
days inactive
4751
days old
linux-audio-user@lists.linuxaudio.org
10 comments
8 participants
participants (8)
-
Al Thompson -
Brett McCoy -
Csillag Kristof -
James Stone -
Jeremy Jongepier -
Nicola Pandini -
Renato -
Robin Gareus