01304 827609 info@use-ip.co.uk Find us

Scrubbing Playback

G

gp116126

Centurion!
Trusted Member
Messages
164
Points
28
Okay. Perhaps this

Scrolling (scrubbing) Through Playback Timeline

Me again folks. Thank in advance to anyone who reads this as it might seem a lengthy explanation. The issue I am about to explain is my main concern with m 7608m2 8p setup. I upgraded from the K2 8p because I wanted to replace some of my G0 4mp cameras with 8mp, because I had to throttle...
www.use-ip.co.uk www.use-ip.co.uk

was a little too long hence no replies.

So how about this:

Does anybody with an M Series NVR have any issues with scrolling (scrubbing) playback through the timeline.
 
johnfitzy said:
Hi @gp116126 ... can't help because I am on V5... I wonder how many M series users have chosen to stay with the V4 firmware?
Click to expand...


Hello johnfitzy.

Thank you for your reply. If you're on version 5 would you be able to tell me if you have had problems with scrubbing, because if not then my solution would be to upgrade to version 5.

Could you also tell me how many channels / cameras you have and spec of cameras so that I can get an idea of whether it could also be processing power, bandwidth or hard drive causing my problem.

Thank you very much.
 
@Dan

Have you guys come across or have any issues that I'm describing with your test equipment. It's not something reported before on this forum as obviously there are other ways to view footage, but scrubbing through the timeline is important to me and I would appreciate you letting me know what you think.
 
gp116126 said:
was a little too long hence no replies.
Click to expand...
It's not a method I use for playback. I read your post and see that you said the settings were the same on each camera whether affected or unaffected but is the I Frame interval the same on each as the will be the image you see while scrubbing.

I'm on V5 like @johnfitzy. I've a mix of G3 platform 2386ISU/SL), G5 platform (2387G2 and G2H) and H13U (the brand new 2347G3). All set to H264 25FPS CBR. Scrubbing only works at night on the 2347G3 and a little during the day. I can't scrub on the others day or night. Perhaps the reason I can with the new H13U is that it's a 4MP camera and a lower bitrate. It could be down to the load on the NVR to decode non consecutive large I frames at speed (just a guess)
 
Last edited:
gp116126 said:
Could you also tell me how many channels / cameras you have and spec of cameras so that I can get an idea of whether it could also be processing power, bandwidth or hard drive causing my problem.
Click to expand...

Screenshot 2025-05-29 114037.png


IMG_4256.jpg


All of the cameras are set to H264, 22 FPS, I-frames 22, 16384 Kbps, constant.


gp116126 said:
If you're on version 5 would you be able to tell me if you have had problems with scrubbing, because if not then my solution would be to upgrade to version 5.
Click to expand...

I just tested... the only camera I can scrub with is the older 3MP DS-2DE4A320IW-DE PTZ:




I used to dual record both main and sub-streams... when I did, I could scrub all cameras using the sub-stream... even 9 together (although there were some pauses when scrubbing all 9 together).
 
@johnfitzy. @JB1970.

Thank you both for letting me know how your systems cope with scrubbing. Very interesting results. At least it tells me that it's not specifically the fact I'm using version 4, so for now I'm going to stick with it.

I've been doing a bit more research. Well basically communicating with the Android AI app called orbit. Wow. AI is scary.

Anyway, according to orbit'what it basically boils down to is having enough I frames in the recorded footage so that the nvr's processing resource isn't used by filling in the gaps. The recommendation is that you have one I frame per FPS. So 25 frames per second equals an I frame rate at 25. My cameras (out of the boxes) are set at 50.

In working all of this out orbit went through all of the other possible scenarios and calculated their impact on what I was experiencing. For instance told me why it would not make a difference by adding another HDD. One of the things I was considering. There's lots more in its analysis and I will send it to use IP admin because I think it's really interesting and they may want to publish it. I can't as it's the document not a picture. It opened up a lot of avenues for me and really helped with my knowledge of how the various settings work with CCTV.

