FifoPi Q7 has a lot of improvements over FifoPi Q3. It is equipped with low noise discrete 1-bit three stages re-clockers, discrete isolators (lower EMI leakage) and a 32bit much powerful Fifo engine. Basically, FifoPi Q7 functionally equivalent to or even better than FifoPi Q3 plus ReClockPi plus better isolator and plus much better FPGA SoC. It also has more new features such as working with MonitorPi as controller, continuous (non-stop) output mode and so on... FifoPi Q7 will be the flagship of FifoPi family.
You don't need the ReClockPi for FifoPiQ7 unless you still want to try it. The three stages 1-bit low noise discrete re-clocker has already been integrated into FifoPiQ7.
FifoPi Q7 clean side takes 3.3V direct power supply. Low noise LifePO4 or ultracapacitor power supplies, such as LifePO4 Mini, LifePO4, UcConditioner 3.3V,PurePi, UcPure are all good to go.
I'm currently feeding my Allo USBridge through a 5V UcConditioner/ConditionerPi combination. My goal is to switch output from USB to I2S to my Topping D90 and I'm waiting on the FifoPiQ7 and HDMI Pro boards to do that. I'm assuming having a separate director power supply for each board would be best, just wondering if the HDMI pro will also be 3.3V and if it will be released close to the FifoPiQ7. I already have my enclosure, transformer and capacitors ready in preparation for when these two products hit your Github for purchase.
Hi Ian, would this solve my click issue which I have in my current setup (RPI / Volumio -> FifoPi Q3 -> DDDAC).
This issue was discussed some while ago:
Post 6194
Hi @iancanada - I am facing an issue/glitch/whatever you may want to call this phenomena that I am facing with my FifoPi Q3 with reclockpi. I am sure this is not a fault in either of these products but a logic I am unable to fathom how it works. Finally posting it here so you could help explain why maybe.
So I use a Beaglebone Black Rev C which receives music signal over the Ethernet (NAA) and passes it on via an isolator board (IL712) to the fifopi Q3 (fitted with Accusilicon AS318 45 & 49M clocks) and reclockpi stack. The reclockpi transfers the signal to my DDDAC via i2s.
The issue is that when i use a player such as HQP, the chain till fifopi is not able to select the appropriate clocks basis the 44.1k or 48k families. Fifopi auto selects any of these clocks as the only one operating and I have to manually select the oversampling range to match that clock to get music to play at proper tempos. Why is this random selection of clocks happening on the fifopi q3? How can i have both 44.1 and 48k families to play and on the fly selection of clocks to take place? Even if there is just one clock that will be operable in my case, why does it keep changing? Sometimes after a new boot up of the BBB, Isolator, Fifopi and Reclockpi chain, the 45M clock gets selected and other times 49M clock.
Happy to receive any assistance to be able to ideally play all frequencies from both these clock families!
Regards
Kartick
So I use a Beaglebone Black Rev C which receives music signal over the Ethernet (NAA) and passes it on via an isolator board (IL712) to the fifopi Q3 (fitted with Accusilicon AS318 45 & 49M clocks) and reclockpi stack. The reclockpi transfers the signal to my DDDAC via i2s.
The issue is that when i use a player such as HQP, the chain till fifopi is not able to select the appropriate clocks basis the 44.1k or 48k families. Fifopi auto selects any of these clocks as the only one operating and I have to manually select the oversampling range to match that clock to get music to play at proper tempos. Why is this random selection of clocks happening on the fifopi q3? How can i have both 44.1 and 48k families to play and on the fly selection of clocks to take place? Even if there is just one clock that will be operable in my case, why does it keep changing? Sometimes after a new boot up of the BBB, Isolator, Fifopi and Reclockpi chain, the 45M clock gets selected and other times 49M clock.
Happy to receive any assistance to be able to ideally play all frequencies from both these clock families!
Regards
Kartick
Just to clarify @iancanada - the I2S from BBB is generating from the clocks on fifopi by accepting mclk from fifopi via IL712. So the main question actually is:
Is it possible to select the needed clock prior to the I2S lines presence on FIFOpi's input? And if yes, then what is the best possible way?
Is it possible to select the needed clock prior to the I2S lines presence on FIFOpi's input? And if yes, then what is the best possible way?
@tods
MonitorPi has no problem working with HifiBerry, in either master mode or slave mode. Please see the picture for the exactly the same case. MonitorPi keeps monitoring the signal on PIN12 and other pins and shows the correct analyzing result on the screen.
MonotorPiHifyberry by Ian, on Flickr
Regarding the fifopi. If i play by the I2s connections -> external I2s dac.
Now i connect a transportPi at the same time and hook up a spdif dac and start playing.
What will happen:
-one source, spdif or i2s is auto selected, if so which one?
-Magic smoke?
-or i need a switch or so?
I ask because i have a streamer fifopi+external dac. And i maybe want the option of external spdif.
Now i connect a transportPi at the same time and hook up a spdif dac and start playing.
What will happen:
-one source, spdif or i2s is auto selected, if so which one?
-Magic smoke?
-or i need a switch or so?
I ask because i have a streamer fifopi+external dac. And i maybe want the option of external spdif.
Thans Ian for the fast reply. But that's not 100% what i mean, almost...
The dac/streamer is my own creation. The Fifopi is connected internaly to the dac i2s.
Now i want to place a transportPi on the fifo and place a spdif to the chassis so that i can connect an external transport to my "streamer".
There are no switch buttons and i rather not use one.
What wil happen when i connect the transport and the fifopi i2s is also connected? Is there a sequence the Fifopi wil select. Or is this not feasible?
Ps. looking forward to the q7. When wil it be released?
The dac/streamer is my own creation. The Fifopi is connected internaly to the dac i2s.
Now i want to place a transportPi on the fifo and place a spdif to the chassis so that i can connect an external transport to my "streamer".
There are no switch buttons and i rather not use one.
What wil happen when i connect the transport and the fifopi i2s is also connected? Is there a sequence the Fifopi wil select. Or is this not feasible?
Ps. looking forward to the q7. When wil it be released?
@Arnolddew
"FifoPi GPIO outputs and u.fl outputs both have independent drivers.". You don't need a switch. The I2S outputs and the spdif output from the TransportPi will work together at the same time. If it is possible, please use the u.fl coaxial cables to connect to you DAC for a better signal quality.
Ian
"FifoPi GPIO outputs and u.fl outputs both have independent drivers.". You don't need a switch. The I2S outputs and the spdif output from the TransportPi will work together at the same time. If it is possible, please use the u.fl coaxial cables to connect to you DAC for a better signal quality.
Ian
You may want to give the ReceiverPi a try. I believe that's specifically designed to get S/PDIF (or Coaxial) signal to your DAC/Streamer. I'm personally using the StationPi Pro (SPP) that has a display and controller (ESS) that allows you to easily select the input. If you're using input from USB, then BridgePi, or the SPP daughter card would be the preferred choice - with an Amanero card. All of Ian boards provide the ability for a very integrated streamer to be built - with endless possibilities.