From: Joe Cooper (joe_at_swelltech.com)
Date: 10/16/03 12:51 EDT
Message-ID: <3F8ECC8A.5030708@swelltech.com> From: Joe Cooper <joe@swelltech.com> Subject: Re: [Ardour-users] Lost effects after upgrade Date: Thu, 16 Oct 2003 11:51:22 -0500 Luke Yelavich wrote: > At 10:20 PM 16/10/2003, Joe Cooper wrote: > >> Hi all, >> >> I'm quite new to Ardour, so I might just be doing something wrong >> (that I somehow managed to to right a few days ago), but plugins seem >> to have stopped working after an upgrade to .9b5 and subsequently the >> latest CVS snapshot. >> >> I was able to make effects work in a CVS snapshot from about a week >> ago, and I think I'm doing the same things now, but I don't get any >> effects options. When I right click (and >> [Shift|Ctrl|Alt]-[L|R]-Click) in the black boxes (near input and near >> output), nothing happens. I was thinking this was all I had to do to >> bring up the effects prompt last week when I was just messing about, >> but now that I'm actually trying to learn my way around Ardour, it's >> not cooperating. > > > You do have numlock turned off don't you? Nope, but I do now, and plugins have returned! You're my hero, Luke! Is that documented somewhere? I've banged around for some time now, and originally it took me a week to stumble onto getting the plugins menu to appear, without realizing why it finally started working...and now I've spent another two days and some of the lists time trying to figure it out again. Maybe I'm just a lot slower with 'intuiting' the interface than most people. ;-) >> If it matters, there are no errors when starting up Ardour, and none >> while clicking madly all about the mixer channels looking for plugins. >> Ardour is otherwise seemingly mostly OK (I'm having recording problems >> as well, wherein recording randomly stops midway through takes, but I >> suspect hardware incompatibilities, since I have a Delta66 and a Via >> KT400, which are notorious for causing trouble). I'm able to record >> and playback mostly OK, busses seem to work, tracks seem to playback >> and mix OK, etc. Jack occasionally speaks up about problems, but they >> are unrelated as far as I can tell. > > > Are you using a kernel with low latency and/or pre-empt, and what buffer > size are you running at? I'm using a CCRMA kernel, but it's just the Red Hat plus caps kernel--the 'good' CCRMA kernel oopses on my machine, and I haven't had time to figure out why (I'm not afraid of building myself a custom kernel package--I do it about once a month for my job, anyway--I just haven't had time to do it yet). It has whichever of the latency or pre-empt patches that have appeared in the ac branch, I believe. I'm not getting any xruns, or errors of the overload sort--so I think I'm OK on latency. I'm running with the following: jackd -d alsa -d hw -r 96000 -p 2048 -n 2 Which seems to work semi-great now that I have a decent sound card--before my Delta 66 arrived I was using the motherboard sound card for playing with ardour, and it had to have a very large buffer to prevent xruns. I am getting popping on playback (not on record, as far as I can tell), which I'm guessing is due to the well-known Via KT chipset and Delta card issues. I have dug up a few recommended fixes for that, and will be putting them in place when I reboot my box tonight. I'll let the list know what happens with that. Worst case scenario, I'll replace the motherboard and CPU with something else, and my girlfriend gets a PC upgrade. I don't know if it matters, but I'm mostly using the digital I/O on the card, coming in via S/PDIF from my mic pre-amp. Anyway, the few Jack errors I do see, from a day long session playing with all of my new gear (new mics, delta66, new pre-amp, etc.): subgraph starting at ardour timed out (subgraph_wait_fd=9, status = 1091114516, state = Triggered) client ardour error: awake_at = 472054386405 state = 2 timed_out = 0 subgraph starting at ardour timed out (subgraph_wait_fd=12, status = 1091114516, state = Finished) client pure_data_0 error: awake_at = 639215331277 state = 2 timed_out = -1 subgraph starting at ardour timed out (subgraph_wait_fd=12, status = 1091114516, state = Finished) subgraph starting at ardour timed out (subgraph_wait_fd=12, status = 1091114516, state = Finished) These don't seem to be directly related to anything in particular that I'm doing in Ardour, but maybe I just didn't notice when the error occurred. The most annoying thing Ardour is doing at this point (aside from the pops, which I'll blame squarely on the hardware) is stopping recording randomly without any error or messages about why. It just stops, as though I had clicked the stop transport control. Weird. Thanks for your quick response, Luke. Now I can have some fun playing with silly effects, and tonight I'll see about getting those pops vanished. -- Joe Cooper <joe@swelltech.com> Web caching appliances and support. http://www.swelltech.com ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Ardour-users mailing list Ardour-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ardour-users
This archive was generated by hypermail 2.1.7 : 10/16/03 12:55 EDT