2014-07-01 0:25 GMT-03:00, Danni Coy <danni.coy(a)gmail.com>:
> I already have jack + wineasio setup, but I was able to get sound
> before this via pulse.
Ah. I do not use Pulse. Here it's only ALSA. Planning to compile
Dssi-VST from Git and/or Wineasio.
Is it possible to add libraries to Kontakt while running as VST
through a host, or just from the standalone app?
> On Tue, Jul 1, 2014 at 12:17 PM, Aiyumi Moriya <aiyumi.br(a)gmail.com> wrote:
>> 2014-06-30 22:58 GMT-03:00, Danni Coy <danni.coy(a)gmail.com>:
>>> [...]
>>> However if you do want to test try running kontakt directly under wine
>>> rather than in a plugin host. It should be configured by default to
>>> play to which ever sound card Wine is configured to play with
>>
>> If testing this way, just after installation, are you able to get past
>> the initial audio setup screen?
>>
>>> On Wed, Jun 18, 2014 at 10:09 PM, Aiyumi Moriya <aiyumi.br(a)gmail.com>
>>> wrote:
>>>> 2014-06-18 5:13 GMT-03:00, Danni Coy <danni.coy(a)gmail.com>:
>>>>> yes kontakt player does work under wine I had problems with connecting
>>>>> midi doing it that way though.
>>>>
>>>> Thank you for the clarification :D .
>>>>
>>>> 2014-06-18 5:15 GMT-03:00, Danni Coy <danni.coy(a)gmail.com>:
>>>>> If memory serves me correctly I did have difficulty installing it from
>>>>> the Linux side. I did have to do the initial installation in windows.
>>>>
>>>> I gave it a try. Here, installation went fine. But I'm stuck on the
>>>> initial configuration (the "audio and MIDI settings" screen that
>>>> appears when Kontakt is run for the first time). This is the problem
>>>> I'm having (from the other thread):
>>>>
>>>> 2014-06-17 22:49 GMT-03:00, Aiyumi Moriya <aiyumi.br(a)gmail.com>:
>>>>> now I'm struggling with Kontakt Player. Any chance it can work without
>>>>> JACK+Wineasio? I'm on a multilib 64-bit system but still don't have
>>>>> 32-bit JACK nor Wineasio. Kontakt Player installed fine, but I'm stuck
>>>>> on the audio setup screen. There's "Wasapi (Shared mode)" as the only
>>>>> audio driver, status says "stopped", my onboard soundcard appears on
>>>>> the dropdown list, my MIDI ports get recognized, but no matter what is
>>>>> done, it complains that I need to set a "valid" audio interface... I
>>>>> don't know what's happening. Wine plays sounds from other apps just
>>>>> fine. Can't it work with the default driver, without JACK and Wineasio
>>>>> (not considering latency or anything yet), or am I missing something
>>>>> else? By what I got from reading their "Getting Started" guide, I
>>>>> can't add libraries if I don't get past this screen...
>>>>
>>>> After that, I gave it some more thought. The "Getting Started" guide
>>>> says it "skips" this audio configuration if used as VST (the audio is
>>>> left up to the host). Would it be possible to add libraries through
>>>> the VST interface?
>>>>
>>>> --
>>>> ____________________
>>>>
>>>> Blog: http://aiyumi.warpstar.net/
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>> Linux-audio-user(a)lists.linuxaudio.org
>>>> http://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>
>>
>> --
>> ____________________
>>
>> Blog: http://aiyumi.warpstar.net/
>> _______________________________________________
>> Linux-audio-user mailing list
>> Linux-audio-user(a)lists.linuxaudio.org
>> http://lists.linuxaudio.org/listinfo/linux-audio-user
>
--
____________________
Blog: http://aiyumi.warpstar.net/
So it's summer, they say.
White bright and light pastel colors sparkling on every corner and turn.
Cheesy and silly season, they say. Alas, southerners don't apply. Sorry
about that. Of course I mean the hemisphere, obviously.
For whom it might concern, all anxiety has come to an end.
Indeed.
It all relates back to this last May 3, when a not-so-formal meeting
(aka. workshop) took place while during LAC2014@ZKM-Karlsruhe, where
some pertinent and undeniable requests were dodged and framed to a
"soonish" implementation. And guess what?
Yup, the "soonish" are no more, or so I think.
Qtractor 0.6.2 (boson walk beta) is out!
Perhaps an additional word is due though, about the riddling code-names
that are branding the post-TYOQA beta releases. They have no personal
nor logical sense, I assure you. Perfectly arbitrary now. Everything in
life and the universe is way more unconventional than just a name.
Without further assay.
Qtractor is an audio/MIDI multi-track sequencer application written in
C++ with the Qt4 framework. Target platform is Linux, where the Jack
Audio Connection Kit (JACK) for audio and the Advanced Linux Sound
Architecture (ALSA) for MIDI are the main infrastructures to evolve as a
fairly-featured Linux desktop audio workstation GUI, specially dedicated
to the personal home-studio.
Release highlights:
* Plugins activation MIDI controller / automation (NEW)
* LV2 UI Idle and Show (>= Qt5) interface support (NEW)
* Discrete editing of automation curve node velues (NEW)
* Missing audio/MIDI files and plugins warning message (NEW)
* MIDI note drawing on tempo-map changes (FIX)
* Automation curves re-adjusted to tempo-map changes (FIX)
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
http://sourceforge.net/projects/qtractor/files
- source tarball:
http://download.sourceforge.net/qtractor/qtractor-0.6.2.tar.gz
- source package (openSUSE 13.1):
http://download.sourceforge.net/qtractor/qtractor-0.6.2-12.rncbc.suse131.sr…
- binary packages (openSUSE 13.1):
http://download.sourceforge.net/qtractor/qtractor-0.6.2-12.rncbc.suse131.i5…http://download.sourceforge.net/qtractor/qtractor-0.6.2-12.rncbc.suse131.x8…
- quick start guide & user manual (severely outdated, see wiki):
http://download.sourceforge.net/qtractor/qtractor-0.5.x-user-manual.pdf
- wiki (help wanted!):
http://sourceforge.net/p/qtractor/wiki/
Weblog (upstream support):
http://www.rncbc.org
License:
Qtractor is free, open-source software, distributed under the terms
of the GNU General Public License (GPL) version 2 or later.
Change-log:
- Prevent linear and spline automation curve modes for all integer
valued subjects. Also, make sure those values are rounded to the nearest
integer away from zero.
- Fixed save of LV2 Presets for plugins with state files.
- A man page has beed added (making up Gürkan Sengün's work on debian,
thanks).
- When moving plugins by eg. drag-and-dropping across tracks, automation
curves were being left behind, maybe leading to unpredictable mistaken
behavior. Hopefully, not anymore.
- Translations install directory change.
- Automation curves are now automatically re-adjusted to tempo map node
changes (after a ticket by Holger Marzen, thanks).
- Audio/MIDI files or plugins found missing on session load are now
subject for an explicit modal warning message and prompt for an
immediate session backup salvage.
- Changing instrument plugin programs is now an undo/redo-able command
operation, especially for DSSI but also for plugins that come with the
LV2 Programs interface extension support
(http://kxstudio.sourceforge.net/ns/lv2ext/programs).
- Drawing, selecting and/or resizing of MIDI note events that extend
across tempo/time-signature changes is now made a bit more correctly
over the MIDI clip editor (aka. piano-roll), especially regarding to
current snap-to-beat setting (after an outstanding ticket by yubatake,
thanks).
- Once again, audio frame/MIDI time drift correction has been slightly
refactored to improve MIDI input monitor and timing.
- Discrete automation curve node values may now be edited via a
numerical entry floating spin-box on double-click (as yet another
request by AutoStatic aka. Jeremy Jongepier, thanks).
- Pressing shift/ctrl keyboard modifiers while double-clicking on a
plugin list entry now briefly reverses the current
View/Options.../Plugins/Editor/Open plugin's editor (GUI) by default
option preference.
- Fixed an old crash lurker when switching output buses that implied a
change on the number of audio channels, while on tracks that have
(auto-)monitor turned on and at least one active plugin in chain (yet
another ticket by AutoStatic aka. Jeremy Jongepier, thanks).
- MIDI Controller assignment (aka MIDI learn) and/or automation of
plugins (de)activation state has been added (as requested by AutoStatic
aka. Jeremy Jongepier, thanks).
- LV2 UI Idle and Show interfaces support added.
- Allow the build system to include an user specified LDFLAGS (patch by
Alessio Treglia aka. quadrispro, thanks).
See also:
http://www.rncbc.org/drupal/node/795
Enjoy && have (lots of) fun.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Because who else would even care besides you lot?
After going for years with anemic video cards because the "good" ones
would sound like a jet taking off, I splurged and got an Asus GeForce
GE640 silent. No fans, just fins and heat pipes, and a GPU that isn't
close to EOL already.
Now, great performance on my two monitors and sweet, sweet silence.
And having replaced video cards in Windows machines and having the OS
freak the frak out about a system change, a renewed appreciation for
Linux. I'd pre-installed the nouveau packages from Arch, and once the
new card was in place, two simple config file changes and a mkinitcpio
later I was rocking it.
--
======================================================================
Joe Hartley - UNIX/network Consultant - jh(a)brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa
Aside from the Mackie and look/work alikes (with motor faders), It seems
there are already some of the ideas I had, out there and being used.
http://lividinstruments.com/hardware_baseii.php uses touch faders in some
interesting ways. First, they are sunken faders as I had thought would
give the best feel as it would keep the finger on the fader. Second, it
includes an LED bar for visual feed back (something I might not have
added). The third thing is probably what makes it the most interesting,
though it is not fully unique to a touch fader. This is the options for
how it is used. It can be used the same as any rotary encoder, showing
width, offset from center, or level. It is interesting to note that a
motor fader with a LED strip could do these things too, I have seen a row
of motor faders that in one mode default to center for graphic eq control.
An encoder is incemental in any case, and the touch fader can be set up to
be as well, that is, it could be set up to work the same as the belted
encoder. The motor fader could be set as incremental... so that it centres
when the finger is lifted without changing the value it gives, but I think
that is probably outside the best use of a fader where the knob give
position feedback.
The touch fader _can_ also work in the traditional fader way where the
finger position matches the level. This can work in two ways: a
semi-inteligent setting where the actual level would not change if the
finger was not right at the current level position until the finger moved
and then it would change the level more incrementally (what the mind would
expect). The other way would be to jump to where the finger is. (the video
show this) So it could go from full scale to no scale with one touch. (One
hopes this sends a slope from one level to the next and that the rate is
setable)
This particular unit is not designed as a DAW controller. It could be used
that way, but in my opinion it is over priced and awkward for that to be
it's main use. However, the faders and how they are used are interesting.
Personally, I would want my faders to have no buttons etc. below them, but
for the use this controller is made for (drum pads etc.) it probably makes
sense.
The cost for a membrane fader is about 75% compared to a motor pot and
still requires a LED strip if position indication is required. SO there is
no cost saving over a motor pot that I can see. The user has to want
something the membrane fader offers that can't be done with a motor fader.
- incremental use.
- less damage prone when thrown in a bag etc.
- Maybe last longer? (maybe not too)
For DAW control use, motor faders seem to be the better deal.
I do want to try the rotary encoder though. either with a large wheel
(actually 2-3inch is not that big) or belt with no LED strip. The on
screen fader position should be good enough.
--
Len Ovens
www.ovenwerks.net
I am wondering how those who like tactile feel in a fader would feel about
a sideways rotary control. I am thinking of something like the pitch or
mod. wheel on a synth. But no middle detent. Rotary encoders are great for
control surfaces, but the feel of a fader as compared to a rotary knob
makes faders easier to think with. I am thinking if I can use the same
idea with a fader feel where the control is endless, it would work well.
The box would have to be thicker of course and may be less use for stage.
The box could be made thinner by making it touch sensitive and self
centering like the pitch wheel, but I think that starts to make the
motorfader look better. The up side of the sideway encoder is that the
midi messages are just direction/number of ticks.
My first thought was a touch strip like the old guitar style stage
keyboards, have it inside a slot so it is easy to feel without seeing it.
Moving the finger up just sends up tics and moving it down gives down
ticks, so the finger can start anywhere on the strip which will be where
the (virtual) fader is now and move from there. I would have to use a adc
and take ticks off the LSB after doing a greater or less than calc. The
encoder has this out directly.
Also, ticks and direction happen to work well with the control board I
have on hand... the software can change that to a hard value if required
though.
--
Len Ovens
www.ovenwerks.net
I recently started writing jingles, because I need them for my podcast and
videos that our skeptic group produces. I did not want to use somebody
else's when I have the ability to write my own.
I found jingles to be a very complex and interesting material to work on.
So far I've written only one jingle that I am completely happy with and I
am presenting it to you here. It is a jingle that we use for our videos,
when the title of the video is shown and then the video proceeds to the
lecturer.
www.louigiverona.ru/files/TV_jingle_1.flac
Has anyone else had this experience?
--
Louigi Verona
http://www.louigiverona.ru/
This tube amp emulation is inspired by the Orange AD200, but didn't
intend to simulate this one.
However, the simulation use 2 x ECC83, 1 x ECC81 and 4 x 6550 tube
emulations, were the Orange usually use 1 x ECC83. This simulation use
one more ECC83 to avoid phase inversion.
Cabinet simulate a 4 x 10 and in front of all sitting a rectifier.
In opposite to the original AD200, which use a 3 band tonestack, this
one use again a 2 band baxandall tone control.
Again, I'm interested if this suite the need of the Bass players here.
get it here :
http://sourceforge.net/projects/guitarix/files/lv2/
Hi
I got a new laptop without firewire. So I bought a delock pcmcia
firewire card to be able to use my firewire soundcard. Since I couldn't
see any hardware specs for the cards I looked at before buying, I simply
went for the cheapest...
I've been working with firewire a lot in the past, but only with build
in controllers, so I'm not sure if I should do something special to get
this card going.
I obviously tried plugging it in and starting jack with the firewire
driver for all available interfaces, but I get these errors:
firewire ERR: FFADO: Error creating virtual device
Cannot attach audio driver
JackServer::Open failed with -1
no message buffer overruns
Failed to open server
10:35:53.707 JACK was stopped with exit status=255.
10:35:54.785 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
Those look familiar, they are exactly the same as on my desktop pc (that
works with wirewire) when I don't have the soundcard plugged in.
Of course it might be that the pcmcia card is simply not working under
linux (I have no other os running, so I have to assume the card is in
fact working under, say, windows).
But what actions could I take to either get it working or convince
myself that it's simply not supported?
NB: I run crunchbang linux (=debian wheezy), which were installed prior
to getting the card. The laptop is a Lenovo x220.
NB2: I couldn't see anything in dmesg after inserting the card and lspci
is the same with the card attached and detached...
Any pointers appreciated!
--
Atte
http://atte.dkhttp://modlys.dk
Hello,
An Alesis Control PAd is connected to Hydrogen. Channel 10.b It
works although quite often when hitting a same pad, the Hydrogen
instrument would not sound but instead some kind of a click is heard.
Makes this with any Hydrogen instrument. When I connect an Axion 25 to
Hydrogen and use the rubber pads, the Hydrogen sounds are always heard,
no matter how fast a hit is repeated.
Has anyone seen that kind of behaviour before and is there something
to do ? I tried varying the Control Pad sensivity/velocity
curve/threshold but still, the Hydrogen instument is oftentimes
replaced by a click.
Thanks !
