|
|
I can duplicate that.Once I've created that 'copy' region it can be moved on it's own track, but moving it to another track crashes Ardour2 with the following error message. ardour-2.0rc1: /usr/include/boost/shared_ptr.hpp:247: typename boost::detail::shared_ptr_traits<T>::reference boost::shared_ptr<T>::operator*() const [with T = ARDOUR::Playlist]: Assertion `px != 0' failed. |
|
|
rather puzzling. sounds like a bug that was fixed before rc1 was released. i just tried duplicating here with current SVN, and it seems to work OK - none of the symptoms reported by audun or oofus show up. oofus - i know you tested this only 2 days ago, could you try it again, and give me a recipe if its still happening? |
|
|
I can confirm, contrary to what Paul is saying; the bug is present on rc2 revision 1744. I have no trouble reproducing it whatsoever. See screenshot. |
|
2007-04-26 01:42
|
ardour-2.0rc2-sshot.png (187,923 bytes) |
|
|
can i get an exact recipe for duplication please? |
|
|
1. Create a new session 2. Add a track 3. Record a region on that track 4. Press CTRL 5. Place the mouse cursor in the waveform area of the recorded region 5. Press down mouse button2 6. While holding down this button, move the cursor a bit (say about 100 pixels) to the right, but keep it inside the track. 7. Release button2 The track will "blink", indicating that a new region, a copy of the old one, is inserted in the track. (7 1/2 release CTRL ;) 8. Press shift 9. Scroll the mouse wheel upwards: The track height will increase, the old region will obtain this new track height, but the copied region will not. I think that eventual crashes after this only reflects this strange behavior, that some pointers or references are zero and/or similar. |
|
|
By the way, it seems like the copied region shares the inner state with the old one. For example, moving one of them or dragging it's fade handler will also be reflected in the other one. But operations on the _track_ will only affect the old one. |
|
|
OK, Use the same recipe as audun up to step 7. Then left-click and drag the new region on the same track. The new region can be moved away from the original (now showing two regions on the track), but when the new region is released it stays where it is dropped and the original region disappears. This can be repeated as many times as you like. If however you left-click and then drag the new region to another track, Ardour crashes. |
|
|
Yes, this indicates that the two regions can't be moved independently of each other. Just change the track height, and you'll see what I mean. The original region doesn't disappear, it is just directly below or above the other one. |
|
|
believed fixed in rev 1750. let me know so we can mark this resolved ASAP. thanks for finding this. |
|
|
Appears fixed to me. |
|
|
see notes. |
|
|
Yes, this is fixed in revision 1750. |
- Anonymous
