Menu
▾
▴
Re: [derbyscoreboard-devel] Load/Save/Lineup questions
|
From: Jon F. <crg...@sa...> - 2011-06-24 09:35:23
|
I for one am very interested in your scoreboard replay capabilities - we've got no AC at our venue this season, so our on-site video production computer regularly overheats. It would be great to be able to add the overlay later, in a much cooler environment ;-) BTW, if anyone is interested in yet another custom overlay, I've developed one (heavily modified from the default) that shows a decent amount of info (including lead jammer), all squished legibly into the upper left corner. Works pretty good with Vidblaster, in my experience. Thanks, -Jon/AdmiralAshborer - TCDG video production, key grip, best boy, janitor > Sorry I'm late to the discussion, was on vacation and took a few days to > dig > out of email once I got back :) > > Nashville eh? Any chance you're inquiring after seeing the score overlay I > did on the footage I took for the KC vs Nashville game Easter weekend? :) > For others - here is reference of what I've done from one of our home team > games: http://vimeo.com/23783235 Score overlay appears about 30 seconds in > on that particular clip. This is why I was bugging the guys running the > scoreboard for the xml file after our bout last month :) > > This was created using code originally developed by $3 Bill and sent to me > through this board actually, checkout some of the archives from a few > months > ago and you'll see our original conversation. I've just modified it > slightly > for our use so far and built a new overlay template. What it does is parse > the saved xml file and generates a .psd file for each second of the > scoreboard data. You just have to import the frame sequence into AE & > Premiere, set as 1fps, and then just sync time with a jam whistle and > you're > good to go. There are some functions to generate stats info from the same > file, but I haven't gotten those working yet and from the sound of things > it > seemed like the 0.2 code of the scoreboard might be ready with a working > stats page before I got the post-processing stats side working. > > I have the UI built for folks without access to a compiler to use, but > there > are one or two other bullet points I need to integrate before an exe could > be shared and it be useful to you. If you or anyone else is interested in > the PSD frame sequence ability, I can get back to work on that and share > when it's ready. > > -James/MysteryClips, KCRW videographer > > On Tue, May 24, 2011 at 9:56 AM, Mr T > <mrt...@ca...>wrote: > >> On Mon, May 23, 2011 at 11:46 PM, Jeff Davis <jef...@gm...> >> wrote: >> > Thanks, very informative. I was able to figure out a way to save and >> later >> > load the lineups for jammer display purposes that worked fairly well. >> When >> > you say the continous saving to xml doesn't work correctly, could you >> give >> > me a brief description of what's wrong with it? We saved our bout from >> last >> > weekend, and someone was going to look at parsing out some stats. I'd >> like >> > to be able to explain the possible problems to them. >> >> Well, saving to file should work fine. You should be able to write an >> XML parser to pull whatever info you want from that file. >> >> Loading from the file currently can only do a "replay" where the >> entire game is played back; and it isn't really perfect, as it does >> not bypass the scoreboard's normal operation, so specifically the >> clocks can have a tendency to "jitter" because both the "replay" and >> the clock's internal timekeeping is trying to make updates to the >> clock. A true "replay" would need to disable all automatic/internal >> functionality of the scoreboard, such as the clocks running >> themselves. Since the replay is of fairly limited usefulness, and >> disabling all the internal functionality of the scoreboard isn't >> trivial, it will be a while (if ever) before correctly implementing >> it. More useful may be to record the initial scoreboard state and all >> incoming user-generated events (e.g. score change, start/stop clocks, >> etc), which should produce an equivalent replay while using the >> scoreboard's internal functionality. >> >> Anyway, if you're only post-processing the saved xml, it should be >> fine; although note that unless you stopped the save before stopping >> the scoreboard itself, the end of the XML probably is missing its >> closing tags. That shouldn't be a problem assuming you're processing >> the xml with a SAX-style processor (and not a DOM-style processor); >> just ignore the error at the end of the file. >> >> > >> > By the way, I'm in Nashville. If you're coming to the CRG/NRG bout >> this >> > summer let me know, and I'll buy you a beer. Your efforts are >> appreciated. >> >> I probably won't be, I haven't been on the road with CRG in a couple >> years now, since my wife (Shirley Temper) and I had twins (in 2009); >> and she's due with our 3rd in Aug, so I'm guessing she will not be >> letting me go anywhere this summer ;-) >> >> But thanks for the offer! :-) >> >> > >> > If there's something I can do to help test the beta let me know, and >> I'll >> > see what I can do. >> >> It'll definitely need plenty of testing; thanks! >> >> > >> > Jeff >> > >> > On Mon, May 23, 2011 at 10:27 PM, Mr T >> <mrt...@ca... >> > >> > wrote: >> >> >> >> On Fri, May 20, 2011 at 9:24 PM, Jeff Davis <jef...@gm...> >> wrote: >> >> > Our Scrimmages are regularly 45 minutes. I've been told you can >> change >> >> > the >> >> > max period time to be greater than 30, but haven't been able to >> figure >> >> > out >> >> > where. I tried changing the below value in the properties file but >> it >> >> > didn't >> >> > seem to help: >> >> > >> >> > >> #com.carolinarollergirls.scoreboard.defaults.DefaultScoreBoardModel.clock.Period.time.max >> >> >> >> The "#" at the beginning is a "comment" character, so you have to >> >> remove that, as well as setting the value. >> >> >> >> > We're also going to start displaying the jammer names using the >> lineup >> >> > control functionality. That part made sense, but I'm wondering >> what >> >> > benefit >> >> > there is to the other positions. Is there somewhere the current >> lineup >> >> > is >> >> > displayed or saved? Also, is there a way to save just the lineups >> for >> >> > reloading purposes? >> >> >> >> Not currently. I got all the controls implemented, but got >> >> sidetracked to other things and haven't got any way to export the >> data >> >> to any usable form. Pulling stats out of the raw data isn't a >> trivial >> >> task, so I'm putting it off until I can get the 0.2 beta done. >> >> >> >> > We're just starting to use the save xml function. From my testing >> the >> >> > save >> >> > part is easy enough. Is there any way to load the end file without >> >> > sitting >> >> > through the entire clock ticking down? >> >> >> >> If you're talking about the continuous save to xml, don't use it. It >> >> "works" in a very narrow sense, i.e. "recording" and "replaying", but >> >> it wasn't intended and won't work for loading the scoreboard back to >> a >> >> specific point. It will still be in the 0.2 code, at least >> continuous >> >> saving, probably not loading, and probably mostly useful to anyone >> who >> >> wants to post-process the data. >> >> >> >> The non-continuous save to xml works better, but still isn't quite >> >> perfect in the 0.1 code - use it if you must, but I'd recommend >> >> avoiding it if possible. It'll work correctly, and more flexibly, in >> >> the 0.2 code (once finished). >> >> >> >> > Is anyone using these xml files for anything other than loading? >> >> > Parsing >> >> > out stats or anything? >> >> >> >> They were used for adding an overlay onto a DVD after the bout, but >> we >> >> haven't done that in a while. Technically, it could be processed to >> >> pull any kind of stats out even after the bout. >> > >> > >> >> >> ------------------------------------------------------------------------------ >> vRanger cuts backup time in half-while increasing security. >> With the market-leading solution for virtual backup and recovery, >> you get blazing-fast, flexible, and affordable data protection. >> Download your free trial now. >> http://p.sf.net/sfu/quest-d2dcopy1 >> _______________________________________________ >> derbyscoreboard-devel mailing list >> der...@li... >> https://lists.sourceforge.net/lists/listinfo/derbyscoreboard-devel >> > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1_______________________________________________ > derbyscoreboard-devel mailing list > der...@li... > https://lists.sourceforge.net/lists/listinfo/derbyscoreboard-devel > |
