View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000965 | ardour | bugs | public | 2005-04-20 10:12 | 2008-11-20 23:42 |
| Reporter | litlnemo | Assigned To | paul | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0000965: ardour-beta29 unusable in my debian testing | ||||
| Description | I installed first the 686 version and froze my system when playing and syncronizing with hydrogen. (I've got a P4 with P4P800 Mother Board so I supposed to be 686 compliant). Then I tried the normal version and tried to play a previously recorded session. I saw that "waveforms" where redrawed in real time in a strange form and I also noticed I wasn't even able to play the whole song without receiving from ardour that he had to shutdown because he lost connection with jack. very strange. I am the only one having these problems or you didn't test ardour before releasing this new beta? I have downgraded my ardour to keep on working... | ||||
| Tags | No tags attached. | ||||
|
|
I'm just realising now that my words could be misunderstood.. "or you didn't test ardour before releasing this new beta?" wasn't supposed to be a troll I wanted to suggest that you could define a chain of 2 or 3 testers to first check that the new releases won't cause lose of data or block people from working in some systems (maybe you could check with 2 persons from debian, gentoo, fedora, mandrake and some other popular distro?). It would be just a way to make "beta-tester"'s work progessively less dangerous and have more bug reports from the comunity. For example, maybe another person will update to beta29 and have the same problems than me. Having in mind that you want to release in a few days the 0.99, it might help to give more confidence to beta-testers. Cheers MarC (I could do it for debian testing) |
|
|
Hi! :) I also have big problems with Ardour on a Debian Testing. This, however, was beta28. At first Ardour started playing fine, and soon it consumed all CPU and hung the whole computer. The same version (?) worked great earlier. I got the beta29 from the Ardour page and compiled it. (Yes, scons is very nice.) Now Ardour only outputs static. :( I also changed the CPU and bus speed recently, but this should not be related? (I tried Jack both in duplex and in playback only-mode.) I got a crash too, when messing around with getting sound. Too bad I threw away the core-file. Are the files backtraceable even though I didn't disable optimization explicitly? Any clues? Thank you as usual! MiK |
|
|
Some clarifications to the previous: The processor upgrade was 400 MHz celeron (clocked to 500) -> 600 MHz P3, the bus speed change was 66 (?) MHz -> 100 MHz. Jack seems to work fine with other applications, e.g. Hydrogen. Further testing reveals that in Ardour, as well as in Hydrogen, the noisy output was caused by the TAP Equalizer. Nice, I use it on almost every track. :( After turning this effect off, Ardour played nicely. So I guess this is not really an Ardour issue? Thanks, Mikael |
|
|
I noticed that there is no problem even if the plugins are inserted, as long as they are bypassed. Activating one of them resulted in good performance during play, but stopping play resulted in load going up above twenty at once. (Without top showing anything interesting.) I temporarily resolved the situation by compiling tap-plugins 0.7.0 from source. Everything seems to work fine now. I don't quite understand this - there seems to be a problem with the debian package, but tap-plugins_0.7.0-1_i386.deb is dated 5th of March and I have performed successful mixing on the 10th of April? I'll notify the packager. Ps. Already found info about dbgging core files. Sorry for asking without checking the docs first. Thanks! MiK |
|
|
see notes for history. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-04-20 10:12 | litlnemo | New Issue | |
| 2005-04-20 10:52 | litlnemo | Note Added: 0002180 | |
| 2005-04-26 16:58 | alcarola | Note Added: 0002184 | |
| 2005-04-26 17:52 | alcarola | Note Added: 0002185 | |
| 2005-04-26 20:47 | alcarola | Note Added: 0002186 | |
| 2005-05-04 10:40 | paul | Status | new => resolved |
| 2005-05-04 10:40 | paul | Resolution | open => no change required |
| 2005-05-04 10:40 | paul | Assigned To | => paul |
| 2005-05-04 10:40 | paul | Note Added: 0002198 | |
| 2008-11-20 23:42 | seablade | Status | resolved => closed |
