All times are UTC

 
 



Post new topic Reply to topic  [ 40 posts ]  Go to page Previous  1, 2, 3
Author Message
 Post subject: Re: Decoding ALS file format
PostPosted: Wed Sep 19, 2012 10:06 pm 

Joined: Thu Dec 29, 2011 9:56 pm
Posts: 13
Location: Sydney
Send me the als file (via the aatranslator web site) and I will see what I can do (no promises).

_________________
http://www.aatranslator.com.au


Top
 Profile  
 
 Post subject: Re: Decoding ALS file format
PostPosted: Sat Apr 20, 2013 5:54 am 

Joined: Wed May 03, 2006 7:15 am
Posts: 524
any luck with .adg files as well?

_________________
Load VST Presets from Push's Browser!
http://www.audiomodder.com


Top
 Profile  
 
 Post subject: Re: Decoding ALS file format
PostPosted: Sat Apr 20, 2013 6:12 am 

Joined: Thu Dec 29, 2011 9:56 pm
Posts: 13
Location: Sydney
queglay wrote:
any luck with .adg files as well?


We have the ALS files down pat - what does the .adg file do?
Send me one of these files and I will check it out

Send it via the aatranslator web site

_________________
http://www.aatranslator.com.au


Top
 Profile  
 
 Post subject: Re: Decoding ALS file format
PostPosted: Sat Apr 20, 2013 7:01 am 

Joined: Wed May 03, 2006 7:15 am
Posts: 524
.adg files are ableton library presets. my idea is to batch generate .adg files for all the native instruments presets, or any vst for that matter so push will play nice with its own library. I'm starting with massive.

I loaded a preset in massive called additivum, then grouped it to save it as a .adg instrument rack.
Extracting the .gz and then opening the xml file reveals the meat of the vst data is stored under the vst preset buffer in the xml.

This buffer section (for the preset called additivum) is 8.5k. And the the .nmsv massive preset file for additivum is also 8.5k
This is great news, cant be too far off...I ran a diff using hexfiend on osx and there are about 130 differences between these two. im not sure where to go from here. pretty sure if i just copied the .nmsv file into there without more formatting it would break.

_________________
Load VST Presets from Push's Browser!
http://www.audiomodder.com


Top
 Profile  
 
 Post subject: Re: Decoding ALS file format
PostPosted: Sat Apr 20, 2013 3:02 pm 

Joined: Thu Dec 29, 2011 9:56 pm
Posts: 13
Location: Sydney
Sorry - the .arg file is outside the scope of my current workload which is daw format conversion

_________________
http://www.aatranslator.com.au


Top
 Profile  
 
 Post subject: Re: Decoding ALS file format
PostPosted: Sun Apr 21, 2013 12:50 pm 

Joined: Wed May 03, 2006 7:15 am
Posts: 524
I've got two files. the first is the vst buffer extracted form the xml. the second is the nmsv file (the preset). they are super close. 137 differences between the two using a hex difference. and similar file size, but not the same.

I had a crack at just pasting in the nmsv straight back into the xml, but it didn't work. i guess i need to understand what the differences are and start to figure out a method of patching.

A great deal of it is readable as acii, but there a bunch of weirdass characters still and im not sure how to interpret what they are all doing.

_________________
Load VST Presets from Push's Browser!
http://www.audiomodder.com


Top
 Profile  
 
 Post subject: Re: Decoding ALS file format
PostPosted: Sat Jun 01, 2013 5:20 pm 

Joined: Sat Jun 01, 2013 5:13 pm
Posts: 7
Hi yall,
I am interesting with the preview sound of a adg file in a pack. I want to use it as a clip.
So I did my research, learned that adg files are compressed xml binary files containing information that might be useful.
So i applied the gzip xxx.adg > xxx.xml in my MBP terminal.
I got a xxx.xml in the folder but it is Zero octet. The adg files is 29Ko.
I dont get why my xml is empty?

