To use 1 configuration file, which I had to create using their tutorial, in which for 1 sampling rate you specify which wave files to use.Example: convolution filter wave file is 44.1 kHz, all the music being played, be it 48 kHz, 96 kHz or DSD64, will be resampled to 44.1 kHz during playback before using that filter wave file. All music sampling rates will be resampled to use the sampling rate of the convolution wave file. One can go to Audio - DSP - Convolution and choose one the options below: Money is tight and it's getting tighter.Īll that said, I will be looking forward to what MC29 has to offer.JRiver Media Center has a very manual way of configuring it to use the convolution wave files ( see here). That said, I, along with many others, would truly appreciate a little more visibility into your roadmap. I believe in the product whole heartedly and want to support it. I have blindly supported the product and paid the upgrades (some early and some later). "is it worth it?" Truth be told, I never know because you guys historically have always been hush about your development cycle. That said, I wanted to provide another voice and/or suggestion on how to approach this topic to help improve new and existing sales while giving the established user base a little something to go on.Īlmost every year that goes by, and your prerelease offer comes out, I always ask myself. I find this entire thread interesting for a variety of reasons. There are ways of being able to communicate upcoming features to the end users without a "build it and they will come" approach. I don't want anything I say here to be construed as negative. I tell anyone who will listen about the application and how awesome it is. I have been an avid user since V16 (now going on 11 years). I can't speak for everyone but I suspect that a fair amount of users would really find any information on upcoming features/functionality very useful especially the lack of information leaves everyone to consider spending hard earned money on something they may not want or need. Those people are unavoidable but I would suggest they are also the 'edge' cases. "well, you said you were going to come out with X but we haven't seen it"? Undoubtedly yes. This is definitely doable and I believe is what many of the users are asking for. This information could be provided so that all the devoted JRiver users have at least a hint of what MIGHT be coming. You guys know what you are working on and what sorts of things you are considering internally. A roadmap can be provided with an explicit statement to the user base that says something about "No guarantees". Difficult is the key word though - not impossible. It's difficult to definitively say what you are going to deliver for the reasons listed. When I have no intention of upgrading it is a real PITA.Īs a developer and 20 year IT professional, I fully understand where you are coming from. It would also be good if the nag screen bidding me for a new version could turned off. The last thing I want to do is to get on board early only to find out I didn't really need the upgrade because there was little in the way of Audio upgrades that were of interest to me, but plenty for other media. The benefit for JRiver is of course in cashflow, plus a much earlier indication of upgrade sales. If you were to list the things that you are definitely working on now, and going to work on later (particularly with respect to Audio) then we can make a much more informed decision as to whether to jump on board with the early bird pricing. So I have a suggestion which would be beneficial for both sides (the Punters, and JRiver). I suspect that virtually everyone uses MC for Audio, many probably only for Audio (me), and a very small few who do not use it for Audio. It's more about knowing what's coming along. That's not the issue Jim - I think all experienced users have complete faith in the JR Team to deliver a fine product.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |