Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

scene_manager.stats_manager.save_to_csv wrong key word in init file #299

Closed
oriel-perl opened this issue Nov 13, 2022 · 2 comments · Fixed by #300
Closed

scene_manager.stats_manager.save_to_csv wrong key word in init file #299

oriel-perl opened this issue Nov 13, 2022 · 2 comments · Fixed by #300
Labels
Milestone

Comments

@oriel-perl
Copy link

In the init file kw argument for the csv file is path but it is an unknown argument in the function:

scene_manager.stats_manager.save_to_csv(path=stats_file_path, base_timecode=video.base_timecode)

it should be -
scene_manager.stats_manager.save_to_csv(csv_file=stats_file_path, base_timecode=video.base_timecode)

@oriel-perl
Copy link
Author

oriel-perl commented Nov 21, 2022

the error is not resolved:
from running -

scene_list = detect(video_path=video_path,
                   detector=AdaptiveDetector(luma_only=True,min_scene_len=300,window_width=2),
                   show_progress=True)

I get the error

  File "/home/user/miniconda/lib/python3.8/site-packages/scenedetect/__init__.py", line 193, in detect
    scene_manager.stats_manager.save_to_csv(
TypeError: save_to_csv() got an unexpected keyword argument 'path'

that references the function call -

scene_manager.stats_manager.save_to_csv(path=stats_file_path, base_timecode=video.base_timecode)

Thanks!!

@Breakthrough
Copy link
Owner

This is fixed in the v0.6.1 branch and will be included in the next release of PySceneDetect. You can download a development version from one of the recent builds in the meantime. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants