View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003925 | ardour | bugs | public | 2011-04-01 22:22 | 2020-04-19 20:15 |
| Reporter | zettberlin | Assigned To | cth103 | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0-alpha3 | ||||
| Target Version | 3.0-beta1 | ||||
| Summary | 0003925: Adding new note at the beginning of a region crashes | ||||
| Description | I get a crash if I: 1.) duplicate a MIDI-Region (thus the copy begins immediately after its original) 2.) fork it 3.) try to add a note at the beginning of the forked region the terminal says: address: /bridge/exiting, type tag: ardour-3.0: ../gtk2_ardour/midi_region_view.cc:815: void MidiRegionView::create_note_at(double, double, double, bool): Zusicherung »start_frames >= 0« nicht erfüllt. Abgebrochen (Speicherabzug geschrieben) | ||||
| Tags | No tags attached. | ||||
|
|
I can't reproduce this. |
|
|
Is this still repeatable for you? Are you building Ardour from SVN? If so, I may need to give you some patches to debug the problem. |
|
|
Thanks for the reminder :-) After your first message I tried to repeat the issue and rebuild from SVN first. Ardour crashed after I prepared the scenario and tried to save the session. Yesterday I tried again with a fresh checkout and could not reproduce the problem described above but A3 kept crashing as I tried to save the session. So in a word: the issue seems to be gone. I will check again with new builds, that allow me to save the session anyway... |
|
|
OK, thanks. Feel free to report the crash-on-save problem separately if it persists. |
|
|
I can consistently reproduce this crash when inserting a note on the first beat of the duplicated region but it doesn't matter if I fork the duplicated region or not, it still crashes with the error above under 9394. |
|
|
Built today from Ardour3.0alpha4 (built using ['9394'] und GCC Version4.4.5) And now I can repeat the error again. It feels like if I try to set the note slightely *above* the left border of one region to another. On the border itself, that is... And the region does not need to be forked, simply multi-duplicate and try the border between region 1 and region 2. This is the terminal: ardour-3.0: ../libs/pbd/pbd/sequence_property.h:202: PBD::SequenceProperty<Container>* PBD::SequenceProperty<Container>::clone_from_xml(const XMLNode&) const [with Container = std::list<boost::shared_ptr<ARDOUR::Region>, std::allocator<boost::shared_ptr<ARDOUR::Region> > >]: Zusicherung »v« nicht erfüllt. Abgebrochen The crash also destroys the session-file. At next start it does not find the MIDI-files: Search path = /home/zettberlin/crashtest3-200411/interchange/crashtest3-200411/midifiles:/home/zettberlin |
|
|
The initial bug in the report should be fixed in SVN 9398. The second crash looks different. Can you get a backtrace for that one? |
|
|
Fixed in latest svn for me - great work C, thanks! |
|
|
> The second crash you mean the crash, when the region is NOT forked? |
|
|
The one with the assertion failure Zusicherung »v« nicht erfüllt |
|
|
Sorry for the delay... With todays revision 9456 I cannot reproduce this behavior anymore. Reason: I cannot put any notes in the place, where the incident was triggered. That is: If I move the pencil-tool to the beginning of a MIDI-Region right after the end of another region, the note snaps to a place in one of these two regions, that is one section of the chosen grid-resolution away from the border between both regions. So placing a note immediately at the border/beginning of region two is not possible. I can, whatsoever move such a misplaced note to the place for the first note of the second region afterwards. Is that a deliberate behaviour to work around the crash described above? |
|
|
I believe this is because you have a region which starts 1 frame after a bar line, so that it is not possible to create a note snapped to a bar line at the start of the region. Ardour shouldn't have let you move a note there, either; this is fixed in SVN 9463. Part of the original fix was to prevent duplicated regions starting 1 frame after a bar line start, so this problem should not occur with new sessions created using current SVN. Does your problem still occur with a newly-created session? |
|
|
I created the region by duplicating a region that I had drawn with snap to grid beat/4 so I would consider it kind of strange, that the duplicated region starts a frame off. Most people will use duplication to loop regions so it would be the correct behaviour, if the first note/frame of a duplicated region starts exactly at "1" in the grid. And I guess, that is indeed the standard behaviour is it? I created the session with a build from SVN yesterday (rev.9456) if it helps you may have a look into it: http://lapoc.de/archiv/ardour/test020511.tar.gz I will rebuild today and report back anyway... |
|
|
Sorry, I'm a bit confused now. What problem are you seeing with that test session? I can create notes at the start of the regions fine. |
|
|
With todays build Revision 9465 (2011 05 04 10:30 GMT) I cannot reproduce this problem either. Loading the session Ardour reported only this: [WARNING]: MIDI note 0000057 not found in model - programmers should investigate this ...then the session works as expected and I cannot provoke any misbehaviour by putting notes at the beginning of regions. So now I would really consider the case closed... |
|
|
OK, closing this one. Thanks for your help! |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-04-01 22:22 | zettberlin | New Issue | |
| 2011-04-02 12:35 | cth103 | cost | => 0.00 |
| 2011-04-02 12:35 | cth103 | Target Version | => 3.0-beta1 |
| 2011-04-03 23:26 | cth103 | Note Added: 0010465 | |
| 2011-04-19 21:02 | cth103 | Note Added: 0010605 | |
| 2011-04-19 21:02 | cth103 | Status | new => feedback |
| 2011-04-19 21:17 | zettberlin | Note Added: 0010606 | |
| 2011-04-19 21:30 | cth103 | Note Added: 0010607 | |
| 2011-04-20 09:25 | danboid | Note Added: 0010614 | |
| 2011-04-20 20:25 | zettberlin | Note Added: 0010618 | |
| 2011-04-20 20:28 | zettberlin | Note Edited: 0010618 | |
| 2011-04-20 23:51 | cth103 | Note Added: 0010620 | |
| 2011-04-21 07:14 | danboid | Note Added: 0010624 | |
| 2011-04-21 14:03 | zettberlin | Note Added: 0010630 | |
| 2011-04-23 00:08 | cth103 | Note Added: 0010643 | |
| 2011-05-02 20:56 | zettberlin | Note Added: 0010665 | |
| 2011-05-03 00:31 | cth103 | Relationship added | related to 0004024 |
| 2011-05-03 00:49 | cth103 | Note Added: 0010671 | |
| 2011-05-03 06:56 | zettberlin | Note Added: 0010672 | |
| 2011-05-03 11:06 | cth103 | Note Added: 0010673 | |
| 2011-05-04 08:58 | zettberlin | Note Added: 0010680 | |
| 2011-05-08 23:46 | cth103 | Note Added: 0010704 | |
| 2011-05-08 23:46 | cth103 | Status | feedback => resolved |
| 2011-05-08 23:46 | cth103 | Resolution | open => fixed |
| 2011-05-08 23:46 | cth103 | Assigned To | => cth103 |
| 2020-04-19 20:15 | system | Note Added: 0022507 | |
| 2020-04-19 20:15 | system | Status | resolved => closed |
