[Rosegarden-bugs] [ rosegarden-Bugs-933041 ] playback pointer wonkiness when stopping recording

[SourceForge.net <no...@so...>]

Bugs item #933041, was opened at 2004-04-11 01:38
Message generated for change (Comment added) made by dmmcintyr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104932&aid=933041&group_id=4932

Category: sequencer
Group: None
Status: Open
Resolution: None
Priority: 6
Submitted By: D. Michael McIntyre (dmmcintyr)
Assigned to: Nobody/Anonymous (nobody)
>Summary: playback pointer wonkiness when stopping recording

Initial Comment:
New doc, point track 1 to Jack #1, hit record. 
 
Record a bit.  Hit the stop button on the DIALOG BOX. 
 
The playback pointer is glued in place until you hit stop 
on the Transport. 
 
I haven't looked, but I'll bet the sequencer is some 
confused "between states" condition at that point.  

----------------------------------------------------------------------

>Comment By: D. Michael McIntyre (dmmcintyr)
Date: 2004-09-29 19:27

Message:
Logged In: YES 
user_id=663564

This is some issue with the countdown dialog, and now it affects all 
recording.  The stop button on the thing should be avoided. 
 
Since the countdown dialog for MIDI will disappear shortly after 1.0 
releases, this will eventually revert to just being an audio issue. 

----------------------------------------------------------------------

Comment By: D. Michael McIntyre (dmmcintyr)
Date: 2004-07-22 16:00

Message:
Logged In: YES 
user_id=663564

I don't have the skill to debug an application this large and complex in 
Linux, and I think this is going to take real debugging.  The debug stream 
messages aren't revealing whatever the difference is, but there must 
obviously be some difference in variable states between one version of 
stopping the transport and the other.  I can't figure it out, and it's 
probably no longer productive for me to continue wasting time with it. 
 
I rate it's annoying enough to make us look bad, and so I think it really 
could stand fixing before 1.0.  Sorry I couldn't fix it.  :( 

----------------------------------------------------------------------

Comment By: D. Michael McIntyre (dmmcintyr)
Date: 2004-07-11 17:56

Message:
Logged In: YES 
user_id=663564

I'm still poking at it, but this is a lot more sneaky and subtle than I had 
hoped.  I can't figure out what the difference is between the dialog's stop 
button and using stop on the Transport.  Nothing obvious at all.  I'm not 
sure where this is buried. 
 
But nobody else has fixed it in eons, so I'll keep rooting around.  I might 
learn something in the process if nothing else.  But...  I'm going to leave it 
for the moment and go dig into the Pitch problem.  I have a more realistic 
hope of fixing that sooner. 

----------------------------------------------------------------------

Comment By: D. Michael McIntyre (dmmcintyr)
Date: 2004-07-11 02:10

Message:
Logged In: YES 
user_id=663564

This also applies to MIDI recording now.  It's irritating as hell.  I'm going to 
try to chase it down. 

----------------------------------------------------------------------

Comment By: D. Michael McIntyre (dmmcintyr)
Date: 2004-06-05 06:14

Message:
Logged In: YES 
user_id=663564

I've managed to get the transport glued in place in this same fashion in 
other ways too, unrelated to audio, and I managed to save a file in a state 
such that I either have to hit stop or hit play three times to get it to start 
playing.  (I can't attach it because it's derived from something with 
uncertain copying rights.)  The sequencer usually craps out at some point 
thereafter.  
 
Which seems silly, actually.  I get a dialog about "Couldn't start the 
sequencer" after I've been playing for five minutes.  No, you mean "The 
sequencer crashed" don't you?  I should think so.  (Or does it try to 
restart it now?) 

----------------------------------------------------------------------

Comment By: Chris Cannam (cannam)
Date: 2004-05-14 09:36

Message:
Logged In: YES 
user_id=13489

Just to add that this one has been annoying me lately too. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104932&aid=933041&group_id=4932