Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Converting markers to regions bug #601
From OuttrOMu...@gmail.com on October 05, 2013 02:27:18
What steps will reproduce the problem? create some markers in an empty project
run related action _SWSMARKERLIST14 alternately with _SWSMARKERLIST13 (convert between markers and regions repeatedly.
you appear to get one less region each time you go back and forth, but they didn't go away, they just got stacked at the project start, which you can see clearly in the SWS Marker List...
What version of SWS extension are you using? (Extensions -> About SWS...)
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=601
From jeffos...@gmail.com on October 10, 2013 01:37:14
@IXix: I was quite sure you replied to this issue ( https://groups.google.com/forum/?fromgroups#!topic/sws-updates/WHc_0NKPAuE ) but I can't see your posts anymore here... strange.
Also, I personnaly agree with the report here: for me, things should be designed so that convert to regions + convert to markers = no-op, and vice et versa. In other words, not sure these actions should "invent" a marker/region at the start of the project...
From OuttrOMu...@gmail.com on October 10, 2013 18:06:05
thanks for the responses, why this is an issue for me is 1: i try to make sure custom actions do not disrupt playback, as myself and others like to edit during playback; and 2: i used converting regions to markers and back to avoid creating overlapping regions, which imo is a bad, annoying feature of regions.
ultimately i tried to create an action to add a new, non-overlapping region at time selection for use on the fly (during playback).
how it would make the most sense to me would be to create markers for the start and end of regions (when converting to markers), ignore the project start if no marker exists, and avoid creating multiple markers at the same location. then the only difference when converting back to regions would be that any space between regions before would now also have a region, which i could not complain about. i think that would be the closest possible match to expectation for those actions.
that way you don't lose the last region because it's end point wasn't marked and you dont gain a region at project start unless desired, and you never get stacks of markers or regions anywhere.
From considin...@gmail.com on October 11, 2013 12:40:40
Yeah, I see the point and I don't mind changing it. I'm up to my ears in maths that I don't understand now but I'll sort it out soon.
@JeffOS Thanks for the heads up about API changes. I've noticed some odd region behaviour myself recently so I wonder if the issues you've linked might be what I was seeing.