-
Notifications
You must be signed in to change notification settings - Fork 1
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
output_dir
parameter ignored
#1
Comments
You are not using the bin2iso version from this github repo. Your output says:
If you were using this github repo, your output would say:
I tried your command line with the version from this github repo, and it produced the iso in the correct output directory, so i guess your bug only exists in the version of bin2iso you are using and not in the version from this repo. The same may apply to the other issues you opened. Can you please try again with the version from this repo? |
Hello, sorry for taking time to respond. Thanks for clarifying about the program version. For these issues I used the one from the AUR: https://aur.archlinux.org/packages/bin2iso But I'm afraid it also happens with the version from this repo, which I compiled. Please see my output below where the .iso should go into the
|
interesting. for "single track bin file indicated by cue file" bin2iso does a rename of .bin to .iso instead of outputting to output_dir, whcih it does for other cue-modes:
hard to tell, why this was intended. why that its just a renaming, so, no data loss. i guess the on could argue its not "nice" to change any original data/filename and this behavior could be changed, bin im not convinced we must do this, because other programs like still the output dir should be respected, also for a rename. |
Also a good question, why using bin2iso for this case, when you could just change the file ending, because in this case iso is identical to bin. |
Thanks for the reply. When I use |
Because it's impossible to know if the bin is a single track unless you first open and look at the cue file. And no one is going to look at the cue files ONE AT A TIME when you're operating on 100, 200 or 5000 files at one time, where some of them might be 1 track, a few hundred might be 2 tracks, a few hundred more might be 50 tracks, etc. I think the bottom line is that bin2iso is not suitable for PS1 or PS2 bin files. Not sure what's then it's useful for, maybe CD music files only? Or standard PC-based ISO that were saved as BIN by some ancient CD ripping app.
bchunk takes a long time by comparison (especially on spinning disks and VM), but as far as I know, it's the only command-line tool that works and that can be used in batch. Some people use Windows to do conversions, but I don't know of any program for Windows that can do more than 1 file at a time. It would take a few years to do a whole PS2 collection that way. Or longer. |
|
I didn't say it was slow, just that it took "a long time" - bin2iso is so fast I can't even measure the speed, and it does an entire folder of bins in a few seconds (of course it's useless because it doesn't work properly). So let's just say comparatively slower when looking at thousands of files. I've edited the previous post to make it clearer. 👌 As I'm working on a lot of files, I don't have them on any of my SSDs - right now they're on an UNRAID array and being processed by bchunk running inside an Ubuntu VM. On my M1 Mac, running with only SSD it takes about 5-8 seconds for 6 bin files totalling 2.6GB :) I think my Mac might be able to do more than 1000 files in the time it takes the VM to do 1. |
Unrelated: thank you for bringing up the slowness subject. It made me remember that I just added a USB3.1 PCIe card to my server which I can use to connect a portable SSD and then work on a batch of files using my Mac. Going to give that a try as the copying + conversion should still be much faster. |
I pass the
output_dir
parameter and yet the .iso is not written to there; the .iso is written to the current directory, which is the default.The text was updated successfully, but these errors were encountered: