You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested the tool that comes with latest r3631. Here below what i found.
Windows:
now it works even if it requires to be run from a cmd administrator prompt
It is very very slow.
The .orgue package is created even if a strange error on organindex.ini is found (unknown filetype).
Linux (Raspbian):
it works like in the past
It is very very slow.
The .orgue package is created even if a strange error on organindex.ini is found (unknown filetype).
I guess the real issue is that it is too much slow. If it remains like so, it is going not to be used as it would take hours and hours and hours to generate the package as compared to wavpack.exe that can be called from batch script.
Note: in case it could help... version 3.5.0.1 didnt show the 'unknown filetype error on organindex.ini. It worked fine under Linux even if other errors arised (see last screenrecord).
The text was updated successfully, but these errors were encountered:
I tested the tool that comes with latest r3631. Here below what i found.
Windows:
now it works even if it requires to be run from a cmd administrator prompt
It is very very slow.
The .orgue package is created even if a strange error on organindex.ini is found (unknown filetype).
Linux (Raspbian):
it works like in the past
It is very very slow.
The .orgue package is created even if a strange error on organindex.ini is found (unknown filetype).
I guess the real issue is that it is too much slow. If it remains like so, it is going not to be used as it would take hours and hours and hours to generate the package as compared to wavpack.exe that can be called from batch script.
Note: in case it could help... version 3.5.0.1 didnt show the 'unknown filetype error on organindex.ini. It worked fine under Linux even if other errors arised (see last screenrecord).
The text was updated successfully, but these errors were encountered: