vTuner Internet Radio stop working - Marantz, Denon - 3$ case

I now have a simplified Raspberry pi based DHCP server for YCast (Vtuner alternative). I will put up the instructions in a few days after I verify the step by step programming.
 
Posting a (hopefully) a simpler version of Raspberry pi DNS server for Ycast. This version does not require tinkering with the Modem/Router but requires changing DHCP setting on the receiver. It has been working fine on my Marantz 6010 and 5007 receivers. Hopefully it will work as is with other models and manufacturers too. Please post positive or negative experience with it for the benefit of others.
 

Attachments

  • YCast on Raspberry pi.pdf
    120.1 KB · Views: 1,754
Posting a (hopefully) a simpler version of Raspberry pi DNS server for Ycast. This version does not require tinkering with the Modem/Router but requires changing DHCP setting on the receiver. It has been working fine on my Marantz 6010 and 5007 receivers. Hopefully it will work as is with other models and manufacturers too. Please post positive or negative experience with it for the benefit of others.
Thanks lilimap for your efforts. I will try this out soon.

I have a Marantz MCR603 and the same problem as everyone else on here. Has anyone tried this Raspberry Pi solution with the MCR603 or similar? Is it likely to work.
 
sorry if this was mentioned before but for ppl with fritzbox router (and maybe others) you can add stream url under home network/media server/web radio and then use media server section on avr instead of internet radio. Not nearly good as real deal but works fine and not a bad solution if you don't cycle through 5838 stations.
 
Thanks lilimap for your efforts. I will try this out soon.

I have a Marantz MCR603 and the same problem as everyone else on here. Has anyone tried this Raspberry Pi solution with the MCR603 or similar? Is it likely to work.
Sorry, I missed this message in November. I have an M-CR610, which was an updated version of the 603, and YCast on a Raspberry Pi works fine. I'm fairly certain it'll work for you too.
 
Is there a way to add stations to my Denon DNP-800 that are not in its memory?
Is this the DNP-800NE or was there any earlier version? The 800NE appears to use TuneIn for internet radio. There is generally no way to add stations on Denon/Marantz systems other than to use whichever internet radio service the particular model supports. You should be OK with TuneIn, though, as it's still supported. If you do have an older model that uses vTuner, you will need to set up YCast as described in this thread.
 
The model is Denon DNP-800. Supports Tunein via HEOS application. There are radio stations that I already have and I would like to add those that are not.
 
The model is Denon DNP-800. Supports Tunein via HEOS application. There are radio stations that I already have and I would like to add those that are not.
You have to add stations via the TuneIn app or website. It'll then appear on the Denon. See:
 
Posting a (hopefully) a simpler version of Raspberry pi DNS server for Ycast. This version does not require tinkering with the Modem/Router but requires changing DHCP setting on the receiver. It has been working fine on my Marantz 6010 and 5007 receivers. Hopefully it will work as is with other models and manufacturers too. Please post positive or negative experience with it for the benefit of others.
Hi,
Would this solution work also for reciva based tuners while reciva service has been shut down?
I have Rotel RT12 tuner.
If yes, what should be changed when following your tutorial?

Thank you in advance for your help.
 
I am afraid not since the article you mentioned tells about time before reciva service has been closed and my question is what could be done now when it is already closed.
 
Thanks - I have read I think all the comments but my question is if Raspberry pi solution can work for reciva based tuners now when reciva service is not available any more.
 
@wuffles
From the Blog you mentioned I have tried solution from this tutorial:
GitHub - jisotalo/reciva-radio-patching: Notes how to patch the Reciva radios (Tangent Quattro etc.) to work without Reciva
but with no luck so far so maybe you (or somebody else can help) if Raspberry pi solution is not possible.

My Rotel RT-12 tuner has Reciva Firmware service pack 265-a-254-a-301-a-007.
I have tried Reciva Patcher via Windows 10 according to mentioned tutorial and everything went well until point 13.

When I have started Firmware Upgrade I did not get on display "Patching sharfing base, Patching Telnet server, etc...".
I got on my display "Writing firmware do not turn off" and after a minute or so it is rebooting than diplaying "Finding Gateway" and than "Network error Port 80 connect failed. Unable to load station list".

