INTERACT FORUM
More => Old Versions => JRiver Media Center 24 for Windows => Topic started by: maid on July 28, 2018, 01:06:37 am
-
Hi, I have a photo taken by my note 8, it is a panoramic shot which displays in acdsee but will not show in jriver.
The size is 8272x3744x24b jpeg
JRiver displays a failed to load.
-
Hi maid,
I have just tried this and a 9434x2682 24bit jpg loaded as per normal in jriver, so it is likely that this is related to something about the particular image file that jriver doesn't like. You could try saving a copy of the jpg file from acdsee to your hard drive and try opening that. When you select the folder in images>album view does jriver show a thumbnail?
-
Saved the photo to my desktop using a different name.
JRiver doesnt open it and I dont see a thumbnail
-
What version of MC is installed?
-
24.0.41
-
It's difficult to see what might be causing the problem without a copy of the jpg to test.
-
The file is 38mb too large to send
-
That is big, how many dots per inch? You might try opening it in some other picture editing software and try to reduce the dots per inch? The one I opened was 72 dots per inch giving an image of about 8 mb.
-
so if i am correct, to display in jriver I have to reduce the quality of the picture?
-
Not too large to upload to google drive or drop box or one drive or.... then allow sharing and post the link....
-
I don't know that Maid, just saying what my panorama was. If we could get a copy we might work out what the problem is. Perhaps JRiver is limited in respect of file size, I just don't know.
-
Did you have motion panarorma selected as the option in this photo, in which case JRiver and a lot of other software options won't deal with it?
-
no just a panoramic taken with note 8
-
Then I would suggest you try to do something like trz916 suggested so that we can get a copy to play with.
-
Link to photo
https://drive.google.com/file/d/1rHBIE3QW0XE1uj_gb5HXLYf_J1jAJ1YV/view?usp=sharing
-
It looks like there is a problem with the header information in the file. MediaInfo says the "Color Space" is YUV, while Windows file properties show the "Color Representation" is set to sRGB. See image below. The file on the left is a random image I had, and shows the "Color Representation" is left blank. So no conflict exists.
This is consistent with colour differences apparent when viewing the file with various other applications.
IrfanView, Microsoft Office 2010, Movie Maker, Paint, and Photos showed the image with the correct colouring. I'm assuming that these programs work out that the file is actually encoded as YUV.
Photo Gallery and Windows Photo Viewer showed the image darker than it should have been. I'm assuming that these programs try to display the image using sRGB encoding, so the colour comes out wrong.
I have one other image application that uses DirectShow filters like MC, Fast Picture Viewer, and it can't display the image either. As Fast Picture Viewer is a professional application that sticks to standards, I am assuming that when it finds the inconsistency between the colour space specified in the file and the actual data in the file, it refuses to open the file. It looks like MC does the same thing, which is actually the correct thing to do.
I would say that MC24, Fast Picture Viewer, Photo Gallery and Windows Photo Viewer all use the file properties to decide what Color Space to decode, but when I opened the file using Photoshop and just saved it to a new name, the inconsistency described above still occurs, but both Fast Picture Viewer and MC24 could open the renamed file. Photoshop must have written the file header correctly, but didn't change the area attributed to Windows file properties. Photo Gallery and Windows Photo Viewer still showed the colour in the renamed file incorrectly, being too dark.
So, no real conclusion.
Do all images from your Note 8 have the same problem?
Are there settings in the Note 8 that could change the Colour Space used, and have you changed any?
When you transferred the file from the Note 8 to your PC, were there any other applications involved?
I guess how did you transfer the file from your Note 8 to your PC?
PS: Nice garden Maid. A cuppa under the palms on a sunny morning would be pleasant.
-
no all other photos are fine just this one
-
Probably just a glitch then. Open it with an editor and save it again with a new name. See if that fixes it for you.
I just edited the post above, but you were too quick for me!
Nice garden. A cuppa under the palms on a sunny morning would be pleasant.
-
thanks re the garden.
I will try your fix tomorrow
-
Just opened the file in paintshop pro and saved it and it opens in JRiver MC now. I wonder why MC is so finnicky in opening a file that other programs can deal with though?
-
Thank you thank you.
Opened in paint, saved over the top, no changes made, and it opens.
Is this an MC tag problem?
-
Is this an MC tag problem?
I don't think so. I think it was an image file header problem. If it was only one file, and it doesn't recur, don't worry about it.
If it starts happening more often, look to problems in the Note 8 or your file transfer process. If you save onto an internal SD card in the Note 8, you may want to pull it out, back it up, format it again, restore your backup to it and see if that fixes the problem.
-
Would not think it is the SD card as all other photos taken are fine, just the Panoramic ones didnt work
-
If all panoramic photos taken by the Note 8 have the problem, I would think it is something to take up with Google/Android.
-
will check
-
It's a Samsung thing. For what it's worth the same thing happens with all panos taken with an S9+ too.
And it's not just MC (or this version of MC; same things happens on v22 also). Some programs can read those files (IrfanView, Photoshop, etc), some will stumble (MC, XnViewMP, etc); your mileage may vary.
So here's what's probably going on: on the panos, which are stitched on the phone, the JPEG segment markers are wrong here and there or are missing (grab exiftool and inspect the headers and good luck with the technical mambo-jambo shown). If this happens too often in the file, a viewer that strictly adheres to the JPEG standard will consider the file unreadable and the music stops. A viewer using relaxed standard constraints will read the file regardless.
In my experience with MC I find it rather unforgiving with damaged or "non-standard" files. If the team wants to relax this behavior might be a topic of debate.
Meanwhile... edit the photos in a program that can read them and save them again. It's a lossy process but can you really tell? Or wait for Jim & team to weight in. Or wait for Samsung to fix it if you're a dreamer :)
-
Fortunetly opening in paint no edits done just saved it and it worked.
LOL like your samsung comment sooooo true