Search found 14 matches
- Thu Jun 20, 2019 2:54 pm
- Forum: Windows
- Topic: Command line information not working on Windows
- Replies: 5
- Views: 394
Re: Command line information not working on Windows
- Wed Jun 19, 2019 2:39 pm
- Forum: Windows
- Topic: Command line information not working on Windows
- Replies: 5
- Views: 394
Re: Command line information not working on Windows
Thanks Steve! I believe this is not good. If the user just want to know the version of Audacity, it should be printed on the cmd and do not require that the user wait for the GUI to fully load and make some clicks to get this information. Maybe this is even worse if the user is using some scripting....
- Fri Jun 14, 2019 4:33 pm
- Forum: Windows
- Topic: Command line information not working on Windows
- Replies: 5
- Views: 394
Command line information not working on Windows
Hi there! I am trying to get the version number of audacity.exe using the cmd on Windows, but nothing returns. Using the exe provided on the zip package: C:\Users\username\Downloads\audacity-2.3.2>audacity.exe /v C:\Users\username\Downloads\audacity-2.3.2>audacity.exe -v C:\Users\username\Downloads\...
- Wed Apr 17, 2019 1:34 pm
- Forum: macOS
- Topic: How to open an AUP file from the command line on macOS
- Replies: 20
- Views: 823
Re: How to open an AUP file from the command line on macOS
What did you do? Just comment out the "#if !defined(__WXMAC__)" and "#endif"? Yes. but you are not willing to say what that use case is? In fact, we have made various modifications on Audacity for use internally by our team, to fit out workflow. The changes are very specific for our needs, not all ...
- Wed Apr 17, 2019 1:22 pm
- Forum: macOS
- Topic: How to open an AUP file from the command line on macOS
- Replies: 20
- Views: 823
- Wed Apr 17, 2019 12:51 pm
- Forum: macOS
- Topic: How to open an AUP file from the command line on macOS
- Replies: 20
- Views: 823
Re: How to open an AUP file from the command line on macOS
I've had a look into the code, and in AudacityApp::OnInit(), passing file list arguments via the command line is implemented for Windows and Linux only: Correct, so I removed this and recompiled on a mac to make it work for me. That's because it is working now for my case. As I said, must be a reas...
- Wed Apr 17, 2019 11:15 am
- Forum: macOS
- Topic: How to open an AUP file from the command line on macOS
- Replies: 20
- Views: 823
Re: How to open an AUP file from the command line on macOS
I did not understand the point, but the AUP location does not matter. I tried on various places.kozikowski wrote: ↑Wed Apr 17, 2019 4:15 amWhat happens if you place the show on the desktop? Do you get the same failures?
- Wed Apr 17, 2019 11:10 am
- Forum: macOS
- Topic: How to open an AUP file from the command line on macOS
- Replies: 20
- Views: 823
Re: How to open an AUP file from the command line on macOS
I explained before, I just want the macOS executable to open an AUP from the terminal just like it happens on Linux and WIndows. What information? Sorry, why does it matter? This is something very specific for my case... if I get some stdout info or if I verify the lack of it... I just need to open ...
- Wed Apr 17, 2019 1:30 am
- Forum: macOS
- Topic: How to open an AUP file from the command line on macOS
- Replies: 20
- Views: 823
Re: How to open an AUP file from the command line on macOS
In my case, I need some information Audacity's stdout provides while the aup is opened. But for you to understand, consider that I need to call audacity executable from the terminal and I need to know (the script needs to continue some tasks) after the project is closed. Just consider how it works o...
- Wed Apr 17, 2019 12:08 am
- Forum: macOS
- Topic: How to open an AUP file from the command line on macOS
- Replies: 20
- Views: 823
Re: How to open an AUP file from the command line on macOS
As I explained, open command will not work for me because it will just open the file and return to the terminal... I need the command to keep locked until I close the Audacity, just like Linux and Windows. But I found the source of this problem. In fact, for me it is a planned bug: https://github.co...