Any clue?
Thanx

Peace Out

DukePack


Top
 Profile  
 
 Post subject: Re: Decoding ALS file format
PostPosted: Mon Feb 12, 2018 10:14 am 

Joined: Sat Jan 14, 2017 8:19 pm
Posts: 12
dr_rock wrote:
I know I'm pretty late to the discussion here, but I was just playing with ALS files and discovered they are gzipped XML files. To decompress them you'll need a tool that can handle gzip. My suggestion is to copy the ALS file then decompress with your favorite tool. If you don't know what you're doing with gzip you may permanently damage your ALS files. Use at your own risk.

On Mac OS X you could simply open Terminal, cd to the file location, and execute this: gzip -cd MySong.als > MySong.xml

They are pretty large and complex XML files. For instance, the default template is 2,082 lines, and a simple live set of mine was over 43,000 lines of XML - but the format is very readable and clear. Their engineers obviously know how to write solid code. They are German after all. ;)

Here's a snip to give you an idea of what's in there:

Code:
<?xml version="1.0" encoding="UTF-8"?>
<Ableton MajorVersion="4" MinorVersion="8.1_225">
   <LiveSet>
      <OverwriteProtectionNumber Value="5" />
      <Tracks>
         <AudioTrack Id="0">
            <EnvelopeModePreferred Value="false" />
            <TrackDelay>
               <Value Value="0" />
               <IsValueSampleBased Value="false" />
            </TrackDelay>
            <Name>
               <UserName Value="Guitar 1" />
               <Annotation Value="" />
            </Name>
            <ColorIndex Value="140" />
            <TrackGroupId Value="-1" />
            <SavedPlayingSlot Value="-1" />
            <SavedPlayingOffset Value="0" />
            <MidiFoldIn Value="false" />
            <MidiPrelisten Value="false" />
            <Freeze Value="false" />
            <VelocityDetail Value="0" />
            <NeedArrangerRefreeze Value="true" />
            <PostProcessFreezeClips Value="0" />
            <MidiTargetPrefersFoldOrIsNotUniform Value="false" />
            <DeviceChain> ... </DeviceChain>


Etc. The <DeviceChain> tag is by far the largest, as it contains the ClipSlot values, gobs of info for each plugin including each parameter and some type of serialized buffer content (big blocks of hexadecimal values).


Hi,

Is there any clue on how to work this around live 9 or 10 .als files?

I maneged to recover few live sets that got deleted accidentaly, when loading them up I get the corrupted file error ¨unknown compound stream type¨ and since I just have a trial license of live I can´t contact suport.
I found a post online that covers my issue and explains this same stuff, just can´t get the sets uncompressed in order to edit them.
I´m pretty sure this live sets were made with live 9.7.4

Here is the post I found: http://news.metaparadigma.de/ableton-ma ... iles-4423/
I´m asking to much here, I know, any hint would be truly apprecieted.


Top
 Profile  
 
 Post subject: Re: Decoding ALS file format
PostPosted: Tue Feb 13, 2018 1:44 am 

Joined: Mon Apr 26, 2010 6:38 am
Posts: 2354
How many projects could you have possibly created that need to be rescued using the 30 day demo?

_________________
Freelance SoundLabs


Top
 Profile  
 
 Post subject: Re: Decoding ALS file format
PostPosted: Tue Feb 13, 2018 9:30 am 

Joined: Sat Jan 14, 2017 8:19 pm
Posts: 12
jestermgee wrote:
How many projects could you have possibly created that need to be rescued using the 30 day demo?


Just enough, I think nobody likes to waste time on a project and, what's worse, having time counted, you wouldn't understand it, would you?

In any case, the method described above works on other projects of mine, I guess the corrupted files were overwritten before I could rescue them and as a result got seriously damaged.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 40 posts ]  Go to page Previous  1, 2, 3

All times are UTC

 
 

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group