-
Notifications
You must be signed in to change notification settings - Fork 260
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
Problems with Inconsistent Paths #182
Comments
I think I have a similar issue, the transcript and individual .mp3 files were created: |
Having the same issue. Any help is welcome. |
Windows OS?
…On Sat, Dec 28, 2024, 7:31 AM Japanjot1 ***@***.***> wrote:
Having the same issue. Any help is welcome.
—
Reply to this email directly, view it on GitHub
<#182 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADTMY3PIU3VPFIMWJDQXVST2HZ4YLAVCNFSM6AAAAABR5SQAX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGI4TCMJSGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Yep. I'm running this on windows. |
I guess I figured it out. Had to install Ffmpeg manually. Now it works perfect. |
Did you have to uninstall ffmpeg first? |
I'm getting an error and an unexpected behaviour because of paths.
When running, Podcastfy will store some of the temporary files (ie. the transcript) in the local directory, but others (ie. the audio files) in the library directory of your Python installation. It seems that the folder the library considers the 'working' folder changes half-way through execution.
This also impacts local FFMPEG installations. PyDub won't complain about FFMPEG if you've got it in the same folder as your .PY file....but by the time it tries to combine each of the audio samples together into one MP3, it's not using the scripts local directory anymore, which means FFMPEG can't be found. This forces Windows users to copy the executables into somewhere on the PATH.
I'd expect this to be more consistent - and ideally, not store any temporary files in the library folder(s). If anything goes wrong (such as FFMPEG not being found), the unprocessed files remain in the library folder, cluttering everything up.
The text was updated successfully, but these errors were encountered: