![]() ![]() The project is highly ambitious, involving state-of-the-art 3D The history of Western civilizations, focusing on the years between 500 B.C.Īnd 500 A.D. Historically-based war/economy game that allows players to relive or rewrite ![]() Real-time strategy (RTS) game of ancient warfare. (pronounced "zero ey-dee") is a free, open-source, cross-platform If you decide to test one of these programs, please let the packagers know your results.įind the appropriate thread in this Forum and let us know how it worked.Ġ A.D. Once enough reports come in that they run properly thse programs will be moved into the main Community Repository. The packager may not be a regular user of a program he or she packaged and needs input from those who know the program better. While care has been taken to ensure these packages are safe and run correctly, nobody has all possible combinations of hardware and software to test with. Please do, that would be great, thank you.These packages have not yet undergone sufficient testing to put into the main Community Repository. If you need something that requires redevelopment of the Audacity code, and it seems like that’s what you’re asking, we’ll add you to Change Requests. Currently, the only workaround for this is to go through the annoying rigmarole of having to delete or rename the “FFmpeg for Audacity” folder every time before selecting “external program” in the Export dialogue, just to get it to see and use the FFmpeg installation in my PATH.Īn acceptable solution for this would be to make Audacity default to looking for a local FFmpeg installation in the PATH, and if it exists, use that one for “external program” instead of “FFmpeg for Audacity”, but I suppose a more complete solution would be to detect for both “FFmpeg for Audacity” as well as any FFmpeg installations in the PATH, and give the user the choice of which one to use for “external program”. The title was my initial question, but since you informed me in your first comment that it’s impossible to use my own FFmpeg installation outside of the export dialog (which I think is what you’re saying?), I would at least like it so that during the Export dialogue, I am able to select my own FFmpeg installation when using “external program”, which currently defaults to using “FFmpeg for Audacity” unless that folder isn’t found. ![]() Going a little deeper, it’s because your other version of ffmpeg does not give the correct responses to Audacity’s calls to the ffmpeg API. ![]() The direct answer to your question “Why won’t Audacity let me use my own ffmpeg?” is, “because your other version of ffmpeg doesn’t work with Audacity”, but that’s obvious. Given your other responses, and the title of this thread, I don’t think it is clear what your actual question is. If this isn’t already a feature, could it be made one? I don’t see the use in having an extra, old version of Audacity when I regularly make use of an external, up-to-date version and the program already supports use of that to some extent. However, doing other basic functions in Audacity seems to require use of “FFmpeg for Audacity”, which also means deleting or renaming that folder isn’t a viable option yet either. I’m not sure whether this is a bug or whether the feature just doesn’t exist, but Audacity doesn’t allow me the option of using my own local, up-to-date installation of FFmpeg (which is in my PATH) unless I rename or delete the “FFmpeg for Audacity” folder from Program Files (I’m using Windows 7, and Audacity 2.3.0). In an ideal world, I’d prefer to use only my own FFmpeg and have Audacity always use that, but in a world where’s that not possible, second-best would be using my own version of FFmpeg for exporting audio and Audacity FFmpeg for the usual functions. If you’re asking why I want to use my own version of FFmpeg to export, it’s because it’s the one I’m most used to and doesn’t require me to set -strictįor audio codecs that stable FFmpeg hasn’t considered experimental for a long time. I understand how the program’s basic functions work, and that much is clear enough from a basic read of my posts, so it’s patronising to be given copy-paste information from the manual as if I haven’t already read it.ĭid you determine that the Audacity FFMpeg was damaged or defective, or are you just assuming it can’t be any good? Why do people on this forum insist on informing me about things I already made clear I’m aware of in my original post while skipping over what I’m actually saying in my posts? It’s highly annoying. You can use your own FFMpeg through the File > Export system.įile > Export > Export Audio > (external program)Įxporting using an external encoder program - Audacity Manual ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |