File name handling bug

[mpvano]

Hi!

I'd actually prefer to bring this up in the Behringer forum, since it affects a lot of users who aren't likely to chase down your github. Of course, that forum is now completely useless!

It would be great if you could figure a way to let users there know that they should workaround the problem until it can be fixed.

It's too bad that the new forum's designers seem to have missed the point of having a forum!

In any case:

I'm seeing a consistent error in the Macintosh version (at least) of X32Xlive_Wav where if a command line like:

 ~/bin/X32mac/X32Xlive_Wav  -n 32 -c 24  ../4E57ABA4/

is used to burst all files to 24 bit and place the results into the current directory, the resulting file names are all prepended with a '.' and become invisible!

Using the '-d .' option solves the problem, but the default for '-d' appears to be broken.

This is a bit confusing, of course, since the files are all created, but don't show up in the finder or in a normal ls command.

thanks again for a great utility and all your work.

[pmaillot]

Hello Thanks a lot! There's indeed a bug (I just forgot to give a default value to the output directory, oops!). Fixed it in the latest version (0.36) which I just uploaded. I'll tell the forum users as well. Thanks again, -Patrick Le mar. 26 févr. 2019 à 15:20, mpvano <notifications@github.com> a écrit :

…

Hi! I'd actually prefer to bring this up in the Behringer forum, since it affects a lot of users who aren't likely to chase down your github. Of course, that forum is now completely useless! It would be great if you could figure a way to let users there know that they should workaround the problem until it can be fixed. It's too bad that the new forum's designers seem to have missed the point of having a forum! In any case: I'm seeing a consistent error in the Macintosh version (at least) of X32Xlive_Wav where if a command line like: ~/bin/X32mac/X32Xlive_Wav -n 32 -c 24 ../4E57ABA4/ is used to burst all files to 24 bit and place the results into the current directory, the resulting file names are all prepended with a '.' and become invisible! Using the '-d .' option solves the problem, but the default for '-d' appears to be broken. This is a bit confusing, of course, since the files are all created, but don't show up in the finder or in a normal ls command. thanks again for a great utility and all your work. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#16>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APOZ_nohk_C8zO9jzgx1jeUETo1Y1FVgks5vRULAgaJpZM4bSSBm> .

[mpvano]

Thanks, I noticed it a while ago but forgot to report it. M

…

On Feb 26, 2019, at 9:25 AM, Patrick-Gilles Maillot ***@***.***> wrote: Hello Thanks a lot! There's indeed a bug (I just forgot to give a default value to the output directory, oops!). Fixed it in the latest version (0.36) which I just uploaded. I'll tell the forum users as well. Thanks again, -Patrick Le mar. 26 févr. 2019 à 15:20, mpvano ***@***.***> a écrit : > Hi! > > I'd actually prefer to bring this up in the Behringer forum, since it > affects a lot of users who aren't likely to chase down your github. Of > course, that forum is now completely useless! > > It would be great if you could figure a way to let users there know that > they should workaround the problem until it can be fixed. > > It's too bad that the new forum's designers seem to have missed the point > of having a forum! > > In any case: > > I'm seeing a consistent error in the Macintosh version (at least) of > X32Xlive_Wav where if a command line like: > > ~/bin/X32mac/X32Xlive_Wav -n 32 -c 24 ../4E57ABA4/ > > is used to burst all files to 24 bit and place the results into the > current directory, the resulting file names are all prepended with a '.' > and become invisible! > > Using the '-d .' option solves the problem, but the default for '-d' > appears to be broken. > > This is a bit confusing, of course, since the files are all created, but > don't show up in the finder or in a normal ls command. > > thanks again for a great utility and all your work. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#16>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/APOZ_nohk_C8zO9jzgx1jeUETo1Y1FVgks5vRULAgaJpZM4bSSBm> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.