Next step for me is to try experiments with settings, I frame in particular to see where it takes me.

I'll report.

Cheers.
 
gp116126 said:
Well that's really interesting because I really didn't want to go to version 5 but if it does solve the issue then I will.

@JB1970 are you seeing the same scrubbing improvements.
Click to expand...
forum.use-ip.co.uk

JB1970

forum.use-ip.co.uk forum.use-ip.co.uk

Hello JB.

Have you had any improvement with scrubbing since installing v5.04.060
 
JB1970 said:
I'm now on 5.04.065 which @Ray Arts posted as released today. I've just tried and it's working normally day and night on all of my cameras.
Click to expand...
Wow. Thank you for letting me know. Before I plunge for the five upgrade if you have time would you be able to summarise what the main outstanding issues are with the firmware. I don't mind having to get used to a new GUI and don't have an intercom.
 
gp116126 said:
Wow. Thank you for letting me know. Before I plunge for the five upgrade if you have time would you be able to summarise what the main outstanding issues are with the firmware. I don't mind having to get used to a new GUI and don't have an intercom.
Click to expand...
I've already covered it in the 'M Series firmware issues/avoid thread'. I just think it's clunky compared to V4 and while there are various improvements usability is not the same. You cannot easily toggle 'skip unrelated playback' to switch between continuous and "Human' playback. That's just my personal opinion so it's not really relevant as everyone will make their own decision as to what they prefer.
 
JB1970 said:
I've already covered it in the 'M Series firmware issues/avoid thread'. I just think it's clunky compared to V4 and while there are various improvements usability is not the same. You cannot easily toggle 'skip unrelated playback' to switch between continuous and "Human' playback. That's just my personal opinion so it's not really relevant as everyone will make their own decision as to what they prefer.
Click to expand...
Thank you JB. I'll have a read of that thread
 
gp116126 said:
Thank you JB. I'll have a read of that thread
Click to expand...
JB1970 said:
I've already covered it in the 'M Series firmware issues/avoid thread'. I just think it's clunky compared to V4 and while there are various improvements usability is not the same. You cannot easily toggle 'skip unrelated playback' to switch between continuous and "Human' playback. That's just my personal opinion so it's not really relevant as everyone will make their own decision as to what they prefer.
Click to expand...
Been through it now. Can't say I understand a lot of it especially as I've no experience of the 5.0 GUI but I do feel your pain and frustration from your comments. You're quip about there being more bugs in the museum was funny but sadly accurate.

Like you I do use motion as a general tool to highlight when there is motion in a scene, but don't have it report continuously when it does and also use line crossing sometimes intrusion detection to focus on specific areas when I want that notification to surveillance or the buzzer to alert me.

