Comments for Tastes Like Chicken http://dylanreeve.com Dylan Reeve, on the internet! Thu, 11 Mar 2010 01:01:52 +1300 http://wordpress.org/?v=2.8.5 hourly 1 Comment on Filtering The Internet by Thomas Beagle http://dylanreeve.com/general/2010/filtering-the-internet.html/comment-page-1#comment-755 Thomas Beagle Thu, 11 Mar 2010 01:01:52 +0000 http://dylanreeve.com/?p=206#comment-755 Sadly it seems that Orcon might be wavering now. http://computerworld.co.nz/news.nsf/security/new-zealands-internet-filter-goes-live Sadly it seems that Orcon might be wavering now.

http://computerworld.co.nz/news.nsf/security/new-zealands-internet-filter-goes-live

]]> Comment on Editor’s Swiss Army Knife by fcp swiss army apps http://dylanreeve.com/videotv/2010/editors-swiss-army-knife.html/comment-page-1#comment-734 fcp swiss army apps Wed, 03 Mar 2010 23:17:04 +0000 http://dylanreeve.com/?p=193#comment-734 [...] on this post by Dylan Reeve I have put together a list of mac apps that I carry around on a usb drive in order to get myself [...] [...] on this post by Dylan Reeve I have put together a list of mac apps that I carry around on a usb drive in order to get myself [...]

]]> Comment on Canon Rumours and the Future by Dylan http://dylanreeve.com/videotv/2010/canon-rumours-and-the-future.html/comment-page-1#comment-718 Dylan Wed, 24 Feb 2010 05:11:04 +0000 http://dylanreeve.com/?p=202#comment-718 Normally I'd agree with your argument about things like 28 Days - although there were a few shots in that I thought the DV simply couldn't deliver (the big wide shots basically). And the 5D is the same - with a good story to tell it can deliver pictures that will do the job. But the issues I am talking about are not just engineering bollocks that is only evident with resolution charts and test equipment - they are issues that will actually ruin otherwise good shots. Check out these examples: <a href="http://vimeo.com/6546960" rel="nofollow">Aliasing 1</a> <a href="http://vimeo.com/7443352" rel="nofollow">Aliasing 2</a> <a href="http://vimeo.com/5652416" rel="nofollow">Aliasing 3</a> These problems apparently aren't very evident on the LCD while shooting. In many cases there will be no issue, especially as the shallow depth of field tends to mean a lot of the frame is safely out of focus. However sharp detail, especially fine horizontal lines with high contrast can create very distracting movement in the frame. Like I say this is a problem I've already encountered in the real world with real footage for a real television show. It's acceptable when we're talking about a DSLR that shoots video, but not acceptable if that same tecnology were put into a "video" camera. Normally I’d agree with your argument about things like 28 Days – although there were a few shots in that I thought the DV simply couldn’t deliver (the big wide shots basically).

And the 5D is the same – with a good story to tell it can deliver pictures that will do the job.

But the issues I am talking about are not just engineering bollocks that is only evident with resolution charts and test equipment – they are issues that will actually ruin otherwise good shots.

Check out these examples:
Aliasing 1
Aliasing 2
Aliasing 3

These problems apparently aren’t very evident on the LCD while shooting. In many cases there will be no issue, especially as the shallow depth of field tends to mean a lot of the frame is safely out of focus. However sharp detail, especially fine horizontal lines with high contrast can create very distracting movement in the frame.

Like I say this is a problem I’ve already encountered in the real world with real footage for a real television show.

It’s acceptable when we’re talking about a DSLR that shoots video, but not acceptable if that same tecnology were put into a “video” camera.

]]> Comment on Canon Rumours and the Future by Morgan Nichol http://dylanreeve.com/videotv/2010/canon-rumours-and-the-future.html/comment-page-1#comment-717 Morgan Nichol Wed, 24 Feb 2010 02:11:03 +0000 http://dylanreeve.com/?p=202#comment-717 <em>The concerns of real users and engineers do intersect.</em> Depends on who you mean by 'real users', if you mean editors then perhaps you're right, if you mean special effects folks, then you're definitely right, but if you mean viewers, then they really don't. Many viewers can't even tell the difference between SD & HD. Some will care about how stable the shot is (see complaints about Cloverfield, Bourne, and such) but they don't give a shit about much else at all - have a look at 28 Days Later, no one complained about the picture quality, and some of it was shot on DV! Clean sound is more important than the fineries of the picture (beyond a certain baseline anyway) for many things, and sound is easy to solve, even with the crappiest of cameras. The concerns of real users and engineers do intersect.

