Topic: So How's MC 17 Now? (Read 8366 times)

glynor · « **on:** October 14, 2011, 04:59:10 pm »

I'm going to update this weekend. But that's always a big risk... I'll keep MC16 installed, of course, but it doesn't take long before rolling back to an earlier, saved version of my library isn't really going to be an option.

SOOOOO.......

How's she lookin?

jmone · « **Reply #1 on:** October 14, 2011, 05:13:42 pm »

Looks good to me - I've been running MC17 for a week with few issues. You will have to resetup your TheaterViews again and once more before it goes public.

raym · « **Reply #2 on:** October 14, 2011, 05:38:23 pm »

The most stable new MC release to date! Been using it since the initial builds without issue. All ok here.

But yes, be warned, you will need to re-gen your Theater View views.

rjm · « **Reply #3 on:** October 14, 2011, 05:54:54 pm »

I saw something about using png instead of jpg for video thumbnails. Is it recommended or required to rebuild thumbnails?

Osho · « **Reply #4 on:** October 15, 2011, 05:44:03 pm »

I am moving to MC17 this weekend - all 3 PCs in the house. Updating my main server PC first then the HTPC and then the office laptop. Hoping all goes well

.

Osho

marko · « **Reply #5 on:** October 15, 2011, 06:32:54 pm »

I cannot consider upgrading until the image crashing issues are addressed.

KingSparta · « **Reply #6 on:** October 15, 2011, 09:37:07 pm »

I have had no problems.

Mr ChriZ · « **Reply #7 on:** October 16, 2011, 10:19:57 am »

I'm running both at present, no problems to report.
Will probably flip to full MC 17 when I've got more time

Osho · « **Reply #8 on:** October 17, 2011, 12:07:36 am »

Upgraded all my 3 PCs (Main Server, HTPC and office laptop) to MC17. They all upgraded well without any issues. Pretty smooth upgrade - very nice

.

A few things I had to do (not unexpected):

Reconfigure TheaterView views
Install latest Gizmo on all android devices that works with MC17.

So far so good. Now, onto playing with the new features in MC17

.

Osho

jmone · « **Reply #9 on:** October 17, 2011, 04:43:34 am »

I've actually had to remove MC16 as I keep getting conflicts in Windows as stuff is still associate with it - so I'd sometimes get MC16 running

fitbrit · « **Reply #10 on:** October 17, 2011, 11:57:38 am »

I've had MC17 crashing when navigating to a folder which had hundreds/thousands of folders and files in the Explorer tree. The same location opened just fine in MC16. I wanted to import some of the files into MC17, but still had shell integration for MC16 on. I thought that by navigating via MC's built-in Explorer I'd be abelt o import the files I wanted. I never got that far.
I'll try to reproduce it later in the week and include a log. No issues other than that really.

glynor · « **Reply #11 on:** October 17, 2011, 02:12:03 pm »

I decided to hold off until next weekend.

Mostly because I didn't have the time, but the image import issues worried me as well.

Magic_Randy · « **Reply #12 on:** October 20, 2011, 05:41:11 pm »

It's been stable for me.

I have not yet un-installed MC16 but have switched over to using MC17 exclusively.

I'll give it another week or so then uninstall MC16.

rjm · « **Reply #13 on:** October 21, 2011, 04:28:23 pm »

Update was smooth. Only 2 issues:

1) I had to manually copy skins from MC16 to MC17 program files.

2) I override the thumbnail cache location in the registry to facilitate sharing the cache between different user accounts and computers. MC17 correctly preserved my cache location but because MC16 and MC17 were using the same cache they got confused and starting rebuilding thumbnails. After I stopped running MC16 and restored a backup of my thumbnails all was ok.

I have uninstalled MC16 and am now committed to MC17.

fitbrit · « **Reply #14 on:** October 21, 2011, 04:51:49 pm »

I'm probably going to uninstall ~~MC17~~ MC16 tonight. I've already imported and tagged hundreds more files in my MC17 library compared to the MC16 one.

[EDIT] Changed the syntax to make it clearer what I meant.

rjm · « **Reply #15 on:** October 21, 2011, 05:23:37 pm »

Quote from: fitbrit on October 21, 2011, 04:51:49 pm

I'm probably going to uninstall MC17 tonight. My MC17 library already had hundreds more files and tags than the MC16 one.

I had exactly the same 267,754 files before and after installing MC17. I ran auto import several times and it came back with zero changes suggesting all is working ok.

