View Issue Details

IDCategoryLast Update
0008859bugs2022-01-14 07:53
Reporterjohne53Assigned To 
Reproducibilityalways 
Status newResolutionopen 
PlatformMicrosoftOSWindowsOS Version10
Product Version6.9 
Fixed in Version 
Summary0008859: Latest dev code cannot load sessions from earlier versions
DescriptionThis 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 InformationThe 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.
TagsNo tags attached.

Activities

x42

2022-01-13 17:55

administrator   ~0026295

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

johne53

2022-01-14 07:53

reporter   ~0026296

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.

Issue History

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