Music currently is not video-related. You should pay to have it removed.
Except that you need to be able to decode mp3/flac/ogg whatnot anyway if you like audio in your videos…
I'm not super happy with the music segment since it introduces a hole lot of other things you want to put into it then. Like a feature request I have seen; gapless-audio. Witch is feature which should be in if there is music playback. Except its not that easy. ffmpeg decode all audio happily but its not a player. It doesn't bother with stuff like that. So to be able to get gapless-audio you need to build it in to an actual player and have it work flawless in the web client as well as the rest. kodi probably have had this feature for years, much like the ability to view comics/pdf but it doesn't matter when the phones/tv/web as well as core server don't.
What you seem to not now is that it's only the plex desktop client which is based on xbmc kodi. All the other clients are not. So you need to implement a full pdf reader and comic book reader in all of them. Not to say anything about all the backend stuff that needs to go into the server itself.
Actually you're both wrong. Comic support came to xbmc after Plex had separated from it. It wasn't removed.
After that moment, due to changes in philosophy and ideology, work from xbmc is not often leveraged although parallel evolution may happen.
Mentioning it's Jon xbmc helps drive the point that it makes sense for it to be integrated (to me it makes even more sense since clients especialized in some media can use PMS while with xbmc it's always the whole enchilada).
But where both of you are wrong is in how irrelevant it is and it should be to the Plex team what xbmc does. Interests and priorities are different for both.
As far as far as I understand these voting forums are for proposing new functionality or changes. In proposed changes it makes sense to vote against but in proposed functionality it doesn't. You don't get (nor should you) to tell the Plex team what they shouldn't do unless it changes something current.
Please stop trying to piss into other people's pots. Go an open a thread where you ask for functionality you don't want to be removed/not added and try to get votes for it.
Well, it looks like we need it now more than ever. I updated to iOS 8 last night, and it killed ComicBookLover on my iPad. I sent an email to the developer, but it looks like there hasn't been much activity. For awhile. I'm trying YAC Reader, but it has some limitations, and organizing a huge library is very frustrating. If anybody has any tips, it would be greatly appreciated!
One-line, unexplained responses tend to go this way, though. Comicrack had been discussed already in the thread, if I recall correctly.
You can run parallels?
The post you're replying to literally says he doesn't want to go the VM route.
Well, it looks like we need it now more than ever. I updated to iOS 8 last night, and it killed ComicBookLover on my iPad. I sent an email to the developer, but it looks like there hasn't been much activity. For awhile. I'm trying YAC Reader, but it has some limitations, and organizing a huge library is very frustrating. If anybody has any tips, it would be greatly appreciated!
If you're willing to pay for it, Chunky has amazing support and feature-set. I'd use that if I could but I'm still with an iPad 1.
For my iPad 1 I've settled for SideBooks, which has support for dropbox and direct transfer. In recent versions they seem to have added support for a network-based library (and even come with sample magazines loaded from a guest one) but the service still doesn't look to be released and isn't clear if it'll be a central service or it can be run individually. The server itself is pretty nice (far from what it could be with Plex, though).
SideBooks runs on an iPad 1 and can load 500MB CBR comics with ease, which is quite a feat.
Thanks for the suggestions guys. Yeah, I really don't want to to the VM or Parallels route if I don't have to.
I tried out Chunky and iComix with the Dropbox integration last night, and both worked great. And for the meantime, will work. The issue is, that I have a huge library, I was (am) using ComicBookLover to keep everything organized. But unfortunately, the iPad app stopped working with the latest iOS.
One-line, unexplained responses tend to go this way, though. Comicrack had been discussed already in the thread, if I recall correctly.
The post you're replying to literally says he doesn't want to go the VM route.
If you're willing to pay for it, Chunky has amazing support and feature-set. I'd use that if I could but I'm still with an iPad 1.
For my iPad 1 I've settled for SideBooks, which has support for dropbox and direct transfer. In recent versions they seem to have added support for a network-based library (and even come with sample magazines loaded from a guest one) but the service still doesn't look to be released and isn't clear if it'll be a central service or it can be run individually. The server itself is pretty nice (far from what it could be with Plex, though).
SideBooks runs on an iPad 1 and can load 500MB CBR comics with ease, which is quite a feat.
Chunky seems like it would be perfect for me if it had an desktop app to keep everything organized with metadata and all that.
I simply want to be able to sync PDF magazines to read on the plane. I was thinking something closer to the Home Photos section than anything else. No meta data downloads, organize in folders as you see fit. Right now plex converts videos to work on my iOS device when they sync, could they not easily convert the PDFs to images when synced and handle it the same as the Pictures are handled? I see plenty of PDF to Image converters so I can't imagine that isn't something they couldn't figure out in short order.
I now invite critics to tell me how my idea won't work or how Plex "isn't for that"
I now invite critics to tell me how my idea won't work or how Plex "isn't for that"
Is it really necessary to invite flaming?
The ones considering this "isn't for Plex" are the Plex devs, so far. The reasons behind this are specific to Plex and probably throw our assumptions of "being easy" out the window. It's them you're antagonizing, when you add this challenge at the end. Right after you've made it clear your wishes have no technical expertise or knowledge behind them (I'm not saying they're worse for it, but that the reasons behind this decision are technical and probably more complex than what we come up with when we ask for it).
This is a forum for proposing and voting "for" features. Any post "against" features should be ignored, since those are for the Plex team to decide. I invite you to be constructive (which your post was, for the most part) and let them decide on their side based on proposals and explanations rather than assumptions and oversimplifications.
This is a forum for proposing and voting "for" features. Any post "against" features should be ignored, since those are for the Plex team to decide. I invite you to be constructive (which your post was, for the most part) and let them decide on their side based on proposals and explanations rather than assumptions and oversimplifications.
I strongly disagree with this statement. Posts about why a feature should not be incorporated into Plex are quite valid to this forum as there is no "Don't like" button therefore posting "I don't want this" is the only way to tell Plex that other feature requests are more important to that feature.
For me full audiobook support support is very important but things like comic books and other reading material is of much less importance. For me Plex is about streaming not about reading.
When I did development I discovered that one user would often want more than most others but within that "want" was a function that many wanted so I encouraged the users to discuss what they wanted in detail so I could glean what the real "wants" were.
I am pretty sure that the Plex developers want as much feedback about feature requests as practical so they can make decisions about where to place their efforts and posts that say "I don't want this" or "I want this part of the request" are as valuable to the decision process as the request itself.
It is Plex's decision as to what to implement but I believe both positive and negative feedback are needed for Plex to make the best decisions they can.
I strongly disagree with this statement. Posts about why a feature should not be incorporated into Plex are quite valid to this forum as there is no "Don't like" button therefore posting "I don't want this" is the only way to tell Plex that other feature requests are more important to that feature.
I'm sorry, but I can't see this having any validity. There's a reason there's not a "Don't like" button. Lack of interest is measured by lack of votes, precisely.
"Positive or negative" feedback come into play in existing or new functionality.
There're multiple reasons why "Don't like" comments should be avoided for the most part. Mainly because then the whole exercise becomes a shouting match, where those who insist the most, or articulate better, have more weight.
Take your example: You don't want this functionality so you vote "against it". But that's pure noise, since working on this shouldn't have a direct effect on the parts of Plex you actually care about. You're shooting down a request for something that wouldn't affect you directly.
I imagine your excuse is that you're killing other people's wishes because you want the Plex team to focus on what's important for you, but then that would be an arrogant statement, the would presume the Plex team can't manage their own teams and time. It would come from the flawed line of thought that development teams can work in only one thing and no more.
I don't use any picture or music functionality in Plex. Should I raise a feature request to have them removed? According to this logic, that would be valid (and egotistical and insensitive on my part)
I can see a point in commenting how a feature request that *changes* existing functionality can be discussed (which isn't the same as "shot down") but I see absolutely no point in people outside the development team trying to get other people's requests off the list.
You can measure interest by having people "like" (or vote) a feature request but presuming to know better than the dev team about their time management and organization is out of place.
By all means, post your disagreement in feature requests. But I see it as unnecessary noise (including the replies, like this one from me, it generates).
I'm sorry, but I can't see this having any validity. There's a reason there's not a "Don't like" button. Lack of interest is measured by lack of votes, precisely.
...
There is a reason for up and down votes but that clearly escapes you.
By your reasoning our voting system should not have choice of referendum item but rather just a "Yes" selection and then let someone decide if there are enough "yes" votes for the measure to pass.
Just counting "yes" votes is missing the very reason for voting at all.
But you are right posts that do not discuss the features are just "noise" so I will stop arguing as there will be no "winner." A quote from LaBoeuf in the original "True Grit" comes to mind here.
There is a reason for up and down votes but that clearly escapes you.
On the contrary. I'm too well aware of when they have a point and when they're just noise. You're not interested in knowing the difference, by your fallacious (yet facile) simile so I'll leave the explanation here for the benefit of others.
The "feature requests" forum exists to gauge interest. It's not a vote to get things in or out. More votes mean more interest but they don't mean a feature will be included. Wildly voted feature requests may never find their way into Plex, since that's not what the votes are for.
Fallaciously comparing this system to referenda misses that in those systems the outcome must follow the voting. The fallacious intention being to use the word "vote" and pretend it's used in only one way, always. Even when patently false.
The feature request forum is like this because it (rightly) doesn't assume to cover a representative cross-section of Plex. Only a fraction of users ever enter the forum and of those an even smaller one gives any opinion.
The feature request part of the forum is a simple wishlist, one designed so the devs don't get spammed by eager users, and one designed in a way that repeated requests can be grouped in a single thread.
Since the interest in features is gauged both by the "likes" and the activity in a thread, having people disagreeing with the feature actually adds up to it's apparent interest, so by all means go ahead and keep "voting against" features.
