|
Post by reden on Jul 27, 2022 3:24:25 GMT
You also must start Audacity manually the first time and enable the Module:
P.S. This might be possible to attain through command-line by editing Audacity's config file and setting the appropriate parameter to 1 (forgot the name of it).
Wow, this should be a default or something.
|
|
|
Post by reden on Jul 27, 2022 3:24:54 GMT
Add -j(corenumber) option to build with several cores. Thanks, great tip; significantly faster. A 2nd core provides the greatest boost by halving compile time.
|
|
|
Post by reden on Jul 27, 2022 3:26:05 GMT
Hmmmm, I wonder if you built audacity with debian-provided libraries, such as Wxwidgets, disregarding their (stupid) recommendations, then you just would need to do apt build-dep audacity and run audacity/build/audacity. It might succeed, it might fail, for example the debian 11 audacity has a lot of errors regarding portaudio for some reason.
|
|
|
Post by reden on Jul 27, 2022 3:35:30 GMT
At last the file has appeared. But it is 86 mb even having specified x16. So I sped it up to x128, doing it one command at a time for extra safety.
|
|
|
Post by AnthroHeart on Jul 27, 2022 9:50:33 GMT
When you clone, you also clone the whole history, so you can rollback those changes yourself if you want. This makes cloning slightly slower as time goes on. You can clone just the latest history entry, I think using --level or something like that.
|
|
|
Post by sound on Jul 27, 2022 12:01:40 GMT
At last the file has appeared. But it is 86 mb even having specified x16. So I sped it up to x128, doing it one command at a time for extra safety. I don't think faster speed will necessarily make the file smaller, because it loops throughout the 30 minutes
|
|
|
Post by reden on Jul 27, 2022 13:31:00 GMT
At last the file has appeared. But it is 86 mb even having specified x16. So I sped it up to x128, doing it one command at a time for extra safety. I don't think faster speed will necessarily make the file smaller, because it loops throughout the 30 minutes It made it 10 MB.
|
|
|
Post by reden on Jul 27, 2022 14:30:56 GMT
Are you sure a part of the file isn't being cutoff by -t 300? Ffprobe the file, extract the duration, divide 1800/duration_in_seconds and -stream_loop by the integer amount (non-decimal).
|
|
|
Post by reden on Jul 27, 2022 14:49:08 GMT
AnthroHeart says it's 3/10 strength.
|
|
|
Post by AnthroHeart on Jul 27, 2022 14:51:22 GMT
AnthroHeart says it's 3/10 strength. That's for 128X speed. It skips when it's that fast.
|
|
|
Post by sound on Jul 27, 2022 14:52:31 GMT
Are you sure a part of the file isn't being cutoff by -t 300? Ffprobe the file, extract the duration, divide 1800/duration_in_seconds and -stream_loop by the integer amount (non-decimal). Do you mean that at the end of the track, it might cut in the middle of speech?
|
|
|
Post by reden on Jul 27, 2022 15:23:07 GMT
Are you sure a part of the file isn't being cutoff by -t 300? Ffprobe the file, extract the duration, divide 1800/duration_in_seconds and -stream_loop by the integer amount (non-decimal). Do you mean that at the end of the track, it might cut in the middle of speech? Yes
|
|
|
Post by sound on Jul 27, 2022 15:29:10 GMT
I don't see that as a problem since it loops many times over before reaching the end. Do you?
|
|
|
Post by reden on Jul 27, 2022 16:04:28 GMT
I used the 16x version and AnthroHeart said it still was the same, 2.5/10 or 3/10. I used the default 1gb ram Repeater. He said Sanskrit written text is stronger.
|
|
|
Post by reden on Jul 27, 2022 16:23:18 GMT
You forgot to specify the .TXT in the intrpt part of the script. But Repeater gets it anyway.
|
|