Hello everyone!
Just a quick notice: I'm going to sell my Roland XP-30 for reasons of space
and the good old mammon. Bit I'd first like to keep it "in the family".
If someone is interested, please send me an e-mail off-list and we can talk
shop. The instrument is in good condition, it's mostly been in the studio and
I don't smoke in a studio. :-)
Right, I'll be waiting until thursday, maybe friday. If I haven't heard
anything by then, I'll get it up on ebay.
Warmly yours and sorry for the OT
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
Hi all! I installed Aeolus through the Ubuntu distribution, but of course, I can't use the GUI. So far I can't get any sound from it, but there could be several reasons.
I'm using the text mode, and it appears that it is working, unless its not actually controling the organ. Does anyone know if this version's text mode actually works?
I can't access the MIDI settings as they're in the GUI. Can I modify those setting in the ./stops/aeolus/definition file?
Or do I just need to run a different version for some reason? I'm making the jack connections for MIDI and audio, and I'm sending MIDI currently with VMPK. VMPK seems to be working according to amididump, and its connections show up in jack, so hopefully that's not the problem. Any suggestions would be appreciated. Thanks much.
Kevin
If I rip the same CD on two different occasions, would I be right to expect
the two sets of tracks to have the same md5sum, or is ripping not that
precise?
I've been using rubyripper and have a difference between two attempts on
the same CD, though rubyripper doesn't report any problems, and each chunk
is matched twice for each rip.
The CD drive is fairly new.
- Richard.
--
Richard Kimber
Political Science Resources
http://www.PoliticsResources.net/
On Thu, May 23, 2013 5:04 pm, Janina Sajka wrote:
> Hi, Len:
>
> Len Ovens writes:
>>
>> On Thu, May 23, 2013 10:55 am, Janina Sajka wrote:
>>
>> > In any case, I certainly don't want pulseaudio to have access to all
>> my
>> > devices, just as I don't want jack running on the audio devices I use
>> > for Speakup and for Orca (two separate devices, unfortunately, because
>> > of driver compatibility issues).
>> >
>> > In any case, this is a moderate priority project at the moment for me,
>> > so I do spend time on it as I have time. So far I have come to believe
>> > it would be possible to restrict pulseaudio either via its
>> client.config
>> > or in udev, but I haven't tried any of this yet.
>>
>> Really simple with the GUI. I am not sure from the command line.
>> pavucontrol has a configuration tab with device profiles. Setting a
>> device
>> to off tells PA to leave it alone. It is persistent from boot to boot,
>> so
>> it must be stored in a file somewhere... looks like binary though. In
>> ~/.config/pulse/
>
> On a per user basis?
> That won't quite work for me, because I also need to avoid the part
> where pulseaudio doesn't allow sound access for a root login.
>
> I really want to go at this on a system-wide level, but then it's
> possible I don't understand pa architecture, i.e. perhaps any pa is only
> invoked user by user.
The recommended way of using PA is by session. This allows more options
and I think is more secure. To run system wide, PA has to be started at
boot time. Normally, PA is set up to auto find and grab ports, but the
config files in /etc/pulse have some commented out lines that might give
some ideas on only connecting PA to one audio IF.
I would first look at the online docs available for PA about running it
system wide. Then put on your sysadmin hat and play. There are some man
pages included as well that may help. You are going into places beyond
what I have tried to do. You are likely to find more help on the pulse
audio mailing list than here though.
> Ah, yes. Thanks for pointing these out. Looks like pacmd is the one for
> sourcing profiles. But, where do these come from? There must be a set
> somewhere? Or, is the profile what one creates with pavucontrol?
look in /usr/share/pulseaudio/ and subdirectories.
--
Len Ovens
www.OvenWerks.net
Seems really cool. (stupid?)question - how do i install io from live to my system? also, io web page says that you can't make a live usb with unetbootin. this was the only way that I could make a live usb. maybe i missed something. dl'ing the rt version right now.
thanks
>Hi,
>
>I'm happy to share with you a new beta release of io GNU/Linux.
>
>The live is based on the free operating system Debian (sid)... and includes a
>large collection of preinstalled programs for all uses, especially multimedia
>creation.
...
http://mk.biniou.net/iognulinux.htmlhttps://sourceforge.net/projects/io-gnu-linux
Hi all,
I release a new version of the AVW.lv2 plugins.
A very minor release:
- The LFO Frequency is now represented as a tempo and devider. I find
it much handier when working on a synth (without being connected to
any master tempo source)... And I don't have to calculate from tempo
to Hz when using it in a song :)
- A few stability fixes in the Beat Repeater and Slicer
- A added a small plugin to convert Ingen controls that goes from 0 to
1 to VC (that goes to -1 to 1)
As usual, you can download it from these places:
- http://sourceforge.net/projects/avwlv2/files/avw.lv2-1.0.4.tar.gz/download
- https://github.com/blablack/avw.lv2
By the way, have you guys tried the latest version of Ingen (svn 5108)?
The stability is very good (I have to see it crash yet) and it's very
usable now - I have been using it for my new album and I'm starting to
get some pretty fat bass synths with a mix of avw.lv2, guitarix.lv2
and a few ladspa using NASPRO.
The bass synth in this song was done with Ingen:
https://soundcloud.com/a-violent-whisper/can-i
Aurélien
Hi all. I hope this hasn't already been covered, but I've been searching the internet and can't find answers yet.
I'm running Ubuntu 12.10 which came with PulseAudio. I chose Jack2 as I have a newer system, I believe with multi-processor support, and I understood it might cooperate with PulseAudio better. I use braille and speech for the screen reader, which is currently routed through PulseAudio. And I want to use Jack through the command line rather than through Qjackctl gui. I used to do this on my older Ubuntu system with Jack1, but things have changed quite a bit since then. Jack2, Jackdbus, and module-jackdbus-detect seem to be working. PulseAudio seems to be re-routing. I don't have Jack running at startup, as I always used to start it manually, and so I could re-start it when necessary. I currently start it with "jack_control start". When I do, "jack_lsp" shows jack ports, but my old friend jackctl.py won't show any ports or make connections. Running "jackd" as I used to seems to generate errors about not being able to start the server. I don't have specifics in front of me, but I can come back with them if it helps. I used to use ~/bin/j.ctl to start jack with the appropriate parameters I believe from ~.jackrc, but that looks as if it relies on something like jack.ctl which no longer exists.
So after all the details here, I'm wondering if I should have gone with Jack1 instead, and found some way of doing without PulseAudio, or if my current Jack2 needs to run without Dbus support, and whether I need a newer jackctl.py if one exists? Or are there other things I should be doing? I'm sorry, but I feel just a little lost here. I know just enough to be dangerous, but not quite enough to know how to fix it.
Thanks for any help. I'm sorry to be so long winded, but I thought the details might be necessary to know why I'm doing what I'm doing. Any suggestions would be greatly appreciated. Thank you again very much.
Kevin
Hi,
I've not been active here for quite some time. So, I've tried something
simple to get my toe back in, as I need to distribute MIDI files to some
musician colleagues.
So, I've wired an old Yamaha 49-key keyboard into Fluidsynth using a
Textech MIDI to USB cable, and provided the aconnect command.
I have sound, but it's about 300 ms latent--effectively unusable.
Fluid synth did complain: "Failed to pin the sample data to RAM." Could
that possibly explain this much latency?
I'm loading Fluidsynth for alsa_seq because I don't believe I need the
complexity of jack just yet. But, might jack do better?
Any suggestions most appreciated.
Janina
Len Ovens writes:
>
>
> On Tue, May 21, 2013 11:31 am, Robin Gareus wrote:
> > [message re-arrange to avoid top-posting]
> > On 05/21/2013 04:52 PM, Axax wrote:
> >> On 05/21/2013 09:30 AM, Abhayadev S wrote:
> >>> Hi,
> >>>
> >>> Anybody had tried using the Focusrite Scarllet 8i6 on Ubuntu Studio
> 13.04?
> >>>
> >>> So far it was not supported under ALSA but from 13.04 it seems it is
> been detected and the JACK is able to list out couple of I/Os.
> >>>
> >>> Last day i just booted up a live version of the 13.04 and was bale to
> do couple of i/o routing. Jack lists 8 inputs and 12 outputs. It seems
> the Inputs 1 to 4 (analog mic/line-ins) are listed as Inpiuts 1 to 4
> and 2 SPDIF are 5 and 6. But i am not sure about the 7 and 8. I am
> getting the same SPDIF signal on these inputs too !
> >>> The output 1 to 4 are Monitors output (1&2) and extra outputs (3&4) on
> the backside of the box. And 5&6 seems to be SPDIF outputs. Still have
> 6 more outputs to be listed/clarified.
> >>>
> >>> Just going ahead with further analysis and if anybody out there has
> any thing to add on please do so..
> >>>
> >>> Regards,
> >>> Abhayadev S
> >>> http://sites.google.com/site/abhayadevs
> >>> http://sites.google.com/site/astudioindia
> >>>
> >
> >> Hi,
> >>
> >> I've the same audio card. It's working as you described, but I can't
> figure out hot to change the input mode for the channels 1-2 from MIC
> to LINE/instr!
> >> Anybody have a clue?
>
> Just a quick addition. The below describes how to change the
> line/instrument inputs back and forth. Mic to line is automatic. If you
> plug into the XLR it is mic mode and into the 1/4inch TRS (or TS) it is
> line/instrument mode.
> >>
> >> A.
> >>
> >
> > see
> > https://focusritedevelopmentteam.wordpress.com/2012/04/23/linux-and-focusri…
> >
> > https://github.com/x42/alsa-driver/tree/s18i6 adds full mixer support
> for the 18i6. According to Focusrite the same will also work for the 8i6
> -- but I lost interest in Focusrite devices for various reasons.
> >
> >
> > Short of patching the alsa kernel driver or using another OS to change
> device config, you can use https://github.com/x42/scarlettmixer to
> change the config on GNU/Linux. It's not a ready-to-use app, however:
> >
> > 1) rmmod snd_usb_audio # so that python script can access the device 2)
> change the python script line 31 to detect the 8i6
> > 3) tweak the "example code" line 492..
> > the "line/inst" switch is there as sw_impedance()
> > 4) modprobe snd_usb_audio # ...
> >
> > best,
> > robin
> > _______________________________________________
> > Linux-audio-user mailing list
> > Linux-audio-user(a)lists.linuxaudio.org
> > http://lists.linuxaudio.org/listinfo/linux-audio-user
> >
>
>
> --
> Len Ovens
> www.OvenWerks.net
>
>
>
> --
> Len Ovens
> www.OvenWerks.net
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina(a)rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Protocols & Formats http://www.w3.org/wai/pf
Indie UI http://www.w3.org/WAI/IndieUI/
