Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,454
» Latest member: Pattienner
» Forum threads: 16,190
» Forum posts: 116,850
Full Statistics
|
Latest Threads |
Full desktop Surfing and ...
Forum: General Discussion on Pinebook Pro
Last Post: Pattienner
4 hours ago
» Replies: 2
» Views: 367
|
Any recommended brands/mo...
Forum: Pinebook Pro Hardware and Accessories
Last Post: fnfgopro
6 hours ago
» Replies: 2
» Views: 794
|
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: tantamount
Yesterday, 02:25 PM
» Replies: 3
» Views: 564
|
Upgrading Armbian from v2...
Forum: Linux on Pinebook Pro
Last Post: Sb2024
08-09-2025, 06:53 AM
» Replies: 1
» Views: 701
|
PulseAudio dropouts after...
Forum: Linux on Pinebook Pro
Last Post: P. Siera
08-09-2025, 03:03 AM
» Replies: 3
» Views: 176
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: P. Siera
08-09-2025, 03:02 AM
» Replies: 6
» Views: 325
|
Hello from Ukraine
Forum: P64-LTS / SOPINE Projects, Ideas and Tutorials
Last Post: Dendrocalamus64
08-08-2025, 07:13 PM
» Replies: 1
» Views: 50
|
Simple Outdoor Weather St...
Forum: General Discussion on PineTab
Last Post: aria22
08-08-2025, 12:47 PM
» Replies: 0
» Views: 64
|
Armbian fix, current vers...
Forum: Linux on Pinebook Pro
Last Post: Sb2024
08-08-2025, 08:49 AM
» Replies: 0
» Views: 55
|
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
08-08-2025, 05:39 AM
» Replies: 2
» Views: 169
|
|
|
HOWTO: jackd on Pine64 |
Posted by: mauritslamers - 06-15-2017, 01:04 PM - Forum: Linux on Pine A64(+)
- Replies (1)
|
 |
As many people have found, the default jackd version that comes with the Pine64 Ubuntu image (which is version 1.9.10) will crash as soon as you start it with a bus error and a message in the kernel log about an aligment problem.
(Edit: strangely enough this error still occurs even if you are using a more recent image with jackd2 v1.9.11.)
In later versions of jackd this has been solved, but as there is no package, you're currently required to compile it by hand. This is not as difficult as it might sound, but it requires some tinkering in the terminal. Also: make sure that your pine64 board has enough power. If you use a 2.0A rated power supply, the board might crash in the middle of the process (as has happened to me). This tutorial assumes you are working with either the Ubuntu Basic Image, or the Ubuntu Mate image. If you are running a different image, the same process will apply, but you might need to adjust some actions.
The first thing we need to do is to install the old version of jack, because we need to make the system think that jackd is installed.
Code: sudo apt install jackd2
During the installation it will ask whether jackd should be run with real time priority. Answer yes on this question. Then install all the audio applications you're going to use, such as for example Ardour.
Then we are going to clone the latest version of jackd from github. Open a terminal by selecting Applications > System Tools > Mate Terminal or something equivalent:
Code: git clone git://github.com/jackaudio/jack2
If you get a message about unknown command, install git first by running
Code: sudo apt install git
.
Then go into the jack2 directory as created by the git command:
.
The compilation of jackd2 requires a few dependencies which we need to install:
Code: sudo apt install libasound2-dev libexpat1-dev
Now we can start the compilation preparation by giving the following command:
Code: ./waf configure --alsa=yes --classic --prefix=/usr
Depending on what kind of hardware you are going to use, you might need to add additional parameters to this line. Check for more info by adding
to the end of the line above. (In case I missed some dependency here, the process will warn you about it).
We start the compilation by running
You will see now a lot of text scrolling over your screen. If everything went fine, you will get a
Code: 'build' finished successfully
message. We are now going to install this version of jackd by running:
Sadly we are not entirely there yet. The source install puts certain files in a different spot compared to the standard packages, so in order to make jack not use the original files, we delete the files from the original package:
Code: sudo rm /usr/lib/aarch64-linux-gnu/libjack*
Now test jackd by running
Jack should now output something similar to
Code: pine64@pine64:~/jack2$ jackd -d alsa
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
If it replies with a message about permissions, it is possible that your user is not part of the audio group. Add yourself by doing
Code: sudo usermod -a -G audio [username]
where you change
for your user.
If you do see the bit of text above, you now successfully installed jackd2 and it is running. You can now stop this process by pressing Ctrl-C. From here you can use qjackctl or any other tool to start jackd.
A few considerations
When using jack on the Pine64, be aware that how smaller the buffer size is the more work it has to do. The latency will go down, but keep in mind that as soon as the CPU-temperature goes over 80 degrees Celsius, the CPU will be throttled. The performance of the board is pretty good. I had 32 mono tracks smoothly playing in Ardour with a few plugins on the side and the temperature didn't rise above 57 degrees C.
I managed to get jackd running in realtime with buffer sizes from 128 frames at a sample rate of 44100hz. Don't go lower as it will keep jackdbus hanging rather badly. I didn't test the upper limit well, but 192000Hz samplerate at 4096 frames buffer also seems to run fine.
I also tried LMMS and found that a sample rate of 192k didn't work very nicely with synthesis, as that is rather heavy on the CPU. You will notice quickly enough if you hear too many sample drops.
Troubleshooting
I had a very weird problem where only one channel was playing of the two I saw playing in Ardour. I then used the builtin audio test of Mate and had the same problem there. It turns out that in my case the left channel was muted. I was able to solve this by using
It turned out that the DACL Mixer AIF1DAOL port (which was the left stereo channel) was muted. It is a bit unclear why this happened, but if you happen to run into the same kind of problem, this is where you should be able to solve it.
Credits
Many thanks to Xalius for his help in getting to the bottom of this.
This guide is also posted (and updated) on github: https://gist.github.com/mauritslamers/32...bc19cb5e75
|
|
|
Remote area surcharge - what is it? |
Posted by: Hatgor - 06-15-2017, 08:02 AM - Forum: General Discussion on Pinebook
- Replies (3)
|
 |
