cmiyc:
I'm sorry to be pedantic, but as your post later indicates, using the phrase "it works perfectly" is dangerous. The circuit may be working, as expected, but without measurements and verification plan that tests for failure, you cannot verify it is "perfect." A minor issue on a breadboard can manifest itself into a non-working circuit board.
So be careful not to trap yourself in that mindset. It worked "as expected."
Ok won't do that error again
You say "the signal" and "this pin" but you never identify the actual pin. Your code refers to the Tiny's pin/port identify but without comments (or reasonable variable name) it isn't clear to me which traces on the schematic/PCB refer to your code. (Sorry, I don't know the Tiny's pinout by memory.)
The binary word sent on PIN2 with RCSwitch
Also, what you mean by "radio" in this context. Are you using a 433MHz radio module? If so, which one? What are the B1, B2, and B3 connections for? What is the frequency of the signal you're measuring?
B1, B2, B3 are the pushbuttons, the tiny sends signal depending on which buttons is pressed.
I'm using the basic cheap 433Mhz module
I don't know the frequency of the default protocol for RCSwitch. PulseWidth is something like 360 micros as far as I remember
That drifting could be a result of the input-filtering of your audio input and not related to the behavior of the circuit.
Keep in mind that breadboards have very lousy ground paths. From your PCB diagram, I can't tell how you did your ground plane. Without one, any signals operating at a relatively high frequency (10KHz+) is going to suffer quite a bit of noise and ground loops. Did you fill the unused top side and the bottom side of the board with a ground plane?
We can see on the graph that the signal is perfectly clear and shows as expected, since it's taken on the radio input pin.
wvmarle:
Also wondering where in that pretty blue on grey image you see a "slow rise and fall". Actually, I wonder what that image even tries to show. Based on the general forum topic I guess it's some kind of signal, but what??
It's a binary signal, 0s and 1s. We can see that the start of the signal is lower than normal.
For the PCB: the few designs I've done so far I gave a ground plane on the bottom (largely unused - a few traces that really couldn't be routed on top) and Vcc plane on the top side (where most of the traces are as well) - all also based on SMD components. For through-hole designs maybe do this upside-down, don't know what'd be better.
Currently is through hole, I'll decide later if I want to go SMD
TomGeorge:
Hi,
You need bypass capacitors and place a 10uF capacitor across the power pins of the Tx at the radio pins on the PCB.
Why ? No schematic shows that on every tutorial I saw and it works on the breadboard
Why do you need D1, D2 and D3?
This prevents the signal from B1, for example, to go in B2 trace. Since I need all buttons to go to VCC pin and I also need to check which button is pressed
Have you measured the voltage on pin8 of the Attiny to see what your supply voltage is?
By memory 4.5 (3x new AAA) minus voltage drop by the diodes
You may need to program in a delay between power up and when you send your data.
Works normally on breadboard
When designing a PCB remember, you have bought a completely clad PCB and you are paying someone to remove the cladding, so try and leave as much on your board as possible, cos you own it.
Will do
All your PCB tracks can be a lot wider for a start.
Wanted to go as small as possible because it must fit in there :
Tom.. 
Thanks for your replies.
I am currently moving, all my eletronic stuff is in my new flat. I'll update you when we're done.
Regards