64-bit Windows 8 : "freaccmd -track 4-7 -o fourtracks.mp3" prints the usage and exits, just as if no args had been given. I've looked at the code and tried every permutation of arguments I can think of.
The problem was due to the tracks argument not being parsed because of too late initialization of CD drives. It is now fixed in CVS and will be fixed in the next snapshot.
If you need a patched exe now, please tell me if you are using the 32 or 64 bit version and I will attach it here.
Please note that your syntax is supposed to work with fre:ac snapshots only - not 1.0.21. Also, you should specify the codec on the command line using "-e LAME".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2013-07-18
Robert,
Thanks very much for your quick attention to this. If you would be so kind as to send a 64-bit freaccmd.exe, I would be very grateful. I had gone down the path of trying to build a 64-bit smooth/freac from CVS , but why does smooth still want libunicows?
Yours most cordially,
Frank Wilhoit
.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here's the fix for the 20130430 64 bit version. It's actually the freac.dll file you need to exchange.
If smooth complained about missing Unicows, you were actually compiling a 32 bit version. The 32 bit version needs Unicows, because it still supports Windows 9x/ME.
To compile smooth and fre:ac on your own, it's best to use the fre:ac CDK (Component Development Kit). It includes a minimal GCC setup that has everything necessary. I also use the CDK for development and for official builds.
I applied this patch, but am having an issue with this version of freaccmd compared to the 32 bit version included with the "freac-1.0.21a.exe" installer. The 20130430 version ("freac-20130430-windows-x64.zip") doesn't want to run when accessed outside the executable's directory.
Basically, this works with the 32 bit version in 1.0.21a:
Nice, a patch for both the 32 and 64 bit windows versions. I patched both versions and can confirm the patches took care of the problems listed above, at least on my machine.
For anyone else interested in applying applying these, the fixes are for the 20130430 snapshots; that's the "freac-20130430-windows.zip" and "freac-20130430-windows-x64.zip" binaries. Do not use either of these to replace the files included with "freac-1.0.20a" (unless you want to break your install like I did).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for reporting this!
The problem was due to the tracks argument not being parsed because of too late initialization of CD drives. It is now fixed in CVS and will be fixed in the next snapshot.
If you need a patched exe now, please tell me if you are using the 32 or 64 bit version and I will attach it here.
Please note that your syntax is supposed to work with fre:ac snapshots only - not 1.0.21. Also, you should specify the codec on the command line using "-e LAME".
Robert,
Thanks very much for your quick attention to this. If you would be so kind as to send a 64-bit freaccmd.exe, I would be very grateful. I had gone down the path of trying to build a 64-bit smooth/freac from CVS , but why does smooth still want libunicows?
Yours most cordially,
Frank Wilhoit
.
Here's the fix for the 20130430 64 bit version. It's actually the freac.dll file you need to exchange.
If smooth complained about missing Unicows, you were actually compiling a 32 bit version. The 32 bit version needs Unicows, because it still supports Windows 9x/ME.
To compile smooth and fre:ac on your own, it's best to use the fre:ac CDK (Component Development Kit). It includes a minimal GCC setup that has everything necessary. I also use the CDK for development and for official builds.
As the patch is available in CVS, I'm setting this ticket to pending. It will be closed once the next snapshot including the fix is released.
I applied this patch, but am having an issue with this version of freaccmd compared to the 32 bit version included with the "freac-1.0.21a.exe" installer. The 20130430 version ("freac-20130430-windows-x64.zip") doesn't want to run when accessed outside the executable's directory.
Basically, this works with the 32 bit version in 1.0.21a:
Running the same command with the 64 bit 20130430 snapshot (after applying the patch file listed above):
I receive 2 error popups with the message:
If I run the command from inside the freac directory, freaccmd seems to run as expected:
edit: fixed file name mixup
Last edit: phosgram 2013-08-11
Thanks for reporting this!
Here's a new patch that fixes both problems.
Nice, a patch for both the 32 and 64 bit windows versions. I patched both versions and can confirm the patches took care of the problems listed above, at least on my machine.
For anyone else interested in applying applying these, the fixes are for the 20130430 snapshots; that's the "freac-20130430-windows.zip" and "freac-20130430-windows-x64.zip" binaries. Do not use either of these to replace the files included with "freac-1.0.20a" (unless you want to break your install like I did).
This should now be fixed in the 20131217 snapshot.