-
YouTube, Video making and editing, etc. coupled to excelfox ( windows Movie Maker )
Thread 2936 https://www.excelfox.com/forum/showt...-Movie-Maker-)
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)
This is post #post23586
https://www.excelfox.com/forum/showt...ll=1#post23586
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23586&viewfull=1#post23586
https://www.excelfox.com/forum/showt...er-)#post23586
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23586
Microsoft windows movie makers
History Introduction
Depending on the time and interest you have for getting clued up on Microsoft windows movie maker, you may want to read more or less of the information here. The index / contents list may help you decide if you want to read all, or skip to some part.
Regardless, it is important to know that there are a few versions and forms and a historical story and the usual Microsoft product confusion caused by their characteristic of changing things a lot. It is advisable therefore to make some attempt to read the first few history posts, and if you think you already have Microsoft windows movie maker is to check what version you have.
Be careful not to take a lot of notice of, or put too much significance to, uses of terms like, new, old, Live, Classic, since the confusing history means that a lot of people lost the orientation and don’t know what they are talking about regarding different versions.
What version have you got?
Get movie maker running somehow, and
_ if you have an "older" version, then at the top header tabs you may see something like Help or a question mark ?
https://i.postimg.cc/cLBn21bT/Help.jpg , https://i.postimg.cc/TPTpSQCB/GB-Mov...stion-Mark.jpg https://i.postimg.cc/ts7JVbyV/Help.jpg https://i.postimg.cc/HrPY80Gt/GB-Mov...stion-Mark.jpg
If you click on that to get a drop down list then you should see towards the bottom something of the form About Windows Movie Maker or Info
https://i.postimg.cc/tCPPdNdK/About-...ovie-Maker.jpg https://i.postimg.cc/cLRvXPMQ/GB-Movie-Maker-Info.jpg https://i.postimg.cc/0bkbPmBn/About-...ovie-Maker.jpg https://i.postimg.cc/YvS2SnP9/GB-Movie-Maker-Info.jpg
_ In "newer" versions, (mostly characterised by a ribbon at the top), this sort of information is often hidden down the drop down list coming from the top right header tab
https://i.postimg.cc/pV3zn6jQ/About-Movie-Maker.jpg https://i.postimg.cc/23FVsT23/About-Movie-Maker.jpg
Once you have found the About Windows Movie Maker. option, then click on it and make a note of the version you have
https://i.postimg.cc/Qd37fK0H/Version-Number.jpg https://i.postimg.cc/43wmTt0y/GB-Mov...rsion-Info.jpg
https://i.postimg.cc/Qd37fK0H/Version-Number.jpg https://i.postimg.cc/43wmTt0y/GB-Mov...rsion-Info.jpg
More advanced version Comparisons:
For more detailed version checks and comparisons, see here
If you are pushed for time, I would never the less recommend reading the next post. That will take you as far as the older, classic stable versions up to around 2007. ( most typically versions starting with numbers of 2.1 , 6, 2.6 – and note that strange sequence order that I listed is deliberate… Once you get clued up on the confusing history, then you will know why. . )
Based on my experiences and researches so far I would avoid the "newer" stuff, coming from around 2009 + (things that may be wrapped in things going by names including words like "Live" or "Essentials", ( mostly version starting with numbers or 2009 2011 2012 ). If you are looking at these "newer" versions then I would strongly advise reading a lot further, after which you may decide to think again, or at least will be armed with enough knowlwwegde to avoid wasting time with a lot of pit falls and problems that catch you out.
Index / Contents
-
History Introduction Summarised
This is post #post 23587
https://www.excelfox.com/forum/showt...ll=1#post23587
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23587&viewfull=1#post23587
https://www.excelfox.com/forum/showt...er-)#post23587
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23587
Movie maker History
Summarised History, (Not Complete) Initial versions History, 1 - 6
There is a bit of overlap, and as often with Microsoft Version Histories, there is confusion and disagreement. The following is the best average I have so far. The (date stamps) are my best average so far and are intended as an approximate time line. Changing when things occurred is something Microsoft cannot change, even if they try with documentation manipulation, so referring to a version by the year it came about and/ or was in common use, is probably the best way to try and not lose your orientation. (Treat any dates or version numbers you see on any third party available downloads of the original windows movie maker with some scepticism: For both legitimate reasons, ( the offered software may have received legitimate updates on the computer it was taken from), and because of some nasty scams with some offered downloads.)
Towards the end and further I attempt to relate the history to the Operating System History. This is handy to know even way into any later Windows Movie Maker usage, since, as with many things Microsoft, a reconditioned older computer often has a better chance to work with some useful stable software from the past. Microsoft seem to be on a crusade to mess you up.
There is some overlap in my Tutorial posts. This reflects both the overlaps and confusion generally in Windows Movie Maker history, as well as making some attempt to make the individual post of some use on their own so that as a compromise you can take a post relevant to your version if you don’t have the time to read through everything
(2000) - Version 1.0 https://i.postimg.cc/8csCfWf2/Movie-Maker-Version-1.jpg https://i.postimg.cc/m1f40Pwj/Movie-Maker-Version-1.jpg
The first release of Windows Movie Maker was included with Windows Me on September 14, 2000 (ME build 2416 https://betawiki.net/wiki/Windows_Me_build_2416 ) . Windows 2000 did not have it, but it could be copied** successfully to it. (** see xxxxxxx )
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP a year later, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2. From about the Service Pack 2 is generally what is regarded as the start of "modern" windows computing, but as I have tried to get across, it's all a bit cloudy
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. ( After the development reset, the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg https://i.postimg.cc/pyg1QpKD/50euro-keks-MM.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
(2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
https://i.postimg.cc/23RzWFyz/GB-Movie-Maker-6.jpg
https://i.postimg.cc/y3j44R05/GB-Movie-Maker-6.jpg
So that was an introduction, going up to around the Vista time. Up to this time Movie Maker was generally a version bundled into an operating system, (although as mentioned, it could often be easily added to operating system’s not having a particular version)
(Around 2007, Microsoft went backwards a bit, giving version 2.6, a refurbished 2.1 – 2.5 version)
From windows 7, it was mostly something to download.
We have approximately got to the point at this stage , typical in Microsoft, an intermediate period stage, where things got newer and in many user’s opinions, worse.
But, as mentioned, in the case of Movie Maker, things are a bit blurred. Not criticising necessarily, just saying. If you keep your wits about you , then you can pick out good stuff from around this period
Attempt to order into Windows Versions
The following 3 posts order Movie Maker approximately into the three main Windows versions which officially supported Movie Maker. ( These posts also are reused to act as an introduction to more pages and notes on specific versions instillations, and some notes on experiments and problems with downloads etc. )
XP era https://www.excelfox.com/forum/showt...er-)#post23588 ( Page #2 https://www.excelfox.com/forum/showt...-Maker-)/page2 )
Vista era https://www.excelfox.com/forum/showt...er-)#post23589 ( Page #3 https://www.excelfox.com/forum/showt...-Maker-)/page3 )
Windows 7 + era https://www.excelfox.com/forum/showt...er-)#post23590
( 2009 https://www.excelfox.com/forum/showt...-Maker-)/page4
https://www.excelfox.com/forum/showt...age4#post23811
2011 https://www.excelfox.com/forum/showt...-Maker-)/page5
https://www.excelfox.com/forum/showt...age5#post23823
2012 https://www.excelfox.com/forum/showt...-Maker-)/page6
https://www.excelfox.com/forum/showt...age6#post23835 )
-
XP era versions
Page 3
This post is https://www.excelfox.com/forum/showt...l=1#post235888 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23588&viewfull=1#post23588
https://www.excelfox.com/forum/showt...er-)#post23588 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23588
XP era versions
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the version 2 – version 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. After the development reset, (the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
( (2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself. https://i.postimg.cc/23RzWFyz/GB-Movie-Maker-6.jpg
https://i.postimg.cc/y3j44R05/GB-Movie-Maker-6.jpg
It included new effects and transitions, support for playback on the Xbox 360,and support for the DVR-MS file format that Windows Media Center records television in. The HD version in Premium and Ultimate editions of Windows Vista also added support for capturing from HDV camcorders. The capture wizard also created DVR-MS type files from HDV tapes. However, the Windows Vista version of Windows Movie Maker removed support for importing video from an analog video source such as an analog camcorder, VCR or from a webcam. There is no "2.7 XP version". People may incorrectly be referring to the Windows Vista version of Windows Movie Maker 2.6 that is basically a CPU-only version using the XP code for those on Vista that didn't have a powerful enough GPU. As some older systems might not be able to run the new version of Windows Movie Maker. Vista at the end of the final pre-release development stages may also have been code-named 2.7 )
(2007) - Version 2.6 https://i.postimg.cc/HLxZ8ksq/Version-2-6.jpg
https://i.postimg.cc/SnB7wq9d/Version-2-6.jpg
So, Microsoft also released an updated older version 2.6 for Windows Vista on Microsoft Download Centre, possibly around 2007-2009. This version is basically the same as Windows Movie Maker 2.1 and included all of the old effects and transitions, but it excludes the ability to capture video. It can only be installed on Windows Vista and is only intended for use on computers where the hardware-accelerated version cannot run. 2.6 is very similar to 2.5, as it was, or at least is often referred to as, a refurbished XP version 2.5
(2008) - Version 2009
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up…
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
As for the "Windows Live" version, A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. Windows Live Movie Maker 2009 is officially the last version to support Windows XP, ( Windows Live Photo Gallery version 14.0.8117.416 )
-
Vista era versions
This post is https://www.excelfox.com/forum/showt...l=1#post235889 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23589&viewfull=1#post23589
https://www.excelfox.com/forum/showt...er-)#post23589 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23589
Vista era versions
( (2006) - Version 6.0 ( 2.7 )
The first next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself. https://i.postimg.cc/23RzWFyz/GB-Movie-Maker-6.jpg
https://i.postimg.cc/y3j44R05/GB-Movie-Maker-6.jpg
It included new effects and transitions, support for playback on the Xbox 360,and support for the DVR-MS file format that Windows Media Center records television in. The HD version in Premium and Ultimate editions of Windows Vista also added support for capturing from HDV camcorders. The capture wizard also created DVR-MS type files from HDV tapes. However, the Windows Vista version of Windows Movie Maker removed support for importing video from an analog video source such as an analog camcorder, VCR or from a webcam. There is no "2.7 XP version". People may incorrectly be referring to the Windows Vista version of Windows Movie Maker 2.6 that is basically a CPU-only version using the XP code for those on Vista that didn't have a powerful enough GPU. As some older systems might not be able to run the new version of Windows Movie Maker. Vista at the end of the final pre-release development stages may also have been code-named 2.7 )
(2007) - Version 2.6 https://i.postimg.cc/HLxZ8ksq/Version-2-6.jpg
https://i.postimg.cc/SnB7wq9d/Version-2-6.jpg
So, Microsoft also released an updated older version 2.6 for Windows Vista on Microsoft Download Centre, possibly around 2006 - 2007. This version is basically the same as Windows Movie Maker 2.1 and included all of the old effects and transitions, but it excludes the ability to capture video. It can only be installed on Windows Vista and is only intended for use on computers where the hardware-accelerated version cannot run. 2.6 is very similar to 2.5, as it was, or at least is often referred to as, a refurbished XP version 2.5
(2008) - Version 2009
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up…
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
This was supplied as a download, from which you could, amongst other things, install "Windows Live" version of movie maker https://i.postimg.cc/hjBqj42L/Window...-installer.jpg
As for the "Windows Live" version of movie maker , A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. ( Windows Live Movie Maker 2009 is officially the last version to support Windows XP , ( Windows Live Photo Gallery version 14.0.8117.416 ) )
This version shows interface changes including ribbon similar to that starting in Microsoft Office in 2007.
This version added functions like "Auto Movie" which can convert a Video directly to YouTube or DVDs
https://i.postimg.cc/7hq9bjvt/Window...Maker-2009.jpg https://i.postimg.cc/ygrcbQ80/Window...Maker-2009.jpg
-
Windows 7 + era versions
This post is https://www.excelfox.com/forum/showt...l=1#post235890 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23590&viewfull=1#post23590
https://www.excelfox.com/forum/showt...er-)#post23590 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23590
Windows 7 + era versions
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up… From windows 7, Movie maker was officially mostly bundled inside something to be downloaded, although it is not clear if there may have been a standalone initial version, perhaps in an overlap period
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
As for the "Windows Live" version, A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. Windows Live Movie Maker 2009 is last version to support Windows XP, ( Windows Live Photo Gallery version 14.0.8117.416 )
Live Movie Maker 2009 supported both Windows Vista and Windows 7. About this time, 2009, Windows Movie Maker was no longer included with the operating system, which most likely means Vista will usually have Movie Maker, and a small chance it might also have Windows Live. I appear to have both on a Vista machine from new, ( it is showing as Windows Live Essentials 2011 https://i.postimg.cc/x8vVRv9Z/Window...nstllation.jpg )
https://i.postimg.cc/7hq9bjvt/Window...Maker-2009.jpg https://i.postimg.cc/ygrcbQ80/Window...Maker-2009.jpg
(2010) - Version 2011
The only way to obtain Live Movie Maker on Windows 7 from this time and later was through the Windows Live Essentials suite, although some manufacturers pre-installed the application on new PCs.
An updated version , Windows Live Movie Maker 2011, was released on August 17, 2010, adding features such as webcam capture, support for high-definition video, the ability to upload videos directly to SkyDrive, Facebook, and YouTube through their respective web APIs, and the ability to add media files stored on network shares to projects .
Windows Essentials 2011, Released on 30 September 2010, "Windows Live Essentials 2011" runs on Windows Vista or later. Accordingly, it runs successfully on Windows 10 (just the same as any other 32-bit program
(So Windows Movie Maker was known as Windows Live Movie Maker for the 2009 and 2011 releases)
https://postimg.cc/sMSHvPb4
https://i.postimg.cc/sMSHvPb4/Window...Maker-2011.jpg
(2012) - Version 2012 2012.1
Windows Essentials 2012 ( discontinuation of the Windows Live brand (and the re-branding of the Windows Live suite as Windows Essentials )
With the discontinuation of the Windows Live brand (and the re-branding of the Windows Live suite as Windows Essentials , Windows Movie Maker 2012 was released in April 2012. Support for recording voice-overs was restored, along with an audio mixer and integration with several free stock music services. H.264/MP4 became the default export format (replacing Windows Media Video, but still can be used), support for uploading to Vimeo was introduced (other sites were added to the list in the Windows 8.1 release of the suite), and hardware accelerated video pila stabilisation was also added as an exclusive feature for Windows 8 users.
So the last version was Movie Maker 2012 (they dropped the "Live" branding, so it makes for confusion with the much earlier original Movie Maker ).
Windows Essentials 2012 was last updated in April 2014, support ended in 2017, it was removed for download on January 10, 2017.
https://i.postimg.cc/0y1MM0Dg/Window...Maker-2012.jpg
https://i.postimg.cc/gn4k1Rg4/Window...Maker-2012.jpg
My best guess, just my opinion, is that Movie Maker was stopped as it was not reaching out to people and using them in the way that Microsoft had hoped. Movie maker is still regarded by many people as very good, but not at the top end of what is currently available.
Ref
https://www.youtube.com/watch?v=0ltJ...LIm9xI-2ZpVF-q
-
-
-
-
-
-
2 Attachment(s)
This is post#post23768
https://www.excelfox.com/forum/showt...age2#post23768
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2#post23768
Some macro refinements: Explorer view
Recap: Simple coding
In the simplest initial coding pairs, the second macro presented in each column a file item from the main Movie Maker folder. The results as presented are perhaps as we might perceive them, all as it were, "at the same level".
https://i.postimg.cc/j26gmtNm/Versio...ub-folders.jpg
https://i.postimg.cc/j26gmtNm/Versio...ub-folders.jpg
Applying the advanced recursion coding to the same gives this:
https://i.postimg.cc/ZnyR2Mgd/Versio...ub-folders.jpg
https://i.postimg.cc/ct008Xdx/Versio...ub-folders.jpg
https://i.postimg.cc/ZnyR2Mgd/Versio...ub-folders.jpg
That is OK, but it might be helpful if we had some way to get a view more of the windows explorer / "full levels type", whereby we could see more clearly which sub folders or main folder the files and sub folders are in.
https://i.postimg.cc/m2C3FXDk/Explor...evels-view.jpg
https://i.postimg.cc/XpNBRg96/Explor...evels-view.jpg
In general, I find it useful to have some indication, perhaps a simple number count in a number variable, of which copy level of the recursion / reoccurring routine is working at any time. Important to avoid confusion here is that I am not saying here a number to indicate how many times the recursion coding is used, but rather which copy level. In other words a number which both increases in value every time the recursion code is run and decreases every time the current running copy of the recursion coding ends
( We may in addition want to keep another number in a variable that increases every time something is done. In our example this would be the column count, Clm , as we use this to read the results across the page )
Reasons for keeping a count of things:
_ One reason is for debugging purposes: the usual F8 debug step mode can be misleading for the case of a recursion. The reason for this is that we don’t actually ever see the code lines that we are running in step mode, even though that is often said that we do that, and it is easy to believe. We are actually stepping through some low level coding or low level compiled coding that we can’t see, and just for our convenience, the written text of the coding we wrote is highlighted in yellow to give us an idea of what code part is being executed. This can confuse for the case of recursion as we see only being used the same recursion coding text, so we don’t know which copy of the recursion coding is in use, and may think we are always using the same highlighted coding, but this would only be the case if no sub levels ( sub folders in our case ). (Check the coding shown here: - In F8 debug step mode, we would not be shown the full coding which is actually used. When in step mode you get to the code line that sets of another copy, what should happen at that point in order to make a clear indication of what is going on, is that another copy appears and you continue going down. But what actually happens is that you appear to jump back to the start of the recursion coding as if you were looping it. That’s wrong. You are not looping it. You are starting a new copy of it whilst you pause the previous one )
_ Another reason is that if the macro is giving you some output in a worksheet, as in our case, then this number can be used to offset the cell used in some way convenient to show the explorer level type structure.
It’s very simple to add the necessary code lines to keep track of this code copy number, and, as I routinely do in recursion coding, I have already put them in
Private Sub ReoccurringFileFolderProps(ByVal Pf As String)
Rem 0
Let Reocopy = Reocopy + 1 ' Originally the variable Reocopy is zero. It will become 1 on first entering the macro. Every time we leave this macro, this number is reduced by 1 So in simple use it will be 1 or zero indicating that a copy is in use. However, should this macro "Call itself", before its finished , ( the recursion idea ) then the value will be 2 and so on. So effectively it tells us which copy is running at any time
Let Reocopy = Reocopy - 1 ' We are finished at this point with this running copy of the macro. (The next code line ends it). This code line here will reduce the value used to keep track of the copy number being run
End Sub
How to use Reocopy to give a more useful level / code copy output
In my requirement of comparing files (and sub folders and their contents) in a main folder, I would like to have something like a row which I can compare with similar results from another main folder. My results for a single main folder are already over a few rows, so making an offset of a few rows may make considering similar results from other main folders. So I think a single row offset will be adequate. I do note that the offset data will no longer match the property name, but as the different properties are characteristically of different looking forms, I think it will be obvious which properties are showing. What I mean from this last bit is that, for example, it will be obvious that something like this, 2.1.4026.0 , will be the version number, and something like this , 20.12.2002 , will be a date, especially as I know that data in the first two columns is correct and has a similar pattern sequence looking down the rows
I need to do no more than change Rw = 1 + Reocopy + 1 in the second recursion coding to Rw = 1 + Reocopy + 1 to achieve the following modified results , whereby files ( or sub folders) are shown one row below the level of the folder in which they are :
https://i.postimg.cc/R0yjqNDf/Versio...els-offset.jpg Attachment 5728
https://i.postimg.cc/R0yjqNDf/Versio...els-offset.jpg
Here is the 3 views comparison:
_ The "one level" view (for just files and sub folders in the ( Movie Maker ) main folder)
_ the full level view ( for all files and sub folders and all contents of sub folders and any further sub folders)
_ the full level view with an offset to help show at what level all the files and sub folders are
https://i.postimg.cc/MGvCWydq/3-view-comparison.jpg Attachment 5729
https://i.postimg.cc/MGvCWydq/3-view-comparison.jpg
Here is the full pair of macros , the new recursion coding, Sub ReoccurringFileFolderProps2( , and the macro that calls it. (The calling macro has had no other modification other than changing the name of the recursion macro it calls to Sub ReoccurringFileFolderProps2( )
https://www.excelfox.com/forum/showt...ll=1#post23923
-
1 Attachment(s)
YouTube, Video making and editing, etc. coupled to excelfox ( windows Movie Maker )
This is post#post23769
https://www.excelfox.com/forum/showt...age2#post23769
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2#23769
Some macro refinements: Improved accuracy of Property values
Recap: The windows shell object folder items way
This is potentially a nice ordered way. If all the properties worked it would be great. It seems to have worked well up to XP, but after that both the order of properties listed changed and more and more of them broke. In addition some numbers, in particular size, when working are in some less precise, perhaps rounded KB or MB number, whereas if it is given in a Bytes number, then it appears to be a more precise figure.
( The different size numbers available can also be seen together if you look at a file or folder manually via the Right click --- Property way, https://i.postimg.cc/DwnT0hy7/Movie-...erties-way.jpg
https://eileenslounge.com/viewtopic....313555#p313555 Attachment 5730 )
So, looking in particular at the size, issue, but also generally at the file and folder property issue, I took a time out to see if I could come across some other ideas to get properties , for example with this forum post
https://eileenslounge.com/viewtopic....313622#p313622
https://eileenslounge.com/viewtopic....313559#p313559
The TLDR outcome of all that is that I will stay with the windows shell object folder items way but also use at some points the Microsoft Scripting Runtime Library way, (commonly also referred to as the FileSystemObject(FSO) way), to get an accurate value of size.
Here is a simple test file to demo what I mean: https://www.excelfox.com/forum/showt...ll=1#post23924 this appears initially to give satisfactory results.
More detailed conclusions and discussions
Some concluding thoughts
File Size: accuracy , or rather the value for Alan to use for the purposes of comparing files that may be similar or the same.
At the moment I am firstly interested into getting some consistent results, preferably not rounded, to compare files that are similar or the same. In terms of size, numbers given vary for a particular file, (or folder) , and I have come to the conclusion its best not to ask anyone about converting a Byte to KB or MB or visa versas. If you do ask, then it’s time to hide in a nuclear fallout shelter for a few months, and wait until world war 3 is finished fighting over it. It seems to be down to what definition is your God that you would fight to death for.
The best I can say is that if, as in my used example so far, I see figures for the same file of 628 KB, 629 KB and 647168 Bytes, then it is likely that some rounding has gone on those KB figures so the Byte figure is the best one for my purposes? I would welcome any comments on just this last statement, I mean does it sound a good idea to take, in such a case the 647168 and not worry too much about the other KB or MB number?
_Ways to get the size ( and some other properties maybe )
At the outset of the little project this is related to, I was not so sure what properties I wanted, so after I caught Microsoft Shell Controls And Automation way (windows shell object way) , I thought great , that’s a pretty full list. Unfortunately by every new Microsoft operating system version both the list order and available properties has changed, and progressively more and more of the property values don’t work – it’s become more broken as time went on. Because of this and because I was narrowing down the list of properties to use, I started looking at other ways.
Conclusions so far about getting the size, and perhaps a few other Properties, comparing the ways
_Built in VBA way, and the VBA Open For Input LOF(1) Close way
I will take a wild guess these two use the same low end coding somewhere. They both give the nice Byte number. But they only work for files. There are not many other properties to get in these ways either
_Microsoft Shell Controls And Automation way (windows shell object way, (WSO))
A bit broken and inconsistent as time goes on, but using this in XP can give some other properties that I can’t seem to get in any other way. For a file we have a couple of ways within the Microsoft Shell Controls And Automation way (windows shell object way). The Item.Sizeproperty gives the nice long figure Byte number, and the objFolder.GetDetailsOf(Item, 1) gives the shorter KB or MB figure, which I presume is rounded. It appears that if the item is a folder, then both these size things are broken, even as far back as XP. The size property gives zero and the GetDetailsOf method
(I note that in any explorer window I have ever seen the folder property never works. I don’t know if there is any connection there?)
_ This seems to be the only way so far to get me a folder size programmatically with VBA. The file size given is the nice full digits Bytes, as it is also for the files size. So this might be the one to use for size
_._______________
So for the time being, in ouder to move on, the macro so far, the recursion / reoccurring one will be modified a bit, mostly to get the accurate and working size property given by the WSO way
See around
https://www.excelfox.com/forum/showt...s-etc-)/page17
https://eileenslounge.com/viewtopic....313792#p313792
https://eileenslounge.com/viewtopic....313792#p313792
https://www.excelfox.com/forum/showt...s-etc-)/page18
-
-
Version 1
-
"XP era" Versions and some initial investigations
Thread 2936 https://www.excelfox.com/forum/showt...-Maker-)/page2
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2
This is post #post23772
https://www.excelfox.com/forum/showt...age2#post23772
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2#post23772
XP era versions
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the version 2 – version 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. After the development reset, (the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
( (2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself. https://i.postimg.cc/23RzWFyz/GB-Movie-Maker-6.jpg
https://i.postimg.cc/y3j44R05/GB-Movie-Maker-6.jpg
It included new effects and transitions, support for playback on the Xbox 360,and support for the DVR-MS file format that Windows Media Center records television in. The HD version in Premium and Ultimate editions of Windows Vista also added support for capturing from HDV camcorders. The capture wizard also created DVR-MS type files from HDV tapes. However, the Windows Vista version of Windows Movie Maker removed support for importing video from an analog video source such as an analog camcorder, VCR or from a webcam. There is no "2.7 XP version". People may incorrectly be referring to the Windows Vista version of Windows Movie Maker 2.6 that is basically a CPU-only version using the XP code for those on Vista that didn't have a powerful enough GPU. As some older systems might not be able to run the new version of Windows Movie Maker. Vista at the end of the final pre-release development stages may also have been code-named 2.7 )
(2007) - Version 2.6 https://i.postimg.cc/HLxZ8ksq/Version-2-6.jpg
https://i.postimg.cc/SnB7wq9d/Version-2-6.jpg
So, Microsoft also released an updated older version 2.6 for Windows Vista on Microsoft Download Centre, possibly around 2007-2009. This version is basically the same as Windows Movie Maker 2.1 and included all of the old effects and transitions, but it excludes the ability to capture video. It can only be installed on Windows Vista and is only intended for use on computers where the hardware-accelerated version cannot run. 2.6 is very similar to 2.5, as it was, or at least is often referred to as, a refurbished XP version 2.5
(2008) - Version 2009
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up…
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
As for the "Windows Live" version, A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. Windows Live Movie Maker 2009 is officially the last version to support Windows XP, ( Windows Live Photo Gallery version 14.0.8117.416 )
-
Basic Code explanation.
_B) When running in the loop for the item that is a folder with some files in it
Because the folder item has just files in it, we can say that for the loop for the item that is a folder, this is the actual coding that is run
Code:
Private Sub ReoccurringFileFolderProps(ByVal Pf As String)
Rem 0
Let Reocopy = Reocopy + 1 ' Originally the variableReocopyis zero.It will become 1 on first entering the macro.Every time we leave this macro, this number is reduced by 1 So in simple use it will be 1 or zero indicating that a copy is in use.However, should this macro "Call itself", before its finished , ( the recursion idea ) then the vallue will be 2and so on.So effectively it tells us which copy is running at any time
Rem 1
Dim objShell As Shell32.Shell: Set objShell = New Shell32.Shell'https://i.postimg.cc/Fz9zrnNm/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg https://i.postimg.cc/sDC9S54h/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg
Dim objFolder As Shell32.Folder: Set objFolder = objShell.Namespace(Pf)'
Rem 2
Dim Fil As Shell32.FolderItem
For Each Fil In objFolder.Items ' ======= Main Loop ==================================================|
' Dim Clm As Long: ' Global variable
Let Clm = Clm + 1
Dim Rw As Long: Let Rw = 1
Let ActiveCell.Offset(Rw, Clm) = objFolder.GetDetailsOf(Fil, 0)' Name
Let ActiveCell.Offset(Rw + 1, Clm) = objFolder.GetDetailsOf(Fil, 1) ' Size
Let ActiveCell.Offset(Rw + 2, Clm) = objFolder.GetDetailsOf(Fil, 2) ' Type
Let ActiveCell.Offset(Rw + 3, Clm) = Left(objFolder.GetDetailsOf(Fil, 3), InStr(1, objFolder.GetDetailsOf(Fil, 3), " ", vbBinaryCompare)) ' Chang Date
Let ActiveCell.Offset(Rw + 4, Clm) = Left(objFolder.GetDetailsOf(Fil, 4), InStr(1, objFolder.GetDetailsOf(Fil, 4), " ", vbBinaryCompare)) ' Made Date
' Let ActiveCell.Offset(Rw + 9, 0) = "Dateiversion": Let ActiveCell.Offset(Rw + 9, 1) = objFolder.GetDetailsOf(Fil, 166)
Let ActiveCell.Offset(Rw + 5, Clm) = objFolder.GetDetailsOf(Fil, 166) ' File Version
'_________________________________________________________________________________________________
' 2bHere we may pause the macro, whilst another copy of it is started
' Pause first macro, start a second copy
Sub ReoccurringFileFolderProps(Pf & "\" & objFolder.GetDetailsOf(Fil, 0)) = ReoccurringFileFolderProps(That to Sub Folder)
Rem 0
Let Reocopy = Reocopy + 1 ' Originally the variableReocopyis zero.It will become 1 on first entering the macro.Every time we leave this macro, this number is reduced by 1 So in simple use it will be 1 or zero indicating that a copy is in use.However, should this macro "Call itself", before its finished , ( the recursion idea ) then the vallue will be 2and so on.So effectively it tells us which copy is running at any time
Rem 1
Dim objShell As Shell32.Shell: Set objShell = New Shell32.Shell'https://i.postimg.cc/Fz9zrnNm/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg https://i.postimg.cc/sDC9S54h/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg
Dim objFolder As Shell32.Folder: Set objFolder = objShell.Namespace(Pf)'
Rem 2
Dim Fil As Shell32.FolderItem
For Each Fil In objFolder.Items ' ======= Main Loop ==================================================|
' Dim Clm As Long: ' Global variable
Let Clm = Clm + 1
Dim Rw As Long: Let Rw = 1
Let ActiveCell.Offset(Rw, Clm) = objFolder.GetDetailsOf(Fil, 0)' Name
Let ActiveCell.Offset(Rw + 1, Clm) = objFolder.GetDetailsOf(Fil, 1) ' Size
Let ActiveCell.Offset(Rw + 2, Clm) = objFolder.GetDetailsOf(Fil, 2) ' Type
Let ActiveCell.Offset(Rw + 3, Clm) = Left(objFolder.GetDetailsOf(Fil, 3), InStr(1, objFolder.GetDetailsOf(Fil, 3), " ", vbBinaryCompare)) ' Chang Date
Let ActiveCell.Offset(Rw + 4, Clm) = Left(objFolder.GetDetailsOf(Fil, 4), InStr(1, objFolder.GetDetailsOf(Fil, 4), " ", vbBinaryCompare)) ' Made Date
' Let ActiveCell.Offset(Rw + 9, 0) = "Dateiversion": Let ActiveCell.Offset(Rw + 9, 1) = objFolder.GetDetailsOf(Fil, 166)
Let ActiveCell.Offset(Rw + 5, Clm) = objFolder.GetDetailsOf(Fil, 166) ' File Version
'_________________________________________________________________________________________________
' 2bHere we may pause the macro, whilst another copy of it is started
'If objFolder.GetDetailsOf(Fil, 2) = "Dateiordner" Then Call ReoccurringFileFolderProps(Pf & "\" & objFolder.GetDetailsOf(Fil, 0))
'_________________________________________________________________________________________________
' If we did pause whilst the above code line set off another copy, then when that is finished we will come here and resume the paused previous copy
Next Fil ' ============================== Main Loop=================================================|
Let Reocopy = Reocopy - 1' We are finished at this point with this running copy of the macro.This code line will reduce the value indicating the copy number is running since this copy ends in the next line
End Sub
'_________________________________________________________________________________________________
' If we did pause whilst the above code line set off another copy, then when that is finished we will come here and resume the paused previous copy
' Stop second macro, resume first macro
'
Next Fil ' ============================== Main Loop=================================================|
Let Reocopy = Reocopy - 1' We are finished at this point with this running copy of the macro.This code line will reduce the value indicating the copy number is running since this copy ends in the next line
End Sub
Private Sub ReoccurringFileFolderProps(ByVal Pf As String)
Rem 0
Let Reocopy = Reocopy + 1 ' Originally the variableReocopyis zero.It will become 1 on first entering the macro.Every time we leave this macro, this number is reduced by 1 So in simple use it will be 1 or zero indicating that a copy is in use.However, should this macro "Call itself", before its finished , ( the recursion idea ) then the vallue will be 2and so on.So effectively it tells us which copy is running at any time
Rem 1
Dim objShell As Shell32.Shell: Set objShell = New Shell32.Shell'https://i.postimg.cc/Fz9zrnNm/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg https://i.postimg.cc/sDC9S54h/Tools-...Automation.jpg
Dim objFolder As Shell32.Folder: Set objFolder = objShell.Namespace(Pf)'
Rem 2
Dim Fil As Shell32.FolderItem
For Each Fil In objFolder.Items ' ======= Main Loop ================================================== |
' Dim Clm As Long: ' Global variable
Let Clm = Clm + 1
Dim Rw As Long: Let Rw = 1
Let ActiveCell.Offset(Rw, Clm) = objFolder.GetDetailsOf(Fil, 0)' Name
Let ActiveCell.Offset(Rw + 1, Clm) = objFolder.GetDetailsOf(Fil, 1) ' Size
Let ActiveCell.Offset(Rw + 2, Clm) = objFolder.GetDetailsOf(Fil, 2) ' Type
Let ActiveCell.Offset(Rw + 3, Clm) = Left(objFolder.GetDetailsOf(Fil, 3), InStr(1, objFolder.GetDetailsOf(Fil, 3), " ", vbBinaryCompare)) ' Chang Date
Let ActiveCell.Offset(Rw + 4, Clm) = Left(objFolder.GetDetailsOf(Fil, 4), InStr(1, objFolder.GetDetailsOf(Fil, 4), " ", vbBinaryCompare)) ' Made Date
' Let ActiveCell.Offset(Rw + 9, 0) = "Dateiversion": Let ActiveCell.Offset(Rw + 9, 1) = objFolder.GetDetailsOf(Fil, 166)
Let ActiveCell.Offset(Rw + 5, Clm) = objFolder.GetDetailsOf(Fil, 166) ' File Version
'_________________________________________________ ________________________________________________
' 2bHere we may pause the macro, whilst another copy of it is started
' Pause first macro, start a second copy
Sub ReoccurringFileFolderProps(Pf & "" & objFolder.GetDetailsOf(Fil, 0)) = ReoccurringFileFolderProps(That to Sub Folder)
Rem 0
Let Reocopy = Reocopy + 1 ' Originally the variableReocopyis zero.It will become 1 on first entering the macro.Every time we leave this macro, this number is reduced by 1 So in simple use it will be 1 or zero indicating that a copy is in use.However, should this macro "Call itself", before its finished , ( the recursion idea ) then the vallue will be 2and so on.So effectively it tells us which copy is running at any time
Rem 1
Dim objShell As Shell32.Shell: Set objShell = New Shell32.Shell'https://i.postimg.cc/Fz9zrnNm/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg https://i.postimg.cc/sDC9S54h/Tools-...Automation.jpg
Dim objFolder As Shell32.Folder: Set objFolder = objShell.Namespace(Pf)'
Rem 2
Dim Fil As Shell32.FolderItem
For Each Fil In objFolder.Items ' ======= Main Loop ================================================== |
' Dim Clm As Long: ' Global variable
Let Clm = Clm + 1
Dim Rw As Long: Let Rw = 1
Let ActiveCell.Offset(Rw, Clm) = objFolder.GetDetailsOf(Fil, 0)' Name
Let ActiveCell.Offset(Rw + 1, Clm) = objFolder.GetDetailsOf(Fil, 1) ' Size
Let ActiveCell.Offset(Rw + 2, Clm) = objFolder.GetDetailsOf(Fil, 2) ' Type
Let ActiveCell.Offset(Rw + 3, Clm) = Left(objFolder.GetDetailsOf(Fil, 3), InStr(1, objFolder.GetDetailsOf(Fil, 3), " ", vbBinaryCompare)) ' Chang Date
Let ActiveCell.Offset(Rw + 4, Clm) = Left(objFolder.GetDetailsOf(Fil, 4), InStr(1, objFolder.GetDetailsOf(Fil, 4), " ", vbBinaryCompare)) ' Made Date
' Let ActiveCell.Offset(Rw + 9, 0) = "Dateiversion": Let ActiveCell.Offset(Rw + 9, 1) = objFolder.GetDetailsOf(Fil, 166)
Let ActiveCell.Offset(Rw + 5, Clm) = objFolder.GetDetailsOf(Fil, 166) ' File Version
'_________________________________________________ ________________________________________________
' 2bHere we may pause the macro, whilst another copy of it is started
'If objFolder.GetDetailsOf(Fil, 2) = "Dateiordner" Then Call ReoccurringFileFolderProps(Pf & "" & objFolder.GetDetailsOf(Fil, 0))
'_________________________________________________ ________________________________________________
' If we did pause whilst the above code line set off another copy, then when that is finished we will come here and resume the paused previous copy
Next Fil ' ============================== Main Loop============================================== ===|
Let Reocopy = Reocopy - 1' We are finished at this point with this running copy of the macro.This code line will reduce the value indicating the copy number is running since this copy ends in the next line
End Sub
'_________________________________________________ ________________________________________________
' If we did pause whilst the above code line set off another copy, then when that is finished we will come here and resume the paused previous copy
' Stop second macro, resume first macro
'
Next Fil ' ============================== Main Loop============================================== ===|
Let Reocopy = Reocopy - 1' We are finished at this point with this running copy of the macro.This code line will reduce the value indicating the copy number is running since this copy ends in the next line
End Sub
So what was happening there was
First macro starts
For Each ' First Macro Main Loop =====|
First macro pauses if current item is a sub folder
__Second macro starts to look at files in sub folder
__For Each ' Second Macro Main Loop ===|
__Next' Second Macro Main Loop ===|
__Second macro Ends
First macro resumes
Next ' First Macro Main Loop =====|
First macro ends
Lets put that in words, with an example. Let’s say the Main Folder has 3 items
A file
A sub Folder with 4 files in it
A file
The first macro starts.
Loop 1 starts and analyses the first file properties. First loop ends
Loop 2 starts and analyses the Folder properties, then the first macro pauses
__The second macro starts
__Loop 1 analyses the first file in the sub folder. Loop 1 ends
__Loop 2 analyses the second file in the sub folder. Loop 2 ends
__Loop 3 analyses the third file in the sub folder. Loop 3 ends
__Loop 4 analyses the final file in the sub folder. Loop 4 ends
__The second macro ends
The first macro resumes, Loop 2 ends
, and it loops a third time and analyses the third item from main folder, then it ends
The actual coding run will get longer and longer, either
_ If there are increasing numbers of sub folders at any level – in this case a copy code will be used again and again, - This sort of thing
1
__ Copy 2
1
__ Copy 2
1
, and/ or
_ If a sub folder contains itself sub folders – in this case more and more copies are made and affectively pasted in the middle, - This sort of thing
1
__ Copy 2
____ Copy 3
__ Copy 2
1
-
"Reoccurring Routine" / "Recursion technique"
This is post#post23774
https://www.excelfox.com/forum/showt...age2#post23774
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2#post23774
Advanced File and Folder analysis coding - Reoccurring or Recursion Codings
Here are both the previous macro and that we are considering here, together. https://www.excelfox.com/forum/showt...ll=1#post23915 Together they form the advance solution being sicudded here
The first macro in this pair, as considered in the last post cannot run on its own since it would error when trying to set off ( Call ) the second macro. The second macro is the Recursion / reoccurring coding ,which we are considering here.
The second macro which we are considering here, has arguments that must be given, so is the form of macro that generally needs another macro to set off ( Call it ) and in doing those setting off / Calling, it passes it the required argument(s) In our example it is passing the full path to our Main Movie Maker program folder. This is what is needed to create the windows shell object, ( pseudo like code line, Set WindShellobjFolder = objShell.Namespace(The full path string to the program folder here) )
Part 1 Recursion / reoccurring coding
The word Recursionor recursion techniques in coding often puts people off, but I think it’s actually straight forward and easy to understand if explained fully but simply and in particular accurately: It seems that some wording is typically used in explanations, or used by people who understand it,when talking about it, and these words are at best incorrect and at worst confusing nonsense.For example, it is often at an early stage of explaintions, said that a code using recursion techniques Calls itself. That is inaccurate nonsense, or maybe something that can be justified to say technically but in a common sense point of view is inaccurate nonsense.
So forget anything you heard before about recursions and start again:
_1) The written code you see, for example in the VB Editor is just that. It’s just written code. It never runs, walks, or drives to the local shops to buy you any Buns. It can’t do anything at all. What actually runs coding is something with perhaps some limited similarity to the written coding somewhere deep in the innards of a computer. Some compile process makes the coding that will actually be run, and it uses the written code to determine what coding you wanted.
(Something similar that is important to realise, if you are familiar with the F8 Debug step mode, is that the F8 Debug step mode is extraorganised just for our Human eye convenience. We can’t actually see the coding being run in the step mode, but some extra software is used for our convenience to show approximately what part of the actual coding is running, since the actual coding is organised into a similarly set out series of instructions.)
_2) Because the actual used coding is not that written one, but rather coding made to the specifications of the written coding, many languages, such as that (VBA), coding associated with MS Office, is happy to make a few copies of the coding you want. Furthermore, whist we can’t easily run more than one copy at a time, we can curiously start another copy before the previous copy is finished. What happens then is that at the start of another copy, the previous copy is paused, and it resumes at the point it paused at,when the new copy is finished.
That’s it. If you understood that you know all about recursion. Perhaps it is just worth notingthat you are not limited to just a couple of copies. You can have a few of them, each one setting off another copy. When a copy sets off another copy, then it is paused and has to wait until the copy it set off is finished before it can continue. In order for this to work, a paused coding needs to work a bit differently to a coding that is finished. In particular, when a copy is paused, any variables that were filled have their values stored , "stacked", somewhere, so that the variables can be refilled when the paused copy restarts. This extra process has to be done because ordinarily variables within coding would usually lose their values when a code stops in the more usual way, which is at the end, when it is finished.
As far as the typical practical coding is concerned, generally at the code line that a copy of coding sets off another copy of the same coding,some sort of conditional If statement or similar is used , so that hopefully at some point all copies started get finished allowing the previous ones also at some point to finish. Otherwise the recursion / code reoccurring goes on for ever, or would do, if something does not get too big, or something runs out of space, leading to some error such as the famous "stack overflow" error.
A pictorial explanation may help here to re iterate the Recursion / Reoccurring coding process:
Here is a quick simple explanation of recursion with some emphasis on our actual next coding, Private Sub ReoccurringFileFolderProps(ByVal Pf As String)
We remember from the last post that, the coding being discussed in this post, Private Sub ReoccurringFileFolderProps(ByVal Pf As String) gets Called by this code line in the first macro,
Call ReoccurringFileFolderProps(Parf & "\Movie Maker")
So that tells us that whenit starts, itisalso "fed" / passed the full path to the Movie Maker Folder that we want analysed
Basic Code explanation, simplified
_A) When running more usually, no recursion / reoccurring coding.
In its simplest working, which it might do, for example the case of only files and no sub folders in the main Movie Maker folder, the codingis just our basic coding using the windows shell object to loop through all the items in the Movie Maker folder. Those items are all files, no sub folders, so the condition at ' 2b ,
If objFolder.GetDetailsOf(Fil, 2) = "Dateiordner"Then Call ReoccurringFileFolderProps(Pf & "" & objFolder.GetDetailsOf(Fil, 0))
, is not met
Effectively then, it is as if the ' 2b section is not there, and we are basically doing our most basic looping of all folder Items ( files in this case ), and listing some of their properties at each loop. So the == Main Loop == :below is the only significant coding
Code:
Private Sub ReoccurringFileFolderProps(ByVal Pf As String)
Rem 0
Let Reocopy = Reocopy + 1 ' Originally the variableReocopyis zero.It will become 1 on first entering the macro.Every time we leave this macro, this number is reduced by 1 So in simple use it will be 1 or zero indicating that a copy is in use.However, should this macro "Call itself", before its finished , ( the recursion idea ) then the vallue will be 2and so on.So effectively it tells us which copy is running at any time
Rem 1
Dim objShell As Shell32.Shell: Set objShell = New Shell32.Shell'https://i.postimg.cc/Fz9zrnNm/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg https://i.postimg.cc/sDC9S54h/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg
Dim objFolder As Shell32.Folder: Set objFolder = objShell.Namespace(Pf)'
Rem 2
Dim Fil As Shell32.FolderItem
For Each Fil In objFolder.Items ' ======= Main Loop ==================================================|
' Dim Clm As Long: ' Global variable
Let Clm = Clm + 1
Dim Rw As Long: Let Rw = 1
Let ActiveCell.Offset(Rw, Clm) = objFolder.GetDetailsOf(Fil, 0)' Name
Let ActiveCell.Offset(Rw + 1, Clm) = objFolder.GetDetailsOf(Fil, 1) ' Size
Let ActiveCell.Offset(Rw + 2, Clm) = objFolder.GetDetailsOf(Fil, 2) ' Type
Let ActiveCell.Offset(Rw + 3, Clm) = Left(objFolder.GetDetailsOf(Fil, 3), InStr(1, objFolder.GetDetailsOf(Fil, 3), " ", vbBinaryCompare)) ' Chang Date
Let ActiveCell.Offset(Rw + 4, Clm) = Left(objFolder.GetDetailsOf(Fil, 4), InStr(1, objFolder.GetDetailsOf(Fil, 4), " ", vbBinaryCompare)) ' Made Date
' Let ActiveCell.Offset(Rw + 9, 0) = "Dateiversion": Let ActiveCell.Offset(Rw + 9, 1) = objFolder.GetDetailsOf(Fil, 166)
Let ActiveCell.Offset(Rw + 5, Clm) = objFolder.GetDetailsOf(Fil, 166) ' File Version
'_________________________________________________________________________________________________
' 2bHere we may pause the macro, whilst another copy of it is started
'If objFolder.GetDetailsOf(Fil, 2) = "Dateiordner" Then Call ReoccurringFileFolderProps(Pf & "\" & objFolder.GetDetailsOf(Fil, 0))
'_________________________________________________________________________________________________
' If we did pause whilst the above code line set off another copy, then when that is finished we will come here and resume the paused previous copy
Next Fil ' ============================== Main Loop=================================================|
Let Reocopy = Reocopy - 1' We are finished at this point with this running copy of the macro.This code line will reduce the value indicating the copy number is running since this copy ends in the next line
End Sub
So now consider that at some point in the looping through the folder items, it did encounter a folder, in other words one of the items was a folder. What will happen now is that after the properties of that item ( the folder ) are outputted, we will carry out this line
Code:
Private Sub ReoccurringFileFolderProps(ByVal Pf As String)
Rem 0
Let Reocopy = Reocopy + 1 ' Originally the variableReocopyis zero.It will become 1 on first entering the macro.Every time we leave this macro, this number is reduced by 1 So in simple use it will be 1 or zero indicating that a copy is in use.However, should this macro "Call itself", before its finished , ( the recursion idea ) then the vallue will be 2and so on.So effectively it tells us which copy is running at any time
Rem 1
Dim objShell As Shell32.Shell: Set objShell = New Shell32.Shell'https://i.postimg.cc/Fz9zrnNm/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg https://i.postimg.cc/sDC9S54h/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg
Dim objFolder As Shell32.Folder: Set objFolder = objShell.Namespace(Pf)'
Rem 2
Dim Fil As Shell32.FolderItem
For Each Fil In objFolder.Items ' ======= Main Loop ==================================================|
' Dim Clm As Long: ' Global variable
Let Clm = Clm + 1
Dim Rw As Long: Let Rw = 1
Let ActiveCell.Offset(Rw, Clm) = objFolder.GetDetailsOf(Fil, 0)' Name
Let ActiveCell.Offset(Rw + 1, Clm) = objFolder.GetDetailsOf(Fil, 1) ' Size
Let ActiveCell.Offset(Rw + 2, Clm) = objFolder.GetDetailsOf(Fil, 2) ' Type
Let ActiveCell.Offset(Rw + 3, Clm) = Left(objFolder.GetDetailsOf(Fil, 3), InStr(1, objFolder.GetDetailsOf(Fil, 3), " ", vbBinaryCompare)) ' Chang Date
Let ActiveCell.Offset(Rw + 4, Clm) = Left(objFolder.GetDetailsOf(Fil, 4), InStr(1, objFolder.GetDetailsOf(Fil, 4), " ", vbBinaryCompare)) ' Made Date
' Let ActiveCell.Offset(Rw + 9, 0) = "Dateiversion": Let ActiveCell.Offset(Rw + 9, 1) = objFolder.GetDetailsOf(Fil, 166)
Let ActiveCell.Offset(Rw + 5, Clm) = objFolder.GetDetailsOf(Fil, 166) ' File Version
'_________________________________________________________________________________________________
' 2bHere we may pause the macro, whilst another copy of it is started
'If objFolder.GetDetailsOf(Fil, 2) = "Dateiordner" Then Call ReoccurringFileFolderProps(Pf & "\" & objFolder.GetDetailsOf(Fil, 0))
'_________________________________________________________________________________________________
' If we did pause whilst the above code line set off another copy, then when that is finished we will come here and resume the paused previous copy
Next Fil ' ============================== Main Loop=================================================|
Let Reocopy = Reocopy - 1' We are finished at this point with this running copy of the macro.This code line will reduce the value indicating the copy number is running since this copy ends in the next line
End Sub
Let’s consider for simplicity, the found folder has only files in it. We consider this fully in the next post.
-
This is post #post23775
https://www.excelfox.com/forum/showt...age2#post23775
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2#post23775
More detailed careful analysis of Movie Maker program files.
A couple of short comings made the comparison of versions so far a bit more difficult than need be.
_ Lack of full examination of contents of any **sub folders in the main Movie Maker folder made it more difficult to determine a good ordered positioning in a list of similar versions.
_ As well as physically checking the dates where possible in the computers for the case of files obtained from existing computers with original installs, doing this by coding on the actual computers, rather than gives more reliable properties, in particular the dates.
Some slightly advanced/ intermediate coding.
Recap. Previous coding.
I have already used some coding from this good source, https://www.youtube.com/watch?v=jTmVtPHtiTg . Summarised, the coding there treats things, (I think probably everything, Folders and files), in a folder as Items of that folder. You loop throughjust those items, and so are able to get a lot of properties for each one. Each property is returned from a code line of this general form PropertyValue = objFolder.GetDetailsOf(Fil, 166)
This will then be a "one level" thing – "across the board", a row, line type look. Files in this folder will have their properties analysed, as will any other thing’s such as Folders, (**in this situation those folders within the main folder are often referred to as sub Folders). But we did not look inside those sub folders.
Recap. The basic looping structure would then be of this sort of form
Dim objShell As Shell32.Shell: Set objShell = New Shell32.Shell ' https://i.postimg.cc/fz9zrnnm/tools-referrences-microsoft-shell-controls-and-automation.jpg https://i.postimg.cc/sdc9s54h/tools-...automation.jpg
Dim objFolder As Shell32.Folder: Set objFolder = objShell.Namespace(FullPathToFolder) '
Dim Fil As Shell32.FolderItem
__For Each Fil In objFolder.Items
___PropertyValue = objFolder.GetDetailsOf(Fil, 166)
__Next Fil
So , briefly, Fil is declared as a folder Item, and we loop through each of them in the folder. At each loop we can get a particular property from a number. In that example I have 166, which so far always seems to give me a version number.
To get the full listing of the numbers for the different properties available, see here https://www.youtube.com/watch?v=jTmVtPHtiTg&t=560s
Also notes on the basic coding using the windows Shell object can be see here
So that was the basic coding.
The advanced coding.
The main advancement will be to examine contents of all sub folders. In other words all folders and files at any level or row in the
This comprises two main codings. Sub PassFolderForReocursig1() and Private Sub FileFolderProps(ByVal Pf As String)
The main purpose of this is
_ To produce the first two columns of output. The first is the property names and the second the corresponding property values for the main folder, Movie Maker
_ This folder, ( actually it’s name, Movie Maker ) is then passed to the next macro, Sub PassFolderForReocursig()
Sub PassFolderForReocursig() Brief code description
' 1b
In this macro, you need to hard code the variable Parf to the Folder path of the Folder that contains the main Movie Maker folder.
Typically in the practice this will be either
_ The path to program files if you are checking out the original Movie Maker folder. This will likely be some form similar to something like, C:\Program
or
_ The path to a copy made or downloaded, which is likely in the same as, or close to, the path to where the Excel file containing the macros are.
The first option is preferable, if possible, since the copy my effect properties changing them from the original, and for the comparison purposes we are interested in, the original non changed values are preferable.
' 1c
In the top left cell of where the output starts, ( which will be the active cell at the time of running ) part of the path you gave will be printed out for future reference to give an indication of where the rest of the files and folders that will be listed are/ were at the time of running the macro.
Rem2 Rem 3
The windows shell object way, ( ) is used to get the names and values. For each of the properties we are interested there are two possibilities to get the name of the property for the first column output. I give both, and the first one is 'commented out. This first one is OK if you are sure you know the number to use for that property. The second line is perhaps preferable, as it will be obvious if for some reason the number is not as you expected since you will not get the correct name that you were expecting. ( Microsoft seem to have changed the properties available and the number referring to some of them https://www.youtube.com/watch?v=jTmV...8sZ9zYqog9KZ5B )
So the first program gives us a listing in the first column of the property names that we are interested in, and the second column gives us the values for the Main Movie Maker folder of those properties.
What we want to do now, is go on to look at all folders and files in this main Movie Maker folder, not just the folder and files seen by looking in the first "level down". In other words we want to delve down further to see what is inside any folders ( "sub Folders" ), within the main Movie Maker folder, so Rem 4 , passes the folder path to the Main Movie Maker folder on to the next code, which forms the main new advanced coding being introduced which uses the so called reoccurring routine, or recursion technique do delve down is and where necessary to get at all files and folders
Here is the first macro
Code:
Option Explicit
Dim Clm As Long, Reocopy As Long ' variable for column number to put file or folder details in, number representin the copy of the second macro
' Select the cell where a main folder(s) last bit of its Parf will go. This macro will list, starting with the folder name under that patf bit, a few property names. In the naxt column the corresponding property value will be given
'
Sub PassFolderForReocursing()
'Sub SchellFolderDetails2() ' Jan 2024 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2#post23775
Rem 0
Let Clm = 0: Reocopy = -1
Rem 1
Dim Ws As Worksheet: Set Ws = Me ' G:\YouTubeVideos&Anaslysis&HackingTricks\VideoRecordingEditing\Windows (Live) Movie Maker\Movie Maker Versions.xls
' 1b
Dim Parf As String
Let Parf = ThisWorkbook.Path & "\Versions Downloads Exes\Verson 2, 2 1 2 5 Downloads 2,1\50 Euro Keks"
Let Parf = ThisWorkbook.Path & "\50 Euro Keks"
' 1c
If Len(Parf) - Len(Replace(Parf, "\", "", 1, -1, vbBinaryCompare)) >= 2 Then
Let ActiveCell = Mid(Parf, InStrRev(Parf, "\", InStrRev(Parf, "\", -1, vbBinaryCompare) - 1, vbBinaryCompare))
Else
Let ActiveCell = Parf
End If
Rem 2 Windows Shell object
Dim objShell As Shell32.Shell: Set objShell = New Shell32.Shell ' https://i.postimg.cc/Fz9zrnNm/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg https://i.postimg.cc/sDC9S54h/Tools-Referrences-Microsoft-Shell-Controls-And-Automation.jpg
Dim objFolder As Shell32.Folder: Set objFolder = objShell.Namespace(Parf) '
Rem 3 Movie Maker Folder Property names and Property values.
Dim Fil As Shell32.FolderItem
For Each Fil In objFolder.Items ' We loop through all items to find the Movie Maker folder ' =======
If Fil.Name = "Movie Maker" Then
Dim Rw As Long: Let Rw = 1
'Let ActiveCell.Offset(Rw, 0) = "Name": Let ActiveCell.Offset(Rw, 1) = objFolder.GetDetailsOf(Fil, 0)
Let ActiveCell.Offset(Rw, 0) = objFolder.GetDetailsOf("Goolies", 0): Let ActiveCell.Offset(Rw, 1) = objFolder.GetDetailsOf(Fil, 0)
'Let ActiveCell.Offset(Rw + 1, 0) = "Größe": Let ActiveCell.Offset(Rw + 1, 1) = objFolder.GetDetailsOf(Fil, 1)
Let ActiveCell.Offset(Rw + 1, 0) = objFolder.GetDetailsOf(71, 1): Let ActiveCell.Offset(Rw + 1, 1) = objFolder.GetDetailsOf(Fil, 1)
'Let ActiveCell.Offset(Rw + 2, 0) = "Elementtyp": Let ActiveCell.Offset(Rw + 2, 1) = objFolder.GetDetailsOf(Fil, 2)
Let ActiveCell.Offset(Rw + 2, 0) = objFolder.GetDetailsOf(Parf, 2): Let ActiveCell.Offset(Rw + 2, 1) = objFolder.GetDetailsOf(Fil, 2)
'Let ActiveCell.Offset(Rw + 3, 0) = "Änderungsdatum": Let ActiveCell.Offset(Rw + 3, 1) = Left(objFolder.GetDetailsOf(Fil, 3), InStr(1, objFolder.GetDetailsOf(Fil, 3), " ", vbBinaryCompare))
Let ActiveCell.Offset(Rw + 3, 0) = objFolder.GetDetailsOf(Ws, 3): Let ActiveCell.Offset(Rw + 3, 1) = Left(objFolder.GetDetailsOf(Fil, 3), InStr(1, objFolder.GetDetailsOf(Fil, 3), " ", vbBinaryCompare))
'Let ActiveCell.Offset(Rw + 4, 0) = "Erstelldatum": Let ActiveCell.Offset(Rw + 4, 1) = Left(objFolder.GetDetailsOf(Fil, 4), InStr(1, objFolder.GetDetailsOf(Fil, 4), " ", vbBinaryCompare))
Let ActiveCell.Offset(Rw + 4, 0) = objFolder.GetDetailsOf(Left("gh", 2), 4): Let ActiveCell.Offset(Rw + 4, 1) = Left(objFolder.GetDetailsOf(Fil, 4), InStr(1, objFolder.GetDetailsOf(Fil, 4), " ", vbBinaryCompare))
' Let ActiveCell.Offset(Rw + 9, 0) = "Dateiversion": Let ActiveCell.Offset(Rw + 9, 1) = objFolder.GetDetailsOf(Fil, 166)
Let ActiveCell.Offset(Rw + 5, 0) = objFolder.GetDetailsOf("Bum", 166): Let ActiveCell.Offset(Rw + 5, 1) = objFolder.GetDetailsOf(Fil, 166)
Rem 4
ActiveCell.Offset(0, 2).Activate
' 4b
Call FileFolderProps(Parf & "\Movie Maker")
Exit For ' Once we have passed on the full path of the folder, Movie Maker , then we are finished with this macro, so we don't need loop further looking fot the Movie Maker folder
Else
End If
Next Fil ' ===========================================================================================
End Sub
The next post considers the main advanced coding of the second macro
-
2.0
This is post #post23776
https://www.excelfox.com/forum/showt...age2#post23776
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2#post23776
Version 2
I only found 1 so far, masquerading as a 2.6 here:
https://archive.org/details/wmm2installer
This is the important download from there, https://archive.org/details/wmm2installer , https://app.box.com/s/1tddomgrqyfm5h97sdtmz8vvhgpohrrv , from late 2002. It may have been updated around April 2008.
The files it has, shown below, are very similar to those for 2.1, 2.5, 2.6
Code:
_____ Workbook: Movie Maker Versions.xls ( Using Excel 2013 32 bit )
|
|
|
|
|
|
|
|
|
WMM2ERES.dll |
|
|
|
|
WMM2RES.dll |
|
license.txt |
MovieMk.chm |
|
|
|
|
|
|
|
|
|
4 KB |
|
|
|
|
4.05 KB |
|
8,16 KB |
714 KB |
| Jewano install 2 5 Dec 2023 Erstellte 13 Aug 2009 |
|
|
|
|
|
|
|
|
20.12.2002 |
|
|
|
|
20.12.2002 |
|
Textdokument |
Kompilierte HTML-Hilfedatei |
| \ archive org details wmm2installer\Jewano Install Dec 5 2023 |
wmm2installer.exe |
5.50.4134.600 |
12.286 11.9 12.580.696 12.0 12.582.912 |
|
|
|
|
|
2.0.3312.0 |
|
|
|
|
2.0.3312.0 |
|
27.01.2003 |
27.11.2002 |
| Name |
Movie Maker |
1033 |
moviemk.exe |
MUI |
sample.wmv |
Shared |
WMM2AE.dll |
|
WMM2ERES.dll |
WMM2EXT.dll |
WMM2FILT.dll |
WMM2FXA.dll |
WMM2FXB.dll |
WMM2RES.dll |
WMM2RES2.dll |
|
|
|
13.1 15.1 15.854.032 15.1 15.888.384 |
|
3,21 MB |
|
628 KB |
|
164 KB |
|
4,00 KB |
7,50 KB |
393 KB |
490 KB |
318 KB |
4,09 MB |
6,00 KB |
|
|
| Elementtyp |
Dateiordner |
Dateiordner |
Anwendung |
Dateiordner |
Windows Media-Audio-/Videodatei |
Dateiordner |
DLL-Datei |
|
DLL-Datei |
DLL-Datei |
DLL-Datei |
DLL-Datei |
DLL-Datei |
DLL-Datei |
DLL-Datei |
|
|
| Änderungsdatum |
05.12.2023 |
05.12.2023 |
20.12.2002 |
05.12.2023 |
19.11.2002 |
05.12.2023 |
14.04.2008 |
|
14.04.2008 |
14.04.2008 |
14.04.2008 |
14.04.2008 |
14.04.2008 |
14.04.2008 |
14.04.2008 |
|
|
| Dateiversion |
|
|
2.0.3312.0 |
|
|
|
2.1.4026.0 |
|
2.1.4026.0 |
2.1.4026.0 |
2.1.4026.0 |
2.1.4026.0 |
2.1.4026.0 |
2.1.4026.0 |
2.1.4026.0 |
|
|
Worksheet: 2 2.1 (2.5)
https://i.postimg.cc/SQLdw105/Version-2-Files.jpg
https://i.postimg.cc/SQLdw105/Version-2-Files.jpg
The basic coding to get the initial results as shown above
What looked potentially a useful coding way I got from this good source, https://www.youtube.com/watch?v=jTmVtPHtiTg . Summarised, the coding there treats things, (I think probably everything, Folders and files), in a folder as Items of that folder. You loop through those items, and are able to get a lot of properties for each one. Each property is returned from a code line of this general form PropertyValue = objFolder.GetDetailsOf(Fil, 166) (For want of a better descriptions I will refer to this as the windows shell object way)
The basic looping structure would then be of this sort of form
Dim objShell As Shell32.Shell: Set objShell = New Shell32.Shell ' https://i.postimg.cc/fz9zrnnm/tools-referrences-microsoft-shell-controls-and-automation.jpg https://i.postimg.cc/sdc9s54h/tools-...automation.jpg
Dim objFolder As Shell32.Folder: Set objFolder = objShell.Namespace(FullPathToFolder) '
Dim Fil As Shell32.FolderItem
__For Each Fil In objFolder.Items
___PropertyValue = objFolder.GetDetailsOf(Fil, 166)
__Next Fil
So , briefly, Fil is declared as a folder Item, and we loop through each of them in the folder. At each loop we can get a particular property from a number. In that example I have 166, which so far always seems to give me a version number.
To get the full listing of the numbers for the different properties available, see here https://www.youtube.com/watch?v=jTmVtPHtiTg&t=560s
https://www.youtube.com/watch?v=jTmV...8sZ9zYqog9KZ5B
https://www.youtube.com/watch?v=jTmV...UOM9zYlZPKdOpm
Also notes on the basic coding using the windows Shell object can be see here https://www.excelfox.com/forum/showt...ll=1#post23920
-
Versions 2.1 (2.5)
This is post #post23777
https://www.excelfox.com/forum/showt...age2#post23777
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2#post23777
Before going any further, I think I would like to take a bit of a tie out and recheck the codiing
-
OBS Classic, Open Broadcaster Software (original stuff).
-
YouTube, Video making and editing, etc. coupled to excelfox ( windows Movie Maker )
Thread 2936 https://www.excelfox.com/forum/showt...-Movie-Maker-)
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)
This is post #post23586
https://www.excelfox.com/forum/showt...ll=1#post23586
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23586&viewfull=1#post23586
https://www.excelfox.com/forum/showt...er-)#post23586
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23586
Movie maker History
Summarised History, (Not Complete) Initial versions History, 1 - 6
There is a bit of overlap, and as often with Microsoft Version Histories, there is confusion and disagreement. The following is the best average I have so far. The (date stamps) are my best average so far and are intended as an approximate time line
(2000) - Version 1.0 https://i.postimg.cc/8csCfWf2/Movie-Maker-Version-1.jpg https://i.postimg.cc/m1f40Pwj/Movie-Maker-Version-1.jpg
The first release of Windows Movie Maker was included with Windows Me on September 14, 2000 (ME build 2416 https://betawiki.net/wiki/Windows_Me_build_2416 ) . Windows 2000 did not have it, but it could be copied** successfully to it. (** see xxxxxxx )
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP a year later, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. ( After the development reset, the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
(2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
So that was an introduction, going up to around the Vista time. Up to this time Movie Maker was generally a version bundled into an operating system, (although as mentioned, it could often be easily added too operating system’s not having a particular version)
From windows 7, it was mostly something to download.
We have approximately got to the point at this stage , typical in Microsoft, an intermediate period stage, where things got newer and in many user’s opinions, worse.
But, as mentioned, in the case of Movie Maker, things are a bit blurred. Not criticising necessarily, just saying. If you keep your wits about you , then you can pick out good stuff from around this period
Attempt to order into Windows Versions
The following 3 posts order Movie Maker approximately into the three main Windows versions which officially supported Movie Maker
XP era
Vista era
Windows 7 + era
-
Windows 7 + era
This post is https://www.excelfox.com/forum/showt...ll=1#post23589 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23589&viewfull=1#post23589
https://www.excelfox.com/forum/showt...er-)#post23589 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23589
Windows 7 + era versions
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up… From windows 7, Movie maker was officially mostly bundled inside something to be downloaded, although it is not clear if there may have been a standalone initial version, perhaps in an overlap period
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
As for the "Windows Live" version, A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. Windows Live Movie Maker 2009 is last version to support Windows XP, ( Windows Live Photo Gallery version 14.0.8117.416 )
Live Movie Maker 2009 supported both Windows Vista and Windows 7. About this time, 2009, Windows Movie Maker was no longer included with the operating system, which most likely means Vista will usually have Movie Maker, and a small chance it might also have Windows Live. I appear to have both on a Vista machine from new, ( it is showing as Windows Live Essentials 2011 https://i.postimg.cc/x8vVRv9Z/Window...nstllation.jpg )
https://i.postimg.cc/7hq9bjvt/Window...Maker-2009.jpg https://i.postimg.cc/ygrcbQ80/Window...Maker-2009.jpg
(2010) - Version 2011
The only way to obtain Live Movie Maker on Windows 7 from this time and later was through the Windows Live Essentials suite, although some manufacturers pre-installed the application on new PCs.
An updated version , Windows Live Movie Maker 2011, was released on August 17, 2010, adding features such as webcam capture, support for high-definition video, the ability to upload videos directly to SkyDrive, Facebook, and YouTube through their respective web APIs, and the ability to add media files stored on network shares to projects .
Windows Essentials 2011, Released on 30 September 2010, "Windows Live Essentials 2011" runs on Windows Vista or later. Accordingly, it runs successfully on Windows 10 (just the same as any other 32-bit program
(So Windows Movie Maker was known as Windows Live Movie Maker for the 2009 and 2011 releases)
https://postimg.cc/sMSHvPb4
https://i.postimg.cc/sMSHvPb4/Window...Maker-2011.jpg
(2012) - Version 2012 2012.1
Windows Essentials 2012 ( discontinuation of the Windows Live brand (and the re-branding of the Windows Live suite as Windows Essentials )
With the discontinuation of the Windows Live brand (and the re-branding of the Windows Live suite as Windows Essentials , Windows Movie Maker 2012 was released in April 2012. Support for recording voice-overs was restored, along with an audio mixer and integration with several free stock music services. H.264/MP4 became the default export format (replacing Windows Media Video, but still can be used), support for uploading to Vimeo was introduced (other sites were added to the list in the Windows 8.1 release of the suite), and hardware accelerated video pila stabilisation was also added as an exclusive feature for Windows 8 users.
So the last version was Movie Maker 2012 (they dropped the "Live" branding, so it makes for confusion with the much earlier original Movie Maker ).
Windows Essentials 2012 was last updated in April 2014, support ended in 2017, it was removed for download on January 10, 2017.
https://i.postimg.cc/0y1MM0Dg/Window...Maker-2012.jpg
https://i.postimg.cc/gn4k1Rg4/Window...Maker-2012.jpg
My best guess, just my opinion, is that Movie Maker was stopped as it was not reaching out to people and using them in the way that Microsoft had hoped. Movie maker is still regarded by many people as very good, but not at the top end of what is currently available.
Ref
https://www.youtube.com/watch?v=0ltJ...LIm9xI-2ZpVF-q
-
Vista era versions
This post is https://www.excelfox.com/forum/showt...ll=1#post23588 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23588&viewfull=1#post23588
https://www.excelfox.com/forum/showt...er-)#post23588 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23588
Vista era versions
( (2006) - Version 6.0 ( 2.7 )
The first next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
It included new effects and transitions, support for playback on the Xbox 360,and support for the DVR-MS file format that Windows Media Center records television in. The HD version in Premium and Ultimate editions of Windows Vista also added support for capturing from HDV camcorders. The capture wizard also created DVR-MS type files from HDV tapes. However, the Windows Vista version of Windows Movie Maker removed support for importing video from an analog video source such as an analog camcorder, VCR or from a webcam. There is no "2.7 XP version". People may incorrectly be referring to the Windows Vista version of Windows Movie Maker 2.6 that is basically a CPU-only version using the XP code for those on Vista that didn't have a powerful enough GPU. As some older systems might not be able to run the new version of Windows Movie Maker. Vista at the end of the final pre-release development stages may also have been code-named 2.7 )
(2007) - Version 2.6 https://i.postimg.cc/HLxZ8ksq/Version-2-6.jpg
https://i.postimg.cc/SnB7wq9d/Version-2-6.jpg
So, Microsoft also released an updated older version 2.6 for Windows Vista on Microsoft Download Centre, possibly around 2006 - 2007. This version is basically the same as Windows Movie Maker 2.1 and included all of the old effects and transitions, but it excludes the ability to capture video. It can only be installed on Windows Vista and is only intended for use on computers where the hardware-accelerated version cannot run. 2.6 is very similar to 2.5, as it was, or at least is often referred to as, a refurbished XP version 2.5
(2008) - Version 2009
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up…
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
This was supplied as a download, from which you could, amongst other things, install "Windows Live" version of movie maker https://i.postimg.cc/hjBqj42L/Window...-installer.jpg
As for the "Windows Live" version of movie maker , A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. ( Windows Live Movie Maker 2009 is officially the last version to support Windows XP , ( Windows Live Photo Gallery version 14.0.8117.416 ) )
This version shows interface changes including ribbon similar to that starting in Microsoft Office in 2007.
This version added functions like "Auto Movie" which can convert a Video directly to YouTube or DVDs
https://i.postimg.cc/7hq9bjvt/Window...Maker-2009.jpg https://i.postimg.cc/ygrcbQ80/Window...Maker-2009.jpg
-
OBS Classic, Open Broadcaster Software (original stuff).
2015
Code:
* Fixed a button label issue when starting/stopping streaming
* Added a check to make sure if adapter still exists; if not, use default
* Added option to advanced settings to allow full color range encoding (partial by default for compatibility purposes)
* Added option to allow the ability to set the YUV color space and color range for video devices
* Added support for IPv6
* Fixed bug where warnings for CBR/keyint/etc wouldn't display for certain services (like hitbox)
* Fixed NVenc CBR to actually be constant bitrate
0.64 Beta - 2015-01-23
* Fixed a few issues with Elgato devices and made sure that buffering is always enabled for them as the default
* Fixed a bug with animated gif handling
* Fixed a bug with with game capture potentially causing crashes in 64bit games
* Updated x264 to the latest revision
* Added Opacity option to slide show source
* Added the scene switcher plugin as an OBS default plugin
0.65 Beta - 2015-03-06
* Updated server list
* Fixed debug files
* Minor Bug fixes
0.651 Beta - 2015-03-25
* Fixed a potential crash with gif files
* Fixed a bug where transitions set to under 3 seconds would get stuck
* Added ability to add custom services
* Added ability to add folders to image slideshow source rather than individual files
0.652 Beta - 2015-07-10
* Fixed a bug where adding folders to the image slideshow wouldn't work properly
0.653 Beta - 2015-07-21
* Fixed an issue with log files not reporting the correct windows version
* Fixed windows 10 slowdown capturing DirectX 9 games with game capture
0.654 Beta - 2015-08-02
* Fixed a windows 10 slowdown capturing DirectX 9 games with game capture (due to a recent windows update that invalidated the last patch)
0.655 Beta - 2015-08-09
* Fix outdated DirectX installer link
* Fix FLV format bug that affected some video file players/demuxers
* Add support for more quicksync CPUs
* Save scenes/sources when windows itself is shutting down the program
* Don't deselect when ctrl-clicking empty space
* Don't snap crop when resizing a source
0.656 Beta - 2015-10-02
* Updated game capture for latest windows 10 update
* Fixed a bug where certain devices (particularly elgato devices) could cause a crash when they change resolution or when starting up
0.657 Beta - 2015-11-24
-
Test Video,YouTube, Video making and editing, etc. coupled to excelfox (windows Movie Maker
2016
* Updated NVENC
* Fixed a bug where game capture could crash certain games if the device had to reset for whatever reason
* Fixed game capture performance issue for DirectX 9 games on the latest windows 10 update
0.658 Beta - 2016-07-28 (from Aug 2016 Log text)
Get OBS Classic Sept 03 2016 https://i.postimg.cc/cL7Nt36W/Get-OB...-Sept-2016.jpg
https://i.postimg.cc/02Y8DFHh/Get-OB...6-redirect.jpg
Summary again
OBS Studio started out as a small project created by Lain Bailey, but quickly grew with the help of many online collaborators working both to improve OBS and to share knowledge about the program. The first version was released in August 2012. In 2013, development started on a rewritten version known as OBS Multiplatform (later renamed OBS Studio) for multi-platform support, a more thorough feature set, and a more powerful API. In 2016, OBS "Classic" OBS Classic (Open Broadcaster Software) lost support and OBS Studio became the primary version
https://obsproject.com/forum/threads...7/#post-585351 Sep 18, 2022 #3 not true. I been running OBS 0.659b With Browser Installer for years on Vista records and streams no problem.
I have also got OBS-Studio-21.0.1-Full-Installer to install but uninstalled right away because i like 0.659b better.
0.6 Feb 16, 2014 obs_0_659b_installer.exe
https://i.postimg.cc/bY9JWTnX/Get-OB...-2016-2016.jpg
https://i.postimg.cc/CLM1gqCR/Get-OB...6-redirect.jpg
https://i.postimg.cc/FzNK1f2n/Get-OB...6-redirect.jpg
https://i.postimg.cc/gjs2hzpc/OBS-0-...ck-Machine.jpg
Share ‘OBS_0_659b_With_Browser_Installer_From Wayback Machine.exe’ https://app.box.com/s/i3n4bxhuadp77ziqfyxl54xbeg01mmmm
-
OBS Classic, Open Broadcaster Software (original stuff).
-
YouTube, Video making and editing, etc. coupled to excelfox ( windows Movie Maker )
Thread 2936 https://www.excelfox.com/forum/showt...-Movie-Maker-)
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)
This is post #post23586
https://www.excelfox.com/forum/showt...ll=1#post23586
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23586&viewfull=1#post23586
https://www.excelfox.com/forum/showt...er-)#post23586
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23586
Movie maker History
Summarised History, (Not Complete) Initial versions History, 1 - 6
There is a bit of overlap, and as often with Microsoft Version Histories, there is confusion and disagreement. The following is the best average I have so far. The (date stamps) are my best average so far and are intended as an approximate time line
(2000) - Version 1.0 https://i.postimg.cc/8csCfWf2/Movie-Maker-Version-1.jpg https://i.postimg.cc/m1f40Pwj/Movie-Maker-Version-1.jpg
The first release of Windows Movie Maker was included with Windows Me on September 14, 2000 (ME build 2416 https://betawiki.net/wiki/Windows_Me_build_2416 ) . Windows 2000 did not have it, but it could be copied** successfully to it. (** see xxxxxxx )
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP a year later, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. ( After the development reset, the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
(2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
So that was an introduction, going up to around the Vista time. Up to this time Movie Maker was generally a version bundled into an operating system, (although as mentioned, it could often be easily added too operating system’s not having a particular version)
From windows 7, it was mostly something to download.
We have approximately got to the point at this stage , typical in Microsoft, an intermediate period stage, where things got newer and in many user’s opinions, worse.
But, as mentioned, in the case of Movie Maker, things are a bit blurred. Not criticising necessarily, just saying. If you keep your wits about you , then you can pick out good stuff from around this period
Attempt to order into Windows Versions
The following 3 posts order Movie Maker approximately into the three main Windows versions which officially supported Movie Maker
XP era
Vista era
Windows 7 + era
-
OBS Classic, Open Broadcaster Software (original stuff).
Thread 2935 https://www.excelfox.com/forum/showt...ed-to-excelfox https://www.excelfox.com/forum/showthread.php/2935-Testing-Videos-YouTube-Video-making-and-editing-etc-coupled-to-excelfox
This is post 23426
https://www.excelfox.com/forum/showt...ll=1#post23426 https://www.excelfox.com/forum/showthread.php/2935-Testing-Videos-YouTube-Video-making-and-editing-etc-coupled-to-excelfox?p=23426&viewfull=1#post23426
https://www.excelfox.com/forum/showt...lfox#post23426 https://www.excelfox.com/forum/showthread.php/2935-Testing-Videos-YouTube-Video-making-and-editing-etc-coupled-to-excelfox#post23426
2014
Code:
* Fix an issue where hotkeys pressed while stream delay is finishing would cause a crash (R1CH)
* Fix an issue where disconnections would report the wrong error code (R1CH)
* Fix an issue with network initialization (R1CH)
* More error/bug checking/logging (R1CH)
* You no longer have to use the nvidia control panel to make nvidia laptops capture properly, you can now simply select the nvidia adapter in OBS and it will function properly (Jim)
* Fix a bug with using two push to talk hotkeys, make it so that if both buttons are down, only when the second button is released will it deactivate push to talk. (Jim)
* Can now "reset" your mic if necessary in audio settings if for whatever reason the mic audio device needs to be reset, which will cause it to reacquire itself. (Jim)
* Fix mic removal/disconnection flaw, if your mic gets disconnected it's no longer required to restart the stream, it will automatically reacquire when it's plugged in again. (Jim. FINALLY. Why, Jim, did you take so long with this? This was a serious issue. Why am I referring to myself in the third person? ..Why am I talking to myself?)
* Fix mic/device gradual syncing issues, remove "Mic Sync Fix Hack" in advanced because it fixes that problem. This was an issue that mostly happened with mics, the Avermedia Live Gamer Portable, and next-gen consoles (Jim)
* More improvements to QSV (Palana)
* Add NVEnc encoder (Written by BtbN. NOTE: requires nvidia key on non-quadro nvidia video devices)
* Because the above required more room, the "Dashboard Link" button has been removed.
* Add separate Start/Stop Recording button to the main window, you can now stop/start recording without stopping the stream. On top of that, reconnecting will no longer stop everything, you will keep recording while reconnecting. Notification also added to the status bar when streaming and/or recording is on/off. (Thanks to the awesome Paibox/Palana duo)
0.60 Beta - 2014-02-02
* Made a workaround for an issue where kona lhi devices wouldn't work properly due to their incomplete directshow filters (Jim)
* Removed the nvidia optimus "workaround" because nvidia optimus drivers seem to be too unstable when handling it and can crash when its used (Jim)
* Make it so the "WTF" log message for system clock only occurs if over a certain threshold (Jim)
* Added a log window that can be opened and viewed while streaming (Palana)
* Fixed a crash that would happen if you press start streaming and stop streaming too quickly (Palana)
* Added a few new options for QSV, and made a few minor improvements (Palana)
* Disable "keep recording" checkbox if file output is disabled (Palana)
* Add start/stop recording hotkeys (Palana)
* If set to both stream and record, enable recording button when not streaming (Palana)
* Moved "Open Log Folder" to help menu (Palana)
* Added new "Log Files" submenu to the help menu. In this menu, you can now run the analyzer on your log files, upload log files to github gists to make it easier for devs to see, or view them yourself without having to go to the folder. (Palana)
* Refactored bitmap handling and allow animated gifs in the slideshow (HomeWorld)
0.610 Beta - 2014-02-16
* I didn't properly recompile QSV stuff, which caused it to crash. Fixed that. (Jim)
* Fixed a bug with elgatos where they wouldn't work (Jim)
* Fixed issue with analyzer (R1CH)
0.611 Beta - 2014-02-16
* Fixed a bug with FLV files (paibox)
0.612 Beta - 2014-02-18
* Add -profile [profile name] command line option to start up with a specific profile (Jim)
* Add a small visual indicator for global sources in the sources list box (HomeWorld)
* Added an "aspect ratio" display to video settings (Palana)
* Moved "Use input device for desktop audio" to advanced settings (Palana) (certain individuals suddenly shed tears of joy)
* Fix right-to-left language support so it displays in the proper order (Palana/Jim/AlderaaN)
* Fix a crash with higher bitrates on nvenc (BtbN and R1CH)
* Make a few adjustments to QuickSync encoder (Palana)
* Move Nvenc/Quicksync encoder selections to encoder settings (Palana)
* Fix start/stop streaming hotkeys when used with the same key (Palana)
* Add support for controller hotkeys (BtbN)
0.613 Beta - 2014-03-07
* Remove 'use input devices for desktop audio' and make it so it can only be used via ini file. If you need to use it, then enable it in your profile ini file in %appdata%\obs\profiles, under [Audio], InputDevicesForDesktopSound=1 -- we are not going to provide an option in the UI for this because people kept enabling it without know what they were doing.
* Reduce the minimum allowable reconnect timeout to 0 (Jim)
* Fix an issue with game capture where the mouse cursor wouldn't always show up after updating its settings (Homeworld)
* Renamed 'audio time offset' to 'audio sync offset' so users actually know specifically what it is (Jim)
* Added some more important logging info, especially things like logging what game capture is trying to hook to, and logging audio sync offsets (Jim)
* Add a fast experimental windows 7 monitor capture method in game capture (homeworld)
* Fix mono audio (Jim)
* Fix 'defaults' button behavior in advanced (paibox)
* Fix audio mute threshold (R1CH)
* Fix invalid log generation (Palana)
* Fix a lot of bugs (Palana & R1CH)
* Implement an 'optimize' button in publish settings (Palana)
* Add optional 'safe' game capture hooks for anti-cheat compatibility (Jim)
* Use safer hooks so that using other hook programs doesn't cause the target game crash with game capture (vulture)
0.620 Beta - 2014-04-23
* Made it so you cannot assign left/right mouse buttons as hotkeys (listen, I know that some people are going to disagree with this, but it's causing some serious problems for new users. They accidentally click the mouse in the box and then don't realize they set a hotkey to their mouse button, and then say "why is this action occuring every time I click my mouse?" ..Please, find a different key/button to use or put it in the ini file manually)
* Clarified some text about the anti-cheat option (basically, don't use it unless the game has anti-cheat protection because otherwise it can flag a false-positive as well, which is INCREDIBLY annoying)
* Fixed a potential anti-virus false-positive with game capture that was happening with 0.62b
0.621 Beta - 2014-04-23
* Fixed an issue with game capture that caused it to stop working for many people
0.622 Beta - 2014-04-25
* Fix game capture performance issues with the latest windows 8.1 update that was causing many games to lag (jim)
* Save the hidden unmuted volume values if exiting the program while volume was muted (jim)
* Add 'set base resolution' back to window capture by popular request (jim)
* Fix potential audio/video sync issues that would happen with hardware encoders (jim)
* Changed to new volume icons (homeworld)
* Make a few minor improvements to quicksync (palana)
* Fix NVenc with the latest nvidia drivers and beta drivers (btbn)
* Warn users if they installed plugins of the wrong architecture (r1ch)
* Show an error if game capture is blocked by an outside source (r1ch)
0.623 Beta - 2014-05-21
* Made a hotfix for streams not loading properly due to a commit that managed to pass initial testing (the quicksync/nvenc sync fix)
0.624 Beta - 2014-05-21
* Update localization files for different languages (slipped by me last time)
* Updated server lists
* Again attempt to fix the bug where QSV/nvenc could sometimes cause streaming to sort of bug out (jim)
* Update nvenc (btbn)
* Update x264 version (btbn)
* Show warning if comodo antivirus is blocking the network connection for whatever reason (r1ch)
* Fix game capture performance issue for D3D9 games on latest windows 8.1 versions (jim)
0.625 Beta - 2014-06-16
* Use application compatibility manifest to prevent OBS from running on unsupported revisions of windows (R1CH)
* Preserve game capture target even if it isn't running (R1CH)
* Move "show log window" to help menu (jack0r)
* Remove help file, replace with online help which is more up-to-date (jack0r)
* Check for XInput support in the installer (R1CH)
* Remember 1:1 preview state on restart (Jim)
* Made it so game capture hotkey will remember as well as save the window it was last assigned to capture to, and always attempt to re-hook it again (Jim)
* Disable QSV encoder settings if QSV isn't selected as encoder (Palana)
* Remove justin.tv references (R1CH)
* Improve game capture hooking (R1CH)
* Make a number of improvements to quicksync encoder (Palana)
* Update NVenc to latest NVenc API and make a number of improvements (BtbN)
* Update x264 to fix a crash that was occurring due to its version (R1CH)
* Fix issues with BF4 and borderless windowed mode (Jim)
* Fix some freezes that could happen when stopping stream (R1CH)
* Fix keyboard tab order of all controls in the properties/settings windows (jack0r)
* Fix other various random minor bugs and potential issues (R1CH)
* Fix bug where the log menu wouldn't display things correctly (Palana)
* Fix issues with some unicode characters not displaying correctly (Jim)
* Fix a crash if removing global sources with no scenes (R1CH)
* Fix a crash in audio settings if no devices are present (R1CH)
* Fix potential github gist API issue (R1CH)
* Fix issue where game capture would stop capturing certain games such as league of legends after the game goes back to lobby (Jim)
* Add a 'Copy To' option in scenes to allow you to copy scenes between scene collections (Glought)
* Add 'import' button to the global sources dialog to allow importing of global sources from other scene files (Glought)
* Add scene collections feature (ability to change between different sets of scenes, accessible via the 'scene collection' menu) (Glought)
* Add option in uninstaller to remove all saved settings and plugins (R1CH)
* Add a dedicated hotkey panel in settings (Palana)
* Add a drop-down to the recording button which has an option to use standard recording, replay buffer, or both at the same time (Palana)
* Add a replay buffer feature that allows you to save video files of the last configured number of seconds (Palana)
* Add DirectX 8 and DirectDraw capture to game capture (bl00drav3n)
0.630 Beta - 2014-09-07
* Fix a bug where sources that have inverted textures would not display
0.631 Beta - 2014-09-07
* Fix a freeze issue with quicksync
* Restore "Push to talk" checkbox
* Fix a bug with "Copy To" in the scenes context menu in 64bit
0.632 Beta - 2014-09-10
* Add "Show replays" menu to the file menu (palana)
* Update service list (r1ch)
* Fix "Show recordings" in the file menu (palana)
* Fix a bug where second push-to-talk hotkey wouldn't stay assigned (palana)
0.633 Beta - 2014-09-13
* Update services
* Fix bugs with recording file names
* Add support for elgato resolution changing (1920x1080, 1280x720, 640x480, 480x360) (Jim)
0.634 Beta - 2014-09-15
* Fix a service that was unintentionally removed (r1ch)
* Fix issues with elgato (Jim didn't test with the elgato 1.x.x software)
0.635 Beta - 2014-09-16
* If an elgato device is in use and 'custom resolution' is not set, it will default to the closest resolution to the OBS base resolution
* Disable QSV on windows vista, as it's not supported (Palana)
* Make it so that streams can close without freezing up the application. You can't start the stream util the stream until the previous stream has stopped, but it will no longer freeze the main window (Palana)
* Add warnings when using invalid file paths with replay buffer or recording (Palana)
* Fix replay buffering being marked as disabled when start recording fails (Palana)
* Fix a crash with elgatos when using 'output to desktop' for audio (FBirth)
0.636 Beta - 2014-10-02
* Fixed a crash on start streaming that could happen (for example if stream delay was enabled) (Palana)
0.637 Beta - 2014-10-04
* Fixed D3D9 game capture performance issues on the latest update of Windows 8.1 (Jim)
* Removed Chicago from twitch ingest list (CommanderRoot)
* Hopefully fixed an MP4 corruption bug that was occurring under certain circumstances (Palana)
* Fixed monitor capture not updating coordinates when switching monitor (Palana)
* Optimized scene transition fade (HomeWorld)
* Fixed the Advanced -> Custom quick sync encoder settings not enabling buttons (Palana)
* Added a "Enable alpha blending" option to game capture that allows the alpha of the capture to be utilized (Mattias Gustavsson)
0.638 Beta - 2014-11-11
-
OBS Classic, Open Broadcaster Software (original stuff).
2013 July - December
Code:
* Someone clone us a few more Palanas, then clone his clones. What's the worst that could happen?
* Prioritize picking FPS rather than resolution for capture devices (primarily for webcams)
* Add option to disable encoding while previewing
* Add additional warnings if trying to use Aero monitor capture on windows 7 and below, allow disabling of Aero at runtime
* Cropping improvements
* Fixed possible crash / corruption when loading multiple GIFs on a scene
* Fixed crash when using network paths for text sources
* Dynamic bitrate changing support
* Updated to latest libx264 build (which now includes OpenCL acceleration options)
* Fixed multiple libx264 crashes (all thanks to R1CH and the x264 devs)
* Per-scene volume support (made by HomeWorld)
* Fixed a stuttering bug that could happen on some systems with game capture
* Fixed a few bugs with OpenGL capturing
* Added game capture support for windows 8.1 preview
* Greatly improved 64bit DirectX 9 game capturing
* Greatly improved OpenGL capturing performance with game capture
* Several methods of deinterlacing support for capture devices (by Palana)
* QuickSync encoding support (by Palana)
0.54 Beta - 2013-07-10
* Fixed a crash with libx264 by switching to linux cross-compiled versions compiled with mingw
0.541 Beta - 2013-07-10
* Added QSV profile for platforms with non-functional D3D11 API version 1.6 support and broken acceleration on API version 1.4 (palana)
* Fixed a crash with retro deinterlacing on I420 and UV12 output from devices (palana)
* Made the "Incompatible hook modules detected" error disableable (r1ch)
* Fixed a few more x264-related crashes (r1ch/x264 devs)
* (Hopefully) Fixed a bug with the stream delay option where if you saved to file while streaming it would cause the network to inadvertently disconnect prior to finishing the rest of delay (Jim)
* Fixed various cropping bugs (r1ch)
* Made it so edit mode is not disabled when going fullscreen (ThoNohT)
* Added more context menu options when right-clicking the preview window (ThoNohT)
* Fixed a bug when using game capture with OpenGL games where the game wouldn't capture on certain systems after updating to 0.54+ (Jim)
* Fixed a pretty bad memory leak when using game capture with OpenGL games that would affect the game itself (Jim)
0.542 Beta - 2013-07-19
* Renamed "lagged frames" to "late frames" to be more descriptive of what they are
* Fixed opacity not working on directshow sources with certain color formats
* Fixed monitor capture rotation issues on Windows 8
* Added support for per-service setting recommendations (currently active for Twitch)
* Added a keyframe interval option to advanced settings
* Added congestion control - reduce bitrate when congestion is detected (experimental, requires .ini editing)
* Added support for RTMP authentication (requires .ini editing)
* Global sources are muted when they not present on a scene
* Allow negative audio offset for video devices
* Fixed a crash when using certain hotkeys
* Improved detection for TeamSpeak 3 and ASUS GamerOSD incompatible hooks
* Support additional D3D versions for Vista game capture
* Refactored network code to minimize risk of disconnects and improve throughput
* Finish processing and flushing all frames before disconnecting a stream or closing a recording
* Fixed a bug where game capture would pick some games up as a 1x1 solid color block
* Reverted GL code for the time being until the newer code is a bit more stable
* Fixed a rather bad mic sync issue that has been happening in rare circumstances
0.550 Beta - 2013-08-15
* Using a new fixed version of fast GL capture
* Fixed some opengl capture crashes
* Fixed game capture causing games to crash with windows vista
* Made the mic sync hack optional (as an option in advanced settings now)
* Fixed a bug with mic cutting out
* Fixed a false positive with norton
0.551 Beta - 2013-08-16
* Fixed a bug with GL game capture that was causing it to use the slower variant on most computers (thanks to kharay for pointing it out and helping debug it)
* Updated some more translations
0.552 Beta - 2013-08-17
* Added streaming requirements check to youtube service listing
* Increased speed of shader loading (palana)
* Added saving of custom colors when bringing up a color dialog
* Updated translations (Many thanks to Gol-D-Ace and dodgepong for helping with new translations)
* Fixed a timeout crash that could occur when stopping stream (kernelbase.dll breakpoint crash, r1ch)
* Added "scroll mode" to text source (by that crazy text-loving homeworld who never sleeps)
0.553 Beta - 2013-08-30
* Re-enabled auto-updater, was off by mistake (if you downloaded 0.553 please download 0.554 instead)
0.554 Beta - 2013-08-31
* Fixed a crash when adding scene with no scenes and preview running (r1ch)
* Added a hook check for Dolby Axon to prevent crashes when in use (r1ch)
* Changed default scene buffering to 700 milliseconds
* Fixed an issue where a cropped source can be moved around by dragging it from outside of its visible area (homeworld)
* Made some minor adjustments to monitor capture (homeworld)
* Added an "x264 Encoder Profile" feature in advanced to change from "high" to "main" x264 encoder profiles
* Made the 64bit and 32bit update checks independent (r1ch)
* Added/Changed a few more services
* Fixed a potential crash when stopping stream (though this might still happen on occasion)
* Removed logging of shader cache files
* Fixed some more issues with quicksync (palana)
* Added date/time for FLV files (palana)
* Reduced minimum selectable FPS to 1 for people who for whatever reasons want to do more slideshow-esque streams
* Added a "projector" feature that allows you to preview the stream on a separate monitor in full screen while using OBS on a another monitor, can be used by right-clicking the preview window and using the "projector" option from the context menu and selecting the monitor to use. The projector window can be disabled by pressing escape on it, by closing it on the task bar, or by using the "disable" option in the context menu.
* Audio can now be encoded in either 48khz or 44.1khz (by Extrems)
* Constant framerate issues resolved and performance improved when using it
* Moved encoding to a separate thread to avoid issues with keyframe interval timing and made CFR default
0.57 Beta - 2013-09-24
* Made a hotfix for a bug where audio can sometimes the mic could cut out. (Need to be careful with those coefficients)
0.571 Beta - 2013-09-29
* Other minor bugfixes and log changes
* Added an option to show only currently plugged in audio devices in the audio section (jim)
* Updated services list (jim)
* Added a -start command line option to start the stream immediately after loading (jim)
* Fixed some issues wth blackmagic/decklink devices to prevent them from blackscreening (don't use the custom resolution checkbox with these devices) (jim)
* Adjusted frame skip threshold to prevent it from triggering too easily (jim)
* Added an option to manually check for updates (r1ch)
* Fixed some crashes caused by external network DLLs (r1ch)
* Made some improvements and fixes to quicksync encoding (Palana)
0.580 Beta - 2013-10-17
* Hotfixed the bug where you couldn't edit the sources properties that somehow managed to squeeze through to release
0.581 Beta - 2013-10-17
* Fixed "push to talk delay", which wasn't working
* Fixed some minor issues with capturing opengl games (hopefully)
* Fixed an issue with windows 8.1 (which just released) where directx 9 games would capture with poor performance
0.582 Beta - 2013-10-19
* Fixed a minor issue where elgato devices would occasionally not initialize properly and have a black screen
* Hotfixed an issue with sources not resizing properly when reconfigured
0.583 Beta - 2013-10-24
* Fixed a bug with window capture's window selection dialog bugging out if there's a window without a title within it (paibox)
* Fixed an issue with game capturing Direct3D 9 games caused by a new windows 8.1 update
0.584 Beta - 2013-11-15
* Switched to the new CBR filler feature of x264 instead of using X264_NAL_HRD_CBR (r1ch)
* Updated x264 to latest development branch (jim)
* Fixed RTMP authentication bug for 64bit OBS (r1ch)
* Added ability to use input devices for the desktop sound channel (for example, use "What you hear" or "Stereo Mix", or even a mic -jim)
* Some QSV fixes/adjustments (palana)
* Fixed some bugs with the shader cache (r1ch/palana)
* Fixed an issue where CoD: Ghosts wouldn't capture properly with game capture (jim)
0.59 Beta - 2013-12-11
* Fixed some issues with locale files
* Force MP3 audio to use 44.1khz to prevent transmission issues, especially with twitch (jim)
* Made it so window capture won't draw a black box if the window isn't found, instead it won't draw anything (so it'll be transparent when the window isn't found -paibox)
* Added "Use WaveOut Renderer" as an option to device source (paibox)
* Fixed an issue where game capture wouldn't capture "Typing of the Dead" properly (jim)
0.591 Beta - 2013-12-16
* Fixed date/time output for FLV files (palana)
* Added 'main' profile override for quicksync, as well as some other minor quicksync tweaks (palana)
* Fixed a potential freeze issue when shutting down stream (r1ch)
* Fixed a bug with per-scene-volume plugin where muting it via hotkey wouldn't properly save settings (homeworld)
* Fixed a bug where device sources sometimes wouldn't properly mute/unmute properly if used as a global source (paibox)
* Fixed an issue with selection of devices that use the same name in the device source (paibox)
* Fixed an issue with game capture performing poorly for DirectX 9 games under certain revisions of windows 7 (jim)
0.592 Beta - 2013-12-28
-
OBS Classic, Open Broadcaster Software (original stuff).
Thread 2935 was original first post https://www.excelfox.com/forum/showt...ed-to-excelfox https://www.excelfox.com/forum/showthread.php/2935-Testing-Videos-YouTube-Video-making-and-editing-etc-coupled-to-excelfox
This is post 23584
https://www.excelfox.com/forum/showt...ll=1#post23426 https://www.excelfox.com/forum/showthread.php/2935-Testing-Videos-YouTube-Video-making-and-editing-etc-coupled-to-excelfox?p=23584viewfull=1#post23584
https://www.excelfox.com/forum/showt...lfox#post23426 https://www.excelfox.com/forum/showthread.php/2935-Testing-Videos-YouTube-Video-making-and-editing-etc-coupled-to-excelfox#post23584
2013 January - May
Code:
* Fixed some more minor memory leaks
* Fixed a bug with MP4 audio/video sync
* Fixed a bug with game capture not being properly movable
* Fixed a bug with stream keys/play paths failing
* Fixed more issues related to mic syncing
* Fixed a bug with frequent disconnects
* Made it so that windows won't go into an idle state while streaming
* Added improved volume meters courtesy of Bill Hamilton once again
* Added a new and improved installer courtesy of R1CH
* Added an auto-updater courtesy of R1CH
* Added options to adjust microphone and capture card audio timing
* Finally implemented capture card audio output options
0.465 Alpha - 2013-01-02
* Added goodgame.ru to services.xconfig after mistakenly taking it out at some point
* Fixed mic crash
0.466 Alpha - 2013-01-04
* Added support for Elgato capture cards (many thanks to the Elgato team)
* Added a "profiles" menu to quickly switch between multiple profiles
* Added the command line option -multi to allow multiple instances of the app to be opened at the same time
* Made numerous changes to the text output, you may need to adjust your text settings or reset the size (coded by HomeWorld)
* Changed the "sub-region" selection window so that it's partly transparent (fixed by HomeWorld)
* Removed the "timestamp" crash and improved compatibility with VAC and many headphones which were having problems
* Added an option to select the desktop sound device (coded by Resonant)
* Added an option for CFR (constant framerate encoding) in advanced for more compatibility with editing programs
* Fixed some more issues with MP4s and improved their compatibility with many editing programs
* Inverted the source list so that sources that are top most are actually at the top and so forth
* Added checkboxes to the sources box so that sources can be disabled while streaming (coded by Bill Hamilton)
* Added an option in advanced to adjust all audio time
* Added an option "Force audio to sync to video time" in advanced settings (just in case there are still any lingering sync issues for anyone)
* Fixed some more issues with mic/audio timing and sync
* Added "low latency mode" which reduces ping issues with multiplayer games and other network applications (coded by r1ch)
0.47 Alpha - 2013-02-04
* Made is so that the scene is periodically saved, can also be saved in the file menu, loading/saving/exporting/importing will probably be added in the future
* Fixed a bug where preset=[preset] or tune=[tune] in custom x264 settings would cause x264 to fail to initialize
* Fixed a few bugs with text
* Fixed a bug where sources would still be active even when disabled
* Fixed a bug with the UYV chroma key shader
* Fixed a bug where the checkboxes in the sources box wouldn't always show up in windows 7 classic theme
* Fixed a bug with new sources being created at the back of the scene instead of the front
* Fixed a crash that could happen while mp4s are building
* Updated x264 dll to the "stable" x264 branch build rather than the latest development master branch, which should hopefully fix the crashes people have been having with it
* Made it so game capture 64bit works with 32bit games and vise versa without having to switch between versions
* Added gamma options to software capture and game capture
0.471 Beta - 2013-02-17
* Added Hashd.tv to the services list
* Fixed a bug with how game capture inject helper was compiled that could cause it to fail under certain circumstances
0.472 Beta - 2013-02-18
* Numerous other bug fixes and crash fixes
* Added a Microphone Noise Gate plugin [Lucas Murray]
* Changed the settings menu and plugin API to allow plugins to have their settings in the main settings window [Lucas Murray]
* Added right click option to the preview area to switch between 1:1 view or stretch to fit [Lucas Murray]
* Added right click option to the preview area to hide the OBS controls [Lucas Murray]
* Added right click option to the preview area to fullscreen it [Lucas Murray]
* Added a message when not previewing or streaming to indicate such [Lucas Murray]
* Updated a number of translations
* Updated x264 to the latest branch
* Updated the help file
* Made a workaround for those buggy homebrew PSeye drivers (I think. ugh.)
* Fixed a number of bugs in the audio subsystem, devices with audio playback issues should now play correctly (Ex. Blackmagic and certain microphones)
* Fixed image sources rendering at 99% opacity when opacity is set to 100
* Fixed a few minor issues with MP4/FLV files
* Fixed issue with CBR transmission in general, should now properly insert the correct SEI data
* Fixed issues with CBR not padding data correctly to make it fully constant bitrate
* Fixed a bug causing the first keyframe not being properly sent with the transmission
* Fixed a couple memory leaks
* Fixed some minor issues with 64-bit Game Capture
* Fixed a bug in advanced with global audio offset
* Fixed a crash related to cursors changing sizes (moving users on teamspeak and mumble. ugh.)
* Fixed a bug where some cursors wouldn't properly display in Game Capture and Windows 8 Software Capture
* Fixed some anti-viruses flagging game capture as a false positive (due to the nature of game capture having to intercept frames directly in the game itself this is always a possibility)
* Added a "use buffering" option to devices. Allows you to specify a buffer duration to delay the device, and will also sync the audio/video. This is a fix especially for Elgato devices and webcams and such.
* Added a hotkey to Game Capture the currently focused window
* Added the ability to delay video capture device sources
* Added a -portable launch option to save settings within the OBS folder instead of in the normal directory. Alternatively, you can also use an empty file named "obs_portable_mode" in the directory to automatically enable it.
* Added the bitrate estimation in the bottom right corner to previewing
* Added a selection of Audio Input Device to the Video Capture Device source. Used for capture cards or forcing a microphone to sync to a video device.
* Added point filtering to Window, Monitor and Video Capture
* Added an opacity setting to the outline option in Text source
* Added a "Defaults" button to the Advanced settings section
* Added a "Video Adapter" dropdown to the video settings to select the video card for OBS
* Added an optimization to the DirectX pipeline
* Added some lower audio bitrate options
* Added "Desktop audio boost" to audio settings, allows boosting of desktop audio sound (in multiples)
* Added an audio filter API for plugins
* Added more downscale options, such as 1.25, 1.75, 2.5, 2.75
* Added Bicubic and Lanczos downscale filters for sharper and more detailed downscaling
* Added an option to use microphone QPC timestamps in advanced settings
* Added an option to adjust the scene buffering time in advanced settings
* Added a compatibility mode option to software capture (renders to RAM first to prevent issues with multiple GPUs)
* Added the ability to duplicate a scene [partouf]
* Added an optional tray notification icon (Configured via general settings) [foxx1338]
* Added right-click options to sources to move to each of the four edges [ThoNohT]
* Added right-click options to sources to center just horizontally or vertically [ThoNohT]
* Added stream start and stop time to log files [ThoNohT]
* Added color key functionality to Image sources [paibox]
* Added a second Push-To-Talk hotkey to audio settings [paibox]
* Added crossbar options to video capture device sources [paibox]
* Made MP4 audio fully seamless as well to reduce editing issues
* Seamless audio data should now fix sync bugs with twitch transcoders for their youtube uploading and the partnered transcoder resolution drop-down
* Fixed audio data so that all audio segments are seamless
* Changed frame timing to a much higher precision technique, should reduce frame jitter
* Changed sources so they don't reset size when you change settings while previewing or streaming
* Changed the network code a bit to remove nearly all of the delay that was caused by internal buffering
* Changed how the frame drop code works
* Split Software Capture into Window Capture and Monitor Capture for clarity, old software capture sources still work
* Removed most of the compile time for MP4 recordings, was getting really annoying.
* Various optimizations to the application itself
0.50 Beta - 2013-04-22
* Added basic cropping support (Hold Alt and drag the edge of the source while editing a scene)
* Fixed a potential mic bug where mic audio can go out of sync (blasphemous sync issues)
* Fixed a bug with the window capture dialog and sub-region selection numbers resetting
* Fixed an issue where capturing would slow to a crawl in certain rare circumstances and computer configurations
* Fixed a bug where game capture would shut down before it had a chance to start on some machines, resulting in black capture or frozen frame
0.51 Beta - 2013-04-26
* Improved error reporting of network and RTMP errors
* Including microsoft's dbghelp.dll in order to ensure proper crash logs are generated
* Fixed an issue where initial disconnects would trigger the reconnect dialog instead of reporting the issue
* Made CBR default for new users
* Increased frame drop thresholds slightly because lower bitrate connections could often drop more frames than desired
* Fixed bug with games such as natural selection 2 not capturing with game capture properly in windowed mode
* Fixed various other minor bugs with game capture
* Improved game capture logging in %appdata%\obs\pluginData\captureHookLog.txt
* Added timestamps to all log entries
* Fixed an issue where OBS would not have required access for game capture to capture certain games even when run as administrator (war thunder, many MMOs)
* Fixed another potential crash hazard that I can't actually remember
* Fixed a crash in directshow
* Made some minor improvements to gif files
* Made is so that unchcked sources are internally destroyed when disabled instead of always active
* Improved optimization for any code that can make use of SSE2
0.520 Beta - 2013-05-07
* Fixed a game capture crash
0.521 Beta - 2013-05-07
* Fixed a crash that could occur with some gif files
* Fixed another game capture crash with certain games (such as guild wars 2)
0.522 Beta - 2013-05-08
-
XP era versions
This post is https://www.excelfox.com/forum/showt...ll=1#post23587 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23587&viewfull=1#post23587
https://www.excelfox.com/forum/showt...er-)#post23587 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23587
XP era versions
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the version 2 – version 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. After the development reset, (the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
( (2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
It included new effects and transitions, support for playback on the Xbox 360,and support for the DVR-MS file format that Windows Media Center records television in. The HD version in Premium and Ultimate editions of Windows Vista also added support for capturing from HDV camcorders. The capture wizard also created DVR-MS type files from HDV tapes. However, the Windows Vista version of Windows Movie Maker removed support for importing video from an analog video source such as an analog camcorder, VCR or from a webcam. There is no "2.7 XP version". People may incorrectly be referring to the Windows Vista version of Windows Movie Maker 2.6 that is basically a CPU-only version using the XP code for those on Vista that didn't have a powerful enough GPU. As some older systems might not be able to run the new version of Windows Movie Maker. Vista at the end of the final pre-release development stages may also have been code-named 2.7 )
(2007) - Version 2.6 https://i.postimg.cc/HLxZ8ksq/Version-2-6.jpg
https://i.postimg.cc/SnB7wq9d/Version-2-6.jpg
So, Microsoft also released an updated older version 2.6 for Windows Vista on Microsoft Download Centre, possibly around 2007-2009. This version is basically the same as Windows Movie Maker 2.1 and included all of the old effects and transitions, but it excludes the ability to capture video. It can only be installed on Windows Vista and is only intended for use on computers where the hardware-accelerated version cannot run. 2.6 is very similar to 2.5, as it was, or at least is often referred to as, a refurbished XP version 2.5
(2008) - Version 2009
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up…
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
As for the "Windows Live" version, A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. Windows Live Movie Maker 2009 is officially the last version to support Windows XP, ( Windows Live Photo Gallery version 14.0.8117.416 )
-
YouTube, Video making and editing, etc. coupled to excelfox ( windows Movie Maker )
Thread 2936 https://www.excelfox.com/forum/showt...-Movie-Maker-)
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)
This is post #post23586
https://www.excelfox.com/forum/showt...ll=1#post23586
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23586&viewfull=1#post23586
https://www.excelfox.com/forum/showt...er-)#post23586
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23586
Movie maker History
Summarised History, (Not Complete) Initial versions History, 1 - 6
There is a bit of overlap, and as often with Microsoft Version Histories, there is confusion and disagreement. The following is the best average I have so far. The (date stamps) are my best average so far and are intended as an approximate time line
(2000) - Version 1.0 https://i.postimg.cc/8csCfWf2/Movie-Maker-Version-1.jpg https://i.postimg.cc/m1f40Pwj/Movie-Maker-Version-1.jpg
The first release of Windows Movie Maker was included with Windows Me on September 14, 2000 (ME build 2416 https://betawiki.net/wiki/Windows_Me_build_2416 ) . Windows 2000 did not have it, but it could be copied** successfully to it. (** see xxxxxxx )
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP a year later, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. ( After the development reset, the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
(2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
So that was an introduction, going up to around the Vista time. Up to this time Movie Maker was generally a version bundled into an operating system, (although as mentioned, it could often be easily added too operating system’s not having a particular version)
From windows 7, it was mostly something to download.
We have approximately got to the point at this stage , typical in Microsoft, an intermediate period stage, where things got newer and in many user’s opinions, worse.
But, as mentioned, in the case of Movie Maker, things are a bit blurred. Not criticising necessarily, just saying. If you keep your wits about you , then you can pick out good stuff from around this period
Attempt to order into Windows Versions
The following 3 posts order Movie Maker approximately into the three main Windows versions which officially supported Movie Maker
XP era
Vista era
Windows 7 + era
-
XP era versions
This post is https://www.excelfox.com/forum/showt...ll=1#post23587 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23587&viewfull=1#post23587
https://www.excelfox.com/forum/showt...er-)#post23587 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23587
XP era versions
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the version 2 – version 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. After the development reset, (the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
( (2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
It included new effects and transitions, support for playback on the Xbox 360,and support for the DVR-MS file format that Windows Media Center records television in. The HD version in Premium and Ultimate editions of Windows Vista also added support for capturing from HDV camcorders. The capture wizard also created DVR-MS type files from HDV tapes. However, the Windows Vista version of Windows Movie Maker removed support for importing video from an analog video source such as an analog camcorder, VCR or from a webcam. There is no "2.7 XP version". People may incorrectly be referring to the Windows Vista version of Windows Movie Maker 2.6 that is basically a CPU-only version using the XP code for those on Vista that didn't have a powerful enough GPU. As some older systems might not be able to run the new version of Windows Movie Maker. Vista at the end of the final pre-release development stages may also have been code-named 2.7 )
(2007) - Version 2.6 https://i.postimg.cc/HLxZ8ksq/Version-2-6.jpg
https://i.postimg.cc/SnB7wq9d/Version-2-6.jpg
So, Microsoft also released an updated older version 2.6 for Windows Vista on Microsoft Download Centre, possibly around 2007-2009. This version is basically the same as Windows Movie Maker 2.1 and included all of the old effects and transitions, but it excludes the ability to capture video. It can only be installed on Windows Vista and is only intended for use on computers where the hardware-accelerated version cannot run. 2.6 is very similar to 2.5, as it was, or at least is often referred to as, a refurbished XP version 2.5
(2008) - Version 2009
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up…
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
As for the "Windows Live" version, A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. Windows Live Movie Maker 2009 is officially the last version to support Windows XP, ( Windows Live Photo Gallery version 14.0.8117.416 )
-
OBS Classic, Open Broadcaster Software (original stuff).
2015
Code:
* Fixed a button label issue when starting/stopping streaming
* Added a check to make sure if adapter still exists; if not, use default
* Added option to advanced settings to allow full color range encoding (partial by default for compatibility purposes)
* Added option to allow the ability to set the YUV color space and color range for video devices
* Added support for IPv6
* Fixed bug where warnings for CBR/keyint/etc wouldn't display for certain services (like hitbox)
* Fixed NVenc CBR to actually be constant bitrate
0.64 Beta - 2015-01-23
* Fixed a few issues with Elgato devices and made sure that buffering is always enabled for them as the default
* Fixed a bug with animated gif handling
* Fixed a bug with with game capture potentially causing crashes in 64bit games
* Updated x264 to the latest revision
* Added Opacity option to slide show source
* Added the scene switcher plugin as an OBS default plugin
0.65 Beta - 2015-03-06
* Updated server list
* Fixed debug files
* Minor Bug fixes
0.651 Beta - 2015-03-25
* Fixed a potential crash with gif files
* Fixed a bug where transitions set to under 3 seconds would get stuck
* Added ability to add custom services
* Added ability to add folders to image slideshow source rather than individual files
0.652 Beta - 2015-07-10
* Fixed a bug where adding folders to the image slideshow wouldn't work properly
0.653 Beta - 2015-07-21
* Fixed an issue with log files not reporting the correct windows version
* Fixed windows 10 slowdown capturing DirectX 9 games with game capture
0.654 Beta - 2015-08-02
* Fixed a windows 10 slowdown capturing DirectX 9 games with game capture (due to a recent windows update that invalidated the last patch)
0.655 Beta - 2015-08-09
* Fix outdated DirectX installer link
* Fix FLV format bug that affected some video file players/demuxers
* Add support for more quicksync CPUs
* Save scenes/sources when windows itself is shutting down the program
* Don't deselect when ctrl-clicking empty space
* Don't snap crop when resizing a source
0.656 Beta - 2015-10-02
* Updated game capture for latest windows 10 update
* Fixed a bug where certain devices (particularly elgato devices) could cause a crash when they change resolution or when starting up
0.657 Beta - 2015-11-24
-
Test Video,YouTube, Video making and editing, etc. coupled to excelfox (windows Movie Maker
2016
* Updated NVENC
* Fixed a bug where game capture could crash certain games if the device had to reset for whatever reason
* Fixed game capture performance issue for DirectX 9 games on the latest windows 10 update
0.658 Beta - 2016-07-28 (from Aug 2016 Log text)
Get OBS Classic Sept 03 2016 https://i.postimg.cc/cL7Nt36W/Get-OB...-Sept-2016.jpg
https://i.postimg.cc/02Y8DFHh/Get-OB...6-redirect.jpg
Summary again
OBS Studio started out as a small project created by Lain Bailey, but quickly grew with the help of many online collaborators working both to improve OBS and to share knowledge about the program. The first version was released in August 2012. In 2013, development started on a rewritten version known as OBS Multiplatform (later renamed OBS Studio) for multi-platform support, a more thorough feature set, and a more powerful API. In 2016, OBS "Classic" OBS Classic (Open Broadcaster Software) lost support and OBS Studio became the primary version
https://obsproject.com/forum/threads...7/#post-585351 Sep 18, 2022 #3 not true. I been running OBS 0.659b With Browser Installer for years on Vista records and streams no problem.
I have also got OBS-Studio-21.0.1-Full-Installer to install but uninstalled right away because i like 0.659b better.
0.6 Feb 16, 2014 obs_0_659b_installer.exe
https://i.postimg.cc/bY9JWTnX/Get-OB...-2016-2016.jpg
https://i.postimg.cc/CLM1gqCR/Get-OB...6-redirect.jpg
https://i.postimg.cc/FzNK1f2n/Get-OB...6-redirect.jpg
https://i.postimg.cc/gjs2hzpc/OBS-0-...ck-Machine.jpg
Share ‘OBS_0_659b_With_Browser_Installer_From Wayback Machine.exe’ https://app.box.com/s/i3n4bxhuadp77ziqfyxl54xbeg01mmmm
-
OBS Classic, Open Broadcaster Software (original stuff).
-
YouTube, Video making and editing, etc. coupled to excelfox ( windows Movie Maker )
Thread 2936 https://www.excelfox.com/forum/showt...-Movie-Maker-)
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)
This is post #post23586
https://www.excelfox.com/forum/showt...ll=1#post23586
https://www. excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23586&viewfull=1#post23586
https://www.excelfox.com/forum/showt...er-)#post23586
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23586
Movie maker History
Summarised History, (Not Complete) Initial versions History, 1 - 6
There is a bit of overlap, and as often with Microsoft Version Histories, there is confusion and disagreement. The following is the best average I have so far. The (date stamps) are my best average so far and are intended as an approximate time line
(2000) - Version 1.0 https://i.postimg.cc/8csCfWf2/Movie-Maker-Version-1.jpg https://i.postimg.cc/m1f40Pwj/Movie-Maker-Version-1.jpg
The first release of Windows Movie Maker was included with Windows Me on September 14, 2000 (ME build 2416 https://betawiki.net/wiki/Windows_Me_build_2416 ) . Windows 2000 did not have it, but it could be copied** successfully to it. (** see xxxxxxx )
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP a year later, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. ( After the development reset, the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
(2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
So that was an introduction, going up to around the Vista time. Up to this time Movie Maker was generally a version bundled into an operating system, (although as mentioned, it could often be easily added too operating system’s not having a particular version)
From windows 7, it was mostly something to download.
We have approximately got to the point at this stage , typical in Microsoft, an intermediate period stage, where things got newer and in many user’s opinions, worse.
But, as mentioned, in the case of Movie Maker, things are a bit blurred. Not criticising necessarily, just saying. If you keep your wits about you , then you can pick out good stuff from around this period
Attempt to order into Windows Versions
The following 3 posts order Movie Maker approximately into the three main Windows versions which officially supported Movie Maker
XP era
Vista era
Windows 7 + era
-
XP era versions
This post is https://www.excelfox.com/forum/showt...ll=1#post23587 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23587&viewfull=1#post23587
https://www.excelfox.com/forum/showt...er-)#post23587 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23587
XP era versions
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the version 2 – version 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. After the development reset, (the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
( (2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
It included new effects and transitions, support for playback on the Xbox 360,and support for the DVR-MS file format that Windows Media Center records television in. The HD version in Premium and Ultimate editions of Windows Vista also added support for capturing from HDV camcorders. The capture wizard also created DVR-MS type files from HDV tapes. However, the Windows Vista version of Windows Movie Maker removed support for importing video from an analog video source such as an analog camcorder, VCR or from a webcam. There is no "2.7 XP version". People may incorrectly be referring to the Windows Vista version of Windows Movie Maker 2.6 that is basically a CPU-only version using the XP code for those on Vista that didn't have a powerful enough GPU. As some older systems might not be able to run the new version of Windows Movie Maker. Vista at the end of the final pre-release development stages may also have been code-named 2.7 )
(2007) - Version 2.6 https://i.postimg.cc/HLxZ8ksq/Version-2-6.jpg
https://i.postimg.cc/SnB7wq9d/Version-2-6.jpg
So, Microsoft also released an updated older version 2.6 for Windows Vista on Microsoft Download Centre, possibly around 2007-2009. This version is basically the same as Windows Movie Maker 2.1 and included all of the old effects and transitions, but it excludes the ability to capture video. It can only be installed on Windows Vista and is only intended for use on computers where the hardware-accelerated version cannot run. 2.6 is very similar to 2.5, as it was, or at least is often referred to as, a refurbished XP version 2.5
(2008) - Version 2009
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up…
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
As for the "Windows Live" version, A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. Windows Live Movie Maker 2009 is officially the last version to support Windows XP, ( Windows Live Photo Gallery version 14.0.8117.416 )
-
XP era versions
This post is https://www.excelfox.com/forum/showt...ll=1#post23587 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)?p=23587&viewfull=1#post23587
https://www.excelfox.com/forum/showt...er-)#post23587 https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)#post23587
XP era versions
(2001) - Version 1.1 https://i.postimg.cc/NMdM0bF8/Movie-...ersion-1-1.jpg https://i.postimg.cc/5YF17Bwj/Movie-...ersion-1-1.jpg
Version 1.1 was included in Windows XP, 25 October 2001 as part of Windows XP, and included support for creating DV AVI and WMV 8 files.
(2002) - Version 2.0 ( Sometimes regarded as XP version ) https://i.postimg.cc/2886gsHH/Movie-Maker-version-2.jpg
https://i.postimg.cc/z368gcYW/Movie-Maker-version-2.jpg
Version 2.0 was released as a free update to 1.1, in November 2002, and added a number of new features. It went some way to answering critic on the first version, and often the Classic/Start of Movie Maker around close to XP start time is regarded as the version 2 – version 2.1 era. –
(2004) - Version 2.1 ( Windows XP Service Pack 2 ) https://i.postimg.cc/L4V5C9VY/Movie-...ersion-2-1.jpg
https://i.postimg.cc/SjJmjp3k/Movie-...ersion-2-1.jpg Version 2.1, a minor update, is included in, so coming from installing, Windows XP Service Pack 2
(2001-2006 overlap) ( Windows Vista development time from before XP in 2001 to final release of Vista in 2006 )
The overlap and confusion may have resulted from the design teams being drunk in between times: Microsoft originally expected to ship Vista sometime late in 2003 as a minor step between Windows XP (codenamed "Whistler") and the next planned major release of Windows, code-named "Blackcomb". Vista's original codename, "Longhorn", was an allusion to this plan, a sort of inbetween idea: While Whistler and Blackcomb are large ski resorts in British Columbia, Longhorn is the name of a bar between the two mountains that Whistler's visitors pass to reach Blackcomb.
2004
A Windows Presentation Foundation (WPF) version of Windows Movie Maker was also included in some development builds of Vista (at the time codenamed "Longhorn"), but was removed in the development reset in August 2004. After the development reset, (the interface for the WPF-based Windows Movie Maker was retained in Windows Vista later)
(2005) - Version 2.5 https://i.postimg.cc/NjK0j1vm/Version-2-5.jpg , https://i.postimg.cc/3JSRhtV3/Versio...ransitions.jpg
https://i.postimg.cc/QFrD6Ktd/Version-2-5.jpghttps://i.postimg.cc/mt9RNyTn/Versio...ransitions.jpg
The Movie Maker in Windows XP Media Center Edition 2005 had more transitions and support for DVD burning.
( (2006) - Version 6.0 ( 2.7 )
The next main version is Windows Movie Maker 6.0 which had both a 64-bit version and GPU rendering of effects and transitions. It was released as part of Windows Vista, https://www.youtube.com/watch?v=GqzeFYWjTxI&t=17s (Vista started in 2006), and – like most Windows components – reported version number 6.0.6000, same as Windows Vista itself.
It included new effects and transitions, support for playback on the Xbox 360,and support for the DVR-MS file format that Windows Media Center records television in. The HD version in Premium and Ultimate editions of Windows Vista also added support for capturing from HDV camcorders. The capture wizard also created DVR-MS type files from HDV tapes. However, the Windows Vista version of Windows Movie Maker removed support for importing video from an analog video source such as an analog camcorder, VCR or from a webcam. There is no "2.7 XP version". People may incorrectly be referring to the Windows Vista version of Windows Movie Maker 2.6 that is basically a CPU-only version using the XP code for those on Vista that didn't have a powerful enough GPU. As some older systems might not be able to run the new version of Windows Movie Maker. Vista at the end of the final pre-release development stages may also have been code-named 2.7 )
(2007) - Version 2.6 https://i.postimg.cc/HLxZ8ksq/Version-2-6.jpg
https://i.postimg.cc/SnB7wq9d/Version-2-6.jpg
So, Microsoft also released an updated older version 2.6 for Windows Vista on Microsoft Download Centre, possibly around 2007-2009. This version is basically the same as Windows Movie Maker 2.1 and included all of the old effects and transitions, but it excludes the ability to capture video. It can only be installed on Windows Vista and is only intended for use on computers where the hardware-accelerated version cannot run. 2.6 is very similar to 2.5, as it was, or at least is often referred to as, a refurbished XP version 2.5
(2008) - Version 2009
Around 2008-2009, when windows 7 started, it seems that some further development was done on windows movie maker. The word Live started to crop up…
(2008) - Version 2009
Windows Live Movie Maker. Windows Live Essentials
As for the "Windows Live" version, A new version of the software, renamed Windows Live Movie Maker 2009, was released as a beta on September 17, 2008, and officially released as a standalone product through Windows Live Essentials suite on August 19, 2009. Windows Live Movie Maker 2009 is officially the last version to support Windows XP, ( Windows Live Photo Gallery version 14.0.8117.416 )
