On 01/11/2014 13:00, linux-audio-user-request(a)lists.linuxaudio.org wrote:
>> >hopefully, the article mentions this more a kind of "proof of concept"
>> >than a real product.
>> >If we start to build real knobs on top of tactile interfaces instead of
>> >building hardware interfaces, then we completely loose our minds
>> >
> 10 years ago you could get knobs that would "stick" onto a laptop/monitor
> screen and sent control data. Nothing new under the sun. That was actually
> a real product. I'm 99.9% certain that the company who did it is out of
> business.
Paul, I'm curious, do you remember the name of the product or company?
We all must admit that in the consumer electronic market it is not about
how novel a product is, but how it is presented, advertised and whether
it comes at the right time or not. Think about the Microsoft guy who
held a tablet in its hands during a keynote well before the Apple guy.
And probably someone before him did the same with an even uglier device. :)
BTW it is not only about market. It happens the same with open SW/HW or
the academic community.
Progress!
I compiled JACK2 (64-bit, and also a 32-bit version because Dssi-VST
Git needs it) and Dssi-VST Git. I put "$HOME/vst" in my "$VST_PATH"
and made a symlink to "Kontakt 5.dll" as "$HOME/vst/kontakt5.dll"
because Jack-dssi-host doesn't seem to like spaces in plugin filenames
(quoting or escaping didn't work). I started JACK, then loaded the VST
through Jack-dssi-host.
$ jack-dssi-host dssi-vst.so:kontakt5.dll&
Kontakt's VST loaded fine. A lot of JACK ports appeared (64 ports!
O_O), automatically connected to "system:playback_*". I connected the
Kontakt's JACK MIDI port to my keyboard's, and chose a freeware
instrument (just for testing) from Kontakt's "Files" tab. It loaded as
it should, and playing my keyboard produced the sounds just fine! Yes!
I could even record the output by using Ecasound!
... However, I didn't have the same luck with the Friedlander
Violin... Choosing an instrument from the "Files" tab doesn't work
because it's encrypted and needs to be activated. It's a "Powered by
Kontakt Player" instrument, and the option to activate it doesn't
appear unless it's loaded through the "Add Library" button first. The
problem is that when I try to "Add Library", Kontakt prompts me to
choose the location where the library is installed, and when I select
the directory, it gives me a "No library found" error. I'm sure I'm
pointing to the right place (the directory containing the
"Instruments" and "Samples" sub directories, the ".nkr" and the
".nicnt" files). Just to make sure, I followed exactly the same steps
on Windows and the library loaded with no problems (but I didn't
activate it because I want to do it on Linux!), though it was the
standalone version instead of the VST. I hope this doesn't mean that
adding libraries only work on the standalone interface, because on
Wine I still can't get past the initial audio setup screen... Any
ideas? I feel so close...
--
____________________
Blog: http://aiyumi.warpstar.net/
I'm relatively new to Arch, and tried to use zyn through jack for the first
time last night but couldn't get any sound from it. I've mostly been an
Ubuntu user in years past and never had this issue.
Had to install a2jmidid to get midi note data to it from my midi keyboard,
and that worked fine.
Verified that my volume settings were OK by playing sound through jack from
other programs.
The level meters in zyn made it look like it was outputting sound, but
nothing through my speakers.
No error messages in qjackctl.
I tried starting zyn from a terminal to see if it would print any errors,
and saw nothing.
I can't think of what to try next. Any suggestions?
Pianoteq doesn't have a ARM version and it ask pretty much CPU.The Intel
NUC seems interesting... similar to a Mac Mini (?). Actually that's what
I'm thinking of, an core duo core 2ghz Mac Mini. Afaik it is known to be
a silent device and has firewire, that's a plus for me atm compared to
the NUC. Maybe even nice to see what OSX offers me in terms of CPU
usage, get a bit experience with OSX etc.
Regards,
Dirk
Hi there,
I'm attending a basic multimedia on mobile devices course at
university. During that course I'll have to do a small project,
possibly together with one or two others. I want to do something audio
related of course. The university staff is pretty much focused on
video, so they won't be of much help.
I'm looking for a reasonably low skill/work project idea.
The problem is that I have to do this for iOS (hence the SEMI-OT). I
wouldn't want to develop for or use that horrible platform but if I have
to do it anyway I might as well get some audio coding experience.
Maybe there is something that would be useful to port? Maybe there's
some need for a iPad as remote control thingy? Or some little thing
from scratch?
Suggestions are welcome.
Regards,
Philipp
2014-10-27 15:45 GMT+00:00 Leonardo Gabrielli <leodardo(a)gmail.com>:
> Carlos,
> for audio over Eth/wireless on ARM I suggest you to give a read to my
> recent papers at:
> http://a3lab.dii.univpm.it/research/wemust
>
> Those didn't involve Fons' zita-[nj|jn]bridge, which has recently been
> released and I will probably use in next refinements of the research
> outcome, being tiny and functional.
>
> So far my experience with ARM cores is that you must be careful with Jack.
> Old platforms such as Xscale will require you effort for compiling and
> working fine. And btw I suggest you to go directly with 2.6 kernel for
> real-time audio. Also, I expect it to be tight as a platform for running
> Jack (how much memory do you have?) especially at low period sizes (the CPU
> risks to be overwhelmed with interrupts).
>
> Definetely Jack has a lot of features that are important even for this
> simple task but I'm wondering if there is any gain in embedding only those
> needed in a library and use it instead of the whole JACK.
>
> BTW: a nice paper you may want to read:
> Reuter, "Case Study: Building an Out Of The Box Raspberry Pi Modular
> Synthesizer", LAC 2014
>
> Leonardo
>
>
Thanks so much for the info, Leonardo. I'll check it ASAP,
>
>
> On 26/10/2014 13:00, linux-audio-user-request(a)lists.linuxaudio.org wrote:
>
>> In practice that is not very likely to happen, the reason
>>>> > >being that interfacing to Jack is so much more easy than
>>>> > >writing an ALSA driver. Also, passing via Jack does not
>>>> > >add any latency, and in most cases users will want the
>>>> > >flexibility it provides.
>>>>
>>> >
>>> >thanks for the answer, I was expecting this, but hadn't measures the
>>> >difference between the jack client and alsa driver.
>>> >So now it looks like I need to learn how to cross compile jack for
>>> various
>>> >ARM devices to have it on the lightweight clients :/
>>> >
>>> >Rapha?l
>>> >_______________________________________________
>>> >Linux-audio-user mailing list
>>> >Linux-audio-user(a)lists.linuxaudio.org
>>> >http://lists.linuxaudio.org/listinfo/linux-audio-user
>>> >
>>>
>> I've thought about a similar idea sometime in the past: A distributed
>> audio
>> network with thin clients/raspberrys for a home studio or distributed via
>> some network. I'd be interested in following whatever progress you make.
>>
>> About that of "distributed band" I red a little about programs to jam via
>> internet: Netjack, Ninjam, Midikit.
>>
>
>
--
C. sanchiavedraZ:
* NEW / NUEVO: www.sanchiavedraZ.com
* Musix GNU+Linux: www.musix.es
Hi
Trying my luck again with recordmydesktop. Found that the following
eventually starts record my desktop:
https://dl.dropboxusercontent.com/u/4343030/recordmydesktop
However it seems to only record in mono. How do I capture two audio
channels?
Even better: is there an alternative out there that actually works?
--
Atte
http://atte.dkhttp://a773.dk
MFP -- Music For Programmers
Release 0.05, "Mighty Fine Patching"
I'm pleased to announce a new version of MFP, containing many new
features, fixes and improvements. This is still a very early
release that is missing a lot of expected functionality, but it's
a significant step forward from 0.04 in every way and I thought
it might be of interest to the wider community.
A summary of changes is below. Please see the GitHub issue tracker
for complete details:
http://github.com/bgribble/mfp
This version is still source-code-only, but the new build system
should make it a bit easier for those who would like to try it.
Significant changes since release v0.04
----------------------------------------
* MFP patches can be saved as LV2 plugins that can be
live-edited while loaded in a host (see doc/README.lv2)
* New build system using 'waf' for one-line build and install
(see doc/README.build)
* Support for user patches with dynamic creation of
inlets/outlets and other objects at instantiation time (with
examples) using the "@clonescope" method
* Lazy evaluation of expressions using a leading "," syntactic
sugar is available in message boxes (i.e. the message
"datetime.now()" is a constant, but ",datetime.now()" is
evaluated each time the message is emitted)
* More sample patches, including a basic tutorial covering app
interaction, "hello, world", and patterns for things like
iteration, conditionals, etc
* Improvements to stability and error handling
* Many other bugfixes and improvements. The complete list of
60+ tickets closed since the 0.04 release is in the 0.05
milestone:
http://github.com/bgribble/mfp/issues?q=milestone%3A%22mfp+0.05%22+is%3Aclo…
About MFP
----------------------------------------
MFP is an environment for visually composing computer programs,
with an emphasis on music and real-time audio synthesis and
analysis. It's very much inspired by Miller Puckette's Pure Data
(pd) and Max/MSP, with a bit of LabView and TouchOSC for good
measure. It is targeted at musicians, recording engineers, and
software developers who like the "patching" dataflow metaphor for
coding up audio synthesis, processing, and analysis.
MFP is a completely new code base, written in Python and C, with
a Clutter UI. It has been under development by a solo developer
(me!), as a spare-time project for several years.
Compared to Pure Data, its nearest relative, MFP is superficially
pretty similar but differs in a few key ways:
* MFP uses Python data natively. Any literal data entered in the
UI is parsed by the Python evaluator, and any Python value is a
legitimate "message" on the dataflow network
* MFP provides fairly raw access to Python constructs if desired.
For example, the built-in Python console allows live coding of
Python functions as patch elements at runtime.
* Name resolution and namespacing are addressed more robustly,
with explicit support for lexical scoping
* The UI is largely keyboard-driven, with a modal input system
that feels a bit like vim. The graphical presentation is a
single-window style with layers rather than multiple windows.
* There is fairly deep integration of Open Sound Control (OSC), with
every patch element having an OSC address and the ability to learn
any other desired address.
* MFP has just a fraction of the builtin and addon functionality
provided by PD. It's not up to being a replacement except in
very limited cases!
The code and issue tracker are hosted on GitHub:
https://github.com/bgribble/mfp
You can find the LAC-2013 paper and accompanying screenshots,
some sample patches, and a few other bits of documentation in the
doc directory of the GitHub repo. The README files at the top
level of the source tree contain dependency, build, and
getting-started information.
Thanks,
Bill Gribble <grib(a)billgribble.com>
I'm posting this in a number of places to try and get some idea of ALSA/JACK
usage, so I'd be grateful for responses.
https://www.surveymonkey.com/s/JZVV7K9
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.