Any chance you could advice what I am doing wrong and do you think I can succeed with Reciva Patcher on Rotel RT-12 or I should try any other solution?

Below please find lines I got on Reciva Patcher during the try:

gui: trying to determine IP.
dns: server is running...
gui: servers started...
gui: patch settings changed.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for 1.100.168.192.in-addr.arpa
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for 1.100.168.192.in-addr.arpa
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal4.7803986842.com
dns: query for portal5.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal4.7803986842.com
dns: query for portal5.7803986842.com
dns: query for portal6.7803986842.com
dns: query for portal7.7803986842.com
dns: query for portal6.7803986842.com
dns: query for portal7.7803986842.com
dns: query for portal8.7803986842.com
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for portal8.7803986842.com
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for portal9.7803986842.com
dns: query for portal9.7803986842.com
dns: query for portal2.7803986842.com
dns: query for portal10.7803986842.com
dns: query for portal2.7803986842.com
dns: query for portal10.7803986842.com
dns: query for portal1.7803986842.com
dns: redirected to local http server.
dns: query for portal1.7803986842.com
dns: redirected to local http server.
http: got request.
dns: query for portal11.7803986842.com
http: failed to handle request
dns: query for portal11.7803986842.com
dns: query for portal12.7803986842.com
dns: query for portal12.7803986842.com
dns: query for portal13.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal13.7803986842.com
dns: query for portal14.7803986842.com
dns: query for portal14.7803986842.com
dns: query for portal15.7803986842.com
dns: query for portal15.7803986842.com
dns: query for portal3.7803986842.com
dns: query for portal16.7803986842.com
dns: query for portal3.7803986842.com
dns: query for portal16.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for www.reciva.com
dns: redirected to local http server.
dns: query for www.reciva.com
dns: redirected to local http server.
http: got request.
server: patch info requested.
dns: query for www.reciva.com
dns: redirected to local http server.
dns: query for www.reciva.com
dns: redirected to local http server.
dns: query for www.reciva.com
dns: redirected to local http server.
http: got request.
server: patch info requested.
http: got request.
server: transferring patch file ...
dns: query for portal3.7803986842.com
dns: query for portal4.7803986842.com
dns: query for portal5.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal3.7803986842.com
dns: query for portal4.7803986842.com
dns: query for portal5.7803986842.com
dns: query for portal6.7803986842.com
dns: query for portal6.7803986842.com
dns: query for portal7.7803986842.com
dns: query for portal8.7803986842.com
dns: query for portal7.7803986842.com
dns: query for portal8.7803986842.com
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal9.7803986842.com
dns: query for portal9.7803986842.com
dns: query for portal2.7803986842.com
dns: query for portal2.7803986842.com
dns: query for portal10.7803986842.com
dns: query for portal10.7803986842.com
dns: query for portal1.7803986842.com
dns: redirected to local http server.
dns: query for portal1.7803986842.com
dns: redirected to local http server.
http: got request.
http: failed to handle request
dns: query for portal11.7803986842.com
dns: query for portal12.7803986842.com
dns: query for portal12.7803986842.com
dns: query for portal13.7803986842.com
dns: query for portal13.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal14.7803986842.com
dns: query for portal14.7803986842.com
dns: query for portal15.7803986842.com
dns: query for portal15.7803986842.com
dns: query for portal16.7803986842.com
dns: query for portal16.7803986842.com
dns: query for portal11.7803986842.com
dns: query for portal11.7803986842.com

Thank you in advance and best regards.
 
@wuffles
From the Blog you mentioned I have tried solution from this tutorial:
GitHub - jisotalo/reciva-radio-patching: Notes how to patch the Reciva radios (Tangent Quattro etc.) to work without Reciva
but with no luck so far so maybe you (or somebody else can help) if Raspberry pi solution is not possible.

My Rotel RT-12 tuner has Reciva Firmware service pack 265-a-254-a-301-a-007.
I have tried Reciva Patcher via Windows 10 according to mentioned tutorial and everything went well until point 13.