Hy there everyone!
Received today the following message from Pine email:
Quote: Wrote:We are pleased to inform you that your order is scheduled to deliver very soon. However, in the midst of your shipment preparation, we come across that your shipping address is located in a remote area. This being said that a remote area surcharge of USD33 will be imposed to the delivery of your shipment.
So Pine team told me that they are going to charge me 33 USD more because my country is "remote area". First of all, I live in Eastern Europe. Not in Africa or North Pole. Why my country is in "remote area"?
Secodly, delivery tariff to my country was mentioned on their website and it is not small - 52 USD per 1 shipment to Ukraine. Why do I need to pay more 33 USD I don't know.
Thirdly, I don't want to pay anything more untill someone does explain to me where the additional costs came from.
Hope to receive answer from Pine representatives ASAP.
Thanks in advance!
|
|
|
I2C Touch Panel |
Posted by: mbt28 - 06-12-2017, 11:32 AM - Forum: LCD and Touch Panel
- No Replies
|
 |
Hi,
I have 8 inch CTP with GT 911 controller but it is 6 pin I2C, as far I see default touch in Pine64 uses SPI for touch. Is it possible to use I2C touch screen?
Thanks
|
|
|
SystemLED *ON* on boot |
Posted by: ecolezen - 06-09-2017, 06:53 PM - Forum: Pi2, Euler and Exp GPIO Ports
- Replies (4)
|
 |
Hi, just want to share a little tip:
How to turn the systemLED ("LED") to *ON* when the board is booting (loading the system).
![[Image: DSC_0045-photo-led.jpg]](http://www13.plala.or.jp/pskitty/img/pa64sysled/DSC_0045-photo-led.jpg)
My 1GB Pine64 Board sometimes start booting process and sometimes don't... so I have to way and "see" activities on the screen or LAN interface...
So, I decided to put an LED on the systemLED holes (label "LED"), and switch it to ON when booting...
![[Image: pine64-drawing-v2-p6.jpg]](http://www13.plala.or.jp/pskitty/img/pa64sysled/pine64-drawing-v2-p6.jpg)
When using without a monitor (remote) this LED is very helpful...
These 3 lines of script turn the LED to "ON":
Code: echo "359" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio359/direction
echo "0" > /sys/class/gpio/gpio359/value
Full instructions on the link below:
http://www13.plala.or.jp/pskitty/pine64-sysled.html
Drawings, source code, high quality photo, etc, on GitHub:
https://github.com/valterfukuoka/pine64-sysled
Regards all,
Valter
|
|
|
Win 10 IoT 15063_20170602 shutdown |
Posted by: dkryder - 06-05-2017, 05:31 AM - Forum: Windows 10 IoT
- Replies (6)
|
 |
hello, nice work on 0602 but i noticed a few things. the about allwinner link has bad url and shutdown via command line or upper right power only reboots device, no actual shutdown. what would be best way to shutdown? oh yeah, cortana, what is best suggested method to get the voice recognition working? is there a list of known good mic/speaker setups?
|
|
|
|