Sound Packager Update
Thursday, October 4, 2007 by Philly0381 | Discussion: OS Customization
Can the sounds under Sound Schemes be used or do they need to be converted or changed to work?
Reply #2 Thursday, October 4, 2007 11:40 AM
Reply #3 Thursday, October 4, 2007 11:43 AM
I like the addition of the password protection option! How does the "Allow users to copy this Package work"? What happens if it's unchecked?
Out of curiosity, does the backup restore process use the Keepsafe framework?
Last thing (at the moment), on the left pane, the icon next to Welcome seems like a better fit for Packages. No?
Otherwise . . it's working well and my only complait is that so many actions on my PC complete before the sounds are done playing. DOH!!
Reply #4 Thursday, October 4, 2007 11:49 AM
Sound schemes are the MS Windows product. You can get Sound Packager themes in th Sound Packager gallery.
Download and they should be associated to Sound Packager and you don't have to do anything.
I misunderstood what you wanted to do. I thought you wanted to make a theme that used the MS Sound Scheme sounds. My mistake, sorry.
Reply #5 Thursday, October 4, 2007 11:55 AM
Reply #6 Thursday, October 4, 2007 12:10 PM
OK, extract them any place you want. Use Soundpackager to create a new package, import those sounds, and then assign to a specific event. Save and you are done.
That's what I would do.
Otherwise, you can save the folder anywhere and use the MS sound thing in control panel to assign each sound.
Using SP make everything more portable.
Reply #8 Thursday, October 4, 2007 12:49 PM
Interesting suggestion. It's currently our contention that the 'Windows Default' and 'None' settings for Sound Schemes are in fact, system default settings, and don't fall under the guise of 'Sound Packages'. Which is why we created the buttons to revert back to those system defaults. The functionality is there, its compact and easy to use and get to. Simply click on the Advanced tab and youre in business.
I like the addition of the password protection option! How does the "Allow users to copy this Package work"? What happens if it's unchecked?
The copy package prevention was a feature that was requested in order to keep people from making copies from within the UI of the application. The default is unchecked (freely allowing people to make as many copies of a package as they like). It will probably be used more frequently in conjuction with the Password protection.
Out of curiosity, does the backup restore process use the Keepsafe framework?
No, it doesnt. The backup process is very very custom. There's a lot going on behind the scenes to ensure proper backups and restores.
Last thing (at the moment), on the left pane, the icon next to Welcome seems like a better fit for Packages. No?
I would disagree 
Reply #9 Thursday, October 4, 2007 1:20 PM
Does uninstalling SoundPackager and reinstalling it get them back?
Reply #10 Thursday, October 4, 2007 1:23 PM
Reply #11 Thursday, October 4, 2007 2:01 PM
Reply #12 Thursday, October 4, 2007 2:30 PM
Reply #13 Thursday, October 4, 2007 2:40 PM
-- [Application] ----------------------------------------------------
Name: Stardock Central
Path: C:\Program Files\Stardock\SDCentral
Version: 2.48.485, build: 160
-- [System Information] ---------------------------------------------
Platform: Microsoft Windows Windows NT4, 6.0.6000
Display: Radeon X1650 Series
Driver Version: 8.380.0.0
System Dir: C:\Windows\system32
Time / Date: 06:34:33 -- Thursday, October 04, 2007
-- [Installing] -----------------------------------------------------
Server: http://sdc2.stardock.com
Server Dir: public
Network Id: odnt
Name: SoundPackager [Beta]
App Id: snd
Installed: True
Version: 0.95[b].014
Type: beta
Reg Key: SoundPackager
Install Dir: C:\Program Files\Stardock\Object Desktop\SoundPackager
Exe: SoundPackager.exe
Last Updated: 10/03/2007
-- [Account] --------------------------------------------------------
. . .
-- [Installation] ---------------------------------------------------
. . .
Extract: C:\Users\ZubaZ\AppData\Local\Temp\sdcentral\PublicDocuments\Stardock\SoundPackager\Basketball.soundpack_ 1 | 10/03/2007 08:04
Extract: C:\Users\ZubaZ\AppData\Local\Temp\sdcentral\PublicDocuments\Stardock\SoundPackager\Football.soundpack_ 1 | 10/03/2007 08:04ments and Settings\Aaron\Documents\Stardock\SoundPackager\Football.soundpack 1 | 09/11/2007 15:13
. . .
Move: C:\Users\Public\Documents\Stardock\SoundPackager\Basketball.soundpack 1 | 10/03/2007 13:04
Move: C:\Users\Public\Documents\Stardock\SoundPackager\Football.soundpack 1 | 10/03/2007 13:04
Delete: D:\Documents and Settings\Aaron\Documents\Stardock\SoundPackager\Basketball.soundpack 1
Delete: D:\Documents and Settings\Aaron\Documents\Stardock\SoundPackager\Football.soundpack 1
. . .
But no football pack there. I did find it here though: C:\Users\Public\Documents\Stardock\SoundPackager
All my other packages (self-made and downloaded) are located here: D:\Documents and Settings\Aaron\Documents\Stardock\SoundPackager
Reply #14 Thursday, October 4, 2007 2:47 PM
Reply #15 Thursday, October 4, 2007 10:43 PM
Reply #16 Thursday, October 4, 2007 11:28 PM
OK, we understand the code path that resulted in this from the update. SoundPackager has been setup to copy the packages from the master all users directory to allow other users on the system the option of editing the packages under their user accounts and not impacting other users on the machine.
However, in this build, that was triggered to only be on new installs rather than updates. So when the directories for the sound packs switched to the new location with the beta, the target local user dir already existed and it didn't recopy the updated "master" set of packages.
We'll adjust the build next week to account for updating those "master" set of included packages under various local users if they are updated. Until then, if you updated from the previous beta, you'll need to copy them to your user's Documents\Stardock\SoundPackager dir from the AllUsers\Documents\Stardock\SoundPackager location.
Technically, the beta is working as designed. We need to tweak the design.
ty for the log, Philly0381.
Kris
Reply #19 Sunday, October 7, 2007 8:09 PM
Reply #20 Sunday, October 7, 2007 8:52 PM
On install it should be moved.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #1 Thursday, October 4, 2007 11:26 AM
---------------------------------
Sound Packages default to installation to the AllUsers\Documents\Stardock\SoundPackager directory. They are copied from there to the local user documents directory when SoundPackager is run. That way, if different users on the PC modify an existing package, they are modifying their local copy vs the master downloaded one.
ADD: Packages can now be removed with option to remove them from the list (into a 'Removed' directory) or delete them outright.
ADD: Currently applied package now displayed on the Welcome page.
ADD: Packages are now automatically backed up.
ADD: Packages can be restored from backups if you've made changes..
ADD: Packages directory can be chosen by the user.
ADD: Added Advanced tab and page.
MOD: Updated dialog text throughout.
MOD: 'Disable All Sounds' and 'Restore Windows Default Sounds' buttons moved to Advanced page.
MOD: Removed 'Company' from package spec.
MOD: 'Import Sounds' and 'Set All to Default' buttons are now hidden on Package Details tab.
MOD: SoundPackage will only default to the Welcome page on first run. Subsequent runs will default to the Packages page.
MOD: Replaced 'Loding Packages..' animation with actual display progress bar.
FIX: 'Restore Windows Default Sounds' on Vista now functional.
FIX: Non-PCM WAV files will not play, and will not crash the application.
FIX: Fixed alignment of version string in the Packages list.
FIX: If no version string has been set in the package, the version does not display.
FIX: Package load time improved.
FIX: XP defaults to Tahoma font, Vista defaults to Segeo UI.
It is so very cool how SD listens to their users!
To philly's point, I also lost those two schemes. A update process bug? I kept all teh other thems I'd downloaded or created.
You can use all the sounds in the default sound scheme but they need to be imported. You can grab them from C:\Windows\Media on Vista and XP.