Depends on who you mean by ‘real users’, if you mean editors then perhaps you’re right, if you mean special effects folks, then you’re definitely right, but if you mean viewers, then they really don’t.

Many viewers can’t even tell the difference between SD & HD. Some will care about how stable the shot is (see complaints about Cloverfield, Bourne, and such) but they don’t give a shit about much else at all – have a look at 28 Days Later, no one complained about the picture quality, and some of it was shot on DV!

Clean sound is more important than the fineries of the picture (beyond a certain baseline anyway) for many things, and sound is easy to solve, even with the crappiest of cameras.

]]> Comment on Canon Rumours and the Future by Dylan http://dylanreeve.com/videotv/2010/canon-rumours-and-the-future.html/comment-page-1#comment-716 Dylan Tue, 23 Feb 2010 23:55:45 +0000 http://dylanreeve.com/?p=202#comment-716 The concerns of real users and engineers do intersect. Having already encountered serious aliasing and moire in real world scenarios with 5D footage it is something that can and does bite people in the ass. And it's often the sort of problem you don't notice until you review the footage later (big problem if you're relying on the shot and have broken down the setup already). Metadata? No Orsen Welles probably wouldn't give a shit, but his editor and his editor's assistant would probably be a little annoyed. With the exception of the problems incurred from the sensor limitations all of these things can be worked around. It'd be better not to have to work around them of course, but while the sensor is limited and there is no video lens options there is not really much point in Canon making a 'video camera' with the technology. The concerns of real users and engineers do intersect. Having already encountered serious aliasing and moire in real world scenarios with 5D footage it is something that can and does bite people in the ass. And it’s often the sort of problem you don’t notice until you review the footage later (big problem if you’re relying on the shot and have broken down the setup already).

Metadata? No Orsen Welles probably wouldn’t give a shit, but his editor and his editor’s assistant would probably be a little annoyed.

With the exception of the problems incurred from the sensor limitations all of these things can be worked around. It’d be better not to have to work around them of course, but while the sensor is limited and there is no video lens options there is not really much point in Canon making a ‘video camera’ with the technology.

]]> Comment on Canon Rumours and the Future by Morgan Nichol http://dylanreeve.com/videotv/2010/canon-rumours-and-the-future.html/comment-page-1#comment-715 Morgan Nichol Tue, 23 Feb 2010 22:45:28 +0000 http://dylanreeve.com/?p=202#comment-715 These pedantic technical issues may be important to engineers, but not terribly much to anyone else. Never mind some moire issue, what people now have (fairly easy) access to is a better movie camera than anyone in the first three generations of filmmakers could get their hands on - whatever the budget. You think Orson Welles would have given two shits about metadata? It's too bad Canon have such a broad range of video cameras already, as they're clearly quite concerned about damaging that part of their business by expanding the DSLRs to too great an extent, so I expect advances will be quite slow - much slower than their technical capabilities in any case. <em>the cameras have no professional audio inputs and some serious ergonomic issues</em> But does it really matter when a Zoom H4N can be picked up so cheaply? These pedantic technical issues may be important to engineers, but not terribly much to anyone else.

Never mind some moire issue, what people now have (fairly easy) access to is a better movie camera than anyone in the first three generations of filmmakers could get their hands on – whatever the budget. You think Orson Welles would have given two shits about metadata?

It’s too bad Canon have such a broad range of video cameras already, as they’re clearly quite concerned about damaging that part of their business by expanding the DSLRs to too great an extent, so I expect advances will be quite slow – much slower than their technical capabilities in any case.

the cameras have no professional audio inputs and some serious ergonomic issues

