View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008859 | ardour | bugs | public | 2022-01-13 14:12 | 2022-03-14 14:12 |
| Reporter | johne53 | Assigned To | x42 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Microsoft | OS | Windows | OS Version | 10 |
| Product Version | 6.9 | ||||
| Summary | 0008859: Latest dev code cannot load sessions from earlier versions | ||||
| Description | This is currently affecting the dev versions for both Ardour and Mixbus What happens here is that if I try to load a session from some previous version, timeline regions get positioned on the correct track - but they're all positioned to start at zero timecode. | ||||
| Additional Information | The problem seems to be in 'timecnt_t::string_to (std::string const & str)' (libs/temporal/timeline.cc) if (isdigit (str[0])) { /* old school position format: we assume samples */ std::stringstream ss (str); ss >> sm; _distance = int62_t (false, samples_to_superclock (sm, TEMPORAL_SAMPLE_RATE)); _position = timepos_t (AudioTime); // <--- PROBLEM IS HERE !!!! /**/ std::cerr << "deserialized timecnt from older " << str << " as " << *this << std::endl; return true; } AFAICT that section only ever gets called while processing a region's "length" property - i.e. whilst importing a session from an earlier format. But the '_position' property isn't getting processed. It's just assumed to be zero. I'm not sure if there's an elegant fix for this problem. A region's 'length' property and its 'position' property are now both part of the same property. But AFAIK it isn't possible to process the two older properties simultaneously. | ||||
| Tags | No tags attached. | ||||
|
|
When you start Ardour pre-alpha there is a "Pre-Release Warning" dialog, please re-read it. In particular: 4) Please do NOT file bugs for this alpha-development versions at this point in time |
|
|
Strangely enough I don't see that message box, I'm not sure why. Anyway, yesterday I filed bug report 0008858 and also this one - so just feel free to delete them. |
|
|
Working again now in git master. |
|
|
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 |
|---|---|---|---|
| 2022-01-13 14:12 | johne53 | New Issue | |
| 2022-01-13 17:55 | x42 | Note Added: 0026295 | |
| 2022-01-14 07:53 | johne53 | Note Added: 0026296 | |
| 2022-01-30 14:14 | johne53 | Note Added: 0026320 | |
| 2022-01-30 16:23 | x42 | Assigned To | => x42 |
| 2022-01-30 16:23 | x42 | Status | new => resolved |
| 2022-01-30 16:23 | x42 | Resolution | open => fixed |
| 2022-03-14 14:12 | anonymous | Note Added: 0026348 | |
| 2022-03-14 14:12 | anonymous | Status | resolved => closed |
