But I *shouldn't have to*.Īnd if I *do* decide to change the code to suit my peculiarity of wanting the interface to be simpler, what about when the code is updated? Can I make a fork where my changes will stay 'constant' even as code around it changes? I have no idea. Yes, I can just click the 'loop playlist' button (Windows apparently) or press Command-L (Mac - there doesn't seem to be a button. The 'ordinary user' who has no programming experience is screwed. This would take about 5 minutes, plus 1-2 hours (at least) to dig around in the code to figure out how everything is hooked up (plain C, OO, Qt with 'meta-interface' files, etc). Yes, I could download the code and make a presumably very small change to make sure the 'playlist loop' flag is off when 'convert-save' is activated, and the set it back afterward. But it surely cannot be the *expected* behavior of a first-time user (I don't even know why the converted file is added to the playlist *all* all. Yes, this is 'I suppose' then 'logical behavior' - given how the code is writte. This is one thing that ticks me off about open-source software: Yes, the fix is easy - turn off Loop playback, so it doesn't try to (I think) play the converted file again, and then re-convert the first file, etc, etc.

Vlc by videolan