Sunday, November 25, 2012

GaDaBaMa 3.1

Changelog
-Added SQL builder / Mass update function
-Added new SyncQueue form/ribbon

Err 2450 on JQE360.com functions happen when JQE360.com is offline - thanks for the bug reports

Friday, November 23, 2012

New functions for GaDaBaMa 3.0, coming soon!

SQL Builder: Mass-update/replace function!
This form allows to change all kind of values.

For example some games have as Developer XYZ inc and others just XYZ. With this form you can update all Games containing XYZ to XYZ inc with a few clicks!

Another example: You don't like TM, (R), (C) in Game names or phrases like (Online Interactions Not Rated by the ESRB) in descriptions, just manage the table tblReplacements accordingly or do it manually and mass-update!

To recover use F3db values. This will update your local table with the F3db values from the last sync. Don't need to connect your Xbox 360 HDD for that!

Here some screens





Sync Queue Enhanced!
Sync Queue functions are now integrated within the SQ-Ribbon. You can add the current game or all games to the Sync Queue and view/edit the Sync Queue through the sq-report (as before - with pictures / slow) or with the new sq-form (without pictures - fast)!


Trailers
You can now add files or links! Use to manual edit form.


GaDaBaMa 3.1 coming soon ...

Sunday, November 18, 2012

GaDaBaMa 3.0 for F3

Thanks goes to TeamFSD for the information provided on the .assets file!

 GaDaBaMa 3.0 has now been released. Please read Important_notes.pdf. Don't complain afterwards... It has been tested as good as possible. Due to time issues I'm not able to test it any further so there might be bugs.

MIGRATE FROM FSD2 TO F3 - IMPORTANT

SAMBA
Since GaDaBaMa 2.1 you need to disable this feature on the database you wish to sync and to enable it in another F3 application you use to connect with GaDaBaMa. Under Settings, enable Samba server.
If you’re successful, you’ll see clients connected: 1.
  • F3 App with all your content -> Samba disabled
  • F3 App – called Samba App -> Samba enabled
    (new install without scanpaths, games etc.)
Each time you wish to sync GaDaBaMa with your main F3 database you must enter your Samba App. This is done to prevent random errors while reading/writing the database. Of course if you connect your Xbox360 HDD through USB/eSATA you don’t need a Samba App, but you must disable Samba on your F3 App as it performs the check either way. I do not recommend syncing over SAMBA!

FILES
32/64bit
Only 32bit version supported. M$ recommends using 32 over 64 bit.

Changelog
  • Changed to F3 database

Infos
GaDaBaMa offers an alternate method to manage your F3 database.

Data functions
  • Import/Export content.db (settings.db) (F3)
  • Import dlc_report.txt/gameSave_report.txt (XM360)
  • Scan Content folder for dlc/gamesaves (x360pkgtool.exe)
  • Export dlc_titles.txt (XM360)
Online functions
  • Get Game/DLC info/images from xbox.com
  • Get boxarts/covers from covers.jqe360.com
  • Get title updates from marketplace.jqe360.com
Picture functions
  • Extract dds from .assets
  • Convert dds to jpg (irfanview)
  • Convert jpg to dds (nvdxt)
  • Convert png to dds (only for icons)
  • Create F3 .assets file

Video functions
  • Stream preview video (if available)

GUI functions
  • Coverflow
  • GameWall
  • Customized themes
  • Filter fields (alphabetic/genre/tabs)
  • Multilanguage thanks to all translators! + Google Translator
  • RSS feed
  • Screenshots Slideshow
  • Search field
  • ShortKeys

Use with caution!
GaDaBaMa syncs with following apps:
  • F3 rev058
  • XM360 2.0d (optional - use x360pkgtool.exe to scan Contents directly)

Please make sure you have these versions installed.
GaDaBaMa modifies content.db directly. This means
  • No content.db backup will be created
  • A faulty content.db or .assets files can cause F3 to crash and even prevent restarting

Please make sure you have a backup plan to access your console (over FTP), in case something happens.

