Creative Commons Soundtracks: And Another 4 Weeks Worth

My project to take the free 8Pack released by Sony each week, to turn it into something else and then release it under the creative commons licence continues. I'm still not confident enough to think that they can stand alone but if you need a clip of music to back some video then I think they work and I have fun making them:
Suck It Up by the other Martin Taylor
Just Sit Back and Chill by the other Martin Taylor
Jigzag by the other Martin Taylor
Go With It Again by the other Martin Taylor

In addition I've been messing around with NanoStudio on my iPhone some more. These couple of tracks were also made with the intention of using them in video work and they're released under the same creative commons licence:
Go To Sleep by the other Martin Taylor 
The Return Trip Effect by the other Martin Taylor

Freesound: Give & Take

If you're a filmmaker at any level from just starting out to an industry expert you know that, in the edit process you always find a few sound effects, foley or ambient noises that you're missing. If you've been in that situation you've probably been to freesound.org. Freesound is a constantly growing library of Creative Commons licensed sounds. If you're looking for something their search engine usually returns a few hits of sounds that might be useful and it is often quicker and much more convenient than digging out your field recording equipment and hunting down the sound for yourself.

That said, I'm sure lots of us have a few eclectic sound recording languishing on our hard drives that we recorded for one project or another. If you have something you're willing to share the process of uploading them is a little geeky (ftp) but they do have a web interface too and it is a simple way of uploading a bunch of files at once. You simply upload your files, then describe and tag them and then wait a couple of days for them to be approved. What's in it for you? What goes around comes around and what good are those files you're hoarding especially if you're not going to use them again. I just uploaded some of the sounds I've collected in recent months and it felt good to share. I hope other filmmakers will consider doing the same and freesound will become an even more comprehensive and useful resource for everyone.

Skullcandy Hesh Headphones: Refinish

I have a slight headphone fetish. As I'm not encouraged to blast my music anymore I listen to music, write music, produce and edit video all while wearing headphone these days. I don't like in ear buds, I prefer big, over the ear headphones with my favorites being the chunky but beautifully solid and neutral Sennheiser HD 280's. As a result of this obsession I have several pairs of decent over the ear headphones lying around both at home and at work.

