Skip to content
View in the app

A better way to browse. Learn more.

ResHax

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Help us keep the site running.

Ghost in the Shell

Featured Replies

  • Author
  • Localization

GoodConduct, posted Fri Jan 20, 2017 10:32 am (20308)


So I was trying to get the sounds for Ghost in the shell Online using FSBext and it seems like I ran into problems when trying to play OGG files. The WAV's that were extracted work like a charm. However, the OGG's do not. I was wondering if there was any way to get the OGG's to work by converting them or giving them a header or would I have to wait until a fix is found for OGG's to work? The FSBext works like a charm on extracting them, but WAV's play and OGG's don't. I heard that I can try attaching an -a to the FSBext but I am not fully sure on how to do that and if it would even work.

The FSB that contains the files is encrypted as well, unsure on how to unencrypt them to try extracting with another program.

Update: I tried using another extraction program that was recommended for extracting sound. However, when trying to drag and drop the file it doesn't extract. When doing it with what I believe is non-encrypted FSB files then sound extracts.
  • Author
  • Localization

brendan19, posted Sat Jan 21, 2017 5:22 pm (20318)


FSBExt cannot properly add a header to the OGG files. You'll need to use id-daemon's tool to transcode them to .WAV from the .FSB container.

There is a tool out there that can extract .ogg files with a header from an FSB, but you need to build it yourself I believe.
  • Author
  • Localization

AnonBaiter, posted Sat Jan 21, 2017 6:20 pm (20319)


Google "phyton-fsb5". You need Phyton 3 to run it if you want your OGG headers.
  • Author
  • Localization

GoodConduct, posted Sat Jan 21, 2017 7:27 pm (20320)


It won't allow me to do this since the files are encrypted. With FSBEXT it allows me to extract the files, however with any other tool it just opens and closes, my main guess is due to it being encrypted. FSBext extracts all the wav's and are able to be played, however id-daemons tool doesn't ask for the encryption password which is why it cannot extract the ogg files. That is pretty much the only part that I am stuck on is the encryption check.
  • Author
  • Localization

brendan19, posted Sun Jan 22, 2017 8:19 pm (20355)


Can you post a sample FSB?

If this is from GitS: Stand Alone Complex - First Assault currently in open beta, the encryption key for the FSB files is

Code:
%lAn2{Pi*Lhw3T}@7*!kV=?qS$@iNlJ
as aluigi has already identified that.

Unless they've changed it.
  • Author
  • Localization

GoodConduct, posted Sun Jan 22, 2017 11:53 pm (20359)


brendan19 wrote:
Can you post a sample FSB?

If this is from GitS: Stand Alone Complex - First Assault currently in open beta, the encryption key for the FSB files is

Code:
%lAn2{Pi*Lhw3T}@7*!kV=?qS$@iNlJ
as aluigi has already identified that.

Unless they've changed it.


That works, the tool Aluigi has is able to accept the code and extract the files, however as we know it won't allow for OGG's to be played. Id-Daemons tool works for unencrypted FSB's however when it comes to the GITs FSB it won't extract anything. Which is where I am stuck, id-daemon's tool won't extract the ogg's and convert them because of the encryption. Aluigi's tool will extract them, however it cannot extract the ogg's into a playable media. I was wondering if there was a way to possibly get pass the encryption to allow for daemon's tool to extract the ogg's into a playable format.
Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.