LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Studio 13.37 (http://www.linuxquestions.org/questions/studio-13-37-99/)
-   -   Jack won't start (http://www.linuxquestions.org/questions/studio-13-37-99/jack-wont-start-4175447238/)

poconoco 01-25-2013 07:20 PM

Jack won't start
 
Hey, first off- love this distro and I'm trying to really incorporate it into my studio -

I've been using the 32 bit version on my compaq laptop for about a year now. I've had some problems with my save file and had to delete it and start fresh a couple times, so I stopped creating save files.

Last time I used Studio 1337 (still on a fresh "no save file" install into RAM) I set up my guitar and checked out Rakarrack and played around with it for a while - was thinking about possibilities as a live effects unit....

anyway... I got some time to mess around with it again today and fired up and now I can't use Jack for some reason. Getting this:


18:53:57.559 Patchbay deactivated.
18:53:57.569 Statistics reset.
18:53:57.635 Startup script...
18:53:57.636 artsshell -q terminate
18:53:57.650 ALSA connection graph change.
sh: artsshell: command not found
18:53:58.045 Startup script terminated with exit status=32512.
18:53:58.046 JACK is starting...
18:53:58.047 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p1024 -n2
jackd 0.121.2
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd 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
could not find any drivers in /usr/lib/jack!
jackd: no drivers found; exiting
18:53:58.064 JACK was started with PID=29077.
18:53:58.071 JACK was stopped with exit status=1.
18:53:58.072 Post-shutdown script...
18:53:58.073 killall jackd
18:53:58.249 ALSA connection change.
killall: jackd: no process killed
18:53:58.486 Post-shutdown script terminated with exit status=256.

messed around with a few setup configs (48000 to 41000 sample rate) and tried using a line6 guitarport when jack wouldn't fire up on the laptops soundcard initially.

I can get into the Jack folder on the usr/lib/jack and see about 20 or so .gz files when using the file browser.

Last time I used it with Rakarrack (off a fresh install) I did not create a save file on shutdown which I have not been doing lately.

Any help is much appreciated.

Gonna use my 64 bit version on my desktop and see if I can get my Studio1337 fix this weekend!

Thanks,
Chris

business_kid 01-27-2013 09:47 AM

Code:

sh: artsshell: command not found
18:53:58.045 Startup script terminated with exit status=32512.

google '+linux +artsshell' or 'jack error 32512' and see wht you get.
it looks like it can't find artsshell.Also run

ldd /path/to/jackd |grep found

the correct output is nothing. Anything it mentions is missing. Install it. This is a useful test for missing libs.

glokraw 01-27-2013 11:57 AM

Quote:

Originally Posted by poconoco (Post 4877688)
Hey, first off- love this distro and I'm trying to really incorporate it into my studio -

I've had some problems with my save file and had to delete it and start fresh a couple times, so I stopped creating save files.

anyway... I got some time to mess around with it again today and fired up and now I can't use Jack for some reason.
Chris

Hi, when you change a usb connection or device, it can alter the order and names that are
in the settings in the qjackctl setup panel, for Input and Output devices,
so jackd is like a batter whiffing on a hard slider, or a skaters triple-axel gone bad.

The proper name for the device you want to use, if the kernel sees it,
is seen within brackets, in the output of these commands:

bash-4.1$ cat /proc/asound/cards
0 [M2496 ]: ICE1712 - M Audio Audiophile 24/96
M Audio Audiophile 24/96 at 0xac00, irq 17
bash-4.1$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: M2496 [M Audio Audiophile 24/96], device 0: ICE1712 multi [ICE1712 multi]
Subdevices: 0/1
Subdevice #0: subdevice #0
bash-4.1$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: M2496 [M Audio Audiophile 24/96], device 0: ICE1712 multi [ICE1712 multi]
Subdevices: 0/1
Subdevice #0: subdevice #0

This was my system output, and ICE1712 multi
is what I choose, or type in, when clicking the
Input/Output Device > or v widgets in qjackctl.

Some devices are input only, (your guitarport?) so you must also choose the right
Output device for your system.
Soon you'll use the easy access flexibility, to your advantage,when swapping out gear
with intent.

If your save file is on a crowded fragmented ntfs partition, I would get an external drive,
move the non-system files to it, so mainly just the OS and installed software are left,
and defragment the drive. Then do a savefile saved in the root of C:
Move things back only if you need to. If it's a linux-only setup, try saving it directly
to / (not in any folder) I also would repeatedly resize it, to the size you want,
before adding things to it. Then back it up. Then use and populate it.
In the long run, as your music/work gains value,
the importance of off-site backups becomes clear. Fire, thieves, flood, user blunders,
(my speciality) just don't give them a fighting chance.
Cheers

l0wt3ch 01-30-2013 07:48 AM

Studio 13.37 uses .sfs files to make the original system unchangeable/unbreakable. So if JACK was working yesterday, it should work today.

You say that you are using a "fresh install", I take it that means you are using Studio 13.37 installed to your hard drive?

If that's the case, then your settings would be saved automatically, and this might have something to do with the problems you are experiencing.

An alternative to what Glokraw suggested above is to open JACK settings, and select your card under "Interfaces".

business_kid 01-31-2013 03:56 AM

@glokraw: Didn't make much of this imaginative comment
Quote:

so jackd is like a batter whiffing on a hard slider, or a skaters triple-axel gone bad.
@poconoco:http://www.arts-project.org/doc/handbook/artsshell.html

poconoco 02-01-2013 01:50 PM

Maybe I'm not saying it correctly. I am installing to ram. Not hard drive. I'm not creating save files, is all I was trying to say. And yes, it was like that, it worked yesterday "played my guitar through rakarracck", loved it, shut down (no save file created or updated), and the next time I loaded into ram on the same computer, its not finding driver files in the Jack directory. I dunno, that's what is happening here.

poconoco 02-01-2013 01:57 PM

Oh and I did set the interface to my line6 device, and to the internal soundcard, and exited Jack in between setting changes. I also tried multiple reboots (no save file created) back into ram. Tried disconnecting the line6 device USB to reload the interface. I've never had problems using it or the internal soundcard.

poconoco 02-02-2013 01:30 PM

Hey, consider this one solved. I guess I actually did do a save file on one of the shutdowns. So I deleted the save file and jack once again started working on boot up with both line6 device or internal soundcard...

consider solved - as far as jack is concerned. But why is it that if I do a save on shutdown, I end up having problems with my next boot up? I've had it so I could not boot up studio1337 anymore, until I loaded another linux os and deleted the save file.

This is why as I mentioned I keep doing "fresh" install to RAM every time I use it. Apparently I did do a save after the last time I used it with no glitch, but then on next boot-up using the save file, jack stopped working this time.

I dunno, but I got this as a replacement for one of my first orders that the USB thumb drive just stopped working. I must say, and I can't remember your first name, but you replaced my thumb drive and also gave me this 32bit version - OUTSTANDING CUSTOMER SERVICE for sure!!. However, maybe that first batch of thumb-drives were not that good? just a question but this one is studio1337 32bit on the "STUDIO4" thumbdrive.

So, again, it seems anytime I create a save file and I load into RAM with that save file, I get unstable activity. When I delete the save file, I am good again.

Now that I am back up and running, I'm really looking to create some music this weekend.

If you are interested, I'm actually building a new career on music licensing. I have had minor success so far with 26+ tracks signed to a publishing library and a placement of one of my songs on a cable show. I am looking to sign another batch of songs I have waiting to be recorded. My intention is to use Studio1337 for as many of the tracks as I can, and see what I can get signed and eventually placed in film or tv. So keep up the great work and let me know if you have any ideas on the save file issue I've been having.

One of the most impressive things I've done so far with this OS is delving into MIDI. I am a guitar player and have lived in the Analog domain my entire life. Only recently did I start using MIDI with a keyboard and Sample Tank on my WIndows computer. Only problem - I don't play key's very well, and it's painful for me to play something on keys as well as I do on guitar. So, I got a "YouRock Guitar - midi controller" I have the same functionality as a keyboard in a guitar form factor!! I've been going crazy with it!

So, I used the YouRock Guitar a while back on Studio1337, connected it to zynsub effects and patched that into Aurdour to record the wave file with the effected midi, then also patch the unaffected midi signal into Rosegarden for use with other synth sounds later... and I can't even remember but I think I was able to print the sheet music of what I recorded from that midi signal in RoseGarden? I didn't get to use it for a long time after that, so I don't remember in detail the steps, but what a powerful tool I can't wait to really start to use on a regular basis.

I'm also using the 64 bit version on my desktop, but I did all what I described below on an old compaq, 2gb ram single core 1.7mhz processor laptop!!! No way I could even come close to that power and flexibility using Windows on this old laptop, not even close.

Later,
Chris
olsonson.blogspot.com
soundcloud.com/olsonson
facebook.com/olsonson

l0wt3ch 02-02-2013 11:01 PM

Hey Chris,

Glad to hear you got your problem fixed. In the future, if you want to boot a clean version when you've already got a save file (instead of having to use another OS), enter this command at startup (when the 13.37 logo appears):

puppy pfix=ram

This will start it without loading the savefile.

HTH

l0wt3ch 02-03-2013 10:20 AM

Hmm, you've got two versions, 32 and 64 bit. Did you use both of those on the same machine and accidentally created a save file? Maybe you loaded the 64 bit save file with the 32 bit OS or something, and maybe that makes a difference?

In any case, you can save directly to the stick and avoid all of those kinds of problems. Have you installed Service Pack 1?


All times are GMT -5. The time now is 02:02 AM.