On Tue, 2010-12-14 at 21:50 -0800, Jonathan Wilkes wrote:
> For example-- right-click on the top left-hand corner of cnv in run mode (since you can't select anything in run mode, this will ensure
> it's not selected). Then choose "Properties".
>
> Now when I click "Ok" under these circumstances I get the segfault.
>
> -Jonathan
Got it and fixed it. Will be uploading it shortly.
Many thanks for the report!
Best wishes,
Ico
Can't reproduce over here. Are you running different libs and are they
precompiled for l2ork?
Also, after you've right-clicked you said cnv is not selected. At what
point did you deselect it in the first place?
Ico
On Tue, 2010-12-14 at 19:35 -0800, Jonathan Wilkes wrote:
> segfault:
>
> 1. New patch.
> 2. Create [cnv].
> 3. Save as test.pd
> 4. Right-click [cnv] and choose "Properties".
> 5. Click "Ok".
>
> Crash.
> (Hardy.)
> -Jonathan
>
> --- On Tue, 12/14/10, Ivica Ico Bukvic <ico(a)vt.edu> wrote:
>
> > From: Ivica Ico Bukvic <ico(a)vt.edu>
> > Subject: [PD] L2Ork Pd update now available
> > To: pd-list(a)iem.at, l2ork-dev(a)disis.music.vt.edu, lau(a)lists.linuxaudio.org, piksel(a)piksel.no
> > Date: Tuesday, December 14, 2010, 6:28 PM
> > Apologies for cross-posting.
> >
> > It appears a few more bugs snuck into the stable release.
> > At the same
> > time I felt like the rest of the iemgui objects could
> > really benefit
> > from the resizing via gui, hence another release.
> >
> > 20101214 Changelog:
> > *implemented resizable options for all iemgui objects (some
> > require
> > different behavior than others (e.g. number2 resizes
> > horizontally based
> > on the number of characters, while vertical resize also
> > adjusts font
> > size as well as gui triangle preceding characters, thus
> > resulting in
> > changes in width as well as height--consequently the target
> > size tries
> > to be as close to the mouse cursor as possible while
> > altering width,
> > height, font size and number of characters visible)
> > *changed the whole project naming scheme to reflect
> > "L2Orkified" version
> > (pdextended becomes pd-l2ork, install dir is
> > /usr/local/lib/pd-l2ork,
> > uses default.pdl2ork config file, reflects different
> > version)
> > *changed appearance and updated content of the about.pd
> > patch
> > *fixed regression where help files for core objects were
> > erroneously
> > replaced by incorrect pddp documentation
> > *synced backport of the new browser and adjusted appearance
> > to match the
> > theme
> > *fixed bug where pddplink failed to open related files
> > *fixed resizable canvas so that it updates scrollbars after
> > resizing,
> > dirties the canvas, and properly relocates scale handle
> > when moved
> >
> > As always, comments/feedback are most appreciated.
> >
> > http://l2ork.music.vt.edu/main/?page_id=56
> >
> > Best wishes,
> >
> > Ico
> >
> >
> > _______________________________________________
> > Pd-list(a)iem.at
> > mailing list
> > UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
> >
>
>
>
Hmmm, just recorded a track in Rosegarden 1.70 using vkeybd. It recorded
durations just fine, complete with rests. Don't have RG10.x here to
checked but I'd expect it to work the same way.
Small, inexpensive (US$49) MIDI keyboards are around:
http://www.jr.com/korg/pe/KRG_NANOKEYB/
Peter Knaggs wrote:
> Hi Beh,
>
> I recently started learning Rosegarden myself, and I found that
> using the "Notation Editor": starting with a new project, middle-click
> and drag to create a "segment" of the desired length (e.g. a few bars
> if your song is short, or more if it's long) then click on the new (yellowish)
> segment and press "n" (lowercase N, shortcut for the notation editor, or
> you can right click and say "open in Notation Editor"). There, you'll see on
> the left-hand-side of the page you can choose the duration of your note.
> Then you select the "pencil" tool and click it somewhere to "record" the note.
> Rosegarden will automatically show the "rests" remaining in the bar. I'm not
> sure how to insert additional rests in between notes, as I haven't needed to
> do that sort of thing yet.
>
> If you're intending to record "live" input from a computer keyboard, I don't
> think that's possible. The normal way MIDI note duration is provided is by
> a MIDI controller keyboard performing a timing operation, then encoding
> that info into the midi stream along with the note pitch and velocity info.
> A computer keyboard doesn't have hardware to determine the timing and velocity
> of your key pressed. I guess perhaps somebody somewhere might have written
> a MIDI simulator "driver" for ordinary computer keyboards, but I'm not aware
> of one for linux. It would be fun though.
>
> Still, if you can get a real MIDI keyboard, it'll be preferable. You don't need
> anything expensive, e.g. I'm using an old Kurzweil MIDIboard built back in
> 1987 and it still works, pretty cheap.
>
> Cheers,
> Peter.
>
>
> On Tue, Dec 14, 2010 at 9:50 AM, beh estelah <behestelah(a)yahoo.com> wrote:
>> Hello
>>
>> I'm trying to learn Rosegarden.
>> I do not have an external midi keyboard.
>> When I use the computer keyboard to play music, Rosegarden does register the
>> notes, however it does not register the duration of notes and the rests.
>> Is there any way to register the duration of notes and rests?
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
On 10-12-14 02:38 PM, ailo wrote:
> On 12/14/2010 08:06 PM, Alessio Igor Bogani wrote:
>> The -lowlatency 2.6.37-8.21~ppa1 kernel have RT_GROUP_SCHED enabled.
>> Instead the 2.6.37-9.22~ppa1 one's have RT_GROUP_SCHED disabled.
>>
>> Anyone could test those?
>>
>> Ciao,
>> Alessio
>>
>
> On Natty, 2.6.37-9.22~ppa1, Virtualbox
>
> ...
I confirm 2.6.37-9.22~ppa1 from abogani PPA (RT_GROUP_SCHED disabled)
works fine.
I will leave the decision to Alessio (or somebody else from the kernel
team) to close or not
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/690010 , since a
proper solution implementing cgroups management may be preferable and
implementable.
Alessio, thanks for the very quick response, now, back to actually
testing this kernel :)
Bye,
Ronan Jouchet
Hello all,
This is to give an update on the qmidiarp development status.
Since the last discussions here there are mainly the following new
features:
Arps:
o There are now three trigger modes selectable from a new combobox:
1) No trigger: the original continuous mode
2) Kbd Restart: the arp will restart its loop on every stakato note
change, i.e. when the previous note is released before pressing a new key.
3) Kbd Trigger: the arp will restart and be triggered by the pressed note.
o The latency should be 2 ticks now, so around 10 milliseconds, with which
I haven't found lost notes so far even with four arps plus lfo running in parallel.
o The arp patterns (along many other controls) can be changed by a
midi-learnable controller, on the fly.
As it seems the alsamodular mailing lists are not much followed anymore, so I will need some support to convince my own team to release it or setup a new dedicated project page. So please test, bash it, critique it, praise it.
Installation is:
cvs -z3 -d:pserver:anonymous@alsamodular.cvs.sourceforge.net:/cvsroot/alsamodular co -P qmidiarp
autoreconf -i
make
sudo make install
Have fun
Frank
The resume of changes since 0.0.2 is as follows.
New Features
o Arpeggio pattern preset infrastructure
o Synchronized MIDI LFO modules added
LFOs have calculated and drawable waveforms, selectable frequency,
amplitude, offset, time resolution and length
o Synchronized step sequencer modules added
Step sequencer can be transposed and velocity-modulated by received
notes, sequence can be drawn on the fly
o Pianoroll-type display of arp patterns and cursor line
o Envelope function for chord arpeggios with high polyphony
o Latch mode or Footswitch for holding notes in arpeggio buffer
o Keyboard-triggered or -restarted arpeggiator mode
o Input note delay strongly reduced making QMidiArp suitable for live
play
o MIDI-learnable control of many live-relevant functions
o MIDI realtime clock slave synchronization
o JACK transport client synchronization
o Event log entries are color-coded, optional MIDI Clock event display
o Re-designed graphical user interface: all modules and dialogs
are dockable floatable windows, main and file icon toolbars added
o New .qmidiarprc file containing GUI settings, user arp patterns and
last file path
o Save and SaveAs functions with modification monitoring
o All relevant session parameters stored in new .qmax XML session file
o Manual pages in English, French and German
o Handler for SIGINT added to handle unsaved or changed files more
carefully at program termination.
o Handler for SIGUSR1 added to provide support for LADISH level 1.
o Separate threads for ALSA Sequencer Queue handler and arpeggio engine
General Changes
o Port form Qt3 to Qt4 library.
o MIDI Channels and ALSA port id's displayed from 1...16
o On-the-fly tempo changes are disabled
Apologies for cross-posting.
It appears a few more bugs snuck into the stable release. At the same
time I felt like the rest of the iemgui objects could really benefit
from the resizing via gui, hence another release.
20101214 Changelog:
*implemented resizable options for all iemgui objects (some require
different behavior than others (e.g. number2 resizes horizontally based
on the number of characters, while vertical resize also adjusts font
size as well as gui triangle preceding characters, thus resulting in
changes in width as well as height--consequently the target size tries
to be as close to the mouse cursor as possible while altering width,
height, font size and number of characters visible)
*changed the whole project naming scheme to reflect "L2Orkified" version
(pdextended becomes pd-l2ork, install dir is /usr/local/lib/pd-l2ork,
uses default.pdl2ork config file, reflects different version)
*changed appearance and updated content of the about.pd patch
*fixed regression where help files for core objects were erroneously
replaced by incorrect pddp documentation
*synced backport of the new browser and adjusted appearance to match the
theme
*fixed bug where pddplink failed to open related files
*fixed resizable canvas so that it updates scrollbars after resizing,
dirties the canvas, and properly relocates scale handle when moved
As always, comments/feedback are most appreciated.
http://l2ork.music.vt.edu/main/?page_id=56
Best wishes,
Ico
Hi,
I have an oddity on Ubuntu Lucid.
Installing libboost1.40-dev, default kernel, no problemo.
Installing libboost1.40-dev, RT kernel, install (unpacking/ processing)
takes minuts!
I have this oddity with another package, but most packages install normal.
$ uname -a
Linux ubuntu 2.6.33-29-realtime #1-Ubuntu SMP PREEMPT RT Wed Aug 4
20:14:20 UTC 2010 i686 GNU/Linux
from: https://launchpad.net/~abogani/+archive/ppa/
$ apt-cache policy libboost1.40-dev
libboost1.40-dev:
Installed: 1.40.0-4ubuntu4
Candidate: 1.40.0-4ubuntu4
Version table:
*** 1.40.0-4ubuntu4 0
500 http://nl.archive.ubuntu.com/ubuntu/ lucid/main Packages
100 /var/lib/dpkg/status
(maybe not interesting, but iotop says: CONFIG_TASK_DELAY_ACCT not
enabled in kernel, cannot determine SWAPIN and IO %)
Regards,
\r
Hey,
Can't seem to start jackd in realtime as user on ubuntu studio. It
does start as root, but that's hardly a consolation (unless I run all
audio software as root, which would be kinda daft IMO)
@audio - rtprio 99
@audio - nice -10
@audio - memlock unlimited
have been added to /etc/security/limits.conf
Nevertheless, starting it as user just doesn't seem to work, and I
just can't figure out why. I've googled the issue, and everybody seems
to agree that modifying limits.conf in the above manner should solve
the problem - yet this is what I get:
mick@kaizoku:~$ jackd -R -P89 -dalsa -dhw:0 -r48000 -p256 -n3 -S &
[1] 3092
mick@kaizoku:~$ no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
cannot use real-time scheduling (FIFO at priority 10) [for thread
-1217255744, from thread -1217255744] (1: Operation not permitted)
cannot create engine
Any ideas?
Mick.
I have a preload demon starting on boot. does that collide with jack. I mean it uses an amount of memory. does used memory make memory-access slow or anything like that? or doesn't used memory affect jack at all (as long as you have enough free memory)?