When I saw the Skullcandy Hesh Headphones in NBA Cavaliers Colors ridiculously cheap (they're usually $40-50) I couldn't resist. They had a built in iPhone microphone which I thought would be useful but I didn't like their paint job - I don't follow any American sport so I planned to refinish them.

This weekend I finally got chance to do that. Here's the process:

Disassembly:
  • Remove the earphone soft pads - they just pull off
  • Undo the 3 screws hidden under the ear pads
  • Separate the plastic holding the driver from the shell
  • Desolder the wires from the drivers (2 joints per driver) making a careful note of what goes were when we get back to reassembly.
  • Unscrew and remove the detail pieces in the shells (they were gold in my case).
  • Remove the connection cord from the left shell.
  • Carefully expand the c-brackets where the headband meets the shells and prize out the shells
Painting:
  • Using a fine sanding block, remove the existing paint from the exterior of both shells
  • Remove all dust then carefully spray paint the shells using several light coats
  • Let the paint cure at least for 24 hours
  • Using cutting compound, cut back the paint surface.
  • Polish the newly painted shell exteriors.
Assembly
  • Assembly is the reverse of disassembly.
  • Take care when soldering wires back in place.
  • All plastic components are labeled Left or Right somewhere in their molding
  • Take care not to scratch your new paint surface when reattaching the shells to the headband.
  • Drivers can only fit back in the shells one way, with the plastic lump towards the bottom.
  • When refitting the soft pads you can persuade the vinyl edge back into the crack between the shell and drivers with a blunt knife blade.

To complete the de-badging I also unpicked the badges from the fabric covering the headband. There you have it; slightly less obnoxious Skull Candy Hesh headphone but how do they perform?

You can tell the market these headphones are aimed at (not me); the headphones are very bass heavy. But it's not just the the bass is over powering the mids and highs - the mids and highs seem to be completely missing. Construction wise the Hesh plastic is very creaky which does affect your listening experience if you move your head at all while wearing them. Ear seals are far from perfect so they don't exclude as much of the outside world as you think they should. A cheap pair of Senneiser HD 202 headphone's easily out performs the Heshes acoustically. The Hesh headphones don't sound that bad if you haven't just been wearing good quality headphones. I do keep them around specifically for use with the iPhone as the cable fits with the bumper in place, they have an inline microphone and they do sound better than the apple included earphones.

Creative Commons Soundtracks: Another 6 Weeks Worth

I"m still continuing my project to take the free 8Pack released by Sony each week, to turn it into something else and then release it under the creative commons licence. As before, these pieces aren't meant to stand alone but be used in video or other media pieces for soundtracks, although I've yet to hear of anyone using them for that purpose but me. But even if I'm the only one using them they serve as a great learning opportunity - I'm now confident I can go in and make something appropriate for a scene in little time.

Ready? Set.... by the other Martin Taylor

Hot & Heavy by the other Martin Taylor

Backyard Siesta by the other Martin Taylor

Lose Changeling by the other Martin Taylor

Forbidden DMZ by the other Martin Taylor

Reabsorbing The Infinite by the other Martin Taylor


Sony Vegas Movie Studio Platinum: Render Error Still Occurs in v11

Update: Since I wrote this post I upgraded to Movie Studio Platinum 12 - the program has gone 64-bit which seems to answer this problem that we were experiencing in prior versions.

I am a huge fan of Sony Vegas Movie Studio Platinum. For the money (around $100) it is impossible to beat on the Windows platform. However, ever since I started using it 3 versions back it has been plagued by a bug that Sony are either unwilling, or unable to fix.

The problem occurs when you are trying to render HD video out above a certain, unknowable complexity on a 64 bit platform. The error you see when you're trying to render out (just before the application crashes) is "The system is low on memory. You may be able to reduce memory usage by closing other applications." I'm here to tell you it doesn't matter how many programs you close, once you hit the threshold and start seeing this error your video will not render. I am also here to tell you it is not an issue with the amount of memory you have in your machine (unless you have less than 3gb). I have 8gb memory in my Vista 64 bit desktop and 3gb in my Win 7 64 bit laptop and both were plagued by this issue trying to render the same project recently - the project had 6 video tracks and 8 audio, with effects on most clips and tracks but it was only three and a half minutes long.

First an introduction to some boring Windows fundamental architecture. 32bit versions of Windows can only use a maximum of 2gb of memory. 64bit versions are not restricted in the same way which is one reason geeks like 64bit systems. Unfortunately many consumer pieces of software are 32bit. Now, you can run a 32bit program on a 64bit version of Windows but it won't be able to use more than 2gb of memory itself. With me so far?

Sony Vegas Movie Studio Platinum is a 32bit program (Pro is 64bit) which runs well on 64 systems but has had this memory leak issue when rendering in all versions I can see to date. Basically the render process is using as much memory as it can get (2gb) but at some point it doesn't release a part of memory it has reserved - it then tries to get more memory and the crash occurs. Why Sony haven't fixed this issue is infuriating - I was sure they would have it done in version 11 but no; I installed the software and the bug was back.

Luckily for us there is a tried and tested way to address this issue that has been documented for previous versions of Movie Studio and this is my update to those instructions for v11.

  • Close Sony Vegas (if it hasn't already crashed on you.
  • Download and install CFF explorer from www.ntcore.com/exsuite.php.
  • Run CFFExplorer
  • File > Open "C:\Program Files (x86)\Sony\Vegas Movie Studio HD Platinum 11.0\VegasMovieStudioPE110.exe
  • In the left plane of CFF Explorer click NT Headers > File Headers
  • Bottom right of the resulting grid will read "Click here" - click there
  • In the resulting dialog window check "App can handle > 2gb address space" and then click "OK"
  • File > Save As and save the file to a local directory (somewhere in your documents or desktop)
  • Close the file in CFF explorer
  • In Windows file explorer make a copy of the original file you just opened (this is so, if things go wrong, you can get back to where you were)
  • In file explorer move the file you saved in a local directory over the one in the installed directory: whenever you try to copy or move a file in the installed directory Windows will probably ask you exactly what you want to do to try and stop you corrupting installed applications - Click "Move and Replace" and then hit "continue" if it says you need to confirm your administrator privileges. This may seem long winded but you have to get around Windows security that is trying to stop you messing up your system.
  • Repeat the CFF edit for the following files:
    • VegasMovieStudioPE110.exe (you just did this one)
    • vegasmoviestudiope110k.dll
    • all dlls in the FileIO Plug-Ins dirrectory - in my installation this was:
      • ac3studioplug\ac3studioplug.dll
      • aifplug\aifplug.dll
      • atracplug\atracplug.dll
      • aviplug\aviplug.dll
      • compoundplug\
        • compoundplug.dll
        • mc_dec_aac.dll
        • mc_dec_avc.dll
        • mc_enc_mp2v.dll
        • sonyjvtd.dll
        • sonymvd2pro_xp.dll
      • fhgaacplug2\fhgaacplug2.dll
      • flacplug\flacplug.dll
      • gifplug\gifplug.dll
      • lpecplug\lpecplug.dll
      • mcmp4plug2
        • mc_dec_aac.dll
        • mc_dec_avc.dll
        • mc_enc_aac.dll
        • mc_enc_avc.dll
        • mcmp4plug2.dll
      • mcplug2
        • mc_config_mp2m.dll
        • mc_config_mp2v.dll
        • mc_config_mpa.dll
        • mc_dec_dd.dll
        • mc_dec_mp2v.dll
        • mc_dec_mpa.dll
        • mc_demux_mp2.dll
        • mc_demux_mp4.dll
        • mc_demux_mxf.dll
        • mc_enc_mp2sr.dll
        • mc_enc_mp2v.dll
        • mc_enc_mpa.dll
        • mc_enc_pcm.dll
        • mc_mfimport.dll
        • mc_mux_mp2.dll
        • mc_mux_mp4.dll
        • mc_mux_mxf.dll
        • mcplug2.dll
      • mp3plug2\mp3plug2.dll
      • mp4plug3
        • aacaenc.dll
        • mp4plug3.dll
        • savce.dll
        • sgcudme.dll
        • sgocldme.dll
        • sgpuclb.dll
        • sony4vem.dll
      • mvcplug
        • mvcplug.dll
        • sonyjvtd.dll
      • oggplug\oggplug.dll
      • qt7plug\qt7plug.dll
      • rm9plug
        • rm9plug.dll
        • pncrt.dll
      • sfpaplug\sfpaplug.dll
      • stl2plg\stl2plg.dll
      • swfplug\swfplug.dll
      • wavplug\wavplug.dll
      • wicplug\wicplug.dll
      • wmfplug4\wmfplug4.dll
This fixed the crashes while rendering for me and I hope it works for you but if you're not comfortable messing around with dll files please be careful - you could do more harm than good .If you can't see the dll files of the folders they are in you may need to make hidden files visible. All the dlls in the file IO directory that I listed may seem like overkill but I just wanted to never face this error again ... until the next time when Sony release v12 and I've forgotten all about this pain. Then again, Sony might actually get its act together and fix this issue for us ... fat chance :)