INTERACT FORUM

It does seem broken.  The video in the screenie should have a 0 value for Watched(1).

I'm a bit puzzled on this one.

If we play more than half and stop, we increment the number of plays.

If the number of plays is more than zero, it counts as watched.

So it seems like logically partially watched would be anything with no plays and a non-zero bookmark. 

As you've found out, this isn't what it's doing.

I'll tighten it up for the next build.

I rely on self-discipline. If I have not entered a rating it means the video has not been completely watched. Or it means I need to watch it again before I consider it watched because I did not pay attention or did not understand the first pass.

I really hope you can look into some logic that will also work for the times you watch past 50% and up to, let's say 90%. I found 95% was to high, but 90% covers the most videos as watched, and you'll not likely leave any not watched behind.

I've often wondered why this hasn't always been the case, even in the case of music and the like. Is there a reason, or was it arbitrary? I would definitely prefer using 90% as the watched/played threshold.

I could also see some sense to using a file's setting for "Use Bookmarking" (whether via default or specific setting) to determine the threshold for a play/watch. e.g. A file set to not use bookmarking uses 50% to mark it as played, while a file set to use bookmarking uses 90%, or something along those lines. This assumes that there is some reason for using 50% (presumably for music?) to begin with. But the theory here being that if the file is just going to start over again anyway, then count it as played earlier but if it will be resumed then the user isn't finished watching it and will come back to finish it later and wants it to count as played/watched once they have done so.

My two cents and all...
-Jon

Exactly. When playing stuff with longer duration, the 50% mark is just not logical. It leaves to much to coincidences. For music and short clip video, sure. Here it might be a problem if the Number Plays increases just when it's reached the 90% mark. Some people change tracks often, or often before it's quite finished.

I just stumbled upon this problem too and decided to try to do something about it today.  Watched(1) is pretty much useless (and the Watched checkmarks trigger too easily).

It should really be decoupled from the [Number of Plays] and triggered where:

Watched(1) = 0:

[Number of Plays] = 0 and the bookmark is at 0%.

Watched(1) = 2:

[Number of Plays] > 0 and bookmarks is at:
>50% for any file with [Duration] < 10 minutes or so (this specific number is open to debate)
>~90% for any file with [Duration] > whatever number you picked above

Watched(1) = 1:

Everything else.

With the checkmark being equivalent to: [=Compare(Watched(1),<,2)]=1

However, if this is too "complex" for the simple function, then I'd much, much rather it always trigger at 90% (or so) than the current "1/2-way watched" behavior.  The problem is that, especially with kids, now I end up watching 1/2 of a show and then stopping, intending to come back later.  This makes building views that depend on the Watched status impossible, and makes the checkmarks have dubious value, for the vast majority of my use-cases.

It works as-is for Music Videos and other short stuff, but that's a tiny fraction of my files, and I can't think of a good use-case where you'd care about the "partial vs. non-partial" watched status of a music video.  You just want to count plays, for those.

The logic of the current system doesn't work well at all for watching TV shows or Movies if you ever come back and finish an episode/film later.

And, while you're at it, a Watched(4) mode that simply outputs a machine-readable (integer) value for the percentage watched would be very handy.  With that, I could make my own column or expression filter that works exactly the way I want it.

Without that, it is probably possible, but more difficult.  You're already doing the math to output the human readable version, so it doesn't seem like much of a stretch to give us a simple percentage output too.

Just recently, I posted what I have been using to display the progress of TV shows. I think it does what you want:

Code: [Select]

listitem(;left(watched(0),3);if(isrange(left(watched(0),2),5-95),left(watched(0),3),✔), watched(1), ;)

Clever.  Just stealing it out of the human readable output using the left() function.

That works, so long as they never change the formatting of the output.

You can use Regex() in test mode so you don't have to compare its output to a 0 or 1.

Alternatively, Regex() can be run in no-output mode, to just fill in [R#] values.  Maybe you'll find this simpler:

ifelse(isequal(watched(1), 2),
   regex(Watched(0), /#(\d+)%#/, -1)/
   if(isrange([R1], 5-95), [R1]%, ✔))

Yeah, it can take a while to discover the quirks of new languages so that the constructs can be employed most efficiently.

If I might add, I think you're doing a fabulous job, and I'm sure others appreciate your thoughtful help.