When I have started Firmware Upgrade I did not get on display "Patching sharfing base, Patching Telnet server, etc...".
I got on my display "Writing firmware do not turn off" and after a minute or so it is rebooting than diplaying "Finding Gateway" and than "Network error Port 80 connect failed. Unable to load station list".

Any chance you could advice what I am doing wrong and do you think I can succeed with Reciva Patcher on Rotel RT-12 or I should try any other solution?

Below please find lines I got on Reciva Patcher during the try:

gui: trying to determine IP.
dns: server is running...
gui: servers started...
gui: patch settings changed.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for 1.100.168.192.in-addr.arpa
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for 1.100.168.192.in-addr.arpa
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal4.7803986842.com
dns: query for portal5.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal4.7803986842.com
dns: query for portal5.7803986842.com
dns: query for portal6.7803986842.com
dns: query for portal7.7803986842.com
dns: query for portal6.7803986842.com
dns: query for portal7.7803986842.com
dns: query for portal8.7803986842.com
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for portal8.7803986842.com
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for portal9.7803986842.com
dns: query for portal9.7803986842.com
dns: query for portal2.7803986842.com
dns: query for portal10.7803986842.com
dns: query for portal2.7803986842.com
dns: query for portal10.7803986842.com
dns: query for portal1.7803986842.com
dns: redirected to local http server.
dns: query for portal1.7803986842.com
dns: redirected to local http server.
http: got request.
dns: query for portal11.7803986842.com
http: failed to handle request
dns: query for portal11.7803986842.com
dns: query for portal12.7803986842.com
dns: query for portal12.7803986842.com
dns: query for portal13.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal13.7803986842.com
dns: query for portal14.7803986842.com
dns: query for portal14.7803986842.com
dns: query for portal15.7803986842.com
dns: query for portal15.7803986842.com
dns: query for portal3.7803986842.com
dns: query for portal16.7803986842.com
dns: query for portal3.7803986842.com
dns: query for portal16.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for www.reciva.com
dns: redirected to local http server.
dns: query for www.reciva.com
dns: redirected to local http server.
http: got request.
server: patch info requested.
dns: query for www.reciva.com
dns: redirected to local http server.
dns: query for www.reciva.com
dns: redirected to local http server.
dns: query for www.reciva.com
dns: redirected to local http server.
http: got request.
server: patch info requested.
http: got request.
server: transferring patch file ...
dns: query for portal3.7803986842.com
dns: query for portal4.7803986842.com
dns: query for portal5.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal3.7803986842.com
dns: query for portal4.7803986842.com
dns: query for portal5.7803986842.com
dns: query for portal6.7803986842.com
dns: query for portal6.7803986842.com
dns: query for portal7.7803986842.com
dns: query for portal8.7803986842.com
dns: query for portal7.7803986842.com
dns: query for portal8.7803986842.com
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for ntp.reciva.com
dns: redirected to local http server.
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal9.7803986842.com
dns: query for portal9.7803986842.com
dns: query for portal2.7803986842.com
dns: query for portal2.7803986842.com
dns: query for portal10.7803986842.com
dns: query for portal10.7803986842.com
dns: query for portal1.7803986842.com
dns: redirected to local http server.
dns: query for portal1.7803986842.com
dns: redirected to local http server.
http: got request.
http: failed to handle request
dns: query for portal11.7803986842.com
dns: query for portal12.7803986842.com
dns: query for portal12.7803986842.com
dns: query for portal13.7803986842.com
dns: query for portal13.7803986842.com
dns: query for 1.100.168.192.in-addr.arpa
dns: query for portal14.7803986842.com
dns: query for portal14.7803986842.com
dns: query for portal15.7803986842.com
dns: query for portal15.7803986842.com
dns: query for portal16.7803986842.com
dns: query for portal16.7803986842.com
dns: query for portal11.7803986842.com
dns: query for portal11.7803986842.com

Thank you in advance and best regards.
I genuinely doubt I can add any help to this, but glancing at the comments there's talk of pointing the ntp.reciva.com domain to another local ntp server. That's the first stumbling block in what you've posted above. I suspect there are better places to get help on this as it's fairly specific stuff. Best of luck.
 
