Building ethernet network with windows 7 and Raspberry

C

carlmart

Gawd
Joined
Sep 17, 2006
Messages
687
Is there a way to build a network with Windows 7 and Raspberry Pi3, by Ethernet, to assemble a video system?

Until now I had been using a media player, but now it's not working anymore due to interface connection protocols.

At the same time I will assemble an external server using another PC, only this time it will be controlled by a Linux server, probably CentOS.

Right now I can't make the Raspberry "see" my Windows 7.

How should I go about this?
 
So, probably going to need a little clarification.

If you're trying to use the RPi3 as a media player, with media hosted on a Windows 7 computer, then yes that's absolutely possible. You'll need to map an SMB share, or use playback software with SMB support built-in like Kodi does. If you want your Pi to exclusively be a media player, then look into a distribution like OpenELEC or LibreELEC, which install a slim OS and bundled copy of Kodi and boot straight into the media playback interface. Using a SMB share from Kodi is simple since it handles it for you essentially.

Beyond that, I can't gather what you might mean by "assemble a video system".
 
sinisterDei said:
So, probably going to need a little clarification.

If you're trying to use the RPi3 as a media player, with media hosted on a Windows 7 computer, then yes that's absolutely possible. You'll need to map an SMB share, or use playback software with SMB support built-in like Kodi does. If you want your Pi to exclusively be a media player, then look into a distribution like OpenELEC or LibreELEC, which install a slim OS and bundled copy of Kodi and boot straight into the media playback interface. Using a SMB share from Kodi is simple since it handles it for you essentially..
Click to expand...

Thanks, that's exactly what I will doing. My RPi3 i already loaded with LibreELEC/Kodi.

Very soon it will connect only to the Linux server with CentOS, non-raided.

In fact running the RPi3 for video is just a short time experiment. The idea is to use the RPi3 for audio manager and an ODROID for video managing. I am not too sure which system, ODROID or any other, would provided the best quality video interface. What do you think?
 
carlmart said:
In fact running the RPi3 for video is just a short time experiment. The idea is to use the RPi3 for audio manager and an ODROID for video managing. I am not too sure which system, ODROID or any other, would provided the best quality video interface. What do you think?
Click to expand...

Not sure it matters. Everything is digital, there isn't much in the way of 'quality' to be had in either case. The only differentiation might be if you're planning on utilizing 4K video, which the Pi cannot handle. Some of the ODROIDs have HDMI 2.0 and can handle 4K60 output, others cannot. I don't understand the concept of having an "audio manager" and a "video manager" though, so I am not sure I'm providing the right advice.
 
The audio of the audio being separate from the video is to handle DSD digital files, putting aa USB and high quality DAC to handle stereo signals.

The audio and video managers will handle different sources with different outputs: HDMI for video & audio from video files; USB to DAC for audio files. Much less processing for the digital to analog signal for audio files.
 
I guess I just assume that folks who had 'media player' type devices also have some kind of home theater equipment to plug them into. Most of modern home theater equipment accepts digital audio input via HDMI, so there would be no need for a USB DAC since the "DAC" portion would happen on the home theater receiver or soundbar or whatever.
 
I had media players with HDMI output, connected to good receivers, and even the coaxial output in the receiver was a LOT better than the HDMI when connected to a DAC.

As people who have tried DSD files through coaxial and USB interface claim the latter sounds much better, so once again it seems that being digital doesn't guarantee anything.

Let me do my own listening tests and I tell you what I found.
 
carlmart said:
it seems that being digital doesn't guarantee anything.
Click to expand...

This isn't true. Or I suppose, isn't true when things are configured correctly, which I suppose I shouldn't take for granted.

Assuming you're watching movies, or TV series on blu-ray, netflix, Hulu, or other content like that, the audio is likely encoded in some flavor of Dolby Digital or DTS. If that's the case, then your HDMI input (or coaxial or optical digital output) should be configured in passthrough mode, and let your receiver handle the decode of the Dolby/DTS signal and then mix it out to your speakers. However, it is of course possible that you might not be configured for passthrough mode and instead are decoding the Dolby/DTS signal on the player device, at which point you're likely just sending flat decoded digital stereo audio out via the digital interface, and sure that might not sound as good as running it through your DAC and then connecting to your speakers via an analog interface. But the only reason that is the case is because you're misconfigured and not passing through the audio like you should be.
 
The configuration is not the problem, the problem are the digital to analog stages.

But I didn't intend to enter into such a discussion here, because we should be going into objective versus subjective opinions which are not the issue of what I needed help with.

The problems I'm having now are related to interface protocols, particularly Windows 7 ones. Let's hope I can get through them.
 
Well, let me tell you that, with the help of a friend, I could get the Raspberry to see my PC.

For that we had to create a new user with password, and add that data on the Kodi configuration for sources.

I don't know why that is so. The PC IP was the same before, when I was using my user name with no password. Why a user name and a password seemed to be obligatory?
 
You must log in or register to reply here.
Back
Top