FreQi
8th April 2003, 06:11
Note: I tried searching for posts similar to this, but forum search seems to be borked atm.
After playing around with BeSplit (and BeSweet) for a few days, I've come accross what seems to be a bug in the display system of BeSplit. If you try to use "Fix File", and the filename (including the dirctory, drive letter and .ac3 extension) is longer then 54 characters, BeSplit will continuously scroll a new "Writing" line for every fraction of a second that is being processed. This seems to horribly lag the program.
To test this, I took an AC3 file that was 21min 22sec long, and put it in two directories. The first one was in a dir with a really long name, the second one was in the root of the same hard drive. The first "fix" of it took nearly 3 mins to process, but when that same file was in the root, it was only 4 seconds. My logs are below.
BeSplit v0.82 by DSPguru.
--------------------------
Logging start : 04/07/03 , 23:38:51.
C:\Program Files\BeSliced\BeSplit.exe -core( -input D:\hd.streams\this is a long ass dir name to mess with besplit\file.ac3 -prefix D:\hd.streams\this is a long ass dir name to mess with besplit\file_Fixed -fix -logfile C:\DOCUME~1\FREQI~1.REG\LOCALS~1\Temp\BeSliced.txt -type ac3 ) -profile( BeSliced v0.2 )
[00:00:00:000] +------- BeSplit -----
[00:00:00:000] | Input : D:\hd.streams\this is a long ass dir name to mess with besplit\file.ac3
[00:00:00:000] | Output Prefix : D:\hd.streams\this is a long ass dir name to mess with besplit\file_Fixed
[00:00:00:000] +---------------------
[00:00:00:032] Stream error : Sync found after 1334 bytes
[00:07:28:896] Stream error : Sync found after 962 bytes
[00:13:02:208] Stream error : Sync found after 1311 bytes
[00:20:25:152] Stream error : Sync found after 2405 bytes
[00:21:22:016] | Writing D:\hd.streams\this is a long ass dir name to mess with besplit\file_Fixed01.ac3
[00:21:22:016] +---------------------
[00:21:22:016] Operation Completed !
[00:02:59:000] <-- Process Duration
Logging ends : 04/07/03 , 23:41:50.
BeSplit v0.82 by DSPguru.
--------------------------
Logging start : 04/07/03 , 23:42:28.
C:\Program Files\BeSliced\BeSplit.exe -core( -input D:\file.ac3 -prefix D:\file_Fixed -fix -logfile C:\DOCUME~1\FREQI~1.REG\LOCALS~1\Temp\BeSliced.txt -type ac3 ) -profile( BeSliced v0.2 )
[00:00:00:000] +------- BeSplit -----
[00:00:00:000] | Input : D:\file.ac3
[00:00:00:000] | Output Prefix : D:\file_Fixed
[00:00:00:000] +---------------------
[00:00:00:032] Stream error : Sync found after 1334 bytes
[00:07:28:896] Stream error : Sync found after 962 bytes
[00:13:02:208] Stream error : Sync found after 1311 bytes
[00:20:25:152] Stream error : Sync found after 2405 bytes
[00:21:22:016] | Writing D:\file_Fixed01.ac3
[00:21:22:016] +---------------------
[00:21:22:016] Operation Completed !
[00:00:04:000] <-- Process Duration
Logging ends : 04/07/03 , 23:42:32.
I figured I'd post this for DSPguru to find whenever he returns... Thanks for the tools ;]
After playing around with BeSplit (and BeSweet) for a few days, I've come accross what seems to be a bug in the display system of BeSplit. If you try to use "Fix File", and the filename (including the dirctory, drive letter and .ac3 extension) is longer then 54 characters, BeSplit will continuously scroll a new "Writing" line for every fraction of a second that is being processed. This seems to horribly lag the program.
To test this, I took an AC3 file that was 21min 22sec long, and put it in two directories. The first one was in a dir with a really long name, the second one was in the root of the same hard drive. The first "fix" of it took nearly 3 mins to process, but when that same file was in the root, it was only 4 seconds. My logs are below.
BeSplit v0.82 by DSPguru.
--------------------------
Logging start : 04/07/03 , 23:38:51.
C:\Program Files\BeSliced\BeSplit.exe -core( -input D:\hd.streams\this is a long ass dir name to mess with besplit\file.ac3 -prefix D:\hd.streams\this is a long ass dir name to mess with besplit\file_Fixed -fix -logfile C:\DOCUME~1\FREQI~1.REG\LOCALS~1\Temp\BeSliced.txt -type ac3 ) -profile( BeSliced v0.2 )
[00:00:00:000] +------- BeSplit -----
[00:00:00:000] | Input : D:\hd.streams\this is a long ass dir name to mess with besplit\file.ac3
[00:00:00:000] | Output Prefix : D:\hd.streams\this is a long ass dir name to mess with besplit\file_Fixed
[00:00:00:000] +---------------------
[00:00:00:032] Stream error : Sync found after 1334 bytes
[00:07:28:896] Stream error : Sync found after 962 bytes
[00:13:02:208] Stream error : Sync found after 1311 bytes
[00:20:25:152] Stream error : Sync found after 2405 bytes
[00:21:22:016] | Writing D:\hd.streams\this is a long ass dir name to mess with besplit\file_Fixed01.ac3
[00:21:22:016] +---------------------
[00:21:22:016] Operation Completed !
[00:02:59:000] <-- Process Duration
Logging ends : 04/07/03 , 23:41:50.
BeSplit v0.82 by DSPguru.
--------------------------
Logging start : 04/07/03 , 23:42:28.
C:\Program Files\BeSliced\BeSplit.exe -core( -input D:\file.ac3 -prefix D:\file_Fixed -fix -logfile C:\DOCUME~1\FREQI~1.REG\LOCALS~1\Temp\BeSliced.txt -type ac3 ) -profile( BeSliced v0.2 )
[00:00:00:000] +------- BeSplit -----
[00:00:00:000] | Input : D:\file.ac3
[00:00:00:000] | Output Prefix : D:\file_Fixed
[00:00:00:000] +---------------------
[00:00:00:032] Stream error : Sync found after 1334 bytes
[00:07:28:896] Stream error : Sync found after 962 bytes
[00:13:02:208] Stream error : Sync found after 1311 bytes
[00:20:25:152] Stream error : Sync found after 2405 bytes
[00:21:22:016] | Writing D:\file_Fixed01.ac3
[00:21:22:016] +---------------------
[00:21:22:016] Operation Completed !
[00:00:04:000] <-- Process Duration
Logging ends : 04/07/03 , 23:42:32.
I figured I'd post this for DSPguru to find whenever he returns... Thanks for the tools ;]