Hi,
Would this solution work also for reciva based tuners while reciva service has been shut down?
I have Rotel RT12 tuner.
If yes, what should be changed when following your tutorial?

Thank you in advance for your help.

Unfortunately not so far, I have tried it with various modifications on my Grace radio which ran on Reciva as well. The radio will simply not redirect itself to the YCast. I also get the port 80 blocked message.

Thanks for posting you results with Sharkfin patch attempt now at least I know it will not work as well. Fortunately, the stored stations still play.
 
So I've come across a solution to this ( not perfect maybe, but free and easy) there is an app in the play store called vradio which can stream internet radio stations via dlna to my Denon piccolo (need to set dlna/upnp setting to enabled, compatibility mode). I don't know if anything similar is available for Apple. Hope this helps.
 
When I had the cd-player serviced on my Marantz CR 611 they also updated the software. Before that I could search for radio stations straight from the device without vTuner. All stations were lost because of the factory reset. But now I need to add stations via vTuner, but after I registered the MAC number of the device I cannot find any icon to brows for stations. I wrote a mail to vTuner but got no answer.
For me the device has lost half of its value without Internet Radio. I wonder why Marantz forces us to use vTuner when previously everything worked fine without.
 
Yes, I have been exhausted by all this because I love internet radio. I have gone through the same with Denon and Yamaha. It is getting difficult to find something that will stream internet radio. I bought the Pioneer SX-N30 thinking it would be reliable but they rely on TuneIn and this is absolutely useless now in the UK after they lost a legal case. I only listen to one genre of music and I have about six stations, all commercial. I want to listen to small independent stations without news or adverts. My Pioneer is useless. I was going to try and go back to Denon but they have gone the same way, they use TuneIn. You end up looking at older equipment. I got a Sonata NP 30 which works but I had a Minx Xi and that only lasted me 10 weeks before the wi-fi developed a fault and this unit has the same niggling issue of spontaneously restarting which was the first indicating that the Minx Xi had a problem.
These units are a nightmare. They don't seem to support the software on them and there seem to be lots of issues. I looked at buying the unit you have but had a message from someone selling one alerting me to the issue with vTuner. I had similar issues with a Yamaha CD-NT670. That spontaneously goes to not being able to load the internet radio every now and then and doesn't rectify itself with a reset. I wish someone would just make an internet radio streamer like the old Denon DNP-f109. No apps. I don't want to link things and use an App via another device. I just want to use a remote control.
 
Thanks for starting this thread. Interesting reading. Looks like the price has now gone up to $5 a year.

I’ve came to this thread after trying to switch from DAB, which has developed a fault, to Internet Radio on my Marantz MCR603.

Luckily, after reading through, I realised that I didn’t need to pay as I already have Radio 6, the only station I listen to, in my favourites. My problem is that DAB came on instantaneously, whereas it takes an age for the receiver to connect and start playing Internet Radio. Would the YCast solution (if I can get this working) speed this up?
 
Thanks for starting this thread. Interesting reading. Looks like the price has now gone up to $5 a year.

I’ve came to this thread after trying to switch from DAB, which has developed a fault, to Internet Radio on my Marantz MCR603.

Luckily, after reading through, I realised that I didn’t need to pay as I already have Radio 6, the only station I listen to, in my favourites. My problem is that DAB came on instantaneously, whereas it takes an age for the receiver to connect and start playing Internet Radio. Would the YCast solution (if I can get this working) speed this u YCast will allow to save new stations to the favorites list.

Thanks for starting this thread. Interesting reading. Looks like the price has now gone up to $5 a year.

I’ve came to this thread after trying to switch from DAB, which has developed a fault, to Internet Radio on my Marantz MCR603.

Luckily, after reading through, I realised that I didn’t need to pay as I already have Radio 6, the only station I listen to, in my favourites. My problem is that DAB came on instantaneously, whereas it takes an age for the receiver to connect and start playing Internet Radio. Would the YCast solution (if I can get this working) speed this up?
YCast will only allow you save new stations to the favorites list. I don't believe it will speed up internet radio playing start.
 

The latest video from AVForums

Is Home Theater DEAD in 2024?
Subscribe to our YouTube channel
Back
Top Bottom