Credits
  • GaDaBaMa DEV (GoodfellaKeyser)
  • dhSQLite (Olaf Schmidt)
  • IrfanView (Irfan Skiljan)
  • x360pkgtool (xorloser)
  • JQE360 (JQE)
  • Samba Team
  • TeamFSD
  • XM360 (node21)
  • AMIT betatester
  • ctm555 Swedish translation
  • darkmurf betatester, themes creator
  • GabLeRoux French translation
  • jappi88 Dutch translation
  • JaRaBcN betatester & Spanish translation
  • Jorge Carvalho Portuguese translation
  • Kysshin French translation
  • MADOFOCS betatester & German translation
  • MeLoS italian translation
  • robins Chinese translation
  • threesixtyuser Dutch translation
  • ZoMBYaKa Russian translation
Thanks to all TeamFSD forum members and bug reporters!
Special thanks to darkmurf

Thursday, November 15, 2012

GaDaBaMa 3.0 teaser


Brief demonstration. Scheduled to be released this week.



Tuesday, November 13, 2012

GaDaBaMa 3.0 for F3 – sync options, thinking out loud

Since F3 the images are saved/packed in a new file: GameDataFolder.assets

Overwrite if dds file newer
In GaDaBaMa 2.x for FSD2 there was an option to overwrite the file (image) if dds file was newer. That was useful when doing a full sync and became - from my point of view - obsolete when SyncQueue was introduced. This function used filedate to determine wether to overwrite or not.
As .assets files only contains the image data without creation dates it is not possible to check which file would be newer. So this option will be gone.

Save dds files locally
In GaDaBaMa 2.x for FSD2 there was an option to save the converted JPG files as DDS locally. F3 still uses DDS format but does not save them as individual files. It would make more sense to give an option to save the .assets file locally but then again all dds files within that .assets file would need to be extracted to rebuild a new file with the changes. Changes done in STEP3 automatically deleted the old converted DDS file. Saving .assets files locally is also not an option.

SyncQueue
My favourite way of syncing. But in F3 you can’t replace individual images. And to avoid blowing up the .assets file a rebuild of that file makes perfect sense.

F3 Sync
Because of that I’m thinking of using only one option to sync: SyncQueue + rebuild .assets file. To achieve a fast & practical sync I thought of this:
All images (JPG/PNG) in the SyncQueue are converted to DDS and saved locally (GaDaBaMa\DDS\GameId_Folder\*.dds). All files in that folder will be overwritten.

The.assets file header of the current game will be read and analyzed. Images that are not present in GaDaBaMa\DDS\GameId_Folder\*.dds will be extracted from the .assets file and saved locally.
All DDS files in the current game folder (GaDaBaMa\DDS\GameId_Folder\*.dds) will be packed in a new .assets file and saved (overwrite existing file) under F3\Data\GameData\GameId_Folder\GameId_folder.assets
  • Those having used GaDaBaMa since the beginning and saved all DDS files locally will certainly appreciate the fact that all previous work done was not in vain.
  • If you migrated to F3 through 2.2.1 you’ll see that each cover.dds was also saved this way.
  •  If you haven’t used GaDaBaMa before or you did not use the Save DDS locally option but you migrated to F3 through 2.2.1 you can copy FSD2\Data\GameData\*.* to GaDaBaMa\DDS\*.*. This way you’ll already have all images in DDS which have been used during migration to build .assets files. So next time you sync a game with new content there is no need for GaDaBaMa to extract those files from the .assets file.
Release date
STEP1/2/3 are already done. Build .assets file was already coded in the migration function. Extract images from .assets file is done as well. Only STEP4 is left. Comment if there is something I missed, otherwise I’ll proceed with STEP4 with the above logic.

Monday, November 12, 2012

GaDaBaMa 2.2.1

There was a nasty bug in 2.2:


That was because an unused Silverlight reference that was accidentally set during dev.

Get the latest version 2.2.1.

Thanks AMIT for the bug report.

Sunday, November 11, 2012

GaDaBaMa 2.2 FINAL





GaDaBaMa offers an alternate method to manage your FSD2 database and to migrate your FSD2 database to F3.

Data functions
  • Import/Export fsd2data.db (fsd2settings.db) (FSD2)
  • Import dlc_report.txt/gameSave_report.txt (XM360)
  • Scan Content folder for dlc/gamesaves (x360pkgtool.exe)
  • Export dlc_titles.txt (XM360)
  • Reorganize FSD2 database
  • Migrate FSD2 to F3

