Robert Keller wrote:
>
> On Jun 11, 2009, at 5:19 AM, Grammostola Rosea wrote:
>
>> lasconic wrote:
>>> I took some time yesterday night to take a look to improvisor code and
>>> estimate the cost of adding musicXML export. Import is indeed more
>>> complicated.
>>> I downloaded the code of improvisor 3.39. It's the last and only code
>>> available. Improvisor inner model is a little bit different than
>>> musicXML
>>> one. Common practice in musicXML is to don't "time" the chords and
>>> put them
>>> in the middle of notes. At least, this is my experience with finale
>>> musicXML
>>> export features. I managed to make a quick and dirty prototype to
>>> export a simple melody (no
>>> tuplet) and chord root and bass (no extension yet). Chords are in
>>> between
>>> notes but lily+musicML2ly shoud be able to deal with it.
>>> Unfortunately, 3.39
>>> is an old version, and according to Bob Keller the code base changed
>>> a lot
>>> but it's not public yet. With some more voices, perhaps we can
>>> convince Bob Keller and his team to
>>> open up the repository to the public. After all, improvisor is a
>>> fine piece
>>> of software which can benefit from open development, moreover if
>>> time and
>>> resources are an issue.
>>>
>>> Lasconic
>>>
>>>
>> Thanks man. I'll forward this to Bob Keller too.
>> I think he mentioned in a message that he is willing to give
>> developers svn access to the recent code.
>>
>> Bob, could you comment on this?
>>
>> Kind regards,
>>
>> \r
>>
>
> I'll be looking toward moving Impro-Visor to a public repository, as
> soon as I stabilize the current version, which I hope will be before
> the end of June.
Ah that's good news. Thanks.
> Is SourceForge the best bet?
>
>
I think SourceForge is good, but others might think different (I have
little experience with it myself, others?)
Let us know when it's up there.
Kind regards
\r
lasconic wrote:
> I took some time yesterday night to take a look to improvisor code and
> estimate the cost of adding musicXML export. Import is indeed more
> complicated.
> I downloaded the code of improvisor 3.39. It's the last and only code
> available. Improvisor inner model is a little bit different than musicXML
> one. Common practice in musicXML is to don't "time" the chords and put them
> in the middle of notes. At least, this is my experience with finale musicXML
> export features.
> I managed to make a quick and dirty prototype to export a simple melody (no
> tuplet) and chord root and bass (no extension yet). Chords are in between
> notes but lily+musicML2ly shoud be able to deal with it. Unfortunately, 3.39
> is an old version, and according to Bob Keller the code base changed a lot
> but it's not public yet.
> With some more voices, perhaps we can convince Bob Keller and his team to
> open up the repository to the public. After all, improvisor is a fine piece
> of software which can benefit from open development, moreover if time and
> resources are an issue.
>
> Lasconic
>
>
Thanks man. I'll forward this to Bob Keller too.
I think he mentioned in a message that he is willing to give developers
svn access to the recent code.
Bob, could you comment on this?
Kind regards,
\r
Robert Keller wrote:
>
> On Jun 10, 2009, at 2:09 PM, Grammostola Rosea wrote:
>
>> but Impro-visor doesn't have musicXML support right? Is it possible
>> to add that?
>
> Correct, it doesn't. It is possible to add musicXML output. Anything
> is possible. However, I have too much else to do at this point in time
> to give that a high priority.
>
> Input would be harder, because Impro-Visor has only a single melody
> line, but musicXML, I'm pretty sure, can specify polyphony, so there
> would be the issue of how to interpret that. Also, I'm not sure how
> musicXML deals with chord symbols, but that could be a second issue.
>
> Regards,
>
> Bob
>
> Robert Keller
> Csilla & Walt Foley Professor
> Computer Science
> Harvey Mudd College
>
>
Thanks again.
I understand, time is scares these days...
Maybe other Lilypond devs or people who can work on adding Musicxml
support could help you a bit. I will Cc this mail to the Lilypond users
mailinglist (you have to check that app!) and the Linux dev list.
We will see. If you have questions, requests or announcements, just let
us know. We (Lilypond and Linux users) like to stay in tune with
Impro-Visor.
Kind regards,
\r
Ps. If people have problems to get sound working on GNU/Linux you can
point them to:
http://linuxmusicians.com/viewtopic.php?f=4&t=860
This is an very interesting application, and it is released as GPL software.
The only drawback on GNU/Linux is that sound is not working very well,
at least in my experience:
http://linuxmusicians.com/viewtopic.php?f=4&t=860
I dunno if there is a way to get better sound out of java applications.
Maybe some devs can help this application with ALSA and/or Jack support?
Kind regards,
\r
I removed some bugs that came up till now and released version 0.3 of
JackMixDesk formerly known as jackminimix.
Get it from http://sourceforge.net/projects/jackmixdesk/
Jackmixdesk is a client/server mixer application with a user defined
number of channels, pre and post fader sends. It has LASH support an OSC
control interface and a XML config file. There is also a gui made with
GTK+. It uses less resources than it's ancestor jackminimix.
I'll soon start further development.
Regards and please report me something
Uli
PS Could someone from the proaudio list please make an ebuild? Thanks!
Greetings;
I'm told that matlab can do this, but this is a one time deal on a home made
instrument. I've not that sort of money to spend.
Do we have anything for linux that can take a microphone input to an audio
card, do an FFT on what it picks up that is accurate to small parts of a hertz
at frequencies in the 1st two octaves of a keyboard?
Thanks all.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
<https://www.nrahq.org/nrabonus/accept-membership.asp>
* knghtbrd does the ET thing
<knghtbrd> anybody got a speak-n-spell?
Ok I have taken the advise to use gstreamer when working with encoded
streams (I read a bit and understood it fits my case better)
I still left with offloading the PCM stream - this is a mandatory
request from me to do it under ALSA.
I have looked at LADSPA interface and saw there are for port types:
#define LADSPA_IS_PORT_INPUT(x) ((x) & LADSPA_PORT_INPUT)
#define LADSPA_IS_PORT_OUTPUT(x) ((x) & LADSPA_PORT_OUTPUT)
#define LADSPA_IS_PORT_CONTROL(x) ((x) & LADSPA_PORT_CONTROL)
#define LADSPA_IS_PORT_AUDIO(x) ((x) & LADSPA_PORT_AUDIO)
If I declare my plugin as control only will I get all the information
such as rate, format, etc... like a driver and will the frames will be
passed to the driver directly?
Ziv Haziz
SW Team Leader
Tel. +972-9-9529-776
Mobile +972-54-5225-398
ziv.haziz(a)dspg.com
www.dspg.com <http://www.dspg.com>
______________________________________________________________________
DSP Group, Inc. automatically scans all emails and attachments using MessageLabs Email Security System.
_____________________________________________________________________
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Everyone,
Just a quick note to advise there are new versions of the Invada Studio Plugins available. These releases are mainly a bugfix releases.
LADSPA (version 0.3.1)
* Added karmic package
* Fixed a bug where compressor release couldn't go past 2s.
* Eliminate DC offset from Tube.
* Updated ER reflection process in line with LV2 version.
More information & tarball download: http://www.invadarecords.com/Downloads.php?ID=00000263
Ubuntu packages: https://launchpad.net/~invada/+archive/ppa
LV2 (version 1.0.1)
* Fixed multiple errors in RDF files.
* Fixed missing linker libs in makefile.
* Improved host compatibility.
* Disabled tool-tips while widgets are active..
More information & tarball download: http://www.invadarecords.com/Downloads.php?ID=00000264
Ubuntu packages: https://launchpad.net/~invada/+archive/ppa
Regards,
Fraser
https://launchpad.net/invada-studio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFKKimQNZroiEh4erwRAi9jAJ4gphnlQurfpVbyP9TmRSSxE1gbiwCeIBox
i78wj63ZqA8NqQhwvHLzrbA=
=a7zP
-----END PGP SIGNATURE-----
Howdy!
Greatest thanks goes to Mathias Krause aka gizzmo, who contributed with
the fundamental code to the new MIDI controller mapping functionality
that now widens the Qtractor horizon with regard from generic control
surfaces. Being the Behringer BCF2000 [1] a notable example, control
feedback is fully supported so that those fancy motorized faders, knobs
and lights, actually reflect the whole mixing and editing session state.
Some pre-made files are here provided for your conveniency:
"bcx2000.qtc" [2] is to import into Qtractor (View/Controllers...) and a
couple of presets goes into your BCF2000, "Qtractor_Mixer_1-8.syx" [3]
and "Qtractor_Mixer_9-16.syx" [4], respectively for the first and second
set of eight channel/track strips.
Ah, the previous hardwired support for the JLCooper-like controls,
provided by the Tascam US-224 and US-428 (via us428control), is now
optional. You can have it back by just adding this file, "usx2y.qtc"
[5], to the controllers map.
That's it:
Qtractor 0.4.2 (flaunty demoness) is out!
Release highlights:
* MIDI controller mapping (mixer) (NEW)
* Audio/MIDI multi-clip merge (NEW)
* Multi-clip selection export (NEW)
* Improved snap precision on drag/moving clips (FIXED)
* and some other asorted fixes (see change-log;)
Description:
Qtractor is an audio/MIDI multi-track sequencer application, written in
C++ on top of Qt Software's Qt4 framework, having JACK and ALSA as its
main infrastructures and Linux as native and exclusive platform.
Specially suited to the lone-wolf composer, arranger and (re)creative
music-maker personal home-studio, it still hopes to evolve as a fairly
featured desktop audio/MIDI workstation or at least, a prototypical part
of it ;)
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
- source tarball
http://downloads.sourceforge.net/qtractor/qtractor-0.4.2.tar.gz
- source package (openSUSE 11.1)
http://downloads.sourceforge.net/qtractor/qtractor-0.4.2-1.rncbc.suse111.sr…
- binary package (openSUSE 11.1)
http://downloads.sourceforge.net/qtractor/qtractor-0.4.2-1.rncbc.suse111.i5…http://downloads.sourceforge.net/qtractor/qtractor-0.4.2-1.rncbc.suse111.x8…
- binary package (Ubuntu 8.04 LTS)
http://downloads.sourceforge.net/qtractor/qtractor_0.4.2-1.rncbc.ubuntu804.…
- user manual (outdated)
http://downloads.sourceforge.net/qtractor/qtractor-0.3.0-user-manual.pdf
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.
Features:
- Multi-track audio and MIDI sequencing and recording.
- Developed on pure Qt4 C++ application framework (no Qt3 nor KDE
dependencies).
- Uses JACK for audio and ALSA sequencer for MIDI as multimedia
infrastructures.
- Traditional multi-track tape recorder control paradigm.
- Audio file formats support: OGG (via libvorbis), MP3 (via libmad,
playback only), WAV, FLAC, AIFF and many, many more (via linsndfile).
- Standard MIDI files support (SMF format 0 and 1).
- Non-destructive, non-linear editing.
- Unlimited number of tracks per session/project.
- Unlimited number of overlapping clips per track.
- XML encoded session/project description file.
- Point-and-click, multi-select, drag-and-drop interaction (drag, move,
drop, cut, copy, paste, delete, split, merge)
- Unlimited undo/redo.
- Built-in mixer and monitor controls.
- Built-in connection patchbay control and persistence (a-la QjackCtl).
- LADSPA, DSSI and native VST plug-ins support.
- Unlimited number of plug-ins per track or bus.
- Plug-in presets, programs and chunk/configurations support.
- Audio/MIDI clip fade-in/out (linear, quadratic, cubic).
- Audio/MIDI clip gain/volume, normalize and export.
- Audio clip time-stretching (WSOLA-like or via librubberband),
pitch-shifting (also via librubberband) and seamless sample-rate
conversion (via libsamplerate).
- Audio/MIDI track export (mix-down, merge).
- Audio/MIDI metronome bar/beat clicks.
- Unlimited tempo/time-signature map.
- MIDI clip editor (matrix/piano roll).
- MIDI instrument definitions (a-la Cakewalk(tm)).
- MIDI controller mapping (mixer).
- JACK transport sync master.
- MMC control surface enabled.
- MIDI Song Position cueuing support.
- Configurable keyboard shortcuts.
Change-log:
- The MIDI clip editor (piano-roll/matrix editor), the main track view
as well, have been subject to usability fixing, the most notable avoids
clearing current selection as much as possible when updating view
contents (eg. changing zoom levels does not reset current selection
anymore).
- MIDI tracks channel bank/program and controller stuff are now only
issued when the respective bus connections have changed, seldom on every
playback start.
- MIDI controller mapping infrastructure, with file based configuration
management (see View/Controllers...), is now in place, following an
original contribution from gizzmo aka Mathias Krause.
- Plugin chain buffer reset on playback start/stop is not guarded by a
momentary plugin de/activation anymore.
- Clip export may now be applied to multiple clips, sharing common
refactored code and same semantics as merging of current selected clips.
- Improved, may be just fixed yet again, audio track export
synchronization and reliability.
- Clip merge is now featured both for audio and MIDI tracks (see
Edit/Clip/Merge...).
- Improved, or better said, fixed (again) the precision of multi-clip
final positioning as result of drag/move and paste operations in main
track view (as in bug #2741611).
- MIDI track program number is now listed in 1-128 range, in an attempt
to be consistent with corresponding MIDI track dialog drop-down list.
- MIDI editor snap grid lines get slight different color then regular
beat divisions.
- Reset local tempo map cursor on newer MIDI file imports in a tentative
to fix incidental but random crashes.
URLs:
[1] http://www.behringer.com/EN/Products/BCF2000.aspx
[2] http://www.rncbc.org/datahub/bcx2000.qtc
[3] http://www.rncbc.org/datahub/Qtractor_Mixer_1-8.syx
[4] http://www.rncbc.org/datahub/Qtractor_Mixer_9-16.syx
[5] http://www.rncbc.org/datahub/usx2y.qtc
Cheers && Enjoy!
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Hi All,
i'm seeking an advise on the preferred way to support a dedicated DSP
chip under ALSA.
The system is an embedded system constructed on a dual core chip - one
core is ARM vanlia and the other is a dedicated DSP core.
The DSP core is capable of both playing both encoded streams (mp3, wma,
various voice coders) and of course PCM streams.
the codec (a2d, d2a) are connected to DSP.
I looking for an elegant design to hide the DSP under the ALSA sysem and
I have several ideas and would like to get your advise:
1. use LADSPA to make the DSP look as a plug-in for both control
and data - what I don't know is if LADSPA forces me to return data to
the ALSA for sending it to the kernel drivers
2. use the LADSPA to make the DSP control only and make another
kernel driver for the audio data pass - is it possible? There can be a
sync problem between the commands and the time the data will arrive?
Will this support JACKD ?
I'm open to other suggestions as well,
Thanks in advance
Ziv
______________________________________________________________________
DSP Group, Inc. automatically scans all emails and attachments using MessageLabs Email Security System.
_____________________________________________________________________
