Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

avid mxf red workflow

jamie parry said:
ok
it does 59.94 now (but only that i think)
i'm not sure it works cos i ain't got any 59.94 stuff so over to you james!!

www.jamieparry.demon.co.uk/mts_fuze_demo.zip

cheers
j
Click to expand...

hmm... it came into a 1080i/5994 project but played back kinda strange. and the clips metadata says its 1080p/29.97. strange.

here's a sample MTS clip if you want to play with it.

http://interdubs.com/r/charlietango/?al=YdxRbBr&an=ck3WBY&e=1ZX5cdT6M

keep it up.


*edit* perhaps my camera is shooting 29.97..... not really sure.
*edit2* added 2 more MTS clips
 
videos done...

videos done...

www.jamieparry.demon.co.uk

also there are links to the demos now on the website
jamfuze
jamfuzeALE
smokeyfuze
MTS_Fuze (although this is a bit squonky at the moment. Only download it if you like seeing software in very early stages.....)
MTS_fuze will probably work in american framerates soon after i get back to the mac.
James has kindly put some files up for me to work with.

anyway, go watch the videos and have a laugh....
i am now on vacation! woo hoo!
j
 
Jamie,

Does JamFuze/SmokeyFuze have a log file for crashes? I have had SmokeyFuze crash on me a couple times in the middle of creating MXF media for offline.

Not sure if all my multitasking on the computer is causing problems or if its an issue with SmokeyFuze. For instance I set it up to convert 10 R3D's to MXF, and it crashed after 6 or 7. I moved the 6 or 7 it already finished and then told it to try again on the other 3 and it worked fine. So I'm not sure why its having problems. Perhaps tonight I'll give it a large task of 20+ clips and see if it works in the morning.

Enjoy your holiday.

-James
 
crashing

crashing

i have pegged jamfuze and all other things i've done to use 8 cores all the time.
i think multi tasking might be a no no!
when i get back i could try and put the processors down to 6 or 4 and see if that makes life any better.
the only thing i can think of at the moment.
everything else is usually rock solid command line stuff
redline ffmpeg etc etc
i haven't got that many R3D's so a large testing session has been out of my hands.
I would suggest if you do a big session
before doing it
restart the mac
don't start any other programs
run smokeyfuze
step away from the mac...don't touch it...don't.........
cross fingers.

i can do a version that doesn't shut the text window at all and that might give us some clues. maybe.
also found this on here
http://www.reduser.net/forum/showthread.php?t=25187&highlight=redline

so maybe taking the cores down,adding more ram or rendering to different disks are things to try.
if its an issue with redline then obviously i can't stop it, but doing the suggestions on this thread seemed to help some people.

j
 
i rebooted. started smokeyfuze and left it going.

i checked it from home and found it had crashed. but processed almost 20 clips before crashing. it ran for about 30 mins. strange. I noticed when it crashes, it seems to continue trying to process the R3D's even though its crashed.

I decided to try again, this time using JamFuzeALE. (i must have an older version, because it creates one ALE per clip. *EDIT* never mind, i see it consolidates into 1 ALE at the end.) Anyway, it got much further than SmokeyFuze did, but also crashed after about an hour. I was monitoring it remotely, and did a quick screen capture after the crash, so you could see what I mean by "still trying process" after crash.

check it out.

http://www.youtube.com/watch?v=7xBXxxl9F-Q

not sure if its a processor thing or what. My mac pro is 'only' a 2x3Ghz Dual-Core Xeon with 4gb ram.

we have a beast downstairs with 8cores and 16gbs of ram. I'll try that tomorrow. I'm going to try a third time tonight and see how it fairs...
 
crashing

crashing

Update:

I have now tested JamFuze and SmokeyFuze on our faster 8core mac. Still crashing. Still at random times. Each time I attempt a batch of 95 clips. And each time I get a different amount done before crashing. On my 8core machine I was able to transcode the most before crashing. (57). On the slower 4core machines, I would range from 15-30 clips before crashing.

Curious if anyone else has attempted a large number of R3D's using JamFuze.

(FYI, I am only counting .mxf files with _v1 in the name)

-James
 
bad news/good news

bad news/good news

hello
boss has now gently expressed "concerns" about me selling jamfuze.
I don't want to get in trouble here so that may be the end of that.
however
Sumners (the company i work for) now has access to programmers which i didn't realize and boss says he will get them to talk to me regarding "productizing" jamfuze properly
ie better gui
looking after licensing issues (lgpl and so on)
Customer support (!)

and then maybe selling it as a Sumners product that i might get some money from. maybe.
so
sorry guys it might be a while before you can use it properly.
However he has said I can give it to beta testers to make my bit as good as i can.
so a few of you will be getting it as a PM thing as long as you keep telling me what is rubbish about it!
James Rayburn we need to sort out the crashing stuff and you seem to be doing the most R3D files so I'll PM you with what we can do to make it (a bit) better......
j
 
jamie parry said:
hello
boss has now gently expressed "concerns" about me selling jamfuze.
I don't want to get in trouble here so that may be the end of that.
[snip]
j
Click to expand...
Hmmm. Since ClipFinder allows the running of post transcoding scripts, it would not be too much effort to knock up something to perform the 2nd stage mxf muxing after ClipFinder had done the grunt. At its simplest level you could have a different script for each resolution you might make, and hard code the parameters.

A neater approach, that would save significant disk space, would be to pipe the RedLine output direct into ffmpeg. If the output was uncompressed then ffmpeg could be used to compress to a far greater range of codecs than the very limited ones allowed by RedLine.

Hans, do you think this idea worth pursuing?
 
disappointment...

disappointment...

I am disappointed too.
I was enjoying my little experiment.
I don't think my boss expected me to make anything that people would want to buy!
I guess I'll just stay in a dark room and fiddle with knobs and balls.
Tim has helped me before with ffmpeg stuff (on windows that was) so he knows what i've done and will be able to sort it all out anyway. for 25fps too....
which kind of makes a mockery of me NOT doing it really.
ah well
j
 
bloody hell! well, looking forward to hearing back from you to further beta test if nothing else.

at least you've shown the community it can be done, and now hopefully people follow your lead.

-jr
 
Hey you guys,

Anyone care to explain to me how bluescreen test footage of my daughter ends up on the internet, together with some commercial footage I shot?

Jamie, that's just plain rude man, you should've asked me first! :head_explode:

Mike Costelloe.
 
sad day

sad day

jamie,

i suppose the good news is that the jamfuze was good enough that your boss was 'concerned'

i too will miss the this VERY useful little utility you developed and the close interaction we have with you... i couple of comments and the software gets fixed (changed, added to).

this doesn't usually happen when 'the programmers' get involved.

i would be happy to continue providing feedback if you're still looking for volunteers.

david
 
public apology

public apology

hello all
this is a public apology
I've already done one in private but i thought a public one wouldn't go amiss.
I have used some of Mike Costelloe's footage in my test videos (now removed)
it never crossed my mind that this would be a problem because i only used a few seconds and because i am an idiot.
Mike is a lovely guy and a great DOP and the mistake is ENTIRELY mine.
sorry to all.
j
i am now going to curl up and die quietly somewhere.....
 
You must log in or register to reply here.
Back
Top