I haven't done this in a while. Here are beta versions for the upcoming version 2.0.1. This is mainly a bug fix versions, some updated camera support, some small feature adds and a bonus easter egg. This links are good for 10 days. Please send your feedback here.

Windows:
Studio Premium http://software.gopro.com.s3.amazonaws.com/PC/GoProStudioPremium-2.0.1.311-Setup.exe?AWSAccessKeyId=AKIAJ2OHNE77HOUYJB6A&Expires=1389331673&Signature=K1JizCRXt%2BtNveHESCdSqg0vo5U%3D

Studio Pro http://software.gopro.com.s3.amazonaws.com/PC/GoProStudioPro-2.0.1.311-Setup.exe?AWSAccessKeyId=AKIAJ2OHNE77HOUYJB6A&Expires=1389331660&Signature=upwNJB/i895gGgPrsn0swAJ6Yg8%3D


OS-X
Studio Premium http://software.gopro.com.s3.amazonaws.com/PC/GoProStudioPremium-2.0.1.246-125.dmg?AWSAccessKeyId=AKIAJ2OHNE77HOUYJB6A&Expires=1389331643&Signature=%2BF0g8/nlbBCZNz80Mkig0IGvYn8%3D

Studio Pro http://software.gopro.com.s3.amazonaws.com/PC/GoProStudioPro-2.0.1.246-125.dmg?AWSAccessKeyId=AKIAJ2OHNE77HOUYJB6A&Expires=1389331379&Signature=vlYwR%2B6eSOntQYyNbPRvJ2vaVBA%3D

Er thanks I guess, still will not convert the file from a Panasonic GH3 (HD Link or GPSP) Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 2.35 GiB
Duration : 7mn 19s
Overall bit rate mode : Variable
Overall bit rate : 45.8 Mbps
Encoded date : UTC 2013-10-07 12:49:15
PANA : DMC-GH3

into Cineform, I had high hopes as Jake said you would be looking at this problem in the next release, that was 6 months ago.

Thanks Roy. This is the type of feedback needed.

Both GoPro Studio 2.0.1 and HDlink still throw up an error and don't convert Nikon D600 mov files in Windows.

HDlink will accept folders of Canon XF305 mxf files, but GoPro Studio doesn't even recognize the mxf files even when navigating to a single file's folder.

So no improvements for me, so far...

Ian

Correct, no XMF in Studio (yet.) Have we broken Nikon D600 MOVs or was that always an unsupported format?

Nikon D600 movs worked in HDLink in the last version but one, but there's a known issues note from Jake somewhere to say that they don't work in Windows in the current version (pre this beta).

I'll follow up with Jake on his return. Thanks.

23.98 vs 23.976 bug still present

We don't consider displaying 23.976 as 23.98 a bug, it is a very common abbreviation. Also 23.976 is itself an abbreviation. 24000/1001 is the only true representation.

By the way, I'd just like to say that it's really good to be involved in these betas a little bit again. Thanks, David.

Happy New Year to Cineform, GoPro and users

We don't consider displaying 23.976 as 23.98 a bug, it is a very common abbreviation. Also 23.976 is itself an abbreviation. 24000/1001 is the only true representation.