So if firmware version V5.04.065 build250530 has not made any difference (didn't see any comments from you about that) it seems that I'll have a choice if the Android AI solution of setting the camera's iframe rate and FPS rate the same doesn't work.

Upgrade to 5 and resolve scrubbing issues but have to deal with more complex ways of seeing motion on the timeline.

Or stick with version 4 that I think you are explaining has a simpler way of viewing and searching for timeline motion, but still have scrubbing issues.

I do have another option which I'm on at the moment which is stick to my K version 3 which I'm very used to and has got all the functionality apart from it can't scrub these newer G2 cameras because NVR ain't got the capability. What I'd then be doing is reinstalling the G0s and flogging all the new kit to some poor sole who can put up with it.

Choices choices.

And they call this advancement in technology.

Cheers
 
gp116126 said:
Been through it now. Can't say I understand a lot of it especially as I've no experience of the 5.0 GUI but I do feel your pain and frustration from your comments. You're quip about there being more bugs in the museum was funny but sadly accurate.

Like you I do use motion as a general tool to highlight when there is motion in a scene, but don't have it report continuously when it does and also use line crossing sometimes intrusion detection to focus on specific areas when I want that notification to surveillance or the buzzer to alert me.

So if firmware version V5.04.065 build250530 has not made any difference (didn't see any comments from you about that) it seems that I'll have a choice if the Android AI solution of setting the camera's iframe rate and FPS rate the same doesn't work.

Upgrade to 5 and resolve scrubbing issues but have to deal with more complex ways of seeing motion on the timeline.

Or stick with version 4 that I think you are explaining has a simpler way of viewing and searching for timeline motion, but still have scrubbing issues.

I do have another option which I'm on at the moment which is stick to my K version 3 which I'm very used to and has got all the functionality apart from it can't scrub these newer G2 cameras because NVR ain't got the capability. What I'd then be doing is reinstalling the G0s and flogging all the new kit to some poor sole who can put up with it.

Choices choices.

And they call this advancement in technology.

Cheers
Click to expand...
Version 4 is just simpler to use, to find what you need in playback and to switch between continuous and event skipping playback in a single click.

Version 5 is modernised. The menu system is not intuitive and makes searching playback tedious. What I term a bug is probably just Hikvisions change of use and intended. There are some things that it adds that are very useful such as setup of individual alarm areas so that you can arm/disarm zones of cameras. Slice Playback to filter quickly when an object appeared/disappeared is handy (available on V4 for many NVRs but the M series went to V5 prior to that feature)
 
JB1970 said:
Version 4 is just simpler to use, to find what you need in playback and to switch between continuous and event skipping playback in a single click.

Version 5 is modernised. The menu system is not intuitive and makes searching playback tedious. What I term a bug is probably just Hikvisions change of use and intended. There are some things that it adds that are very useful such as setup of individual alarm areas so that you can arm/disarm zones of cameras. Slice Playback to filter quickly when an object appeared/disappeared is handy (available on V4 for many NVRs but the M series went to V5 prior to that feature)
Click to expand...
A very good summary.

And I read somewhere that if I go to v5 then there's no going back to V4. Is that correct.
 
gp116126 said:
A very good summary.

And I read somewhere that if I go to v5 then there's no going back to V4. Is that correct.
Click to expand...
You can go back. It's just that the NVR gets restored to an unactivated state when downgrading, so that you have to set it up again; that makes trying out V5 a pain. It's not a huge issue if your cameras are plug and play connected, but if you've manually added them on the network it's a little more work. One important recommendation when downgrading is to first disable and unbind the NVR from Hik-Connect and rebind it afterward. There have been some instances reported of users getting their NVR blacklisted such that it won't connect after downgrade and that extra step gets around that happening.
 
Last edited:
JB1970 said:
You can go back. It's just that the NVR gets restored to an unactivated state when downgrading, so that you have to set it up again; that makes trying out V5 a pain. It's not a huge issue if your cameras are plug and play connected, but if you've manually added them on the network it's a little more work. One important recommendation when downgrading is to first disable and unbind the NVR from Hik-Connect and rebind it afterward. There have been some instances reported of users getting their NVR blacklisted such that it won't connect after downgrade and that extra step gets around that happening.
Click to expand...
Thank you for all of your responses JB. I took a break from cctv and have now just caught up.

Thanks again.
 
You must log in or register to reply here.

Similar threads

G
Scrolling (scrubbing) Through Playback Timeline
Replies
1
Views
365
gp116126
G
talksr
Hik-Connect iOS Playback Issues
Replies
1
Views
211
johnfitzy
J
JB1970
VPro (Acuseek) NVR - First Impressions
2 3 4
Replies
64
Views
3K
JB1970
JB1970
S
How to Initialise a CCTV HDD in Windows for Footage Recovery?
Replies
3
Views
10K
trempa92
trempa92
JB1970
Firmware M Series 5.04.020_241106 Released - Issues/Avoid
7 8 9
Replies
178
Views
16K
uvs-300
U
Back
Top