Online functions
  • Get Game/DLC info/images from xbox.com
  • Get boxarts/covers from covers.jqe360.com
  • Get title updates from marketplace.jqe.com

Picture functions
  • Convert dds to jpg (irfanview)
  • Convert jpg to dds (nvdxt)
  • Convert png to dds to blobs (only for icons)
  • Create F3 .assets file
Video functions
  • Stream preview video (if available)

GUI functions
  • Coverflow
  • GameWall
  • Customized themes
  • Filter fields (alphabetic/genre/tabs)
  • Multilanguage thanks to all translators!
  • RSS feed
  • Screenshots Slideshow
  • Search field
  • ShortKeys

Credits
  • GaDaBaMa DEV (GoodfellaKeyser)
  • dhSQLite (Olaf Schmidt)
  • IrfanView (Irfan Skiljan)
  • x360pkgtool (xorloser)
  • JQE360 (JQE)
  • Samba Team
  • TeamFSD
  • XM360 (node21)

  • ctm555 Swedish translation
  • darkmurf betatester, themes creator
  • GabLeRoux French translation
  • jappi88 Dutch translation
  • JaRaBcN betatester & Spanish translation
  • Jorge Carvalho Portuguese translation
  • Kysshin French translation
  • MADOFOCS betatester & German translation
  • MeLoS italian translation
  • robins Chinese translation
  • threesixtyuser Dutch translation
  • ZoMBYaKa Russian translation

Thanks to all TeamFSD forum members and bug reporters!
Special thanks to darkmurf.

Use with caution!
 GaDaBaMa syncs with following apps:
 - FSD2 2.2 rev 1072
 - F3 rev058 (migration function)
 - XM360 2.0d

 Please make sure you have these versions installed.

 GaDaBaMa modifies fsd2data.db directly. This means
 - No fsd2data.db backup will be created
 - A faulty fsd2data.db can cause FSD2 to crash and even prevent restarting

 Please make sure you have a backup plan to access your console (over FTP), in case something happens.

Performance

Performance check on USB 3.0
Creating .assets files with migration function for 3526 files (3.2 GB)

**************
S T A R T
11.11.2012 13:50:56
**************
pass > Import FSD2DATA.DB >
pass > content.db - content.backup >
pass > settings.db - settings.backup >
pass > Database operations: ContentItems >
pass > Database operations: ScanPaths >
pass > Database operations: Favorites >
pass > Database operations: UserRatings >
pass > Database operations: GlobalSettings >
pass > F3 Delete GameData contents >
pass > FSD2 Extract icons from database >
pass > GaDaBaMa Convert cover.jpg to cover.dds >
pass > Assets >
**************
E N D
11.11.2012 13:59:14
**************

Due to this outstanding result there will be no further optimizing.

Friday, November 9, 2012

How to migrate FSD2 to F3

Good news! The migration function works wonderfully even over Samba. I highly recommend connecting the Xbox HDD directly to the PC though...

Minor things must be corrected. Few other things must be tested. It is scheduled to be released this week.

Here the tutorial on how to do it. Subtitles will follow asap.
(consider: it shows the process and not the time it takes!)


Thanks to Blackmagic for this awesome recording device! Shame on you Micro$oft!  Shame on you Micro$oft!  Shame on you Micro$oft, for disabling HDMI recording!

Wednesday, November 7, 2012

Translation file for GaDaBaMa 2.2

As usual, here is the file with all available and missing translations for the upcoming release of GaDaBaMa 2.2.

Thanks for contributing.

Tuesday, November 6, 2012

Upcoming features in GaDaBaMa 2.2 Final

TreeView -  Works like a filter. 

New functions in Edit local database
- add current game to syncQueue
- create .assets file for FSD3 

Final version of migration form

To be released this week.

Monday, November 5, 2012

Migrate FSD2 to FSD3

As announced in this post GaDaBaMa 2.2 will have an option to migrate your FSD2 database/Game contents to FSD3.

The options in mind are these:


Please comment if you miss something. Thanks to TeamFSD for the information about the new .assets file!