favor existing arguments from parameters (kwargs) over global (args) #336
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
insufficient info
invalid
news
not a bug
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mrq/ai-voice-cloning#336
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ben_mkiv/ai-voice-cloning:master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi last one for today...
which you should please review as i'm not sure if this could lead to unintended behavior. (i've tested generation in web interface, cli and with websockets to ensure that it still behaves as expected)
made this change because i couldn't find another way to force load a model specified from my websocket requests (which are passed into generate as kwargs)
if possible, could you give a short explanation of args? had a hard time twisting my head around the parameter parsing...
is this some global settings which get deduced from ai-voice-cloning defaults and whatever the user has configured in the webui settings?
It looks fine, but I've been a bit out of my element for a while in terms of AIVC, so.
If you tested it and it works fine still, it should be fine.
That argument is already grabbed under
./src/utils.py
and referenced asargs.autoregressive_model
.Yes.
args
will load defaults from the./config/exec.json
, and any passed in arguments are applied on top of it (without saving).The arguments under
./src/cli.py
extend those arguments with generation parameters (and those defaults are pulled from./config/generate.json
) as a bandaid, because desu this entire repo is a mess of stapling spaghetti on top of one another and is in dire need of a rewrite.This is because, if you're relying on the generate function handling model loading, the web UI will load the TTS backend with whatever's specified under
args.autoregressive_model
first naively, and then look at whatever generation settings require it.I would need to have
args.autoregressive_model
updated before theload_tts
call.3ad0685620
toce24ba41e2
thank you, i've reduced the PR to overriding the args parameters in the websocket server, ignore the commit spam... squashed it down to one commit
No worries.