Am Freitag, 15. Juli 2005 17.15 schrieb Chris Cannam: > On Friday 15 Jul 2005 15:52, Toni Arnold wrote: > > Currently, I have the famous "no sound at all" problem. Oops, the output part of the problem seems to be difficult to reproduce and not having directly something to do with the rg sequencer. For the recording part see below.
The "Playing simultaneously along with vkeybd works fine." part of the last protocol was with a wrong MIDI file (false channel). But we had something similar with tied notes: rg again sometimes produces MIDI events which crash the interface on the instrument side, and I have no clue what it is. Switching the piano on and off again solves the problem. Is there a way to dump any MIDI byte traffic between rg and the instrument to nail the offending commands down somewhen? > This is with current CVS HEAD, yes? yes, 4-1.2_cvs > Are you running JACK? usually yes, now tried with and without - playback works now again. > Can you uncomment the line > > #define DEBUG_ALSA 1 > > from near the top of sound/AlsaDriver.cpp and rebuild? Then let's look > at playback first: > > -- Ensure the sequencer timer is set to "(auto)" > -- Create a single segment of one bar and put four beats in it, and set > it to repeat > -- Ensure the track for that segment is connected to something you > should be able to hear > -- Hit play, leave for about five seconds, hit stop. > > What I'd like (assuming that makes no sound) is the console output from > the sequencer. Anything done, sound working again for now with Profiler : id = StudioControl::sendQuarterNoteLength - elapsed = 0ms CPU, 0.000017000R real AlsaDriver::setMIDIClockInterval( 0.020833333R) AlsaDriver::stopClocks AudioInstrumentMixer::resetAllPlugins! AlsaDriver::stopClocks: ALSA time now is 0.000000000R AlsaDriver::startClocks AlsaDriver::startClocks: started clocks RosegardenSequencerApp::incrementTransportToken: incrementing to 5 Profiler : id = CompositionModelImpl::computeSegmentOrigin - elapsed = 0ms CPU, 0.000011000R real rosegarden: CompositionModelImpl::computeRepeatMarks : repeatStart = 3840 - repeatEnd = 3843840 Profiler : id = CompositionModelImpl::computeSegmentRect - elapsed = 0ms CPU, 0.004183000R real ------------ Recording is still not working, no segment gets created. Here again a protocol: Start / End of the composition is 1 / 1001 If I press the red record button, the timer goes back as expected and the play/pause button is pressed, too (unlike 1.0 which directly records). If I press the play/pause button to start, the transport starts, but no segment for the recording gets created, and no "Recording time remaining" window pops up as in 1.0. I am never able to "unpress" the record button again with the mouse in the transport window, it remains (at least optically) be stuck in down position. Space-bar punch-in behaves differently: It toggles the record button as expected. But this creates another problem with the 4beat repeating segment above: 1. Position is 0, any button is up. 2. Press play 3. Press space for punch-in record 4. Press Stop -> The Stop button suddenly behaves like the "back to beginning button". 5. Press the Play/Pause-button: no direct effect, but the stop button is working again. Regards Toni ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