But does it really matter when a Zoom H4N can be picked up so cheaply?

]]> Comment on Canon Rumours and the Future by Matt Dwen http://dylanreeve.com/videotv/2010/canon-rumours-and-the-future.html/comment-page-1#comment-714 Matt Dwen Tue, 23 Feb 2010 19:16:47 +0000 http://dylanreeve.com/?p=202#comment-714 FFS, they're stills cameras. People need to stop being greedy and expect everything out of a $2K DSLR body. FFS, they’re stills cameras. People need to stop being greedy and expect everything out of a $2K DSLR body.

]]> Comment on The Apple Codec Problem by Andy http://dylanreeve.com/videotv/2010/the-apple-codec-problem.html/comment-page-1#comment-705 Andy Thu, 18 Feb 2010 07:37:09 +0000 http://dylanreeve.com/?p=197#comment-705 Hey Dylan Just wanted to note that in the case of IMX/FCP then there is also the option of rewrapping clip's that are in Quicktime's .mov container back to the more universally compatible MXF container format, using Sony's free Export > Sony XDCAM... method. Best Andy Hey Dylan
Just wanted to note that in the case of IMX/FCP then there is also the option of rewrapping clip’s that are in Quicktime’s .mov container back to the more universally compatible MXF container format, using Sony’s free Export > Sony XDCAM… method.
Best
Andy

]]> Comment on Editor’s Swiss Army Knife by Zak Ray http://dylanreeve.com/videotv/2010/editors-swiss-army-knife.html/comment-page-1#comment-704 Zak Ray Sun, 14 Feb 2010 19:02:26 +0000 http://dylanreeve.com/?p=193#comment-704 These are all for Mac, but most have Windows counterparts. AJA Data Rate Calculator.app AJA System Test.app AppleProResQuickTimeDecoder.pkg aspectRatio.app AvidCodecsLE.pkg BatchReformat'em.app Carbon Copy Cloner.app Celtx.app ClipBrowserForMacV2_5_0.zip Compressor Repair.app Disksomnia 2.0.mpkg DPX4MacQuickLook.A0004-0.1.dmg FCP HDV to ProRes Easy Setups My own FCP plugins FCS Remover.app FCS Utility v1.1.app ffmpegX.app Final Cut Assistant.app Flip4Mac WMV.mpkg FxFactory Freebies.fxpack HandBrake.app HD Speed Test.app Install FxFactory 2.pkg Install x264 Codec.pkg JES_Deinterlacer_v3.5.3 Levelator.app Max.app MPEG Streamclip.app Name Mangler.app P2CMSInstaller.pkg Perian_1.1.4.dmg Pixie.app Preference Manager.app simpleBIT-Budget.app Sony Recording Unit.pkg Sound Grinder 3.3.9c Subtitle Xtractor 0.2.0.app SxS_Device_Driver_Mac_v1_0_34300.dmg SyncTwoFolders.app UnRarX.app VideoSpec.app VLC (64-bit): VLC.app XDCAM Transfer 2.10.mpkg XDCAM_EX_Log_and_Transfer_Plugin_1_0_0.dmg These are all for Mac, but most have Windows counterparts.

AJA Data Rate Calculator.app
AJA System Test.app
AppleProResQuickTimeDecoder.pkg
aspectRatio.app
AvidCodecsLE.pkg
BatchReformat’em.app
Carbon Copy Cloner.app
Celtx.app
ClipBrowserForMacV2_5_0.zip
Compressor Repair.app
Disksomnia 2.0.mpkg
DPX4MacQuickLook.A0004-0.1.dmg
FCP HDV to ProRes Easy Setups
My own FCP plugins
FCS Remover.app
FCS Utility v1.1.app
ffmpegX.app
Final Cut Assistant.app
Flip4Mac WMV.mpkg
FxFactory Freebies.fxpack
HandBrake.app
HD Speed Test.app
Install FxFactory 2.pkg
Install x264 Codec.pkg
JES_Deinterlacer_v3.5.3
Levelator.app
Max.app
MPEG Streamclip.app
Name Mangler.app
P2CMSInstaller.pkg
Perian_1.1.4.dmg
Pixie.app
Preference Manager.app
simpleBIT-Budget.app
Sony Recording Unit.pkg
Sound Grinder 3.3.9c
Subtitle Xtractor 0.2.0.app
SxS_Device_Driver_Mac_v1_0_34300.dmg
SyncTwoFolders.app
UnRarX.app
VideoSpec.app
VLC (64-bit):
VLC.app
XDCAM Transfer 2.10.mpkg
XDCAM_EX_Log_and_Transfer_Plugin_1_0_0.dmg

]]> Comment on Network Rendering with MetaFuze by The Editblog » Valentine’s Day Linkage: February 2010 http://dylanreeve.com/videotv/2010/network-rendering-with-metafuze.html/comment-page-1#comment-703 The Editblog » Valentine’s Day Linkage: February 2010 Sun, 14 Feb 2010 17:42:34 +0000 http://dylanreeve.com/?p=189#comment-703 [...] If you’re interesting in network rendering with Avid Metafuze check this out. [...] [...] If you’re interesting in network rendering with Avid Metafuze check this out. [...]

]]>