Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#4462 - Rosegarden recording is broken aswell as pkgbuild
Attached to Project:
Arch Linux
Opened by Lou (cmf) - Saturday, 15 April 2006, 13:22 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 14 April 2007, 14:12 GMT
Opened by Lou (cmf) - Saturday, 15 April 2006, 13:22 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 14 April 2007, 14:12 GMT
|
DetailsRecording audio in rosegarden is broken, appears it can't connect to jack as a client. Tried to recompile but the pkgbuild isn't working.
Recording in ardour via jack is working fine. jack message output: new client: rosegarden, id = 3 type 2 @ 0xb6dd2000 fd = 18 removing disconnected client rosegarden state = Not triggered errors = 0 removing client "rosegarden" removing client "rosegarden" from the processing chain ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. client qjackctl-2495: start_fd=5, execution_order=0. client qjackctl-2495: wait_fd=10, execution_order=1 (last client). -- jack_rechain_graph() 14:19:56.166 Audio connection graph change. rosegarden>settings>configure rosegarden>sequencer>show detailed status: Rosegarden 4-1.2.3 - AlsaDriver - alsa-lib version 1.0.10 JackDriver::initialiseAudio - JACK sample rate = 48000Hz, buffer size = 256 JackDriver::initialiseAudio - creating disk thread JackDriver::initialise - client activation failed ALSA Client information: 16,0 - (Audigy MPU-401 #2, Audigy MPU-401 (UART)) (DUPLEX) [ctype 2, ptype 2, cap 127] 16,32 - (Audigy MPU-401 #2, Audigy MPU-401 #2) (DUPLEX) [ctype 2, ptype 2, cap 127] 17,0 - (Emu10k1 WaveTable, Emu10k1 Port 0) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] 17,1 - (Emu10k1 WaveTable, Emu10k1 Port 1) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] 17,2 - (Emu10k1 WaveTable, Emu10k1 Port 2) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] 17,3 - (Emu10k1 WaveTable, Emu10k1 Port 3) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] Creating device 0 in Play mode for connection 16:0 Audigy MPU-401 (UART) (duplex) Default device name for this device is MIDI output system device Creating device 1 in Record mode for connection 16:0 Audigy MPU-401 (UART) (duplex) Default device name for this device is MIDI input system device Creating device 2 in Play mode for connection 16:32 Audigy MPU-401 #2 (duplex) Default device name for this device is MIDI output system device 2 Creating device 3 in Record mode for connection 16:32 Audigy MPU-401 #2 (duplex) Default device name for this device is MIDI input system device 2 Creating device 4 in Play mode for connection 17:0 Emu10k1 Port 0 (write) Default device name for this device is MIDI output system device 3 Creating device 5 in Play mode for connection 17:1 Emu10k1 Port 1 (write) Default device name for this device is MIDI output system device 4 Creating device 6 in Play mode for connection 17:2 Emu10k1 Port 2 (write) Default device name for this device is MIDI output system device 5 Creating device 7 in Play mode for connection 17:3 Emu10k1 Port 3 (write) Default device name for this device is MIDI output system device 6 System timer is only 250Hz, sending a warning Current timer set to "system timer" WARNING: using system timer with only 250Hz resolution! AlsaDriver::initialiseMidi - initialised MIDI subsystem System timer is only 250Hz, sending a warning Current timer set to "system timer" WARNING: using system timer with only 250Hz resolution! ALSA Client information: 16,0 - (Audigy MPU-401 #2, Audigy MPU-401 (UART)) (DUPLEX) [ctype 2, ptype 2, cap 127] 16,32 - (Audigy MPU-401 #2, Audigy MPU-401 #2) (DUPLEX) [ctype 2, ptype 2, cap 127] 17,0 - (Emu10k1 WaveTable, Emu10k1 Port 0) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] 17,1 - (Emu10k1 WaveTable, Emu10k1 Port 1) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] 17,2 - (Emu10k1 WaveTable, Emu10k1 Port 2) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] 17,3 - (Emu10k1 WaveTable, Emu10k1 Port 3) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] makepkg output for rosegarden pkg: [root@rubarb rosegarden]# makepkg -f ==> Making package: rosegarden 4.1.2.3-2 (Sat Apr 15 14:23:37 BST 2006) ==> Checking Runtime Dependencies... ==> Checking Buildtime Dependencies... ==> Retrieving Sources... ==> Using local copy of rosegarden-4-1.2.3.tar.bz2 ==> Found 4.1.2.3-fix-icon-destdir.patch in build dir ==> WARNING: MD5sums are missing or incomplete. Cannot verify source integrity. ==> Extracting Sources... ==> tar --use-compress-program=bzip2 -xf rosegarden-4-1.2.3.tar.bz2 ==> Removing existing pkg/ directory... ==> Starting build()... patching file scons_admin/kde.py scons: Reading SConscript files ... ** installation prefix for the project set to: /opt/kde Checking for kde-config : kde-config was found as /opt/kde/bin/kde-config Checking for kde version : 3.5.2 Checking for the qt library : qt is in /opt/qt Checking for uic : uic was found as /opt/qt/bin/uic Checking for moc : moc was found as /opt/qt/bin/moc Checking for the qt includes : ok /opt/qt/include/ Checking for the kde includes : ok /opt/kde/include/ Checking for pkg-config ... yes Checking for alsa >= 1.0 ... yes Checking for jack >= 0.77 ... yes Checking for dssi >= 0.4 ... yes Checking for C header file ladspa.h... yes Checking for lrdf_init() in C library lrdf... yes Checking for liblo >= 0.7 ... yes Checking for xft >= 2.1.0 ... yes -> LIRC support disabled by user scons: Reading SConscript files ... Checking for pkg-config ... yes Checking for alsa >= 1.0 ... yes Checking for jack >= 0.77 ... yes Checking for dssi >= 0.4 ... yes Checking for C header file ladspa.h... yes Checking for lrdf_init() in C library lrdf... yes Checking for liblo >= 0.7 ... yes Checking for xft >= 2.1.0 ... yes Checking for int lirc_init() in C library lirc_client... yes TypeError: can only concatenate list (not "str") to list: File "SConstruct", line 54: toolpath=['./', 'scons_admin/']) File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Memoize.py", line 819: None File ".../SCons/Memoizer-init-lambda<<unknown>>", line 1: None File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Memoize.py", line 778: None File "<unknown>", line 1: None File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Memoize.py", line 781: None File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Memoize.py", line 819: None File ".../SCons/Memoizer-init-lambda</home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Environment.py>", line 471: None File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Memoize.py", line 778: None File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Environment.py", line 517: None File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Environment.py", line 133: None File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Environment.py", line 1091: None File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Tool/__init__.py", line 128: None File "scons_admin/rosegarden.py", line 52: env.AppendUnique(CCFLAGS = env['OPTLIB_CCFLAGS'] ) File "/home/arch/extra/devel/scons/pkg/usr/lib/python2.4/site-packages/SCons/Environment.py", line 738: None ==> ERROR: Build Failed. Aborting... apologies for the long report, wanted to be thorough. Thanks |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Saturday, 14 April 2007, 14:12 GMT
Reason for closing: Fixed
Additional comments about closing: build problem fixed
Saturday, 14 April 2007, 14:12 GMT
Reason for closing: Fixed
Additional comments about closing: build problem fixed
the nolirc=1 does not work right... they fixed it in SVN and if i find some time, i will backport this to our pkg (there is also rosegarden-devel that i need to update too, but that is low priority)... that's about the build issue
the record issue... hmm... i don't know what's wrong here, but i also didn't try to record wave audio with rosegarden till now... always used ardour. a wild guess: have you tried to run jack in a sample rate of lower than 48000Hz? have you tried a kernel with a timer resolution of >=1000Hz?
if you feel like trying, you can find the PKGBUILD rel 1.6 here:
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/multimedia/rosegarden/PKGBUILD?rev=HEAD&cvsroot=Extra&only_with_tag=CURRENT&content-type=text/vnd.viewcvs-markup
rosegarden 4.1.4.0-1
can you reproduce the recording problem with this version?
rosegarden 4.1.5.1-1
i would say, we close this... if there is problem in recording, it is not the packaging of rosegarden, that is causing it