I am getting a consistent crash when I turn on mp4 subtitles but I don't know if this is a new problem and I can no longer test MC16.

Magic_Randy · « **Reply #16 on:** October 21, 2011, 07:40:26 pm »

OK, MC16 has been uninstalled.

Too much tagging in MC17 to go back. And MC17 is working fine, so onwards and upwards

rjm · « **Reply #17 on:** October 22, 2011, 01:00:26 am »

I spent the last 6 hours pushing MC17 really really hard doing the things it sometimes does not like doing like rebuilding video thumbnails while simultaneously doing heavy filtering and editing. I have not seen a single hiccup. It's really stable.

marko · « **Reply #18 on:** October 22, 2011, 02:11:04 am »

Just for clarity now that this has moved, the image import issues I was experiencing appear to have been fixed. I'm moving to 17 full time from this weekend.

I understand why they don't, but I don't care!! I just wish the upgrade engine would bring in my plugins too... time to fire up regedt32 and start the export-edit-import shuffle! I did PVDImport last night... playingnow and soundspectrum today, redo theatre view, and I'll be all set.

[dig]it's high time playingnow was included as part of the default installation, don't you think?[/dig]

I don't mind doing the skins for it...

-marko

MarkCoutinho · « **Reply #19 on:** October 22, 2011, 04:44:18 am »

Quote from: marko on October 22, 2011, 02:11:04 am

[dig]it's high time playingnow was included as part of the default installation, don't you think?[/dig] I don't mind doing the skins for it...

-marko

I second that!

Magic_Randy · « **Reply #20 on:** October 22, 2011, 11:52:28 am »

I'd also like to comment that the migration works really well.

My options and views went over very nicely. I did redo everything in Theater view.

Thanks to the JRiver team.

ElQuia · « **Reply #21 on:** October 23, 2011, 12:48:06 pm »

I dont know if upgrading is worth it for me. I am mainly on audio only (pc output connected to HiFi rack), some downloaded HD movies. I dont use TV and don´t use it for images (xnview is better for that) ...
So, if some audio feature justifies maybe. ... I bought 16 upgrade in april, and having to pay AGAIN ... ?

fitbrit · « **Reply #22 on:** October 23, 2011, 04:21:54 pm »

Got rid of MC16 on the media room HTPC last night.

phusis · « **Reply #23 on:** October 25, 2011, 06:15:17 pm »

Excuse me for asking, but why does so many here uninstall MC16 when "converting" to MC17? Couldn't one leave MC16 installed on ones HTPC as is, and just install/upgrade to MC17 and go with that?

At least that's what I've done when I upgraded to MC17 a few days ago.. But please let me know if it's of vital importance, for whatever reason, to uninstall MC16 when going over to MC17.

Thanks for the continuing great work with J River MC!

Best,
M

EDIT: In fact I haven't uninstalled MC15 either...

JimH · « **Reply #24 on:** October 25, 2011, 06:38:33 pm »

Didn't the Greeks burn their ships so they couldn't retreat?

From the Iliad:

Quote

Zeus wakes and reinvigorates the Trojan line. Apollo helps Hector back into battle and the Trojans again push to the Greek Ships. Ajax defends these valiantly and Nestor continues to spur on the Troops. Hector calls for torches to burn the boats as Patroclus observes the panic in his compatriots.

steveklein · « **Reply #25 on:** October 25, 2011, 06:49:03 pm »

can anyone confirm if G-Force 4.01 works with the early builds of MC17?

rick.ca · « **Reply #26 on:** October 25, 2011, 07:12:01 pm »

Quote

can anyone confirm if G-Force 4.01 works with the early builds of MC17?

For some time now (4.0?), G-Force has registered itself for MC versions 11 to 18. If 4.01 doesn't, it should work if the necessary registry key is copied from MC16 to MC17.

eapool · « **Reply #27 on:** October 25, 2011, 07:52:05 pm »

This is a very minor issue and I really don't know how many people it affects, but I thought I would mention it. I have a scheduled task to issue a command stop at 1:00 AM (wife likes to fall asleep with the TV on, so I used the TV's timer to shut it off and a scheduled task to stop whatever she is watching). Anyway, I used the MC16.exe /CommandStop to do this. However, after the upgrade, the Scheduled task was still using MC16.exe to instead of MC17.exe. I technically don't consider this a bug because it did exactly what I programmed it to do (use MC16.exe), but it is something I noticed that I thought people may want to look out for.

Alex

Magic_Randy · « **Reply #28 on:** October 25, 2011, 08:42:59 pm »

