About SeeDeClip

History

1. A few years ago now a strange 'buzzing' from the HiFi was heard when playing CDs. Speakers, connections and wires were all checked, amplifiers were changed but all was well. Then it became clear that LPs and all older CDs played perfectly, only the modern CDs buzzed.
   
   Eventually the search ended at the DAC/CD combination when it was discovered that the (pro-audio) DAC was sensitive to DAC overload when it was fed from modern CDs. The problem became clear when the CD was ripped and then examined with Audacity, exposing the full horror and scale of the problem.
   
   
2. CuteStudio's initial TxtDeClip was originally a text-only command line program created to fix this problem in WAV files, which could easily be ripped from the offending CDs.
   
   
3. SeeDeClip3 was the first commercial graphical/batch product to roll out this fix. It was great for fixing WAV collections for later listening and repairing the odd track that was mistakenly clipped during recording, it's saved a few projects around the world.
   
   
4. As music collections grow one ends up with a variety of file formats, duplicates, and the actual daily access to that collection becomes occasional and limited. Plus all of the tunes downloaded from iTunes/Amazon etc are still clipped. So this unsatisfactory condition prompted the writing of SeeDeClip4, to fulfill basic requirement most people have:
   
   To be able to access your entire music library from any device at the best possible quality.
   
   To achieve this requires:
   
   • Networking and outputting text, graphs, images and audio on a wide variety of devices.
     
   • The proper app for this is a web browser, i.e. SeeDeClip now had to become a web program.
     
   • ..but it still has to function like a modern app.
     
   • ..and being a webserver makes it multi-user and multi-tasking.
     
   
   
   SeeDeClip4 is a major jump forward in both audio and software technology.
   

Architecture

• The first thing to note is that the program is threaded - i.e. it does a number of things at the same time, so imagine it as a teaming hive of choreographed activity that only stops when you pause the music.
  
  
• All web traffic is buffered in FIFOs, so stuff can be written out around the time new stuff is still being generated. Outgoing FIFOs are throttled to prevent memory exhaustion, so when a 1GB stream is requested and you press 'pause' the task is halted for a while, rather than letting that 1GB build up in memory. These general purpose FIFOs are also used for base64 and json I/O.
  
  
• Behind each page the CTL scripting system interfaces to the core modules. One such module is 'control' that manages each control, option and value, and custom items like graphs. This text is managed by the 'text' module.
  
  
• Caching is fundamental to the system. All audio data is segmented and managed via this cache. The cache is a single, thread aware, manager that manages around 5 different actual caches, e.g. the imported files, META data, segments, analysis results.
  
  
• The declipper sits in the middle behind a 'processed segment' cache aquire, getting raw audio from the 'raw segment' cache as demanded. It has a single job - to fixing clipping damage.
  
  
• Note the 'meta' box, SeeDeClip directly reads file meta data (artwork or embedded artist/album/track name text) and does not use external importers for this. Importers are purely for audio data.
  

Client-server

The Server

The Client

Updating

1. seedeclip4 boot manager
   
2. seedeclip4 installer
   

Technical FAQ