Hi all,
in case anyone is interested, I just uploaded my
first song I decided to make publicly available.
It's a very very simple song with only one guitar
with moi singing, all recorded with Ardour and mixed
using TAP-plugins (naturally).
Some more info and the song itself in Ogg Vorbis format
is available here: http://www.hszk.bme.hu/~st444/music/
In case anyone has constructive criticism, I'm
happy to read it, although it is highly unprobable
that I will ever re-record or re-mix it. Anyway,
here it is. Let's hope some of you will like it.
Tom
On 26 March 2005 at 18:54, Scott Helmke <scott(a)scotthelmke.com> wrote:
> I would be surprised if the cheap cable really worked out
It's been working fine, even with all channels active.
> - does the 1010 send audio signals through that cable?
Nothing analog, only digital data traverses the cable.
Cheers....
--
Kevin
Hi,
In my studio situation the two halves of my Delta 1010 are too far
apart for the DB-25 (serial looking) cable to connect them. I found
plain DB-25 extension cable which does a great job. At a local shop
the cable was $11US. The M-Audio website has a similar cable for
about $20US. If you need to get an extension cable, you might want
to try an electronics parts store close to you. Be sure to avoid
modem and serial cables. Get a "strait through" cable instead.
Cheers....
--
Kevin
Hi, I'm having some silly questions, I'm new to the midi world:
I just bought a Boss GT-8 guitar effects processor and I know it supports
downloading patches to your computer. I understand this works over midi by
doing a sysex dump. What I don't understand is: How does the program I use
"know" what kind of data I download? A patch? The system configuration?
Everything? I know it does not need to be able to interpret the contents of
those things but I'm not quite sure how this stuff works at all.
And the other way round: Could I do any harm to my GT-8 (or another midi
device) by uploading wrong data to it? Or will it just give me an error
message and reject the upload?
What programs can I use under linux? I know sysexxer, but I would rather like
to use a command line tool.
As I said, silly questions
On 23/03/05 15:12:34, Ryan Gallagher wrote:
> On Tue, 2005-03-22 at 10:08 -0500, Spencer Russell wrote:
> > Wow, seems like you're having pretty much exactly the same kinds
> > of troubles I've had, right down to the occasional keyboard
> > lockup. Maybe something strange with the via chipset?
>
> Nope, keyboard lockups happen here too. And others have reported the
> same, for me it's when I unplug my ua-25 so it's not card specific.
I am right in thinking the UA-25 used only standard USB Audio drivers? I can see nothing om the kernel tree that looks specific to a UA-25.
Do people find these keyboard lockups occur with a variety of USB sound cards but not with other USB devices? Perhaps people can e-mail me accordingly as it may give a clue as to where that problem lies.
> I also suspected IRQ issues, and digging through kernel-parameters.txt
> brought me this boot option: acpi_irq_balance
I'll try this just in case it makes a difference.
Steve.
Greetings all.
I've recently come into the ownership of s Delta 10/10 and I was
wondering if anyone had been able to get this puppy fully configured. I
currently am able to see incoming signals on the 8 analog channels using
envy24control, but that is about it.
Both aplay and arecord given me their own variation of the "missing file
or directory" error when I try to use them, leading me to check the
/proc/asound/ directory and I found that I only have pcm0p and pcm0c.
This leads me to believe that there is a driver issue going on, but this
is the first crack I've taken at doing any serious work with ALSA so I'm
not quite sure.
I'm currently using kernel 2.6.11 with the Ken Colivas patchset, and I
do have the realtime-lsm module installed and loaded. /proc/asound/cards
shows both my SBLive and the Delta. My .asoundrc and /etc/modules.d/alsa
are posted at the bottom.
Is there a better kernel to use, preferably under the portage tree? (not
an absolute necessity)
Has anyone gotten this card fully functional under Gentoo?
I have a feeling that I'm pretty close, but I'm nearing the limits of
what I can Google without asking.
- Brian Gant
---------- Start .asoundrc ----------
# SBLIVE stuff
pcm.emu10k1 {
type hw
card 0
device 0
}
ctl.emu10k1 {
type hw
card 0
}
# DELTA 10/10 stuff
pcm.ice1712 {
type hw
card 1
device 1
}
ctl.ice1712 {
type hw
card 1
}
# adcdac 1
pcm.ch1in {
type plug
ttable.0.0 1
slave.pcm ice1712
}
# adcdac 2
pcm.ch2in {
type plug
ttable.0.1 1
slave.pcm ice1712
}
#adcdac 3
pcm.ch3in {
type plug
ttable.0.2 1
slave.pcm ice1712
}
# adcdac 4
pcm.ch4in {
type plug
ttable.0.3 1
slave.pcm ice1712
}
# adcdac 5
pcm.ch5in {
type plug
ttable.0.4 1
slave.pcm ice1712
}
# adcdac 6
pcm.ch6in {
type plug
ttable.0.5 1
slave.pcm ice1712
}
#adcdac 7
pcm.ch7in {
type plug
ttable.0.6 1
slave.pcm ice1712
}
# adcdac 8
pcm.ch8in {
type plug
ttable.0.7 1
slave.pcm ice1712
}
#SPDIF channels only
pcm.ice1712_spdif {
type plug
ttable.0.8 1
ttable.1.9 1
slave.pcm ice1712
}
# digital mix
pcm.mon_mix {
type plug
ttable.0.10 1 # digital mix left
ttable.1.11 1 # digital mix right
slave.pcm ice1712
}
# outputs
pcm.multi_send {
type plug
ttable.0.0 1
ttable.0.1 1
ttable.0.4 1
ttable.0.5 1
ttable.0.6 1
ttable.0.7 1
slave.pcm ice1712
}
# all HW outs set to PCM OUT in envy24
pcm.hwout {
type plug
slave.pcm ice1712
}
---------- Start /etc/modules.d/alsa ----------
# ALSA, OSS definitions
alias char-major-116 snd
alias char-major-14 soundcore
options snd cards_limit=2
# SBLive
alias snd-card-0 snd-emu10k1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
# Delta 10/10
alias snd-card-1 snd-ice1712
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-1 snd-seq-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-8 snd-seq-oss
alias sound-service-1-12 snd-pcm-osshree
Well, here's my quick alternative mix. It's not polished, but it
illustrates what I was trying to say before.
http://dis-dot-dat.net/sailor_mixtest.ogg
I've tried to get rid of the muddyness, by altering your organ sound
(taking out a lot of the mid/low end) without removing it completely.
I've also cut back on the stereo separation. This is a personal taste
thing, but I find over-use of stereo a little strange sounding,
especially on headphones. Of course, everyone has a different
defenition of over-use. I like to use the stereo space to give some
separation between sounds without making them sound like they come
from the far edges of the stage.
There's a break in the drums where I thought it needed it, but I
haven't bothered making a nice fill to connect it back up - still,
sounds OK.
And I didn't bother with the echoeyness, even though I like the sound
you had for that.
I think I may have the vocals up too much, but what do you think?
Just something different. It was fun to do. I really do like this
song.
Hope you don't mind what I've done to it.
James
--
"I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb. Thank you."
(By Vance Petree, Virginia Power)
I just got an Echo Indigo IO card. It works (and I like it a lot so
far), but alsamixer's sliders are all mixed up. Left channel over
here, corresponding right channel way over there on the other page,
etc. After I figure out what each one does, can I submit a bug report
somewhere and have them rearranged and labeled better?
HA! Not a patch, but a lawsuit! Finally, Creative gets nailed (well,
kind of) for years of deceptive marketing.
http://www.theinquirer.net/?article=22019
The executive summary is that because Creative blatantly lied about
24/96 support for the Audigy1, if you bought any Audigy1 based sound
card in North or South America, you are entitled to $62 off the next
Creative sound card you buy.
Whatever you do, don't spend it on an Audigy LS! Bwahahahahaha....
Lee
Wolfgang,
> JP, great tutorials, very laid-back -- you're a teacher man.
> The MIDI filtering/output is neat. So is the tap pulse feature.
Good stuff, I'm glad the tutorials are doing their work.
> * Seeing it done in your tutorial I want to get my footswitch into
> action too. It's a simple sustain pedal connected to my midi master
> keyboard and works as that. But Freewheeling doesn't react to it.
> Maybe you're talking about a different kind of footswitch? Can you
> direct me somewhere?
This should be a simple matter. It occurs to me now that I'm using a
non-standard controller # for my switch- thanks for pointing that out. I use
one switch (controller #64) for sustain on piano parts, and another
(controller #67) for grabbing loops.
You can check what controller # your keyboard is transmitting from inside
Freewheeling. Start it up and press the gray enter to display debugging info
to the console. Press and release your footswitch. In the console window you
should see what midi controller and values your MIDI keyboard transmits for
the footswitch.
If you want your sustain (#64) controller to grab loops, change this line in
the config file:
<declare var="VAR_midi_footswitch" type="int" init="67"/>
Change init="67" to init="64".
I think I'll make this change for the next release. It's confusing to talk
about footswitch and use a non-standard number.
> * Freewheeling sometimes doesn't startup. Called from the console
> it would say FreeWheeling 0.5pre3 Brought to you by a
> grant from Mother Earth. which is nice but nothing else happens.
Well, you could look at it as a bug, or you could look at it as a built in
opportunity to reflect on all that the Earth gives us. ;-)
It's a mystery to me. Some people have reported strange pauses on startup.
Here's some test code for you:
Find Fweelin::setup() in src/fweelin_core.cc and replace the start of the
function with:
int Fweelin::setup()
{
char tmp[255];
printf("MAIN: Start 1\n");
// Keep all memory inline
mlockall(MCL_CURRENT | MCL_FUTURE);
printf("MAIN: Start 2\n");
if (!XInitThreads()) {
printf("MAIN: ERROR: FreeWheeling requires threaded Xlib support\n");
return 0;
}
printf("MAIN: Start 3\n");
/* Initialize SDL- this happens here because it is common to video, keys &
config */
// SDL_INIT_NOPARACHUTE
if ( SDL_Init(SDL_INIT_VIDEO | SDL_INIT_EVENTTHREAD) < 0) {
printf("MAIN: ERROR: Can't initialize SDL: %s\n",SDL_GetError());
return 0;
}
atexit(SDL_Quit);
printf("MAIN: Start 4\n");
// Memory manager
mmg = new MemoryManager();
printf("MAIN: Start 5\n");
// Load configuration from .rc file
cfg = new FloConfig(this);
printf("MAIN: Start 6\n");
-- Now you will see a series of messages when you start- this will help me
determine where it's hanging.
> Ctrl-C and calling fweelin again will sooner or later result in
> Freewheeling starting up. This happens *sometimes* and I have no
> clue at all as it seems to happen under different circumstances.
Thanks again for your reports,
-Mercury
