(Prepare Dataset) List indices must be intergers or slices, not dict #335

Closed
opened 2023-08-22 20:36:25 +00:00 by MrMustachio43 · 6 comments

I don't know why this isn't working or what's wrong.
First two images is the error, then the last is the files I'm using to clone.

I don't know why this isn't working or what's wrong. First two images is the error, then the last is the files I'm using to clone.
Owner

What's odd is that I did use the openai/whisper backend the other day with no apparent issues, but regardless I'll take a look at it when I get a chance.

What's odd is that I did use the `openai/whisper` backend the other day with no apparent issues, but regardless I'll take a look at it when I get a chance.
Owner

I haven't gotten a chance to actually look at it, but from the other issue I referenced to, you might need to chick Slice Segments, and set your offsets to -0.05 and 0.2 for safety. I think I did actually get an issue when not having slicing enabled and I forgot to look into it the other day.

But again when I get a chance to actually look and experiment and debug, I will.

I haven't gotten a chance to actually look at it, but from the other issue I referenced to, you *might* need to chick `Slice Segments`, and set your offsets to `-0.05` and `0.2` for safety. I think I did actually get an issue when not having slicing enabled and I forgot to look into it the other day. But again when I get a chance to actually look and experiment and debug, I will.
Author

The fix worked perfectly. Odd though, as I never needed to before haha. Thank you for your assistance :)

The fix worked perfectly. Odd though, as I never needed to before haha. Thank you for your assistance :)
Owner

Odd though, as I never needed to before haha.

I'm very, very certain it was a regression I've introduced when committing the changes from my training rig back to this repo (commit 72a38ff2fc), as I'm very very messy and forgetful when I do work on that machine.

Although, looking at it now, I think I see the issue. Should be fixed in commit 29290f574e. I haven't gotten a chance to test it, but running the logic in my head, it looks sound.

> Odd though, as I never needed to before haha. I'm very, very certain it was a regression I've introduced when committing the changes from my training rig back to this repo (commit 72a38ff2fc6aeb8b8184bb8e8103497a37ce151d), as I'm very very messy and forgetful when I do work on that machine. Although, looking at it now, I think I see the issue. Should be fixed in commit 29290f574eb2f8aa9c2cf19b9aaf131a2fd1c3ff. I haven't gotten a chance to test it, but running the logic in my head, it looks sound.
Author

Yes, it's been fixed! I shall close this issue, thank you :)

Yes, it's been fixed! I shall close this issue, thank you :)
Author

Yes, it's been fixed! I shall close this issue, thank you :)

Yes, it's been fixed! I shall close this issue, thank you :)
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mrq/ai-voice-cloning#335
No description provided.