psketch wrote:
> Yep, I keep my custom lircd.conf as well, but that didn't work either.
> However, I think there's two things here. After the insitu update, it
> seems that lirc is running ok. Mine seemed to be running, but didn't
> respond to commands. I'll need to investigate that
Hammerhead wrote:
> I read here that I could theoretically I could use a Zero mounted on a
> Pi3 via the GPIO header.
Anything is possible, I guess.
But the fact its never been done before doesnt necessarily mean its a
good idea...
3 SB 3 Libratone Loop, Zipp Mini iPeng (iPhone +
epoch1970 wrote:
> In a way, yes...
> Your audio system expects a mass-storage device, the Pi does too. This
> means they both act as USB hosts, and you can't connect 2 hosts
> together.
> You'd want the Pi to present itself as a mass-storage -device-, while
> playing its mp3fs trick over FLAC
psketch wrote:
> Yep, I keep my custom lircd.conf as well, but that didn't work either.
> However, I think there's two things here. After the insitu update, it
> seems that lirc is running ok. Mine seemed to be running, but didn't
> respond to commands. I'll need to investigate that
Jeff07971 wrote:
> My lirc is fine after an insitu update, I have a custom lircd.conf which
> I had to reload but apart from that its fine
>
> I did a Jivelite update also today and I didn't even have to reload lirc
> again (even though the help said I would have to)
>
> Jeff
Yep, I keep my
My lirc is fine after an insitu update, I have a custom lircd.conf which
I had to reload but apart from that its fine
I did a Jivelite update also today and I didn't even have to reload lirc
again (even though the help said I would have to)
Jeff
*Players:* SliMP3,Squeezebox3
Paul Webster wrote:
> lirc running fine on my in-situ upgraded 3.50.
> I just verified it with a slim remote.
>
> >
Code:
> >
> tc@PiTouch:~$ ps -ef | grep lirc
> 2458 root 0:01 /usr/local/sbin/lircd --device=/dev/lirc0
--log=/var/log/pcp_lirc.log --uinput
psketch wrote:
>
> So, feels like lirc may be generally broken on 3.5
>
lirc running fine on my in-situ upgraded 3.50.
I just verified it with a slim remote.
Code:
tc@PiTouch:~$ ps -ef | grep lirc
2458 root 0:01 /usr/local/sbin/lircd
Hammerhead wrote:
> So, if we could get the Pi to make the file system available to the
> car's USB port and appear as though it was just mass storage, then this
> would do the trick.
In a way, yes...
Your audio system expects a mass-storage device, the Pi does too. This
means they both act as
Hi Paul
I've come across a new problem with one of my other players when I
upgrading to 3.5.0 - lircd doesn't seem to be working. I have another
old armv6 Pi which was running 3.22 fine with lircd configured with an
old Microsoft infrared receiver on lirc1 controlling jivelite. I did an
Roland0 wrote:
> If you settle for mp3, you may be able to use 'mp3fs'
> (https://khenriks.github.io/mp3fs/) to avoid this (depending on the
> platform your library is hosted on).
> Sound quality: AAC > MP3 > Bluetooth
> I don't see any reason to use a Pi in this setup (unless you use
>
Anyone happen to do an lircd.conf for the silver/aluminum apple tv
remote they could share? Thanks!
Scott Kramer - 'AudioSystem' (http://bit.ly/2o2opXv) - 'YouTube'
(http://bit.ly/1ULq4fT) - 'Twitter' (http://bit.ly/1q8dTgc)
jmccoy555 wrote:
> Hello all.
>
> I'm trying to get this going, following Post 1 I have got the kernel to
> load and end up with a terminal session. PiCorePlayer is not yet
> loading.
>
> I'm a bit lost at point 3, where do I put the script?
>
> I've had a bit of a poke around and have
Hammerhead wrote:
>
> Yes, I was trying to avoid two separate libraries.
>
If you settle for mp3, you may be able to use 'mp3fs'
(https://khenriks.github.io/mp3fs/) to avoid this (depending on the
platform your library is hosted on).
>
> I was also hoping to benefit from the lossless
d6jg wrote:
> For this reason the best option remains USB thumb drive with 320kbps
> MP3. I have a 32Gb drive which holds more than suffiicient music for
> even the longest journey.
The biggest problem for me is that I'm not aware of any car-based MP3
player (disc or USB) that's fully gapless.
Hello all.
I'm trying to get this going, following Post 1 I have got the kernel to
load and end up with a terminal session. PiCorePlayer is not yet
loading.
I'm a bit lost at point 3, where do I put the script?
I've had a bit of a poke around and have found the default
/opt/bootlocal.sh,
garym wrote:
> Or 192kbps for that matter except with particularly troublesome samples
> that produce artifacts (these are rare, and would be even more rare to
> hear in an automobile setting). In my own case, I keep a mirror image
> of my FLAC library as mp3s for use in my ipods, iphones,
I have been adding code to handle failed memory allocation requests and
fixed several memory leaks in jivelite over the past few months.
The current version 0.1.0-7778117 is in the picoreplayer 3.5.0
repository so if you institu upgraded and didn't reinstall jivelite you
could still be running
w3wilkes wrote:
> I built me a PCp using a Pi 3 Model B with a Hifiberry DAC+ Pro and have
> loaded up PCp 3.5.0. Thanks so much for creating this wonderful package
> that should keep the Squeeze things alive indefinitely!
>
> I am older and my higher freq hearing is getting worse. I use the
>
d6jg wrote:
> In truth there is very little point having FLACs in car as opposed to
> 320kbps MP3. You won't hear any difference even with top end Bose kit or
> similar due to road and wind noise etc.
Or 192kbps for that matter except with particularly troublesome samples
that produce artifacts
psketch wrote:
>
>
> Yep - that fixed it.
>
> Anything else you'd like me to take a look at?
>
> pete S
Nope, glad its working now.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://sites.google.com/site/picoreplayer/home
Please 'donate'
In truth there is very little point having FLACs in car as opposed to
320kbps MP3. You won't hear any difference even with top end Bose kit or
similar due to road and wind noise etc.
Its an interesting project but you will never get the infotainment
system to read the contents of a Pi no matter
paul- wrote:
> Pete,
>
> Please confirm which RPI board and pCP version you are using. If using
> on a armv6 device and using plain pCPCore, then there is a module
> missing. I guess I never tested USB on an armv6 device.
>
> After you install 3.5.0 and boot up.open a ssh session and run
It looks like my previously reported issues were due to the power
supply. 3.5.0 must have tipped it over the edge. Powering it from a
battery I did a fresh install without any issues, including Samba.
Thanks for the great work.
24 matches
Mail list logo