Indeed, 24000/1001 is the only true representation, however GoPro Cineform Studio incorrectly interprets any and all 23.976 footage at an exact frame rate value of 23.98000, effectively making 23.98 not a shortcut but an actual frame rate of the footage. All of the footage that is allowed to be interpreted by the GP studio Auto (keep source) footage settings will read in any app as a 23.9800 Even when the original video before Cineform conversion (including the GoPro Hero 3 footage is correctly read by the video editing apps (Premiere Pro, After Effects, and others) is read as a correct 23.9762.
It is also worth mentioning that HDLink does not suffer from this particular issue.
Practical implication is that the converted footage has different duration than the original (at least 1 frame difference for a 10 seconds clip making it difficult to conform in certain workflows) and the sound is out of sync (sound is about 0.010 seconds late in the beginning of the clip when compared to the original source, and about 0.002 by the time we get to 10 seconds.
Force selecting 23.976 in the conversion settings for the clip in GoPro studio is not a viable workaround. While it forces converted clips to be properly presented a 23.976 fps and preserves the correct length of the medias the sound shift still happens just as with misinterpreted 23.9800 conversions.

Yet again, none of this happens when using HDLink app.

This beta version still cant convert mov to CFavi from Nikon D7100. The same error message.

We are now seeing the 23.98 weirdness. Look at that now.

Nikon D600 movs worked in HDLink in the last version but one, but there's a known issues note from Jake somewhere to say that they don't work in Windows in the current version (pre this beta).

Ian, is this on Windows 8? To my knowledge mov conversion should work on Windows 7 but something in Windows 8 has caused this to stop working.

This beta version still cant convert mov to CFavi from Nikon D7100. The same error message.

Windows 8 right? This should work in Windows 7.

Nope Window8.

That is consistent with what i have found. MOV files don't convert on Windows 8...but they should on Windows 7. If anyone is having MOV conversion problems on Windows 7, please let us know.

didn't look in yesterday.... Yes, the problem is Windows 8 (and 8.1). On my Win7 laptop, Nikon ,mov files convert ok.

Slightly newer betas, with 10-days more on the download link. Only bug fix that was listed on the forum is the 23.976 vs 23.98 issue

Windows:
Studio Premium http://software.gopro.com.s3.amazonaws.com/PC/GoProStudioPremium-2.0.1.313-Setup.exe?AWSAccessKeyId=AKIAJ2OHNE77HOUYJB6A&Expires=1390599581&Signature=bHsDGzO86sP7nsfN91FjW95Udv8%3D
Studio Pro http://software.gopro.com.s3.amazonaws.com/PC/GoProStudioPro-2.0.1.313-Setup.exe?AWSAccessKeyId=AKIAJ2OHNE77HOUYJB6A&Expires=1390599610&Signature=zbkk9O37yU122OG/YL0J3LAQzSE%3D


OS-X
Studio Premium http://software.gopro.com.s3.amazonaws.com/Mac/GoProStudioPremium-2.0.1.246-150.dmg?AWSAccessKeyId=AKIAJ2OHNE77HOUYJB6A&Expires=1390599635&Signature=zuug86HfOq0m5M5UXpgmuDVy7TM%3D
Studio Pro http://software.gopro.com.s3.amazonaws.com/Mac/GoProStudioPro-2.0.1.246-150.dmg?AWSAccessKeyId=AKIAJ2OHNE77HOUYJB6A&Expires=1390599648&Signature=dQ8Og3GGwHh9txcGhmhgTMdzjvs%3D

I tried the Studio Pro and yes the mov's converted. :-)

Win Beta premium in a file format that isn't recognized: 313-SETUP[1] File (.313-Setup[1]) I believe I need an extension? UPDATE: added .exe and it worked

Please allow Windows 8 users availability of your software, I have been convinced (by your marketing) of the value in a "Cineform" workflow which is not available for virtually every DSLR out there, I originally brought the problem to support in early September when it was acknowledged.
Oddly: I can convert my native .mov files from my GH3 and Nikon D800 in both Sony Vegas and Davinci Resolve to Cineform, a very taxing way to do it.
I realize that the thrust of the company has been to support the Go-Pro camera, but I hope that some corporate sympathy is extended to a few "before Go-Pro" customers and anyone that has bought a new (WIN) computer in the last year + 3 months (Win 8)

I use cineform for 3D. For years now if I have found that if I convert an mvc file to cineform I would get a thin green line at the bottom of the picture. I suspect this was a studio problem as other applications such as vegas pro and mvctoavi worked correctly.

The premiere pro plugin still does not support page flip mode very well. For instance if I apply the warp stabalizer the two images are displaced vertically relative to each other. When this clip is exported the image is correct. Applying other effects can also produce the same problem

When is the GoProSTudioPC going to be updated for converting Nikon mov to CF?
It works in the Studio Pro latest version.

doesn't work for me in Studio Premium 2.0.1.319 on WIn 8.1

Just crashed for me...had to go back to v.1.3.x

So when are we going to get some lut's that are exportable for protune? Even the new prof. version won't export lut's it seems....that would save me mucho tiempo.....