Quote from: steveklein on October 25, 2011, 06:49:03 pm

can anyone confirm if G-Force 4.01 works with the early builds of MC17?

I no longer have 4.01, but I can confirm MC17 works with G-Force 4.3 without having to mess with the registry keys.

phusis · « **Reply #29 on:** October 26, 2011, 03:08:57 pm »

Quote from: JimH on October 25, 2011, 06:38:33 pm

Didn't the Greeks burn their ships so they couldn't retreat?

From the Iliad:

I'll pass bravery and invigoration on the battle field and go by reasoning in my livingroom. So, war analogies aside, what's the reason for the suggestions to uninstall earlier MC-editions?

Best,
M

JimH · « **Reply #30 on:** October 26, 2011, 03:15:55 pm »

Quote from: phusis on October 26, 2011, 03:08:57 pm

I'll pass bravery and invigoration on the battle field and go by reasoning in my livingroom. So, war analogies aside, what's the reason for the suggestions to uninstall earlier MC-editions?

I think it's just less confusing.

phusis · « **Reply #31 on:** October 26, 2011, 03:22:31 pm »

Quote from: JimH on October 26, 2011, 03:15:55 pm

I think it's just less confusing.

Kind of psychologically, or even emotionally getting invested in the next step by "breaking up" with the former? Ah well, ok..

rjm · « **Reply #32 on:** October 27, 2011, 10:47:59 am »

Quote from: phusis on October 25, 2011, 06:15:17 pm

Excuse me for asking, but why does so many here uninstall MC16 when "converting" to MC17? Couldn't one leave MC16 installed on ones HTPC as is, and just install/upgrade to MC17 and go with that?

When you install MC17 it makes a copy of the MC16 library. Thereafter (most) changes made in MC16 will not be seen by MC17. If you are super disciplined and only make changes in MC17 there is no problem leaving MC16 installed. However MC16 and MC17 look almost identical so it would be quite easy to make a mistake.

I've also heard others report that shell integration can get confused when both are installed but I have not verified this.

phusis · « **Reply #33 on:** October 27, 2011, 05:20:03 pm »

Quote from: rjm on October 27, 2011, 10:47:59 am

When you install MC17 it makes a copy of the MC16 library. Thereafter (most) changes made in MC16 will not be seen by MC17. If you are super disciplined and only make changes in MC17 there is no problem leaving MC16 installed. However MC16 and MC17 look almost identical so it would be quite easy to make a mistake.

I've also heard others report that shell integration can get confused when both are installed but I have not verified this.

rjm -

Thanks for your reply and explanation. To begin with, I believe uninstalling MC15 on my HTPC should be the save move to do, but I'm a little uncertain about letting go of MC16 just now, also being that I'm encountering playback failure with a few Blu-ray titles via MC17(http://yabb.jriver.com/interact/index.php?topic=67277.0), and would therefore like MC16 as a back-up. Unless of course the issue is dealt with in the near future...

globetrotters1 · « **Reply #34 on:** October 30, 2011, 03:36:42 am »

I bought the upgrade, installed it and found out that the whole connecting business from client to server had been changed and I needed some time to figure out how to make it work. But finally it did its job.

The main problem is the re-definition of the Theater View schemes. Invested a lot of time and efforts to make those in MC16 the way they are useful for our huge library and have to do them again... annoying... and now I read here that I have to do them again when MC17 goes public? No thanks, then I prefer to work on with MC16 until MC17 goes public...

And the same bugs exist in MC17, so no need to do the switch now

thanks

)p( · « **Reply #35 on:** October 30, 2011, 04:26:24 am »

What I do is make my theater view schemes in standard mode. You can then always add them to theater view when necessary.

JimH · « **Reply #36 on:** October 30, 2011, 07:33:21 am »

Quote from: globetrotters1 on October 30, 2011, 03:36:42 am

The main problem is the re-definition of the Theater View schemes. Invested a lot of time and efforts to make those in MC16 the way they are useful for our huge library and have to do them again... annoying... and now I read here that I have to do them again when MC17 goes public?

No, that won't happen again. I'm sorry for the extra work, but it's finished now.

JimH · « **Reply #37 on:** January 31, 2012, 05:24:09 pm »

koldby,
I moved your post where you can probably get some help:

http://yabb.jriver.com/interact/index.php?topic=68828.msg469403#msg469403

INTERACT FORUM

Author Topic: So How's MC 17 Now? (Read 8366 times)