INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: glynor on October 11, 2012, 08:20:57 pm
-
So, I've been MIA for a while. Excuses:
First, I went on vacation, which was awesome and relaxing, but I was far too busy to make many check-ins on Interact.
Then, since I've been back, I've been involved in a seemingly never-ending-string of craziness at work. But the biggest looming project is done (literally as-of 10 seconds ago), and I should have much more time to goof off online now.
In any case, I'm back.
This isn't the big project referred to above, but here's one little thing I've been doing (http://youtu.be/QpebiLV3WVM). It was fun.
-
Very nice "Film".. Something to be proud of for sure....
Ken
-
When I saw this thread title in the recent posts list it showed "kensn" as the last poster. I thought he started the thread.
I was going to ask "did you happen to see Glynor while you were MIA?"
But I'm glad to see it was actually Glynor posting. I miss you Glynor when you're not around.
I assume that was you on the crotch-rocket in the video, doing a Hitchcock-esque cameo?
-
As much fun as it would be to kidnap and hang out with Glynor and have him critique my setup... I do not condone such actions....
Just saying...
Ken
-
I assume that was you on the crotch-rocket in the video, doing a Hitchcock-esque cameo?
I work behind the camera, not in front of it.
-
Welcome back. Things are just not the same without you 8).
-
I work behind the camera, not in front of it.
So you have a "Noggin like a smashed crab / dropped pie or a face for radio?" :)
-
So you have a "Noggin like a smashed crab / dropped pie or a face for radio?" :)
I don't know. You tell me:
(http://glynor.com/img/etc/its_me.png)
;) ;D
-
Great work on the video, and welcome back!
-
Kids these days. They do the craziest stuff...
-
Welcome back...
-
I'm glad your back. I will admit I checked your profile to see if you were at least browsing Interact just to make sure you were okay.
-
I was just looking back through my PM's and realized I haven't seen any posts by gappie for a long time. He only posted once since March (in May) and hasn't even been logged into his profile since May. I wonder why he is MIA.
-
Matt seems to be another MIA candidate...I wonder what he plots atm
-
I was just looking back through my PM's and realized I haven't seen any posts by gappie for a long time. He only posted once since March (in May) and hasn't even been logged into his profile since May. I wonder why he is MIA.
Hmmm... Yeah. Where is that guy?
I need to get in on this MC18 tip. Too much crap to do during weeknights to deal with switching all of my scripts and remote control programming over though. Sigh... Next time, can you guys include a mc.exe in addition to the mc19.exe, which always points to the current launcher? That would save me a pile of time for each major version upgrade.
-
You could create a batch file that calls MC18.exe with arguments passed to it. Use that batch file in your scripts.
Would that work?
-
You could create a batch file that calls MC18.exe with arguments passed to it. Use that batch file in your scripts.
Would that work?
Unfortunately, not cleanly (I've tried). It slows down every execution, which is a big problem when you're programming remote control buttons.
Mainly I don't even point at MC17.exe, because even it is too slow. Instead, I use Windows Messages to program my remote (which call Media Center 17.exe, not Media Center.exe), so I have to go through all my GMLs and find/replace all of the instances of MC17.exe with MC18.exe and Media Center 17.exe with Media Center 18.exe. This seems like not a big deal, but every time I try it, I go through two or three "iterations" of the process before I catch all of the edge cases. And, making things worse, I have two separate GMLs (one for the HTPC and one for my other machines) since they work slightly differently.
And all of them target the MC window, not the "foreground application", so I have to fix all of that.
Then, I have a variety of different scripts that run in an automated fashion that I have to sort out. Most of these could use the batch file trick, of course, but then I have one method for some, and another for others, and I have to remember which is which...
I get why they do it the way they do, but it would be nice if we had a simple way to "set this version as the default copy of MC" during the install, and then it would create a "Media Center.exe" and "MC.exe" in the appropriate places, which would be kept up to date and whatnot until MC19 comes out. Then, we could install beta builds (and not check that box), run until we were ready to put it in production, and then just run the installer and flip the switch.
Sigh... Just complaining here. It is probably just me and a handful of other nerds it impacts. But it dramatically slows my adoption of the new version with every new major release.
-
Alright, alright, Jim....
Finally.
(http://glynor.com/img/screenshots/MC18-Finally-small.png)
-
Alright, alright, Jim....
Finally.
Ta da!
(http://www.pix01.com/gallery/8D12431D-7EA0-495D-9EA2-775091458CB9/Prairie_Chicken/881503567_orig0.jpg)
Spectacular catch of a routine fly ball.
-
Spectacular catch of a routine fly ball.
I'd call it foul.
-
Just wondering, I had this problem with remote commands as well. Could we use custom fields in the commands, so in future we would only have to change one field?
-
Did you try just doing a binary find & replace of the string "Media Center 17" to "Media Center 18" in your configuration files? It might be that simple.
-
Did you try just doing a binary find & replace of the string "Media Center 17" to "Media Center 18" in your configuration files? It might be that simple.
That's basically what I do (GMLs are just XML plain text inside), but it is fiddly and I have to do three or four "passes" to catch:
MC17 > MC18 - for the few places I use the launcher app
Media Center 17.exe > Media Center 18.exe - for the Windows Messages executable calls
Media Center 17\ > Media Center 18\ - for the few places where it references the directory itself
I tried once just doing a global Media Center 17 > Media Center 18 global replace, and it hosed the files badly because there are a few places where it references the name as part of the GML Structure. That actually might not be a problem anymore, as it was way back in MC13 > MC14 days that I'm remembering, but it was bad and I had to start over. The GML text is plain text, but it isn't exactly easy to read. It is one big, giant string all on one line, with limited spaces, and it is touchy if you add a space in the wrong spot.
Like I said... Possible, and not the end of the world, but between doing that twice, and then fixing the six or seven VBS scripts I have that reference MC in some way, it took about an hour and a half last night, and made my brain hurt. Cutting that down would be sweet, and would mean I wouldn't need to change the GML or scripts at all with a major version upgrade (unless the MCC commands themselves changed).
-
Did you try just doing a binary find & replace of the string "Media Center 17" to "Media Center 18" in your configuration files? It might be that simple.
Hey!
I just noticed!
You're the dog again! My wife will be pleased. She was very disappointed before (seriously). She said that she complains, but she likes the "pretty dog".
-
Time to start a new thread with an appropriate topic.
Clank.