Issue with new CLI ?

[Nurb4000]

I am assuming this is me, so not a bug.

I am just now this evening working on getting my GUI changed over for the new CLI stuff, ( moving most command-line parameters into the json ) and during basic CLI testing by hand i noticed that im only getting 30 second generations, no errors. Am i doing something wrong here im not catching?

img of json of the duration below. no matter what i set it to ( even less than 30.. ) it outputs 30 second runs.

oh and both cpu and ( newish ) gpu.. i always try it on both just to be sure its not my hardware :) Also regardless of output format.

[Nurb4000]

Ok its clearly my json, i took one generated from the server ran it by hand, and it worked. So I'm totally confused on what is amiss and overriding, since duration is correct... attached one of the tests. ( super simple.. )

musicgen_20260508_200333.json

[maysamassaf-beep]

I found the same issue, not only, it seems the problem is more deep. if i "ear" a song of 7 minutes mostly of the times all the data extracted from the song is wrong, bpm not coincide, time is reduced to 30sec, lot of times the generation is just a silence for all the song, then i noticed that at least in my pc the simple caption is not sent anymore for CoT (when all the buttons are red), so the synthetize generates always the same song and it lost its creativity, it works good only if i use a complete caption or if i click compose (doing that it will still utilize my simple caption without passing it to the Cot), really hope this will be solved, just few days ago it was running very well, what i did in this before the issue it was just one time i clicked on the lock, and iI nstalled the vulkan sdk, utilizing the binary files provided here for acestep.cpp , if can help... thanks

[Nurb4000]

Silence was another issue for me on older hardware, but that was fixed ( via parameter to pass in ). I am using different hardware now, but i do need to test the latest on the older stuff too, just to be sure its still working for people that need it. And ill do that once i get past this blip.

In this case i dont believe its the actual cli, as server is working fine, and cli worked with json output from the server, unless its borked reading something 'extra' in the json and its not 'me' so much as that i added all the parameters, just left most at defaults.

When i have time this weekend ill start stripping down line by line, and see when it starts working. ( but that will take time ) I dont really need 90% of what is there, i was just using the example in the documentation as a starting point, so with luck its something i can drop. Before this i used bare minimum json, but the example was easy to copy/paste, and i did plan on expanding options later so kept it all there, figured if its there and stays at default forever, no harm.

EDIT: i had a little bit of time this morning to start testing.. and it seems its inconsistent. I had a bare minimum small json that was only outputting 30 seconds. Was going to start adding fields one by one to it from the 'large working' one to see where it went sideways, instead of removing ones from the working one. But then then suddenly it started outputting the requested time, even with an empty caption. At first i was leaning towards possibly too short of a caption due to my testing method earlier, but that's not it either. But now that my earlier consistent failure to test against is working.. im at a total loss. ( not that i expected quality out of a couple of words, it was just for me to test for errors during manual testing )

[maysamassaf-beep]

Thanks you very much for your work Nurb4000, do you think the problem i have with the simple caption not sent to the CoT can be related to that or maybe there is a way to unlock it manually? the behaviour is the same of when 'lock' is checked in few words, and it probably happened just after i clicked 'lock' for the first time, like its variable ramain constantly locked and is unable to return back to unlocked... im sorry if i can't help more but im not properly a professional coder, just amateur.... thanks btw

[Nurb4000]

Thanks you very much for your work Nurb4000, do you think the problem i have with the simple caption not sent to the CoT can be related to that or maybe there is a way to unlock it manually? the behaviour is the same of when 'lock' is checked in few words, and it probably happened just after i clicked 'lock' for the first time, like its variable ramain constantly locked and is unable to return back to unlocked... im sorry if i can't help more but im not properly a professional coder, just amateur.... thanks btw

I am assuming you are using the out of box web interface instead of cli like i do. I can try that tomorrow to see if it doesn't unlock even when it said it did. Worst case you could do a reset at the top, that should reset all that stuff no matter what, but ill check to be sure the json output reflects toggling it off/on and if it doesn't, we can report it as a bug.

Oh, and be sure you are hitting compose between runs if you are changing things.. i missed that once when i was playing with the first release of web interface and got burnt. My GUI rebuilds on the fly when you generate, but the native web gui, you need to 'tell it' you have made changes and have it rebuild and didn't think about it. Neither way is right or wrong, just different.

[Nurb4000]

Ok i got home earlier than expected, and the exporting to json is working as expected, so i suspect its that you are not doing a compose between runs. That is exactly what burnt me before i understood the flow. i was only changing the duration in my case, and it was not changing during the actual generation, but that was why, as without the "recompose" step it was not really picking up my changes either. its just a step in the process.

[Nurb4000]

Get things sorted? if not its worth creating a new thread so it can be seen.

[Nurb4000]

Ok i think i found it, and im a moron ( again ) . looks like sometimes i had duration in quotes by accident, which forced it to default. Sorry for the noise, but if anyone else notices this if they are hand editing the json, keep an eye out for typos!.